Unable to correct invalid SQL Server Network Configuration on clustered SQL Server causes clustered SQL Server fail to start “permanently”

Published Mar 23 2019 04:13 AM 80 Views
Microsoft
First published on MSDN on Dec 06, 2005

Recently, we encountered an issue reported by a customer on a clustered SQL Server. What happens is the following.

The Customer needs to restrict the number of IP addresses SQL 2005 Server is listening. He uses the following procedure for that: open “SQL Server Configuration Manager” (SSCM)  -> “SQL Server 2005 Network Configuration” -> “Protocols for XX” , right clicked TCP/IP choosing Protocols and set “Listen All” to “NO”. After that he wants to set the proper IP-addresses. This is working fine on a non-clustered system. On a clustered system the following happens when he is restarting SQL Server: SQL Server does not come online anymore. And the SQL Server error log reports the following.

SQL Server 2005 errorlog

2005-11-28 10:53:29.02 Server      Error: 17182, Severity: 16, State: 1.

2005-11-28 10:53:29.02 Server      TDSSNIClient initialization failed with error 0x32, status code 0x1c.

2005-11-28 10:53:29.02 Server      Error: 17182, Severity: 16, State: 1.

2005-11-28 10:53:29.02 Server      TDSSNIClient initialization failed with error 0x32, status code 0x1.

2005-11-28 10:53:29.03 Server      Error: 17826, Severity: 18, State: 3.

2005-11-28 10:53:29.03 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

2005-11-28 10:53:29.03 Server      Error: 17120, Severity: 16, State: 1.

2005-11-28 10:53:29.03 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Configuring the server to listening on individual IP-addresses is not supported on Clustered SQL Server, thus the failure indicated by the error log is accurate. However, the customer can NOT set “Listen ALL” to “Yes” any more to bring the server online. To be more accurate, even though the customer can set “Listen ALL” to “Yes” using SSCM on each physical node, each time he try to bring SQL Server online, the value will be overwritten to “NO” and the clustered SQL Server will end up failing. This is a serious issue that causes frustration of our customers.

The root cause of this issue is because of cluster checkpoint service behavior. If a setting is changed while the resource is online, that change will get check-pointed to the CPT hive file in the cluster quorum disk. If the resource is offline while you make the parameter change, then it will never be check-pointed. Each time you bring up the resources, the check-pointed value will overwrite the local value. SQL Server network configuration is one resource that is check-pointed. So, if you put the SQL Server resource offline while you change the “Listen All” from “NO” to “YES”, and then you try to put the resource back online, it will fail as the "local" change was overwritten (during resource startup) with what was persisted in the checkpoint file.

Because of this check-pointing behavior, any time that SQL Server network configurations are modified into invalid values while the server is online, restarting the clustered SQL Server will cause the server fail to start “permanently”.

To get out of such BAD state, one workaround is to disable the check-pointing for SQL Server network configuration, described as following.

1. While SQL Server instance is in offline/failed state, disable cluster checkpointing for network configuration by:

cluster res "SQL Server" /removecheck:”SoftwareMicrosoftMicrosoft SQL ServerMSSQL.XXXMSSQLSERVER”

2. Correct the configuration by using SSCM. Verified the key was corrected on both nodes.

3. Bring SQL cluster back online.

4. Re-enabled cluster checkpointing for network configuration by:

cluster res "SQL Server" /addcheck: ”SoftwareMicrosoftMicrosoft SQL ServerMSSQL.XXXMSSQLSERVER”

Note that, for named instance, the resource display name "SQL Server" should be replaced with "SQL Server (<instance name>)".

If the workaround does not resolve the issue described as above in your case, please let us know.


Do you know that you can post question w.r.t SQL Server data access, connectivty issues at http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=87&SiteID=1 ?


Nan Tu, Software Design Engineer, SQL Protocols



Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights


%3CLINGO-SUB%20id%3D%22lingo-sub-383041%22%20slang%3D%22en-US%22%3EUnable%20to%20correct%20invalid%20SQL%20Server%20Network%20Configuration%20on%20clustered%20SQL%20Server%20causes%20clustered%20SQL%20Server%20fail%20to%20start%20%E2%80%9Cpermanently%E2%80%9D%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-383041%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20MSDN%20on%20Dec%2006%2C%202005%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CP%3ERecently%2C%20we%20encountered%20an%20issue%20reported%20by%20a%20customer%20on%20a%20clustered%20SQL%20Server.%20What%20happens%20is%20the%20following.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EThe%20Customer%20needs%20to%20restrict%20the%20number%20of%20IP%20addresses%20SQL%202005%20Server%20is%20listening.%20He%20uses%20the%20following%20procedure%20for%20that%3A%20open%20%E2%80%9CSQL%20Server%20Configuration%20Manager%E2%80%9D%20(SSCM)%26nbsp%3B%20-%26gt%3B%20%E2%80%9CSQL%20Server%202005%20Network%20Configuration%E2%80%9D%20-%26gt%3B%20%E2%80%9CProtocols%20for%20XX%E2%80%9D%20%2C%20right%20clicked%20TCP%2FIP%20choosing%20Protocols%20and%20set%20%E2%80%9CListen%20All%E2%80%9D%20to%20%E2%80%9CNO%E2%80%9D.%20After%20that%20he%20wants%20to%20set%20the%20proper%20IP-addresses.%20This%20is%20working%20fine%20on%20a%20non-clustered%20system.%20On%20a%20clustered%20system%20the%20following%20happens%20when%20he%20is%20restarting%20SQL%20Server%3A%20SQL%20Server%20does%20not%20come%20online%20anymore.%20And%20the%20SQL%20Server%20error%20log%20reports%20the%20following.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ESQL%20Server%202005%20errorlog%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E2005-11-28%2010%3A53%3A29.02%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Error%3A%2017182%2C%20Severity%3A%2016%2C%20State%3A%201.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E2005-11-28%2010%3A53%3A29.02%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20TDSSNIClient%20initialization%20failed%20with%20error%200x32%2C%20status%20code%200x1c.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E2005-11-28%2010%3A53%3A29.02%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Error%3A%2017182%2C%20Severity%3A%2016%2C%20State%3A%201.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E2005-11-28%2010%3A53%3A29.02%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20TDSSNIClient%20initialization%20failed%20with%20error%200x32%2C%20status%20code%200x1.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E2005-11-28%2010%3A53%3A29.03%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Error%3A%2017826%2C%20Severity%3A%2018%2C%20State%3A%203.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E2005-11-28%2010%3A53%3A29.03%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Could%20not%20start%20the%20network%20library%20because%20of%20an%20internal%20error%20in%20the%20network%20library.%20To%20determine%20the%20cause%2C%20review%20the%20errors%20immediately%20preceding%20this%20one%20in%20the%20error%20log.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E2005-11-28%2010%3A53%3A29.03%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Error%3A%2017120%2C%20Severity%3A%2016%2C%20State%3A%201.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E2005-11-28%2010%3A53%3A29.03%20Server%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20SQL%20Server%20could%20not%20spawn%20FRunCM%20thread.%20Check%20the%20SQL%20Server%20error%20log%20and%20the%20Windows%20event%20logs%20for%20information%20about%20possible%20related%20problems.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EConfiguring%20the%20server%20to%20listening%20on%20individual%20IP-addresses%20is%20not%20supported%20on%20Clustered%20SQL%20Server%2C%20thus%20the%20failure%20indicated%20by%20the%20error%20log%20is%20accurate.%20However%2C%20the%20customer%20can%20NOT%20set%20%E2%80%9CListen%20ALL%E2%80%9D%20to%20%E2%80%9CYes%E2%80%9D%20any%20more%20to%20bring%20the%20server%20online.%20To%20be%20more%20accurate%2C%20even%20though%20the%20customer%20can%20set%20%E2%80%9CListen%20ALL%E2%80%9D%20to%20%E2%80%9CYes%E2%80%9D%20using%20SSCM%20on%20each%20physical%20node%2C%20each%20time%20he%20try%20to%20bring%20SQL%20Server%20online%2C%20the%20value%20will%20be%20overwritten%20to%20%E2%80%9CNO%E2%80%9D%20and%20the%20clustered%20SQL%20Server%20will%20end%20up%20failing.%20This%20is%20a%20serious%20issue%20that%20causes%20frustration%20of%20our%20customers.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EThe%20root%20cause%20of%20this%20issue%20is%20because%20of%20cluster%20checkpoint%20service%20behavior.%20If%20a%20setting%20is%20changed%20while%20the%20resource%20is%20online%2C%20that%20change%20will%20get%20check-pointed%20to%20the%20CPT%20hive%20file%20in%20the%20cluster%20quorum%20disk.%20If%20the%20resource%20is%20offline%20while%20you%20make%20the%20parameter%20change%2C%20then%20it%20will%20never%20be%20check-pointed.%20Each%20time%20you%20bring%20up%20the%20resources%2C%20the%20check-pointed%20value%20will%20overwrite%20the%20local%20value.%20SQL%20Server%20network%20configuration%20is%20one%20resource%20that%20is%20check-pointed.%20So%2C%20if%20you%20put%20the%20SQL%20Server%20resource%20offline%20while%20you%20change%20the%20%E2%80%9CListen%20All%E2%80%9D%20from%20%E2%80%9CNO%E2%80%9D%20to%20%E2%80%9CYES%E2%80%9D%2C%20and%20then%20you%20try%20to%20put%20the%20resource%20back%20online%2C%20it%20will%20fail%20as%20the%20%22local%22%20change%20was%20overwritten%20(during%20resource%20startup)%20with%20what%20was%20persisted%20in%20the%20checkpoint%20file.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EBecause%20of%20this%20check-pointing%20behavior%2C%20any%20time%20that%20SQL%20Server%20network%20configurations%20are%20modified%20into%20invalid%20values%20while%20the%20server%20is%20online%2C%20restarting%20the%20clustered%20SQL%20Server%20will%20cause%20the%20server%20fail%20to%20start%20%E2%80%9Cpermanently%E2%80%9D.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ETo%20get%20out%20of%20such%20BAD%20state%2C%20one%20workaround%20is%20to%20disable%20the%20check-pointing%20for%20SQL%20Server%20network%20configuration%2C%20described%20as%20following.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E1.%20While%20SQL%20Server%20instance%20is%20in%20offline%2Ffailed%20state%2C%20disable%20cluster%20checkpointing%20for%20network%20configuration%20by%3A%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3Ecluster%20res%20%22SQL%20Server%22%20%2Fremovecheck%3A%E2%80%9DSoftwareMicrosoftMicrosoft%20SQL%20ServerMSSQL.XXXMSSQLSERVER%E2%80%9D%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E2.%20Correct%20the%20configuration%20by%20using%20SSCM.%20Verified%20the%20key%20was%20corrected%20on%20both%20nodes.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E3.%20Bring%20SQL%20cluster%20back%20online.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E4.%20Re-enabled%20cluster%20checkpointing%20for%20network%20configuration%20by%3A%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3Ecluster%20res%20%22SQL%20Server%22%20%2Faddcheck%3A%20%E2%80%9DSoftwareMicrosoftMicrosoft%20SQL%20ServerMSSQL.XXXMSSQLSERVER%E2%80%9D%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ENote%20that%2C%20for%20named%20instance%2C%20the%20resource%20display%20name%20%22SQL%20Server%22%20should%20be%20replaced%20with%20%22SQL%20Server%20(%3CINSTANCE%20name%3D%22%22%3E)%22.%3C%2FINSTANCE%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3EIf%20the%26nbsp%3Bworkaround%20does%20not%20resolve%20the%20issue%20described%20as%20above%20in%20your%20case%2C%20please%20let%20us%20know.%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EDo%20you%20know%20that%20you%20can%20post%20question%20w.r.t%20SQL%20Server%20data%20access%2C%20connectivty%20issues%20at%20%3CA%20href%3D%22http%3A%2F%2Fforums.microsoft.com%2FMSDN%2FShowForum.aspx%3FForumID%3D87%26amp%3BSiteID%3D1%22%20mce_href%3D%22http%3A%2F%2Fforums.microsoft.com%2FMSDN%2FShowForum.aspx%3FForumID%3D87%26amp%3BSiteID%3D1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20http%3A%2F%2Fforums.microsoft.com%2FMSDN%2FShowForum.aspx%3FForumID%3D87%26amp%3BSiteID%3D1%20%3C%2FA%3E%20%3F%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ENan%20Tu%2C%20Software%20Design%20Engineer%2C%20SQL%20Protocols%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3EDisclaimer%3A%20This%20posting%20is%20provided%20%22AS%20IS%22%20with%20no%20warranties%2C%20and%20confers%20no%20rights%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-383041%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Dec%2006%2C%202005%20Recently%2C%20we%20encountered%20an%20issue%20reported%20by%20a%20customer%20on%20a%20clustered%20SQL%20Server.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-383041%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESQLServerProtocols%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Mar 23 2019 04:13 AM
Updated by: