Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

OpsMgr 2012: Management Servers might not reconnect to SQL after a SQL outage

OpsMgr 2012: Management Servers might not reconnect to SQL after a SQL outage

  • Comments 2
  • Likes

 

I wrote about this new feature we added to control this in SCOM 2007 R2 with the advent of CU4:  http://blogs.technet.com/b/kevinholman/archive/2011/02/07/a-new-feature-in-r2-cu4-reconnecting-to-sql-server-after-a-sql-outage.aspx

A scenario might occur where a SQL outage exists, and then the management servers will not automatically connect to SQL again once it comes back up on the network.  If you have experienced this you should consider applying this resolution.

However – those registry locations have changed in OM 2012.  This was done to sync the Data Access layer between Service Manager and SCOM.  There has been some confusion if these configuration settings are supported and/or work in SCOM 2012.

The new locations are documented at:  http://support.microsoft.com/kb/2913046/en-us

Start the Registry Editor.

Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center\2010\Common\DAL

Create the following two new DWORD values:

  • DALInitiateClearPool
    Type: DWORD
    Decimal value: 1
  • DALInitiateClearPoolSeconds
    Type: DWORD
    Decimal Value: 60

image

 

DALInitiateClearPool should be set to Decimal value “1” to enable it.

DALInitiateClearPoolSeconds should be set to Decimal value “60” to represent 60 second retry interval.  The DALInitiateClearPoolSeconds setting controls when the management server drops the current connection pool and when the management server tries to reestablish an SQL connection. We recommend that you set this setting to 60 seconds or more to avoid performance issues. 

Restart the System Center Data Access Service, and the System Center Management/Microsoft Monitoring Agent service on the management server for these settings to take effect.

 

This solution applies to SCOM 2012, 2012 SP1, and 2012 R2.  Along with the same versions of Service Manager 2012.

Comments
  • Awesome! We have this issue in our SQL Cluster environment. Hope this resolves it!

  • Great info. Do you know if this will work for the SCSM Data Warehouse or just the management server?

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Search Blogs