SQL Server Performance Forum – Threads Archive
New Installation of Yukon
Hi, I have installed Yukon on one of my servers. I am trying to register a new server, and I am getting an error. I can’t figure out why I am getting this. Any help on this would be appreciated.<br /><br /><br />TITLE: Microsoft SQL Server Management Studio<br />——————————<br /><br />A connection was successfully established with the server, but then an error occurred during the pre-login handshake. <br />(provider: Named Pipes Provider, error: 0 – No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)<br /><br />For help, click:<a target="_blank" href=http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476>http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a><br /><br />Help!
‘ />]<br />Launa
I believe the default protocol is not enabled as TCP/IP, so check and re-enable it. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS†with no rights for the sake of knowledge sharing.
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by launa</i><br /><br />Hi, I have installed Yukon on one of my servers. I am trying to register a new server, and I am getting an error. I can’t figure out why I am getting this. Any help on this would be appreciated.<br /><br /><br />TITLE: Microsoft SQL Server Management Studio<br />——————————<br /><br />A connection was successfully established with the server, but then an error occurred during the pre-login handshake. <br />(provider: Named Pipes Provider, error: 0 – No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)<br /><br />For help, click:<a target="_blank" href=http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476>http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476</a><br /><br />Help!![<img src=’/community/emoticons/emotion-6.gif’ alt=’
‘ />]<br />Launa<br /><hr height="1" noshade id="quote"></font id="quote"></blockquote id="quote"><br /><br /><br />We had the same problem. Look into the SQL Configuration Manager -> SQL Native Client Configuration -> Client protocols. Enable VIA. <br /><br />Also make sure that in Network Configuration -> Protocols; VIA is disabled.<br /><br />Doesn’t make any sense but its Microsoft[<img src=’/community/emoticons/emotion-2.gif’ alt=’
‘ />]<br /><br />Best of luck<br />NASCREATIVE
To resolve this problem, you will have to upgrade the client side data access stacks as follows:
If it is a managed application, upgrade the client to Visual Studio Beta 2. If it is a native application, upgrade the client to CTP February 2005 or later. says athttp://download.microsoft.com/download/E/1/1/E1196B19-DE92-4AB2-BAFD-5B5AD26E67B4/AprilCTPNotes.mht —————————————-
http://spaces.msn.com/members/dineshasanka
True in order to workout anything on SQL 2005 its better to work from July CTP until end of November 2005, where you can get hands on first RTM. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS†with no rights for the sake of knowledge sharing.
]]>