April 18, 2008 at 10:46 am
Hi,
I have a teradata SSIS package which uses 32 bit oledb connection, running on a 64 bit operating system. When I changed the properties not to use the 64bit inside BI dev studio, the package runs fine there. But when I schedule the job I am having problem. Whether someone faced this issue?
I use comand line arguments inside Job scheduler to schedule the SSIS job. So I ask the sql server agent to run the job using dtexec.exe instead of 64 bit exe. the command prompt exec is following.
"C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\dtexec.exe" /SQL "packagename" /SERVER "servername" /CONNECTION "connection_name1";"Data Source=mssqlservername1;Initial Catalog=database_name;Provider=SQLOLEDB.1;Integrated Security=SSPI;" /CONNECTION connection_name2;"Data Source=teradata_server_name;User ID=user_id;pwd=password;Provider=TDOLEDB.1;Persist Security Info=True;" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EW
the job history error is following.
Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2008-04-17 23:30:13.06 Code: 0xC0202009 Source: connection_name Connection manager "teradata_server_name" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E21. End Error Error: 2008-04-17 23:30:13.06 Code: 0xC020801C Source: Get Sales Out OLE DB Source [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection... Process Exit Code 1. The step failed.
October 16, 2009 at 9:48 am
Promod,
Did you ever solve this problem? I am currently working on the same issue. I am in the process of writting a console app to just work around this issue. The SSIS packages works fine on my local 64 but one I fold the sql job into the mix it blows up. I can even run the package directly from SSIS on the 64 bit box with no issues. I tried the command line to force the 32bit execution as well with no.
Any updates?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply