July 17, 2009 at 11:22 am
Any idea what is the cause and how to solve this issue?
By the way I am using a linked Server
SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
OLE DB provider "SQLNCLI" for linked server "VCDB" returned message "Login timeout expired".
OLE DB provider "SQLNCLI" for linked server "VCDB" 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.".
Thanks
-Hunter
July 17, 2009 at 11:55 am
Does the target server allows remote connections?
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.July 17, 2009 at 12:38 pm
Yup it allow remote connection..
September 1, 2009 at 8:19 am
Do you finally find the solution for your problem ?
I think i have the same problem for 1 week. If you're still there and have something to help, please let me know.
thank.
January 11, 2010 at 3:43 pm
I am getting same error message when I trying to create a linked server.
SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
OLE DB provider "SQLNCLI" for linked server returned message "Login timeout expired".
OLE DB provider "SQLNCLI" for linked server 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.". (.Net SqlClient Data Provider)
Please let me know if there is any workaround for this.
The target server does allow remote connections.Thanks.
M&M
January 11, 2010 at 4:00 pm
mohammed moinudheen (1/11/2010)
I am getting same error message when I trying to create a linked server.SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
OLE DB provider "SQLNCLI" for linked server returned message "Login timeout expired".
OLE DB provider "SQLNCLI" for linked server 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.". (.Net SqlClient Data Provider)
Please let me know if there is any workaround for this.
The target server does allow remote connections.Thanks.
Have you mapped a user to remote sql login in the security tab?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
January 11, 2010 at 4:18 pm
Yes, but still same error.
M&M
January 11, 2010 at 4:29 pm
Are you using named instances by chance?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
January 11, 2010 at 4:37 pm
Yes, both source and target are named instances
M&M
January 11, 2010 at 4:45 pm
Is the Browser Service running in both instances?
Also, is the server defined using the \InstanceName or using the ,portNum method? Have you tried both methods?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
January 11, 2010 at 5:04 pm
SQL server browser is running on both the source and target server.
But on target it is running on local account, wheras on source it is running on service account.
Do you think, this would be a problem?
Also, I tried both instance names with port and without.
M&M
January 11, 2010 at 5:06 pm
Worth a shot on the service account. Set both to use the same account.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply