Re: Event 1000 Windows SharePoint Services 2.0 Error

Where I see is is when there is Backupexec installed, where the upgrade didn't take, or some other issue at hand. I'm not seeing this on a bog standard SBS box. Not a single SQL instance got nailed on any of my boxes.

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

Relevant Pages

  • RE: How do I restore from mdf and ldf files?
    ... Tasks -> Backup Database ... Tasks -> Restore Database ... Windows 2003 Server with Latest Service Pack ... Pre-requisites for Sharepoint Backup and Restore: ...
    (microsoft.public.sharepoint.portalserver)
  • RE: ESENT Logging
    ... SBS server 2003 has a backup job that will ... 145881 How to Use Jetpack.exe to Compact a WINS or DHCP Database ... newsgroups so that they can be resolved in an efficient and timely manner. ...
    (microsoft.public.windows.server.sbs)
  • RE: ESENT Logging
    ... SBS server 2003 has a backup job that will ... 145881 How to Use Jetpack.exe to Compact a WINS or DHCP Database ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: Backups have Shadow Copy Problems
    ... and restarted the server. ... suggested and changed the recovery model to simple on the one database called ... I understand the issue to be: the backup task failed ... You back up data from a volume that contains a Microsoft SQL Server ...
    (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)
Loading