Cannot connect to server

[EuanPirie]

I'm fairly new to this SQL Server stuff, so I may have done something silly. However, as I had a list of instructions to follow, I dont think I did. <br>
<br>
I have an NT 4 Server, running service pack 5, a SQL Server 6.5 with service pack 3 installed. I have set it up, and gone into the Enterprise manager. I went to register a server, gave it a name, choose standard security, and the logon as SA. I clicked on Register, only to be faced by<br>
<br>
Unable to conect to Server (reason: [D-B library] Unable to connect: SQL Server is unavailable or does not exist. Specified SQL Server not found) Register Anyway?<br>
<br>
I clicked on yes. But when you try and do anything it just states that you cannot access the database, there is an error message. I'll post it later (dual boot machine, no web access on NT, forgot to write it down)<br>
<br>
Any suggestions?

 

[Lehtoant]

Something to check:<br>
<br>
1. Is SQL Service running? (Control Panel/Services)<br>
<br>
2. Gave it a name(???) SQL Server name and NT Server network name should be the same (check NT's name from Netwrok Neib. Properties/Identification). Try to list available server names by pushing Servers button in the registering window<br>
<br>
Good luck,<br>
Al<br>

 

[EuanPirie]

The SQL Server is running, and the name has been changed to the same as the network name, and still the same result.<br>
<br>
When I try and start the server that I just attempted to register, I get the following error:<br>
<br>
Error 1722 - (The RPC server is unavailable) occured while performing this service operation on the MSSQLServer service<br>
<br>
I can only cick on OK, and then I am stuck where I was.

 

[Shchepa]

This error ([D-B library] Unable to connect: SQL Server is unavailable or does not exist.) could appears if both the server and the client parts don't set to use the same protocol. Try to check what protocols is used by server (SQL Setup -&gt; Change network support) and the client (SQL Client Configuration Utility -&gt; Net library).<br>
Then, use the correct ID for server when you register it in the Enterprise Manager. If you set the protocol to Named Pipes, you should use the computer name, if TCP/IP Sockets - the IP address or (localhost), etc.<br>
<br>
Best wishes.<br>