November 12, 2007 at 2:37 pm
Why is it so hard to even schedule a package to run in SSIS. I thought I was done with the most difficult package that I have ever made in my life but now when everything is done, I am having trouble scheduling it. Can someone show me step by step how to 1. schedule this package which has the following error:
Code: 0xC0016016
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 have tried everything including the protection levels and all that. PLEASE HELP ME!!!
Basically I am bringing in something from FTP to flat files and then to SQL destination. That's all. please make this easy for me!
[font="TimesNewRoman"] “I haven't failed, I've found 10,000 ways that don't work”........Thomas Alva Edison[/font]
November 16, 2007 at 7:01 am
-Make sure you can execute the package from Visual studio (I'm sure you have)
-Make sure the account you're using to schedule the job has permissions on the folders etc the job is accessing
Here's what I would.
Create a REALLY simple SSIS package, maybe one that does nothing, move it to SQL server and see if you can execute it.
take it from there!
November 16, 2007 at 8:52 am
Actually mine is very complicated than that. But thanks though. I have tried your way, it worked. But I am doing a FTP download to Flatfile. There is a UID and password matter there. Then from my box, I am accessing the server. There is another different set of UID and password there. Then I have to send the package to QA server which is somewhere else. Now, thats a catch! There are two different connection managers and I don't understand why it is failing to work in the QA server. It works fine in my box and the server that I am attached to. I have even tried package config. Anybody out there? Hello SQL master?
[font="TimesNewRoman"] “I haven't failed, I've found 10,000 ways that don't work”........Thomas Alva Edison[/font]
November 16, 2007 at 9:09 am
which user is being used to execute the JOB?
STEPS->Run as:
November 16, 2007 at 11:11 am
SQL Server service account. Well, How do I bring the total package over in to the QA server though? It is still failing. I tried package config. But when this happens, my package where it is already been is failing with the error all the connection manager is lost. Then when I delete the package config, the my package runs back okay. This is in the server that I have created it itself.
[font="TimesNewRoman"] “I haven't failed, I've found 10,000 ways that don't work”........Thomas Alva Edison[/font]
November 19, 2007 at 2:36 am
sorry i don't get your question...
however, does the service account have access to the folders/ftp your trying to aceess?
does anyone else have any advice on this?
November 19, 2007 at 1:42 pm
Did you encrypt your package with a password? In the package properties set the ProtectionLevel to EncryptAllWithPassword and specify the package password. When deploying on the server when uploading the package set the very last entry to relay on the server for package password. This should help.
Thanks,
Manisha
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy