Sign in
 
HomeOnline20132010Other VersionsRelated ProductsLibraryForumsGallery
TechCenter >
> 
> 
SP2010 on Windows 7 - "Cannot connect to Configuration Database" message received after I changed my password - any suggestions ?

Respondida SP2010 on Windows 7 - "Cannot connect to Configuration Database" message received after I changed my password - any suggestions ?

  • Monday, May 21, 2012 11:51 AM
     
     
    Sign In to Vote
    0

    Hi All,

    background.

    I recently installed SharePoint 2010 on my work laptop (windows7 , 8GB RAM) using my own domain account.

    the domain at work have a policy whereby we need to change our passwords every 30 days.

    I tried to access central administration after I changed the password and received a "cannot connect to Configuration database" .

    I rather hastily uninstalled SharePoint and then reinstalled SharePoint but received an error when running the Product and config wizard.

    Was there an alternative ? i.e. once I changed the domain password was there a place in SharePoint/IIS/SQL where I could have updated the existing password and thus enabling SharePoint to function ?

    also - is removing SharePoint via setup.exe enough to remove all traces of SharePoint from a machine.. are modifications to SQL and IIS also required ?

    I look forward to hearing your responses.

    best regards,

    Counie

    SharePoint Farmer in training

     

All Replies

  • Monday, May 21, 2012 12:21 PM
    Moderator
     
     Answered
    Sign In to Vote
    1

    Hi,

    You have to update the application pool account password as well. Follow the below steps:

    1. Open IIS and goto application pools.
    2. You might able to see few application pools stopped. (This is because of mismatched password)
    3. Right click on stopped pool and select advanced settings. New window appears.
    4. Browse for tab “process model”, and select Identity tab which located first under process model.
    5. In the right side of identity, click the browse button and select custom account. Type the user name and password. (If SharePoint server in domain type “domain name\username”)
    6. Start the pool
    7. Repeat the steps for all stopped pools.

    Let us know your result

    Cheers, Hemendra-MCTS "Yesterday is just a memory,Tomorrow we may never see"

     
  • Monday, May 21, 2012 12:21 PM
     
     
    Sign In to Vote
    1

    Hi,

    Have you try to reboot?

    Better install MSS2010 under the local admin account.

    If you will remove MSS via setup.exe you also need to delet DB in your SQL server.

     
  • Monday, May 21, 2012 3:56 PM
     
     
    Sign In to Vote
    0
    thanks for the reply but I have already removed SharePoint so now I just get a 404. I will try this in future

    SharePoint Farmer in training

     
  • Monday, May 21, 2012 4:23 PM
     
     
    Sign In to Vote
    0

    thanks for the reply.

    I reinstalled SharePoint and reconfigured using the Products and Config wizard ( the only hiccup was that I had to remove the Central Admin V4 website manually via IIS) in standalone mode.

    I then checked the backend using SQL Server 2008 R2 management studio ( I have an evaluation copy of SQL Server 2008 R2 also installed on my machine )

    there is no sign of any WSS_* databases even though there clearly are databases for the root site collection when I view in Central admin.

    is this (i.e. not being able to view content databases via SSMS ) typical for standalone installs on windows 7 ?

    cheers,

    Counie

    SharePoint Farmer in training

     
  • Monday, May 21, 2012 5:28 PM
     
     
    Sign In to Vote
    1

    Hi,

    If you have installed SharePoint as stand alone, then you will probably have a SQL express version installed in your machine. Try to download SQL server Express management studio to be able to connect to your databases!

      http://www.microsoft.com/en-us/download/details.aspx?id=22985

    Regards
    Henrik A. Halmstrand
    sharepointrevealed.com
    getspconfig.codeplex.com
    Please click Mark As Answer; if a post solves your problem or Vote As Helpful; if a post has been useful to you.

     
  • Monday, May 21, 2012 6:24 PM
     
     Answered
    Sign In to Vote
    1

    I would suggest using Managed Accounts in the future.  They allow you to change the password of the account right through Central Admin, and by doing this, SharePoint will update the credentials in all the appropriate places so you don't run into issues like this.

    Here's a link for more information: http://blogs.technet.com/b/wbaer/archive/2010/04/11/managed-accounts.aspx

    Bob Guidinger

     
  • Tuesday, May 22, 2012 9:58 AM
     
     
    Sign In to Vote
    0

    I thought that the express database would still be visible to the installed version of SQL Server Management Studio 2008 R2.

    And in fact it IS visible .. once you know how.

    There were in fact 3 seperate SQL Server instances on my machine ( as I discovered when I tried to install SQL Server Management Studio Express.

    MSQLServer

    SharePoint

    SQLExpress

    In order to view the various instances I had to enter .\<instance> name into the "connect to" dialog.

    the SharePoint relevant databases were all hosted on the "SharePoint" instance.

    SharePoint Farmer in training


    • Edited by Counie Tuesday, May 22, 2012 10:20 AM
    •  
     
  • Tuesday, May 22, 2012 10:24 AM
     
     
    Sign In to Vote
    0

    Absolutely

    Would you believe I have in the past actually configured managed accounts myself when configuring a farm.

    I forgot that I may also have needed to do this when installing on my own machine.

    we live and learn :)

    SharePoint Farmer in training

     
  • Tuesday, May 22, 2012 10:33 AM
     
     
    Sign In to Vote
    0

    thanks oleksandr.

    indeed from looking at the databases in my SharePoint instance it appears that the uninstall did not drop the databases created by SharePoint and the reinstall created new databases using a new GUID.

    good to know.

    SharePoint Farmer in training