Recently I received a new laptop at work with windows 7 on it. Having BIDS 2008 installed. I wanted to test an existing SSIS package (stored on our network) that others developed months ago. But I can’t execute this package on that machine as I get this error:
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: “Microsoft JET Database Engine” Hresult: 0x80004005 Description: “Unspecified error”.
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: “Microsoft JET Database Engine” Hresult: 0x80004005 Description: “Unspecified error”.
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 “MyConnectionManager” 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 “MyConnectionManager” 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 “MyConnectionManager” (72) failed validation and returned error code 0xC020801C.
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 System admin 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.
So now let c how I fix the prblm step by step.
Permissions
To perform its functions, SQL Server Agent must be configured to use the credentials of an account that is a member of the sysadmin fixed server role in SQL Server. The account must have the following Windows permissions:
-
Log on as a service (SeServiceLogonRight)
-
Replace a process-level token (SeAssignPrimaryTokenPrivilege)
-
Bypass traverse checking (SeChangeNotifyPrivilege)
-
Adjust memory quotas for a process (SeIncreaseQuotaPrivilege)
To configure SQL Server Agent
-
Click the Start button, and then, on the Start menu, click Control Panel.
-
In Control Panel, click System and Security, click Administrative Tools, and then select Local Security Policy.
-
In Local Security Policy, click the chevron to expand the Local Policies folder, and then click the User Rights Assignment folder.
-
Right-click a permission that you want to configure for use with SQL Server and select Properties.
-
In the permission’s properties dialog box, verify that the account under which SQL Server Agent runs is listed. If not, click Add User or Group, enter the account under which SQL Server Agent runs in the Select Users, Computers, Service Accounts, or Groups dialog box, and then click OK.
-
Repeat for each permission that you want to add to run with SQL Server Agent. When finished, click OK.
-
Vision Binary 
Leave a comment