November 17, 2004 at 4:53 am
Host SQL Servers were at SP3a + MS03-031 (Version 8.00.818) when this problem occurred.
After changing the login properties of linked servers between two servers we saw an intermittent (but prolific) error that caused blocking on our databases.
The error was...
Executed as user: SERVERA\Administrator. OLE DB provider 'SQLOLEDB' reported an error. [SQLSTATE 42000] (Error 7399) [SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ::CreateSession returned 0x80004005: ]. [SQLSTATE 01000] (Error 7300). The step failed.
This was raised by certain scheduled jobs that run every minute. The jobs run a stored procedure on SERVERA that generates dynamic SQL that is then executed on SERVERB via a linked server connection. Other jobs/processes using the linked server worked successfully.
We performed a OLEDB Error trace in SQL Profiler and the problem reoccurred and gave us the following errors
All the errors logged are mentioned as symptoms in the http://support.microsoft.com/?kbid=822668 article indicating an issue with linked servers under peak load.
We hunted around and found a Hotfix download at http://support.microsoft.com/?kbid=838166 which takes version of SQL to 8.00.878 that contained all the files (or even newer versions) mentioned in the kb822668 article.
We applied the 8.00.878 and now all is OK!! The application of the hotfix takes approximately 5 minutes and the process stops and starts the SQL Server Services.
In all it took us over 20 hours to find the resolution to the original error so I hope this might help anyone in the same situation.
November 22, 2004 at 8:00 am
This was removed by the editor as SPAM
May 6, 2011 at 6:23 am
Hi All,
I am getting same error in SQL Server 2008. So what could be the problem. I had set The remote query expire to the infinite. But the problem persist so please analyze the problem . the error i am getting like
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "SQLNCLI10" for linked server "XXXXXX" reported an error. The provider did not give any information about the error.
Msg 7312, Level 16, State 1, Line 1
Invalid use of schema or catalog for OLE DB provider "SQLNCLI10" for linked server "XXXXXX". A four-part name was supplied, but the provider does not expose the necessary interfaces to use a catalog or schema.
May 6, 2011 at 8:45 am
Try using OPENQuery instead of Four-Part Query
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply