MS SQL Server - SQL Server Resolution Protocol not working

Author

SQL Server Resolution Protocol not working

Carlos Selonke

2006-10-24, 6:38 pm

Hello

I have a server with five SQL Server 2000 instances installed (default
and four named).
The directory structure for the default instance (MSSQLSERVER) was
removed and the both MSSQLSERVER and SQLServerAgent services stopped
working. Right now both services are disabled.

After that problem all my connections from the client computers to the
named instances that are still running on the server stopped working.
If I create an alias on the client computer mapping the name of the
server and the port number from the instance the connections works.
Port number UDP\1434 is not blocked on the server.

I search on the internet and found that SQL Server uses SQL Server
Resolution Protocol to map the named instance to the port number. With
a little more research I found a registry key
HKLM\Software\Micros
oft\Microsoft SQL Server\ SsrpActiveServer with a
value of MSSQLSERVER on my server.

Is the above key responsible for staying what instance is responsible
for the SQL Server Resolution Protocol?
If it is, and my MSSQLSERVER is down, should I change the value of the
key to a instance that is up and running?
Is there any other way to solve the problem?

Thanks for your help

Carlos Selonke

2006-10-24, 6:38 pm

Since I solved my problem I will post the solution:

I changed the value of HKLM\Software\Micros
oft\Microsoft SQL Server\
SsrpActiveServer to the name of one of the named instances that are
working.
I stopped all the instances and started only the instance that I choose
for SsrpActiveServer. After that I started the other instances.

Carlos Selonke wrote:
> Hello
>
> I have a server with five SQL Server 2000 instances installed (default
> and four named).
> The directory structure for the default instance (MSSQLSERVER) was
> removed and the both MSSQLSERVER and SQLServerAgent services stopped
> working. Right now both services are disabled.
>
> After that problem all my connections from the client computers to the
> named instances that are still running on the server stopped working.
> If I create an alias on the client computer mapping the name of the
> server and the port number from the instance the connections works.
> Port number UDP\1434 is not blocked on the server.
>
> I search on the internet and found that SQL Server uses SQL Server
> Resolution Protocol to map the named instance to the port number. With
> a little more research I found a registry key
> HKLM\Software\Micros
oft\Microsoft SQL Server\ SsrpActiveServer with a
> value of MSSQLSERVER on my server.
>
> Is the above key responsible for staying what instance is responsible
> for the SQL Server Resolution Protocol?
> If it is, and my MSSQLSERVER is down, should I change the value of the
> key to a instance that is up and running?
> Is there any other way to solve the problem?
>
> Thanks for your help

Sponsored Links