Re: Event 1000 Windows SharePoint Services 2.0 Error
- From: Aplima <Aplima@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 17 Jul 2008 10:33:05 -0700
Ok.
I hope my English will be good enough to explain myself...
After that day, when I updated applying the patches from MS I lost
connection to companyweb/sharepoint...
I read about fixing this... And will try it asap.
But, and here I have to assume that I might have gotten things worse while
trying to fix what I didn't knew it was happening.
Everytime I tried to start the SQL services the service would start and
stop. That is what everyone is experiencing. So I looked on what could be
missing and tried to apply the SP4 over the SQL installation I had.
Then, the error is: Service cannot start, system can't find the specified
file.
This error comes when I start sql services or exhange pop3 connector.
Why? Wish I knew :(
What can I provide so someone can help me?
"Susan Bradley" wrote:
Let's take this one at a time and stop ripping things out so drastically :-).
First off what exact error message do you get?
I've not seen Exchange pop connector get mangled by removing SQL so lets
debug that separately.
Feel free to start a new thread.
Aplima wrote:
I have my server a total mess for a week...
Due to this update...
I realized what caused it 3 days after...
I tried to fix it on my own and now I think I got a bigger problem...
First I read about WUS could cause the problem... So I uninstalled it.
After that, I had all SQL server instances to a complete stop.
They don't start and I get an error: "The system could not find the
specified file"
WHAT FILE?????
And it gets worst!
Exchange pop3 connector fails with the same error.
I need help... I don't want to try any other solution unless someone
garantees it will work for sure.
I will call MS again, because in my country on the day after the update the
answer was: "It's hardly an update issue, but you can fill a form for a paid
support". I paid a lot for this software. The last thing I wanted to hear was
something like that.
I'll call them again tomorrow. I'm willing to pay, anyone that solves me
this issue... :(
"Pete at Glassblade" wrote:
It IS widespread - SBS is used by small companies who often don't have
dedicated IT staff - they are obliged to trust Microsoft's expertise. So when
an update is pushed out that kills something as inherently flakey as SQL it
is MS who should stand up and be counted. The 'I'm not bothered, it is only
the small guys who are suffering' approach will prove very expensive for our
MS oriented community if we aren't careful.
I don't see symantec as an admirable model to copy in that respect.
Pete
"Susan Bradley" wrote:
You have a backup of the entire server, yes?
You control patching, yes? I'm not trying to be mean here but patching
SQL should be planned.
And these patches don't barf on everyone, so this isn't widespread.
Ed Podowski wrote:
I think I found my answer and it doesn't look good. Our drives are mirrored,
but Volume Shadow Copy for C Drive is disabled. Volume Shadow Copy for D
Drive is enabled. [Naturally, the information is on C Drive.] If anyone has
any suggestions, i would greatly appreciate it.
Thank you,
Ed Podowski
P.S. I'll take responsibility for not having a backup and / or volume shadow
copy enabled, but Microsoft should take responsibility for publishing a patch
that is causing millions of dollars in loss productivity.
Microsoft should be responsible for doing a back up before applying any
update. What is the first rule before you update - Backup?
If you are from Microsoft, please do not respond to my P.S. I just need
this fixed.
"Ed Podowski" wrote:
Thanks for posting this.
I am experiencing the same problem and do not have a backup. How do use
shadow copy to restore the file?
Thank you!
"wrytat" wrote:
Hi
I'm using Small Business Server 2003. At 3 am this morning, my
MSSQL$Sharepoint service stopped running and the server restarts by itself,
most probably due to an update. And this morning when I came to work, I
discovered that when I try to access http://companyweb/, I receive the
"Cannot connect to the configuration database." error message. I followed
KB823287 and KB833183, but still couldn't access the website. I managed to
ping, nslookup, and even login to the SQL server successfully.
I checked my Events Log, and discovered that the Event 1000 Windows
SharePoint Services 2.0 Error appeared almost every 5 seconds. The error
description reads, "#50070: Unable to connect to the database STS_Config on
servername\MICROSOFT##SSEE. Check the database connection information and
make sure that the database server is running."
Besides, it sometimes accompanied with a 18456 Failure Audit, which reads,
"The description for Event ID ( 18456 ) in Source ( MSSQL$MICROSOFT##SSEE )
cannot be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote computer.
You may be able to use the /AUXSOURCE= flag to retrieve this description; see
Help and Support for details. The following information is part of the event:
NT AUTHORITY\NETWORK SERVICE, [CLIENT: <named pipe>]."
What can I do? Please advise, thank you.
- References:
- RE: Event 1000 Windows SharePoint Services 2.0 Error
- From: Ed Podowski
- Re: Event 1000 Windows SharePoint Services 2.0 Error
- From: Susan Bradley
- Re: Event 1000 Windows SharePoint Services 2.0 Error
- From: Pete at Glassblade
- Re: Event 1000 Windows SharePoint Services 2.0 Error
- From: Aplima
- Re: Event 1000 Windows SharePoint Services 2.0 Error
- From: Susan Bradley
- RE: Event 1000 Windows SharePoint Services 2.0 Error
- Prev by Date: RWW Printer Problems
- Next by Date: Re: Server Hangs at " Applying Computer Settings" on SBS 2003 R2/HP ML
- Previous by thread: Re: Event 1000 Windows SharePoint Services 2.0 Error
- Next by thread: Re: Event 1000 Windows SharePoint Services 2.0 Error
- Index(es):
Relevant Pages
|