sql server does not exist or access denied connectionOpen(connect())
I am trying to link SQL SE 2000 (Local server at head office) to MSDE 2000 (remote server). After creating the server group in local server, I try to register SQL server Computers (MSDE 2000) to place in it.
But I received this error message.
"SQL server registration failed because of the connect failure displayed below. Do you wish to Register anyway
SQL Server does not exist or access denied connectionOpen(Connect()).'"
I checked the setup for client and server utilities.
Client Utility is TCP/IP
Server Utility is Named pipe
Please, help me. I don't know what went wrong here.
Is sql service running on remote server? Which authentication used to register the server? Is your windows account a valid sql login on that server? Did you use correct sql login and password if use sql authentication?
SQL Server does not exist or access denied. connectionopen(Connect())
I am getting the above error when I try to connect to a remote sql server.
I have tried to connect using Named Pipes. However, that did not solve the issue.
I have verified the username, password.....and they are correct.
I have also re-installed my sql server, even that did not solve the issue.
I could connect a couple of weeks back...this error started popping only a couple of weeks ago. I have not installed any new software, firewalls etc on my machine since then, neither have I installed any new service packs.
Can anyone help me out here please !!!!
This may be way out in left field but maybe enabling ping for the sake of your investigation may help establish the fact that you can actually see the machine.
Now if the sql client network util only has TCPIP and the server only has named pipes then I fail to see how that is going to work. You can add TCPIP to the server.
Further I believe that named pipes requires that your connection request must first log onto the server before it can log onto SQL server. Thus if you are using named pipes then you may want to confirm that you can connect to a share that is set up on the SQL server (if you can connect to a share then you should be able to connect to the SQL server).
TCPIP does not require that you must first must first log onto the server so it would seem that adding TCPIP to the server is a cleaner way to test your issue rather than changing the client to named pipes. Well, thats the theory anyway.
Also make sure that when using TCPIP that the both client and server are set to same port number (change the client port to the server port).
Further, you should also look at the current SQL Server log and determine what SQL Server is actually listening on. It will tell you what netlibs are being used and what port is open. Be aware that the server network util settings can be changed but the settings dont come into effect until after a restart of the SQL service - thus you need to know the current settings thus the reference to the SQL log. Be on the lookout for reported errors such as failed to bind to port.