locked
Databases Moved: Cannot connect to the configuration database now. RRS feed

  • Question

  • Hi -

    I followed the steps here to move all of our databases from an old sql2005 server to a new sql 2008 server.

    http://technet.microsoft.com/en-us/library/cc512725.aspx

    The backup/restore was completed and I created the new alias on each web front end.   After starting up the services, I get the following error below.    Am I missing a step somewhere?   thanks

     

    EDIT:   the old server had the default instance name.  The new server has a new named instance.    Is this going to be an issue? 

     

    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) +740
       Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.BeginRequestHandler(Object oSender, EventArgs ea) +164
       System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80
       System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +171
    

    • Edited by XRS Thursday, October 20, 2011 2:37 PM
    Thursday, October 20, 2011 2:34 PM

Answers

All replies

  • Have you added back the correct permissions?
    Regards | Aaron www.aaron-rendell.co.uk | SharePoint Consultant | Microsoft Gold Partner - Silversands, Poole, Dorset, England
    Thursday, October 20, 2011 2:36 PM
  • The different instance may cause this issue. Please try to detach the servers from the farm (make a backup of your IIS settings first) then reattach them to the restored config database.
    Regards, Stanisław Delost, NETPRIME. http://www.net-pro.net
    Thursday, October 20, 2011 2:47 PM
  • If you've changed instances, SharePoint's connection string will be wrong. You need to update SharePoint using Powershell/STSADM with the new address.

    http://sharepointsherpa.com/2008/04/18/sharepoint-2007-move-content-and-configuration-databases/


    Regards | Aaron www.aaron-rendell.co.uk | SharePoint Consultant | Microsoft Gold Partner - Silversands, Poole, Dorset, England
    Thursday, October 20, 2011 2:48 PM
  • yes, the SQL logins were transferred from the old database to the new.     I will double-check again with our DBA to make sure everything is synced.  thanks

     

    I assume I don't need to run the SP Product Configuration Wizard? 

    Thursday, October 20, 2011 2:48 PM
  • i got it working.     i didn't have to install Configuration Manager.  Just running the cliconfg.exe command and adding the old server instance and new servername/instance seemed to do the trick.
    Thursday, October 20, 2011 7:03 PM
  • Thanks for sharing valuable knowledge, this has helped me.

    http://support.jesoba.com
    Errors, Troubleshooting, Problem Cases, Performance Monitoring, Best Practices etc.

    Monday, May 21, 2012 8:16 PM