Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Perry Dyball - perrydyball NOSPAM-AT-NOSPAM hotmail.com	Report As Irrelevant
Written: 11/16/2004 9: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: SHELL0\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. Error 7399 points to an issue with Linked Servers (mysteriously refers to MSAccess) Error 7312 points to a connectivity issue when specifying 4 part object names ie SERVER.DB.OWNER.OBJECT OLE/DB Provider 'SQLOLEDB' ::CreateSession returned 0x80004005 points to kb 822668 We performed a OLEDB Error trace in SQL Profiler and the problem reoccurred and gave us the following errors OLE/DB Provider 'SQLOLEDB' ::GetSchemaLock returned 0x80004005: OLE DB provider SQLOLEDB supported the Schema Lock interface, but returned 0x80004005 for GetSchemaLock .]. OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ::CreateSession returned 0x80004005. 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.78 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.

Anonymous User	Report As Irrelevant
Written: 4/16/2007 12:39 AM
I had this error, or one very similar and managed to get the service work again by checking the current activity on the linked server and killing all processes from the original server.