June 6, 2011 at 12:28 pm
This is odd!
I recently encountered some problem on setting up linked server using a dedicated account, so I made some changes to my working linked server, it was not working but I figured out a work around to do my job.
However, because of the change, my old application is broken now, and I can't re-establish it even using the original setting, in stead, I got this error:
OLE DB provider "SQLNCLI" for linked server "h1datap1nt" returned message "Login timeout expired".
OLE DB provider "SQLNCLI" for linked server "h1datap1nt" 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 2, Level 16, State 1, Line 0
Named Pipes Provider: Could not open a connection to SQL Server [2].
I have double checked with the server's DBA, I was told nothing has been touched on their side.
So, what's going on there? Thank you very much. Any clue is deeply appreciated.
June 6, 2011 at 12:54 pm
verify that the account is not locked out..
might be easier to create a new 'test account' to setup the link - use SQL auth.
June 6, 2011 at 1:17 pm
Thanks for your reply.
The account is a SQL account, I guess this lock out scenario doesn't apply, right?
June 6, 2011 at 2:02 pm
no it applys...
in SSMS go to that account and verify that it is not locked out.
June 6, 2011 at 4:22 pm
Even if this applies, it should be the other side server, that server is a SQL 2000, does it have this function? I don't know.
Anyway, it suddenly works, no any clue.
Thank you.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply