February 25, 2010 at 2:27 am
TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
Named Pipes Provider: Could not open a connection to SQL Server [53]. (Microsoft SQL Server, Error: 53)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.4035&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
Cheers,
- Win.
" Have a great day "
February 25, 2010 at 3:06 am
Named Pipes
Remote Connections
TCP/IP ports
Firewall
Network all are fine...
When i add the same linked server to another server its working fine, even local machine PC is also connected but the TEST server failed to retrieve..
Any thoughts.... Please post.... Wasted half day already on this.... Trying FIX this asap....
Cheers,
- Win.
" Have a great day "
February 25, 2010 at 3:20 am
Some more points to add:
OLE DB provider "SQLNCLI" for linked server "OPSRVDB" returned message "Login timeout expired".
OLE DB provider "SQLNCLI" for linked server "OPSRVDB" returned message "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 SQL Server does not allow remote connections.".
Msg 53, Level 16, State 1, Line 0
Named Pipes Provider: Could not open a connection to SQL Server [53].
-Win.
Cheers,
- Win.
" Have a great day "
February 25, 2010 at 9:28 am
What port is the destination SQL Server machine listening on? Make sure it's not being blocked by a host based firewall.
----------------------------------------------------------------------------
Sacramento SQL Server users group - http://sac.sqlpass.org
Follow me on Twitter - @SQLDCH
----------------------------------------------------------------------------
February 25, 2010 at 9:35 am
were you able to ping the server?
February 25, 2010 at 10:14 pm
yes am able to Ping the server...
Also able to create linked server on the same server with another Instance...
But this instance is not able to...
Any thoughts...
Cheers,
- Win.
" Have a great day "
February 26, 2010 at 12:48 am
Hi
Both the SQL Server installations should be of either 64bit or 32bit.
i've seen instances where SQL Server Linker Server works fine in one way but failed to connect the other way.
Regards,
Sarabpreet Singh 😎
Sarabpreet.com
SQLChamp.com
Twitter: @Sarab_SQLGeek
February 26, 2010 at 1:44 am
:hehe:
Yes both the instances on the machine or of 64 BIT standard edition.
One instance is linked fine but the other failed.
Cheers,
- Win.
" Have a great day "
February 26, 2010 at 9:34 am
Once again, check the port that the destination server instance is listening on and make sure it's not blocked by a firewall. Ping'ing the server is not a valid test for connectivity, as SQL Server and ICMP traffic could be manipulated by a different firewall rule.
----------------------------------------------------------------------------
Sacramento SQL Server users group - http://sac.sqlpass.org
Follow me on Twitter - @SQLDCH
----------------------------------------------------------------------------
February 26, 2010 at 11:20 am
Are both instances of SQL Server the same version 2K/2K5/2K8 ??
Are they at the same patch level ??
Verify that both instances are configured the same.
Might be a security issue ... verify security.
Have someone else compare the settings ... sometime everything looks the same after a couple of hours:crying:.
hope this helps ...
Enjoy
"Give them the tools:crazy: ... Not the keys:smooooth:"
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply