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

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

Error when opening SharePoint 3.0 Centeral Administration, Cannot Connect to the Configuration Database

This is a SBS 2008 with SharePoint v3.0 installed.
While trying to do some additional configuration on our Sharepoint site I noticed the task on Administrator Tasks that said
Central Administration application pool account should be unique...

I googled this phrase and then followed the instructions on these two sites:
http://costas.cpstechgroup.com/2008/07/03/wss-30-on-sbs2k8-central-admin-application-pool-account/
and:
http://social.technet.microsoft.com/Forums/en/sharepointadmin/thread/1c359912-ac3a-42ad-81b7-f68f7bd9db1c

Which means basically that I
1. Created a new user account. Removed any group memberships it had
2. Ran these three commands
stsadm -o updatefarmcredentials -userlogin spch\wssuser -password <ubercoolpassword>
stsadm -o updateaccountpassword -userlogin spch\wssuser -password <ubercoolpassword> -noadmin
stsadm -o spsearch -farmserviceaccount spch\wssuser -farmservicepassword <ubercoolpassword>
All three finished with no errors
3. Restarted IIS and the sharepoint services

The sharepoint site appears to be working fine, but when I try to open the SharePoint 3.0 Centeral Administration site I get this message:
 Cannot Connect to the Configuration Database Cannot Connect to the Configuration Database

I have spent hours googling this and can't come up with much. What do I need to do to fix this or at the very least revert the user back to the Network Service so that everything is back to how it was.

Security updates were installed a month ago, but when I run a new check for updates I notice that the following are NOT installed and need to be, but at this point I don't want to until this is fixed, unless someone knows that this will actually fix this issue.
- Windows Internal Database Service Pack 3
- Windows SharePoint Services 3.0 Service Pack 2
- Update Rollup 5 for Small Business Server (I can't tell which Rollups are installed, though the BPA says Rollup 4 is not installed either)
0
AmbientIT
Asked:
AmbientIT
1 Solution
 
NormanMainaCommented:
This doc explains the error in detail.
http://support.microsoft.com/kb/823287

In your case,i think when you created the user for the app pool ,you did not give that user permissions in sql server.
You'll need to give that a/c permission dbo to these db's
Sharepoint_Config
WSS_Content

and any other Sharepoint database
0
 
AmbientITAuthor Commented:
The only sql database I could find was the one called sbsmonitoring. I assumed it was using the windows internal database. Am I incorrect and if so how do I find and manage the databases?
0
 
NormanMainaCommented:
using sql server connect to the sharepoint instance .
Run sp_helpserver in sql server management studio to find out the instances in a server.

Them conenct to the sharepoint instance -should be sqlespress/sharepoint
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
AmbientITAuthor Commented:
I was finally able to find and connect to the database. It is indeed the Windows Internal Database, but you can connect to it using SQL Server Management Studio Express if you tell it to connect to database:
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

Of the five databases that seem to be related to Sharepoint:
- SharePoint_AdminContent_random_looking_set_of_letters_and_numbers
- SharePoint_Config_random_looking_set_of_letters_and_numbers
- ShareWebDB
- WSS_Content
- WSS_Search_WIN-EUGSO7LO7PY

WSS_Content was the only one that didn't have the new user set up with rights. I set it to DBO, but that hasn't fixed it.

By granting DBO rights I mean I went to Databases -> <Specific Database> -> Security -> Users -> spch\wssuser. Then under Role Members I made sure there was a check next to db_owner

Any other ides?
0
 
NormanMainaCommented:
make sure the user is dbo in:
SharePoint_AdminContent
SharePoint_Config

0
 
AmbientITAuthor Commented:
The user already had DBO rights on those two
0
 
NormanMainaCommented:
Make sure SQL Intance is running by checking your services -also enable sql browser service,check credentials are also ok and IIS isn't in the 5.0 isolation mode. The problem may occur if sharepoint simply can't find the database. Reasons for this may be many: the database has moved, dns has changed, ... In my case was the later. By changing the DNS server in the network we've had to add one more record manually to point to the correct one and the sites started to work

This problem is comprehensively tacled here- have a look at all possible causes.
http://support.microsoft.com/kb/823287

Have a look athis blog too.(lots of brainstorming here)
http://webborg.blogspot.com/2007/05/connect-to-configuration-database-and.html
0
 
NormanMainaCommented:
in partiicar try this suggested in the blog

1. Open Server Manager.
2. Click on Roles.
3. Choose Web Server (IIS)
4. Choole IIS.
5. Open server in the Connections panel.
6. Choose Application Pools.
7. For every item in Application Pools, click on it once, and then choose Advanced Settings.
8. Under Process Model, Identity,
change it, choose "Custom Account".
9. Enter an account and password for an account with a lot of permissions. I used the Sysadmin.
10. Restart the Web Server. Then it worked. 

Open in new window

0
 
AmbientITAuthor Commented:
The database is the Windows Internal Database and it is running.

Right now the Identity is set to Network Service for all of them other than the SharePoint Administration one, it is set to the new user I created SPCH\wssuser

I will switch the accounts around that they use later this evening when people aren't using the server.
0
 
AmbientITAuthor Commented:
I ran the SharePoint Product and Technologies Configuration Wizard found in Administrative Tools. It ran through 10 steps and whatever it did fixed the issue.
0
 
AmbientITAuthor Commented:
This is what fixed my issue
0
 
Raquel AdamsIT DirectorCommented:
I too ran the update and it took down my site. I ran the Wizard, and it was halted by this error
"An exception of type System.Data.SqlClient.SqlException was thrown.  Additional exception information:  Cannot open database "..." requested by the login.  The login failed.  Login failed for '.../Administrator.

What now?
0
 
kinetikk2011Commented:
Probably is your ShareWebDb marked as "Suspect"?
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now