Help (Out-of-process use of OLE DB provider):
We have a SQL server (SQL2005 Sp2 (3054) on our company that every night executes a SQL job (use Stored Procedures, no executables involved) that sends records to 4 different remote servers in the Same Building. All these servers are SQL2000 SP4 (8.00.2187) Enterprise Edition. The operating System in all servers is MS Server 2003- NT 5.2 (3790). The SQL job usually takes about 2 hours to complete but this week is started to fail only for one of the servers our Development team found a problem with a store procedure and is working on a hot fix, But last night our DBA team decided to put a trace in the SQL job to find out if there was any other error that we can capture and found the following error in the trace : Msg 7430, Sev 16, State 3, Line 10 : Out-of-process use of OLE DB provider "SQLNCLI" with SQL Server is not supported. [SQLSTATE 42000]
After that happened we resubmitted the job on the same step and it completed without errors in less than 15 minutes, we have researched the internet to try to find out an explanation of this error but so far there is not much luck.
We only found this document but it has not been much help (http://msdn.microsoft.com/en-us/library/ms143359.aspx)
THis is na extract of that document:
--=========================================================================A linked server that was defined by using 'SQLOLEDB' as the provider name will be modified to 'SQLNCLI' (SQL Native Client OLE DB Provider) upon upgrade. The sys.sysservers compatibility view shows linked servers that use 'SQLNCLI' as 'SQLOLEDB'. The SQL Server 2005 catalog view sys.servers shows linked servers that use 'SQLNCLI' as 'SQLNCLI'.
Heterogeneous queries and the use of OLE DB providers are not supported when SQL Server is running in fiber mode. Fiber mode is enabled when the lightweight pooling advanced configuration option is set to 1.
The SQL Native Client OLE DB Provider cannot be instantiated out-of-process.
If anybody has any additional information regarding this error will be greatly appreciated.
Rafael A. Colón
Database Administrator, Information Systems