Multiprotocol-Regestering Server

[I/B/E/S User]

I used SQL Server/Setup/Change Network Support to add Multiprotocol
Support to SQL Server 6.5(upgraded
with SP3). I configured Client Configuration Utility to use Multiprotocol
for this Server. When I tried to register
this server, I got an error: Unable to Connect to Server (reason:
[DB-library] Unable to connect. SQL Server is
unavailable or does not exist. General network error. In Event Viewer (NT
Server) I got a message:
Error 17832 Sev. 18 State 0 Unable to read login packet(s).

[Jim Prussack]

Check the error log to see if the server is listening on that protocol.
Multi-protocol depends on RPC services being started prior to SQL Server.
If those services failed or were not started, that protocol will not be
available.

Check out KB article @ http://www.microsoft.com/kb/articles/q160/8/71.htm
for reasons why and how to fix it...

Hope this helps

Jim

I/B/E/S User wrote in article <01bca353$7d908e90$67022e9b@alla>...