Cannot connect to the configuration database - after IIS reset or machine reboot
After an IIS reset or rebooting the machine. If I then open up a sharepoint website the message isCannot connect to the configuration database. as detailed below Server Error in '/' Application. Cannot connect to the configuration database. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: Microsoft.SharePoint.WebPartPages.WebPartPageUserException: Cannot connect to the configuration database.Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [WebPartPageUserException: Cannot connect to the configuration database.] Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.EnsureInitialize(HttpRequest request) +525 Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.BeginRequestHandler(Object oSender, EventArgs ea) +3032 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +171 Version Information:Microsoft .NET Framework Version:2.0.50727.3053; ASP.NET Version:2.0.50727.3053 The only way to fix this temporarily as it will break again after the next IIS reset or machine reboot is to run the SharPoint technologies and configuration wizard and disconnect the current server from the server farm then once the wizard completes re run the wizard and re connect to the server farm then go to the other servers in the farm and set theFiles and permissions for Office SharePoint Server 2007 as perhttp://technet.microsoft.com/ko-kr/library/cc721637.aspxand all will be well until I need to reboot the machine or reset the IIS and I will have to go through the process all over again which is more complex for the machine hosting the central admin site as Ineed to recreate all the searches as well.I have my only little groundhog day going on please helpMy head feels like it will explodeConfiguration4 Servers all win 2003 x641 x sql server1 x application server220.127.116.11352 x wfe servers18.104.22.16834
March 20th, 2009 12:50am
check the application pool, it can be the case that there have been some password changes for the account in the identity, and after the IIS reset it failed to start.
March 20th, 2009 3:01am
The application pools are all fine they are configured as different domain users per pool with spn's registered they are the same obviously on each server the application pools are all started and running if they wern't I wouldn't get the error as depicted above. In fact there are no errors reported in the event viewer when this happens on either the wfe in question or the SQL it's like it has just lost its connection.If I were able to put a manual connection string in a webconfigor registry I'm sure it would work fine.
March 20th, 2009 2:43pm
How is this an answer?? The person having the problem confirmed the applciation pools were not the problem. We're now suffering the same issue and some dimwit's effectively stopped anyone else providing a real answer to this thread.If at first you don't succeed, ask an MVP. Or find someone who really knows. ;)
September 21st, 2009 7:04am
You could try to set the application pool to Sharepoint Center Admin pool. It would be work.
October 9th, 2009 10:49pm
Hi,I do have the same error on my system. Should I go with the first answer on the topic?Ckotsis
January 5th, 2010 2:19pm
This worked for me. This particular app pool was set with a user's account whose account probably was deleted or the password would have changed. Now I set it with admin account . It works like a charm. Thanks xwindow!
October 21st, 2010 8:06pm