May 29, 2024 at 11:17 am
I getting the bellow error when runing query on linkedserver from another server after adding linkedserver.
OLE DB provider "MSOLEDBSQL" for linked server "xxx.xxx.x.xxx" returned message "Protocol error in TDS stream".
OLE DB provider "MSOLEDBSQL" for linked server "xxx.xxx.x.xxx" returned message "Communication link failure".
Msg -1, Level 16, State 1, Line 11
Session Provider: Connection has been closed by peer [xFFFFFFFF].
OLE DB provider "MSOLEDBSQL" for linked server "192.168.1.112" returned message "Communication link failure".
Msg -1, Level 16, State 1, Line 11
Session Provider: Connection has been closed by peer [xFFFFFFFF].
OLE DB provider "MSOLEDBSQL" for linked server "192.168.1.112" returned message "Communication link failure".
Msg -1, Level 16, State 1, Line 11
Session Provider: Connection has been closed by peer [xFFFFFFFF].
May 30, 2024 at 12:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
June 14, 2024 at 8:34 pm
Have you tried googling the error? There are a lot of pages on google with similar errors such as this one:
https://dba.stackexchange.com/questions/188833/sql-linked-server-returning-error-suddenly-upon-query
In that scenario, the problem was a faulty NIC.
I recommend checking your windows logs and see what you can see.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply