May 23, 2014 at 2:06 am
Hello all,
I have a big issuer with job ssis in SQL 2012. Please help me review and give me some advise.
I create a ssis package with have connection DB2 (I install ibm_data_server_client_win32_V97 in server) in sql2008 (run ok). I deployment in SQL 2012. When i run with Visual Studio or run direct package (*.dtsx). File run OK.
But, i run with job have a error as below.
Error: 2014-05-15 14:18:08.82 Code: 0xC0202009 Source: Package Connection manager "TESTING.cardpro1"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80004005 Description: "Unspecified error".
End Error
Error: 2014-05-15 14:18:08.82 Code: 0xC020801C Source: Xuat Report AUDCAR Cardpro-cp_audcar [2] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.
The AcquireConnection method call to the connection manager "TESTING.cardpro1" failed with error code 0xC0202009.
There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error
I run with user full permission. I run job success with dtxs no contain DB2 connection. Do you have a this case?
May 23, 2014 at 2:14 am
The account that executes the job step must have sufficient privileges to load the provider and connect to the target database.
That account will (hopefully) be different from your user account.
Depending on your setup it could be:
* The SQL Server Agent service account
* The job owner
* The proxy account specified for the SSIS job step
Also keep in mind that you're executing the package on a different machine, that could be missing some component (e.g. OLED provider)
I would try to log on to the remote machine impersonating the account that runs the job step and execute the package manually.
That should put you in the right direction.
Hope this help
Gianluca
-- Gianluca Sartori
May 23, 2014 at 2:25 am
Dear Gianluca,
Thanks for your quick reply. Yes, it package is created on server A (Win Server 2k8/ SQL 2008). And i deployment this package on Server B (Win server 2012/ SQL 2012).
Only error when i run with job (run with bouble click *.dtsx or open visual studio is ok). I do not know it loss driver OLEDB DB2 or any one? This error only with connection DB2
December 19, 2018 at 8:13 am
RESOLVED
For future reference, we found that adding the SSIS proxy account to the DB2ADMNS local users group solved this problem.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply