|
Friends, I Have a problemn. I cant configure Linked server to other sql server. I received the following error? A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.) (.Net SqlClient Data Provider) Windows server 2003 R2 Standandard SQL Server 2008 Standandard I believe that is a imcopatibility between SQL 2008 and Windows 2003 R2. Can anyone help me??
(comments are locked)
|
|
No, it means you're trying to connect using the Shared Memory Provider which is probably not possible unless you're trying to connect to a different instance on the same machine. Check your set up. You probably need to enable, on a guess, TCPIP to get the right connection. I trying to connect a different instance. The protocols TCP/IP, Named Pipes e Shared memory was enable in SQL Configuration Manager. What can i do?
Aug 04 '10 at 12:09 PM
Felipe Silva
Assuming you're using TCP like everyone else, I wouldn't bother with named pipes or shared memory. I usually disable named pipes in fact. Make sure the protocols are enabled on both servers. Make sure the second server allows remote connections. Check the connection string to be sure you have it right. Are you using SQL Native Client or SQL OLEDB Provider? I usually use the Native Client. It's easier to set up. You just need the server & instance name.
Aug 04 '10 at 12:17 PM
Grant Fritchey ♦♦
I use sql native client. There are other server that can connect second server. The login configured in linked server was sysadmin;
Aug 04 '10 at 12:28 PM
Felipe Silva
That's probably not a real login. You need to set up security using a known acccount.
Aug 04 '10 at 12:34 PM
Grant Fritchey ♦♦
I used sa account. It has the same psasword in all servers.
Aug 04 '10 at 12:37 PM
Felipe Silva
(comments are locked)
|
|
A workaround is probably to go with TCP/IP as Grant says, but I don't believe you are actually doing anything wrong - I think you've stumbled across a bug. One suggestion I would have is to check the event log on the server to check for any events being logged at the same time as your error. As an aside, I stumbled across this KB article while digging for info, which has the most scary list of possible side-effects for an ALTER TABLE statement - ever! : http://support.microsoft.com/kb/916780 I formated the server, reinstall sql server, configured the linked server (the same way) and work correctly. I think this is a any configuration on server, but i dont know what configuration. Anyone can help me?
Aug 29 '10 at 12:27 PM
Felipe Silva
(comments are locked)
|
