April 18, 2007 at 7:00 am
Hello - in a 3 node clustered SQL 2000 with several instances, there is one instance where we cannot do tcp/ip connection, it fails with the generic Sever not found message and the SQL shows it as: "SuperSocket Info: Bind failed on TCP port *" (where the * is the port of the instance). Named pipes work fine.
Anyone had this before
April 18, 2007 at 11:35 am
Began getting the same messsage in early March of 2007 and the error has been occuring about once a week when the cluster keep-alive process has been restarting SQL Server.
The SQL Server is at Service Pack 3 and is supporting a third party application in a version that has not been tested with Service Pack 4. Will be upgrading the application and applying SP 4 next weekend and hope this will solve the issue. If SP 4 does not solve the problem, we will be opening a case with MS.
If you already have SP4 installed, please let me know.
Also, take a look at what Window patchs were applied before the problem occured.
SQL = Scarcely Qualifies as a Language
April 19, 2007 at 4:53 am
had something simialar (but not identical) and it was down to permissions service account had on the registry, in particular HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib
there is a good free tool from sysinternals called regmon you can use to se how SQL interacts with the registry on startup
---------------------------------------------------------------------
April 19, 2007 at 12:51 pm
Everyone, problem resolved and it was due to a conflicting IP address in one of the nodes registry with the actual ip of the cluster (of that instance). I guess a few main things to look for (beside permissions and protocol installation) in a similar case would be, is there a firewall, IPSec or anything on the network that may prevent proper communication? Run a netstat to see what is listening on that port, and finally check your registry settings under HKLM/MS SQL, for integrity and check against actual installation.
A.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply