Lynn 2010-04-03 13:26:44
We only enable Shared Memory and TCP/IP protocal in server side. And, those
are the error they are getting.
osql — SQL server doesn’t exist or access denied
Query Analyzer — General network error. Check your network documentation
VS 2005 — (without specifing TCP protocal in connection) A connection was
succssfully established with the server, but then an error occured during the
pre-login handshake. When connecting …..(provider: Named Pipes provider,
error: 0 – No process is on the ther end of the pipe)
VS 2005 — (specify TCP protocal in connection) An error has occurred while
establishing a connection to the server. When connecting to SQL server 2005,
this failure may be caused by the fact that under the default settings …
(provider: TCP provider: 0 — A connection attempt failed because the
connected party didn’t not properly respond after a period of tiem, or
established connection failed because connected host has failed to respond.)
Again, this developer is able to login by using my machine with his WIN
After I enable Named Pipes in server. This developer is able to connect to
server on his machine by using Named Pipe.
Firewall is off in the server, so I can’t think of the issue for TCP
connection on developer’s machine.
Please advise. Thank you.