April 3, 2014 at 9:07 am
I am executing an SSIS package which pull data from an .xls spreadsheet and loads into Teradata table. The package runs absolutely fine in SSIS 2008. When I schedule the same jon with target being SQL Server not Teradata in SQL Server Agent, it works perfectly fine. But when the target is teradata table and when I schedule the package in SQL Server Agent 2008 the job abends.I get the below error
Message
Execute Package Utility Version 10.0.2531.0 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:03:31 AM Error: 2014-04-03 11:03:32.13 Code: 0xC0016016 Source: Description: 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: 2014-04-03 11:03:49.00 Code: 0xC0208452 Source: Data Flow Task ADO NET Destination [104] Description: ADO NET Destination has failed to acquire the connection {D5300ABA-09F3-4C2D-8415-CDB61042FF0C}. The connection may have been corrupted. End Error Error: 2014-04-03 11:03:49.00 Code: 0xC0047017 Source: Data Flow Task SSIS.Pipeline Description: component "ADO NET Destination" (104) failed validation and returned error code 0xC0208452. End Error Error: 2014-04-03 11:03:49.00 Code: 0xC004700C Source: Data Flow Task SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2014-04-03 11:03:49.00 Code: 0xC0024107 Source: Data Flow Task Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:03:31 AM Finished: 11:03:49 AM Elapsed: 17.472 seconds. The package execution failed. The step failed.
Can anyone help me out on this issue. Thanks in advance.
April 3, 2014 at 10:00 am
Looks like the protection level is set to "encrypt with user key", if moved to another scope, it will fail.
😎
April 3, 2014 at 11:33 am
Thanks for your reply.I have changed it to DontSaveSensitive. Still the same error persists. Please let me know if I need to change anything else.
April 3, 2014 at 11:36 am
I changed the Protection level and when I run the job. It gives me the below error.
Execute Package Utility Version 10.0.2531.0 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Argument "Excel" for option "connection" is not valid. The command line parameters are invalid. The step failed.
April 3, 2014 at 12:20 pm
If I remember correctly, you should re-configure the connections which before the protection level changes, where using the users credentials.
If you are using a SSIS configuration settings, walk through the settings to make certain it is refreshed.
Some more information on protection/dtsexec
and here
😎
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply