June 12, 2008 at 4:17 am
Hey,
Hoping someone can assist with this one, as I am not so clued with when migrating a component sample to another environment.
I am using the remove duplicates component sample in one of my packages, and after migrating this to our preprod environment, the following error is thrown by the agent:
"... 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 ..."
I assumed it had to do with the remove duplicates component sample which is part of the package, so I went on site with the server administrator, and attempted to troubleshoot. What we did manage to do is copy the dll to the pipeline components, whereafter we added this to the global assembly cache. Still the error appeared...
I made the assumption that the keypair could not be found, so we tried to install the component sample from the beginning.
1) We generated the required keypair sn -k Sample.snk. No probs
2) When we want to open the .sln on the server in order to build the project, the following error is thrown:
"...Removeduplicates.vbproj is not installed"
We dont have the full MS Visual Studio installed on the server, just the SDK and BIDS.
A couple of questions on this one:
a) Can we not just copy the dll to the server and add this to the GAC? Do we really have to generate a new key, and even if so, would the key not suffice for the dll?
b) If we HAVE to generate the component sample server side and rebuild, what software are we missing in order to do this?
No ideas on this one
~PD
June 12, 2008 at 7:21 am
You are looking at a warning about the decryption of passwords in a package that has it's package security set to excrypt sensitive with user key. This is the default and it means that all passwords in the package will be encrypted with the user key of the NT user that created the package. Unless you are using SQL Authentication for your connections and are not using SSIS Package Configurations to set the passwords, this will be a problem. Otherwise it is just a warning. The only thing it could indicate is a problem connecting to data sources and has nothing to do with your .dll.
You need to turn on package logging to get to the actual error message. It is probably much further down in the messages.
As for your questions. You can just copy the .dll to the server and add it to the GAC. You MUST put the .dll into the .Net framework folder - it cannot simply go anywhere regardless of registering it in the GAC.
You do not have to generate a new key pair.
June 12, 2008 at 7:28 am
:blush:
oiiiii
I was so sure I had dont save sensitive selected. You dont want to know how much time I wasted looking at a problem where the problem was with the encryption of a user key.
Thanks Michael, it solved my problem.
~PD
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply