Share via

SQL browser fails to come online after changing it to a static port

  • Article

Issue

SQL clustered service fails to come online after an attempt to change a static port

 

· We noticed the following error in the SQL server error logs

2010-10-24 09:10:53.92 spid6s The resource database build version is 9.00.4230. This is an informational message only. No user action is required.
2010-10-24 09:10:54.25 spid6s Error: 15466, Severity: 16, State: 1.
2010-10-24 09:10:54.25 spid6s An error occurred during decryption.
2010-10-24 09:10:54.26 spid10s Starting up database 'model'.
2010-10-24 09:10:54.26 Server Error: 17182, Severity: 16, State: 1.
2010-10-24 09:10:54.26 Server TDSSNIClient initialization failed with error 0xd, status code 0x10.
2010-10-24 09:10:54.26 spid6s Server name is 'SQ02PDB\SQ02PDB'. This is an informational message only. No user action is required.
2010-10-24 09:10:54.26 Server Error: 17182, Severity: 16, State: 1.
2010-10-24 09:10:54.26 Server TDSSNIClient initialization failed with error 0xd, status code 0x1.
2010-10-24 09:10:54.26 spid6s The NETBIOS name of the local node that is running the server is 'GRRAPICL21B'. This is an informational message only. No user action is required.
2010-10-24 09:10:54.26 Server Error: 17826, Severity: 18, State: 3.
2010-10-24 09:10:54.26 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.
2010-10-24 09:10:54.26 Server Error: 17120, Severity: 16, State: 1.
2010-10-24 09:10:54.26 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.

 

· We were running into a known issue: KB 907853 SQL Server 2005 does not start if the server-side TCP Port field contains trailing spaces

· We looked at this registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\Tcp\IPAll and there was a trailing space in the hive: TcpDynamicPorts

· Since this hive was check pointed went ahead and removed the checkpoint:

cluster res "SQL Server (instancename)" /removecheck: "Software\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLSERVER"

· We deleted the trailing spaces and re-added the checkpoint :

cluster res "SQL Server (instancename)" /addcheck: "Software\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLSERVER"

 

Regards,
Amrutha Varshini