Problem with Sharepoint Windows Services on Win 2003 SBS Server



Hi,

I have tried requesting assistance on the
Microsoft.public.sharepoint.windowsservices news group but unfortunately I
haven't received any replies so hope that you may be able to help as the
issue is on a Windows 2003 SBS server.

The other day we had a server that crashed for some unknown reason.
Restarting the server brought it back on-line however, ever since, users are
unable to connect to the company intranet site http://companyweb and instead
get the following error:

"Cannot connect to the configuration database. For tips on troubleshooting
this error, search for article 823287 in the Microsoft Knowledge Base at
http://support.microsoft.com.";

I should point out at this stage that the OS is Windows 2003 Small Business
Server. The event viewer has multiple "Event ID: 1000" logs in the
Application Log. "Event ID: 1000" reports as follows:

Type: Error
Source: Windows SharePoint Services 2.0
Category: None
Event: 1000
User: N/A
Description: #50070: Unable to connect to the database STS_Config on
Server1\SharePoint. Check the database connection information and make sure
that the database is running.

I have also noticed that the service MSSQL$SHAREPOINT, although set to start
automatically does not start. Trying to start the service manually, it
appears to
start but then stops again a few seconds later.

MSDE is used as the database engine.

I have tried several suggestions found on articles in the MS Knowledge bases
but so far without luck. I have tried repairing, re-installing MS Windows
SharePoint Services 2.0 and tried re-installing MSDE by launching
"sqlrun16.msi" but to no avail.

Other websites hosted on the server appear to be unaffected, for example,
OWA appears to work fine so it doesn't appear to be an issue with IIS.

I would appreciate any help in resolving this issue. If you require any
further info, please post back.

Thanks in advance.
Sergio


.



Relevant Pages

  • Re: SharePoint Services 3.0 unable to display content
    ... "Tim Tate" wrote: ... When connecting to the original configuration database, ... The virtual server that is referenced here is not in the config database. ... Microsoft Windows SharePoint Services 2.0 ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: SharePoint Services 3.0 unable to display content
    ... When connecting to the original configuration database, ... The virtual server that is referenced here is not in the config database. ... I am 100% about the WSS. ... Microsoft Windows SharePoint Services 2.0 ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: help with 2000i on win2k server (sp3 on database)
    ... See Leonard's post for the config options. ... If the server is mangling itself, then ANYTHING running on the server ... that I work with will support the database AND the application. ... As for Windows vs. Linux/NetWare, I can agree, but I also see MANY ...
    (comp.databases.btrieve)
  • Re: nt4.5 to w2003
    ... keep in mind that there basically is two different things you can do to move from an NT 4 (SAM Database) domain to an Active Directory Domain. ... You can choose to upgrade the domain from NT 4 to Windows 200x Active Directory. ... The thing to keep in mind here is that you have to Upgrade an NT 4 PDC to Windows 200x. ... You could download and install Virtual Server 2005 if you needed to upgrade an NT 4 machine to Windows 200x and your real hardware either does not support NT 4, or the NT 4 hardware you have does not really support Windows 200x. ...
    (microsoft.public.windows.server.migration)
  • Re: Sharepoint Instance problem
    ... 'New SQL Server Registration ¡­ ' item to open Register SQL Server wizard. ... Critical update for SQL Server 2000 Desktop Engine (Windows) on Windows ... database" error message when you access your Windows SharePoint Services ...
    (microsoft.public.windows.server.sbs)