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

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

anliu — Wed, 14 Dec 2005 19:22:52 GMT

there is a similar story in sql 2000

a resource kit tool clusterrecovery.exe can do the same thing (refresh the registry checkpoint) with a GUI, without having to know the registry keys

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

Manik Mittal — Mon, 06 Feb 2006 13:08:03 GMT

I am trying to connect to a server which is installed with SQL server 2000, using SQL server 2005 client. I am getting the following error

When connecting to SQL server 2005, his failure may be caused by the fact that under the default settingsSQL server does not allow remote connections. (Provider: Named pipes Provider, error: 40 - could not open a connection to SQL server)(Microsoft SQL server, Error:53)

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

Nan Tu — Fri, 03 Mar 2006 04:56:48 GMT

Manik,

This is a connectivity issue not pertain only to Cluster Scenario. In your case, you need to check:

(1) Remote connectivity is enabled. If not, you can use SQL Server Surface Area Configuration to enable that.

(2) Make sure that the listening port of SQL Server is not blocked by Windows Firewall

SQL error

SQL error — Tue, 06 Jun 2006 06:07:08 GMT

When connecting to SQL server 2005, his failure may be caused by the fact that under the default settingsSQL server does not allow remote connections. (Provider: Named pipes Provider, error: 40 - could not open a connection to SQL server)(Microsoft SQL server, Error:53)

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

Bob Dean — Thu, 18 Jan 2007 05:30:36 GMT

I get the error message above.

I have made the exception in the firewall for both Database engine and the Browser processes. I configured Surface Area config to allow remote with TCP and Named Pipes. I turned on the service "Browser". I still get the error above.

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

SQL Protocols — Thu, 18 Jan 2007 22:56:56 GMT

Please try to answer questions in

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1,

If it doesn't solve your problem, please post your question on the forum. It'll be answered in a timely manner.

Thanks,

Nan

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

Ralph Schoch — Thu, 07 Jun 2007 03:51:39 GMT

Thanks for your blog Nan. I was expecting to have to make a call but was saved hours of heartache by being able to stop the cluster checkpoint. I found your explanation doing a search on the network error.

May I suggest that KB docs 823938 and 265808 be updated to warn folks like me that do not realize static ports are not supported on a cluster? I struggled a bit with the syntax but eventually got it. Fortunately, it was not a production machine.

Ralph

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

Nilton Pinheiro — Sat, 16 Feb 2008 07:41:42 GMT

Hi all,

I did use this but got error as below:

C:\>cluster res "SQL Server" /removecheck:"Software\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLSERVER"

The 'removecheck' option does not require any parameters to be specified.

See "CLUSTER RESOURCE /?" for correct syntax.

So, I open a case with support team and the soluction was:

1.With SQL offline on cluster

C:\>cluster res "SQL Server" /checkpoints

--- List all checkpoint to SQL Server

2. Run /removecheckpoints

C:\>cluster res "SQL Server" /removecheckpoints:"Software\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer"

3.Correct the configuration by using SSCM.

4.run /addcheckpoints

C:\>cluster res "SQL Server" /addcheckpoints:"Software\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer"

5. Bring SQL cluster back online.

Yes....it´s ok now !!

regards

Nilton Pinheiro

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

Brent Ozar — Wed, 26 Mar 2008 23:41:15 GMT

Worked like a champ. Thanks for the post - we looked everywhere trying to fix this.

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

Spicoli — Sat, 10 May 2008 06:09:04 GMT

Thanks heaps, worked perfectly - just the commands in the original post weren't right but Nilton Pinheiro's correctios were. It's /removecheckpoints not /removecheck and /addcheckpoints not /addcheck

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

Jorge Martinez — Thu, 26 Jun 2008 10:18:30 GMT

Nilton, you save me from a new support call... txs!

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

Adam — Thu, 12 Feb 2009 02:40:16 GMT

This post just saved me from insanity, thank you so much!

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

Daniel Roberts — Tue, 31 Mar 2009 04:27:43 GMT

Thanks Nan and Nilton, worked perfectly