locked
Moved DBs to new server, "Cannot connect to config DB" from external WFE RRS feed

  • Question

  • Our MOSS 2007 Farm is 2 internal WFEs, one DMZ WFE, a SQL server, and an Index server. We were tasked with moving to a new SQL server. The new SQL server uses the same version of SQL 2005, but the old server is Win2003 and the new Win 2008.

    We moved our DBs to a new SQL server, and used cliconfg.exe on each MOSS server to point to the new server name.

    The sites hosted on the internal server are connecting without issue. However, the extended site hosted on the DMZ server cannot connect to the configuration db. The ODBC connection between the external WFE and the new SQL server works fine.

    No changes were made to the web.config.

    Any recommendations? Thank you!

    Sunday, January 9, 2011 8:20 PM

Answers

  • Hi scogordo,

     

    Thank you for your post.

     

    Could you please check the following two KB articles:

    http://support.microsoft.com/kb/833183;

    http://support.microsoft.com/kb/823287.

    I think these would be useful and enlightening to you, maybe you can solve this issue through the methods there.

     

    Hope this could help you.

     

    Regards.

    • Marked as answer by David HM Thursday, January 20, 2011 4:36 AM
    Monday, January 10, 2011 7:18 AM
  • The problem was, VERY interestingly, stemming from the Registry.

    On the WFE that had the issue, went into regedit,

    HK_LOCAL_MACHINE/SOFTWARE/Microsoft/Shared Tools/Web Server Extensions/12.0/Secure/ConfigDB/dsn

    And saw that the Data Source was not FQDN, as it was on the other WFEs (that were working).

    Switched to the Data Source=... info to match that on the WFEs where it was working, and presto, it worked.

    I can't give much information on how or why this happened, but this worked in our situation.

    Good luck!

    • Marked as answer by scogordo Tuesday, February 22, 2011 7:45 PM
    Tuesday, February 22, 2011 7:45 PM

All replies

  • Hi scogordo,

     

    Thank you for your post.

     

    Could you please check the following two KB articles:

    http://support.microsoft.com/kb/833183;

    http://support.microsoft.com/kb/823287.

    I think these would be useful and enlightening to you, maybe you can solve this issue through the methods there.

     

    Hope this could help you.

     

    Regards.

    • Marked as answer by David HM Thursday, January 20, 2011 4:36 AM
    Monday, January 10, 2011 7:18 AM
  • The problem was, VERY interestingly, stemming from the Registry.

    On the WFE that had the issue, went into regedit,

    HK_LOCAL_MACHINE/SOFTWARE/Microsoft/Shared Tools/Web Server Extensions/12.0/Secure/ConfigDB/dsn

    And saw that the Data Source was not FQDN, as it was on the other WFEs (that were working).

    Switched to the Data Source=... info to match that on the WFEs where it was working, and presto, it worked.

    I can't give much information on how or why this happened, but this worked in our situation.

    Good luck!

    • Marked as answer by scogordo Tuesday, February 22, 2011 7:45 PM
    Tuesday, February 22, 2011 7:45 PM