snowsurfer
asked on
Cannot connect to the configuration database
We have had Windows Sharepoint Services up and running now for two months with no issues. We have an internal webserver that hosts the front end and our SQL 2000 server hosting the backend. Over the weekend something has happened. We are now getting
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 have searched the web fdar and wide with no answers. The Microsoft article doesnt help. All of the items listed have checked out. Our SQl is running on the default port.
I created a new account for the Appliction Pool to use and made sure it has the correct permissions in SQL with no luck.
Anyone have any ideas?
I have not yet rebooted the SQL server. I am going to try that tonight, but I have cycled the SQL services so I dont think its going to change anything.
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 have searched the web fdar and wide with no answers. The Microsoft article doesnt help. All of the items listed have checked out. Our SQl is running on the default port.
I created a new account for the Appliction Pool to use and made sure it has the correct permissions in SQL with no luck.
Anyone have any ideas?
I have not yet rebooted the SQL server. I am going to try that tonight, but I have cycled the SQL services so I dont think its going to change anything.
cjones_mcse
Be sure that the account you are using as your DB administrator for Sharepoint has not had a password change recently. Generally that is the cause of these errors especially if it WAS working and then suddenly is not. Just to be certain, I would temporarily change the account to one you KNOW has rights to the DB (i.e. the Domain Admin account) and see if that resolves the problem. If it does, you know you have a permissions issue with the account you are using normally and can troubleshoot from there. If it doesn't, then you have a more serious issue.
ASKER
I have done what you suggested. I made a brand new account and got it all setup. As of now, I have uninstalled and reinstalled sharepoint with no change. I uninstalled sharepoint and then uninstalled IIS. I have reinstalled both and I still have the same error except that now its when trying to connect to the config db for the first time. Hopefully once I get this all up and going my site is still safe inside my sql database.
I have installed the SQL client tools on the web server and I can connect with no problems. I wrote a simple ASP page to retreive some data from one of the tables and it comes back with information. I dont know what is broken
I have installed the SQL client tools on the web server and I can connect with no problems. I wrote a simple ASP page to retreive some data from one of the tables and it comes back with information. I dont know what is broken
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Where is the config db stored?
ASKER
Are you talking about the one is SQL? If so, yes I have a godo backup of that. We keep backups back to three weeks
ASKER
If for whatever reason, that does not work can I create a new config db without losing everything else? The site has been failry stagnant for a while so there is not much in there, except some nice look and feel work our developer did to the home page.
ASKER
to test the config idea i made a new db called test and setup the permissions and users and tried to conect to that with the same results.
ASKER
Well still at a stand still. Tuesday we are putting in a new web server, I am going to try an connect with it and see what happens
The config db is stored in SQL. It will have config_db in the name and does not get backed up with all the others unless you back it up through SQL. According to Microsoft, it isn't worth backing up anyway. There is too much possibility of it becoming corrupted.
You should be able to restore everything without your config db.
You created a new SITE called test or a new CONFIG DB called test? Two very different things.
Your web server really shouldn't have much to do with this problem. It is a permissions issue or an issue with the config_db.
Sorry for the delay in answering. Got a little busy.
You should be able to restore everything without your config db.
You created a new SITE called test or a new CONFIG DB called test? Two very different things.
Your web server really shouldn't have much to do with this problem. It is a permissions issue or an issue with the config_db.
Sorry for the delay in answering. Got a little busy.
ASKER
I created a new DB called test. Just a blank one. then I tried connecting to it from Sharepoint
ASKER
I found something that may help. When you expand Databases in the Enterprise Mangager and then expand our Sharepoint DB. There is a users section. What accounts should be in there. I see one called dbo with a login name of our original sharepoint service account and there is the one I put in there trying to troubleshoot this issue
ASKER
Rebooted everything this weekend with no change
ASKER
Got it. Whoohoo.
I re registered the oledb32 file in c:\Program Files\Common Files\System\ole db
From there I was able to reconnect to my site and extend and all is well.
I re registered the oledb32 file in c:\Program Files\Common Files\System\ole db
From there I was able to reconnect to my site and extend and all is well.
Glad you got it working! You ought to request that your points be refunded as I didn't really answer your question.
ASKER
You gave me some where to vent, its worth every point. I have a few thousand points to use anyway. I help out in Citrix and Windows 2000 questions on here.
Thanks again
Thanks again
For anyone else that has issues I found that the username domain\servername$ (the servername of the web application tier) hadn't been added to the security for those databases. Once I'd added it it worked.