issue : unable to start SQL server cluster instance and got it following error message.
Error message:
So we checked Sql browser service and found that the sql browser service was stopped and was in manual mode.
Sql Browser is the one which is responsible to route all the incoming connections for the sql server to their appropriate TCP port on which the sql server is listening. Sql browser service itself listen on port 1434 on UDP protocol. So whenever a client attempts to connect to the named instance of sql server, it will first try to connect to the Sql browser service which runs on port 1434 and then routes to the appropriate port on which sql server instance is listening.
However the above explanation does not hold true for default instance of the sql server which runs on port 1433 and hence the client does not require sql browser to route it’s connection but instead connects directly to port.
RESOLUTION
=========
So we started the sql browser service and changed it state to Automatic from manual. We observed that sql server came online fine without any error on node 2 without any error.
Error message:
Sql Server Resource Fails to come online on Cluster with Error Error Locating Server/Instance Specified [xFFFFFFFF]
CAUSE =====So we checked Sql browser service and found that the sql browser service was stopped and was in manual mode.
Sql Browser is the one which is responsible to route all the incoming connections for the sql server to their appropriate TCP port on which the sql server is listening. Sql browser service itself listen on port 1434 on UDP protocol. So whenever a client attempts to connect to the named instance of sql server, it will first try to connect to the Sql browser service which runs on port 1434 and then routes to the appropriate port on which sql server instance is listening.
However the above explanation does not hold true for default instance of the sql server which runs on port 1433 and hence the client does not require sql browser to route it’s connection but instead connects directly to port.
RESOLUTION
=========
So we started the sql browser service and changed it state to Automatic from manual. We observed that sql server came online fine without any error on node 2 without any error.
No comments:
Post a Comment