Re: Event 1000 Windows SharePoint Services 2.0 Error



BTW I do differentiate between the DIYer and the VAR/VAP but you can call into MS support, explain the situation and it will be a free call.

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.
.



Relevant Pages

  • WSUS Errors after System state restored
    ... recover sufficiently and the server went off whilst running. ... no avail and in the end just restored system state from the backup. ... Connection to database failed. ... see Help and Support Center at ...
    (microsoft.public.windows.server.sbs)
  • Re: Event 1000 Windows SharePoint Services 2.0 Error
    ... And these patches don't barf on everyone, so this isn't widespread. ... Volume Shadow Copy for D ... I'm using Small Business Server 2003. ... "Cannot connect to the configuration database." ...
    (microsoft.public.windows.server.sbs)
  • RE: Inconsistent Schema Versions
    ... on the existing server, to try to force it to upgrade to the same version. ... Microsoft MSDN Online Support Lead ... Subject: Inconsistent Schema Versions ... The schema version of the database ...
    (microsoft.public.sharepoint.portalserver.development)
  • RE: Adding Full Text Search to SBS 2003 - Yes I have searched and Read Everything
    ... You receive a "The database this server is using does not support search" ... SQL Enterprise Manager. ...
    (microsoft.public.windows.server.sbs)
  • RE: EventID1000: #50070:Unable to Connect to Database - WSS 2.0
    ... Microsoft Support Engineer by contacting Microsoft Customer Support ... Subject: EventID1000: #50070:Unable to Connect to Database - WSS 2.0 ... lot work for server that has lots of virtual servers/sites. ...
    (microsoft.public.sharepoint.windowsservices)