[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 27284
  • Last Modified:

Windows SharePoint Services (WSS) 3.0 Cannot connect to the configuration database

Windows SharePoint Services 3.0 running on Windows Server 2003 SP2. Everything was working fine. One morning, at 3am, the server installed a Windows update and rebooted. After that reboot, all we get when trying to hit our SharePoint site AND the Central Admin site is this error message:

Cannot connect to the configuration database.

I've done extensive searching on this error and have gone through all the recommendations from Microsoft (KB823287) and the error persists.

The following error is proliferated in my event log:
Event Type:      Error
Event Source:      Windows SharePoint Services 3
Event Category:      Database
Event ID:      3760
Date:            10/10/2007
Time:            2:17:02 PM
User:            N/A
Computer:      SPS01
Description:
SQL Database 'SharePoint_Config_31037d2d-30f5-44a7-9227-106d3f2a20e6' on SQL Server instance 'sps01\Microsoft##SSEE' not found. Additional error information from SQL Server is included below.

Cannot open database "SharePoint_Config_31037d2d-30f5-44a7-9227-106d3f2a20e6" requested by the login. The login failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-------
Also there is this error in the event log:
Event Type:      Failure Audit
Event Source:      MSSQL$MICROSOFT##SSEE
Event Category:      (4)
Event ID:      18456
Date:            10/10/2007
Time:            2:17:02 PM
User:            NT AUTHORITY\NETWORK SERVICE
Computer:      SPS01
Description:
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>].
Data:
0000: 18 48 00 00 0e 00 00 00   .H......
0008: 16 00 00 00 53 00 50 00   ....S.P.
0010: 53 00 30 00 31 00 5c 00   S.0.1.\.
0018: 4d 00 49 00 43 00 52 00   M.I.C.R.
0020: 4f 00 53 00 4f 00 46 00   O.S.O.F.
0028: 54 00 23 00 23 00 53 00   T.#.#.S.
0030: 53 00 45 00 45 00 00 00   S.E.E...
0038: 07 00 00 00 6d 00 61 00   ....m.a.
0040: 73 00 74 00 65 00 72 00   s.t.e.r.
0048: 00 00                     ..      
-----

I've tried changing the Application Pool for the sharepoint app to run as Administrator and another admin-level account (although it was working fine as the default NETWORK SERVICE). It SEEMS like a permissions problem, but you'd think that would be solved by logging in as Administrator. It was not. Same error.

Also, I tried installing SQL Server Mgmt Studio on the computer and tried connecting to the SPS01\MICROSOFT##SSEE (SPS01 being the server name) instance and it won't let me connect, presumably because this is the embedded edition of SQL server that came with WSS3.0.

So, I have no way to trouble shoot the SQL portion, and no way to re-configure things in SharePoint because Central Admin won't come up either.
0
tresearch
Asked:
tresearch
  • 7
  • 4
  • 3
  • +4
1 Solution
 
tresearchAuthor Commented:
Fixed it myself. Re-ran SharePoint Products and Technologies Configuration Wizard and that fixed it.
0
 
zephyr_hex (Megan)DeveloperCommented:
fyi - i've seen similar problems on other discussions boards and newsgroups.  seems like an update hosed something in sharepoint....
0
 
amcompsolCommented:
Two points:

One, make sure to close this question and take back the points.

Two, I have a similar issue and tried running the Sharepoint.exe with no luck, what exactly did you run to fix the issue?
0
Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

 
tresearchAuthor Commented:
Start...Administrative Tools...SharePoint Products and Technologies Configuration

Just went through the wizard and it fixed everything.
0
 
griffisblessingCommented:
I'm having the same issue. When I start the Config Wizard I get a message that it failed to detect if the server is joined to a server farm.  Did you get something similar?  Did you just proceed through all prompts?  If I try to continue then I get a message that if I do indeed continue the server will no longer host the SharePoint Central Admin Web App.  It currently is hosting this.

I have a full backup (.dat file) of our WSS 3.0 site, but I prefer to not have to rebuild everything.  Help?  Ideas?

Thanks.
0
 
griffisblessingCommented:
Also forgot to mention ... this just starting happening this weekend, after I applied the WIndows Updates that were released on July 8th, 2008.
0
 
Gavilan123Commented:
Griff - I am having this EXACT issue as well, RIGHT after the update this started occurring.  Has Microsoft release any info on the updates?  I believe the updates are KB 951746 and KB 951748.

Anyone??
0
 
griffisblessingCommented:
I believe this is related to KB951748.  I had one WinXP machine the office that was acting bonkers this morning - could not update/process Group Policy, and could not access the Internet.  Even though it could ping/resolve servers internally, it was acting really strange.  I just removed KB951748 and rebooted and it's fine now.

I'm going to do the same now to my Win Server 2k3 that's hosting WSS and see if my issue gets resolved without having to run the config wizard, etc..  I'll post an update shortly.
0
 
Gavilan123Commented:
I'll be awaiting your results eagerly!!
0
 
griffisblessingCommented:
No luck.  KB951748 was removed from the WSS server and the server was restarted.  Still experiencing the same issues as before.

Ideas?
0
 
Gavilan123Commented:
I stumbled upon a solution and it is working now.

I read in one of my endless forum trolls that someone had attempted to switch the logon account that the Windows Internal Database (MICROSOFT##SSEE) uses from Network Service to Local Service.  I stopped the service, switched the logon accounts and restarted.  It appears to be working.  I've can access the site from multiple computers and users are saying the same.

I'm going to run the updates again with this fix in mind and see what happens.  Needless to say, I'll be backing up Sharepoing first.
0
 
griffisblessingCommented:
Thanks for the tip, but unfortunately that didn't work for me.  I'm still throwing errors left and right in regard to the WID ##SSEE database.  I tried switching it to Local Service, restart, no change.  Changed it back to Network Service, restart, no change.

I may have to blow it away and start from scratch - I do have a full backup.  Please leave any remarks/thoughts you may have about this.  Thanks.
0
 
griffisblessingCommented:
Update.

I got my WSS 3 up and running again.  I noticed that after I ran through the steps above with the WID service logon accounts that the Event Log was no longer showing SQL authentication errors.  I then ran the SharePoint Products and Technologies Configuration wizard again and it went through without issues this time.  I then had to go in to the Central Admin website and setup a new app for our Intranet.  Then I restored from the .dat file I had using the stsadm.exe app (not the restore options from within Central Admin).

So, after a long couple of days it's back up.  Thanks to everyone for their help.
0
 
bmpetersonCommented:
You do not have to run the config wizard again, but rather add the permissions.

The service is running with the NetworkSerivce account. The file permissions on the mdf and ldf are not being inherited from the parent directory. You may just need to allow the parent to propagate to the child objects. On a default setup this is "Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT". Also, you can verify the security on the mdf and ldf files prior to doing anything and you will see only administrator access.
0
 
omagieCommented:
The initial problem description seems to relate to the installation of microsoft patches:
951746 and 951748.  These patches were applied on 8/12/08 to my ms 2003 server running sharepoint. Right after the install, sharepoint crashed.....
0
 
griffisblessingCommented:
omagie - you are correct.  you can also see that I posted the fix that worked for me.  not ideal, but it got us back up and running.  moral of the story - backup, backup, backup!!
0
 
bmpetersonCommented:
Omagie

Yes, after the installtion of the patches you need to check your permssions as I stated above..they will be wrong. I am not sure if the patch changes the run as, but it might. Whatever the cause.. the default logon for the service is now NetworkService you can see this under services. This account has no permssion of the actual mdf and ldf database files and just needs to be applied.

You can see the failed logon attempt by looking at a the log files under "\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG"

You just need to add an NTFS permssion for NetworkService on your mdf and ldf files default is "Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\DATA" (Just check the permssion on the data folder and apply to child objects)

Running the config will do the same thing, but I found the above approach faster, easier, and less intrusive.
0
 
omagieCommented:
Can you be more specific about permissions....I did notice the folder is set to administrator only but when I change that I stop getting access to the sharepoint administrator and when I click on the link to the site from a PC I also get page can't be displayed.


You just need to add an NTFS permssion for NetworkService on your mdf and ldf files default is "Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\DATA" (Just check the permssion on the data folder and apply to child objects)

Running the config will do the same thing, but I found the above approach faster, easier, and less intrusive.
0
 
bmpetersonCommented:
Your DATA folder under "Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\DATA" only has administrator set on the permissions?

What about the ldf and mdf files located in the DATA folder?
0
 
omagieCommented:
the ldf and mdf files are set to administrator. The data folder itself has other permissions noted. Which permissions should be assigned beyond administrator. I note that the main folder: mssql$sharepoint has - administrator, authenticated user, creator,server operator,system

Thanks
0
 
bmpetersonCommented:
On the DATA folder just go to properties, then security, then advanced.

Once you click advanced a new window will open. On the bottom you will see two boxes and only the top one is checked correct? Click the bottom one as well and say apply..this will repopulate the security permissions on the child objects below this folder(the ldf and mdf files).

0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 7
  • 4
  • 3
  • +4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now