Microsoft KB Archive/933835

= Error message when an SSIS package runs that is scheduled to run as a SQL Server Agent job: &quot;An OLE DB error has occurred. Error code: 0x80004005&quot; =

Article ID: 933835

Article Last Modified on 11/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems

-





SYMPTOMS
When you schedule a Microsoft SQL Server 2005 Integration Services (SSIS) package to run as a SQL Server Agent job, you receive error messages that resemble the following when the job runs:

OnError,SQL1V5,MyDomain\MyAccount,Execute Source To Common Package,{BD5416B7-B16A-4788-99C9-5A1F674E326B},{E4B9AD56-627E-4801-A262-C9EFA9F163AC },11/21/2006 4:11:31 PM,11/21/2006 4:11:31 PM,-1071636471,0x,An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: &quot;Microsoft JET Database Engine&quot; Hresult: 0x80004005 Description: &quot;Unspecified error&quot;.

OnError,SQL1V5,MyDomain\MyAccount,DataSourceImport,{91A4C5D3-AC64-4DF8-B49E-7 3CFC9DAF979},{E4B9AD56-627E-4801-A262-C9EFA9F163AC},11/21/2006 4:11:31 PM,11/21/2006 4:11:31 PM,-1071636471,0x,An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: &quot;Microsoft JET Database Engine&quot; Hresult: 0x80004005 Description: &quot;Unspecified error&quot;.

OnError,SQL1V5,MyDomain\MyAccount,Execute Source To Common Package,{BD5416B7-B16A-4788-99C9-5A1F674E326B},{E4B9AD56-627E-4801-A262-C9EFA9F163AC },11/21/2006 4:11:31 PM,11/21/2006 4:11:31 PM,-1071611876,0x,The AcquireConnection method call to the connection manager &quot;MyConnectionManager&quot; failed with error code 0xC0202009.

OnError,SQL1V5,MyDomain\MyAccount,DataSourceImport,{91A4C5D3-AC64-4DF8-B49E-7 3CFC9DAF979},{E4B9AD56-627E-4801-A262-C9EFA9F163AC},11/21/2006 4:11:31 PM,11/21/2006 4:11:31 PM,-1071611876,0x,The AcquireConnection method call to the connection manager &quot;MyConnectionManager&quot; failed with error code 0xC0202009.

OnError,SQL1V5,MyDomain\MyAccount,Execute Source To Common Package,{BD5416B7-B16A-4788-99C9-5A1F674E326B},{E4B9AD56-627E-4801-A262-C9EFA9F163AC },11/21/2006 4:11:31 PM,11/21/2006 4:11:31 PM,-1073450985,0x,component &quot;MyConnectionManager&quot; (72) failed validation and returned error code 0xC020801C.



CAUSE
This issue occurs because the SQL Server 2005 Agent proxy account does not have permission for the Temp directory of the SQL Server Agent Service startup account.

This issue occurs because the SQL Server 2005 Agent proxy account does not have permission for the Temp directory of the SQL Server Agent Service Startup account.



RESOLUTION
To resolve this issue, you must change the permissions for the Temp directory of the SQL Server Agent Service startup account. Grant the Read permission and the Write permission to the SQL Server 2005 Agent proxy account for this directory.



STATUS
This behavior is by design.



MORE INFORMATION
The owner of the job determines the security context in which the job is run. If the job is owned by a SQL Server login account that is not a member of the Sysadmin fixed server role, the SSIS package runs under the context of the SQL Server Agent proxy account.

If you want the SQL Server Agent proxy to run jobs that connect to an instance of SQL Server, the SQL Server Agent proxy account must have correct permissions to the instance of SQL Server.

If you want the SQL Server Agent proxy account to run a job that runs as an SSIS package, the SQL Server Agent proxy account must have the Read permission and the Write permission to the Temp directory of the SQL Server Agent Service startup account.

Keywords: kbtshoot kbprb kbexpertiseadvanced kbsql2005ssis KB933835

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.