Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS from 64 bit to a 32 bit machine, error on key not valid Expand / Collapse
Author
Message
Posted Monday, January 21, 2013 1:28 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 1:32 PM
Points: 29, Visits: 119
From a SQL Server agent job I execute the following:

"C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTExec.exe" /FILE "D:\Nickname2\Nickname2\Nickname2.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E

But I get the following error:

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: 2013-01-21 14:30:29.00 Code: 0xC0202009 Source: Nickname2 Connection manager "CPICFED.db2admin" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "IBM OLE DB Provider for DB2" Hresult: 0x80040E4D Description: " SQL30082N Attempt to establish connection failed with security reason "3" ("PASSWORD MISSING"). SQLSTATE=08001 ". End Error Error: 20... Process Exit Code 1. The step failed.


I change, or update the password, still error, very fustrated.

Pablo
Post #1409695
Posted Tuesday, January 22, 2013 9:15 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Thursday, October 16, 2014 6:18 PM
Points: 3,952, Visits: 7,170
Have you tried to set the "Use 32-bit runtime" under the job step's Execution Options?

______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1410328
Posted Wednesday, January 23, 2013 7:18 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, April 24, 2014 9:12 AM
Points: 285, Visits: 504
Who's the owner of the package vs. the account that's running it? dtsx packages will ask for saved credentials if the person running it is different from the owner. You can try encrypting the package with a password and then provide the password at runtime. (Either EncryptSensitiveWithPassword or EncryptAllWithPassword). If you encrypt with user key you can setup a configuration file/table and store the password there.
I don't remember for sure but unless you encrypt the package when you save it it doesn't save the connection password. It's been a while since I worked with SSIS and DB2 but that's what I seem to remember. I used to have all kinds of weird situations with DB2 connections.


---------------------------------------------------------------
Mike Hahn - Future MCM 2025
Right way to ask for help!!
http://www.sqlservercentral.com/articles/Best+Practices/61537/
I post so I can see my avatar
I want a personal webpage
I want to win the lotto
I want a gf like Tiffa
Post #1410565
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse