August 22, 2014 at 8:29 am
Hello
Could someone offer some advice on how to adapt to the following...
I receive a .dtsx and
I import by connecting to Integration servics through SSIS
I import the package into File System
When I right click and select "Run Package" it fails.
I will provide the errors but what I am wondering - is there a checklist for things to check when you get an SSIS package that was developed on another instance so I can troubleshoot how to get them to work on another server? I feel like I'm shooting in the dark.
Error 1 Error loading Adult_Care_MainFeed.dtsx: 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. D:\SQLDBA\SSIS\Adult_Care_MainFeed.dtsx 1 1
The ProtectionLevel was set to "EncryptSensetiveWithUserKey" I changed it to "DontSaveSensetive" -
Error: SSIS Error Code DTS_E_OLEDBERROR; An OLE DB error has occured. Error code: 0x80040E4D. An OLE DB record is available. Source "Microsoft SQL Server Native Client 10.0" Hresult 0x80040E 4D Description; 'Login failed for user 'childcaresnp_user"
I checked the connection string...
Provider=SQLNCLI10.1;
Persist Security Info=True;
Application Name=SSIS-Package-{82EF2964-C447-4417-906E-9D06469AA696}Auto Translate=False;
I'm using SQL Server 2008 R2 SP2.
In ODBC I verified that SQL Server Native Client 10.0 is listed as a driver.
Thanks in advance for any help
Dave
August 22, 2014 at 8:34 am
Quick thought, two options, the developer should change the security setting to "Do not save sensitive..." or the second option, open the package in a text editor and remove the design time values in question.
😎
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply