April 17, 2014 at 2:29 am
hi
i have an ssis job, which runs various calculations, creates a .txt file and then uploads to an FTP site.
when i run it in bids it works fine, but when i schedule to run using sql agent, it fails with the below error..
"An error occurred in the requested FTP operation. Detailed error description: The password was not allowed"
how should i be saving my FTP password?
thanks
mal
April 17, 2014 at 3:02 am
dopydb (4/17/2014)
hii have an ssis job, which runs various calculations, creates a .txt file and then uploads to an FTP site.
when i run it in bids it works fine, but when i schedule to run using sql agent, it fails with the below error..
"An error occurred in the requested FTP operation. Detailed error description: The password was not allowed"
how should i be saving my FTP password?
Try using configurations:
Understanding Integration Services Package Configurations
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 17, 2014 at 3:04 am
do i need to change protection level - should it be "encrypt sensitive with password?"
i can only run the app out of hours hence why i cant test now
April 17, 2014 at 3:15 am
not sure what configurations will do for me Koen?
April 17, 2014 at 3:18 am
dopydb (4/17/2014)
do i need to change protection level - should it be "encrypt sensitive with password?"i can only run the app out of hours hence why i cant test now
That is an option as well.
I guess your current protection level is EncryptSensitiveWithUserKey. When run with SQL Agent, another user is used so the password is lost.
Personally I prefer configurations (XML or SQL Server), but changing the protection level should work as well.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
April 17, 2014 at 5:18 am
i logged in on the same account that the sql agent service runs under, changed security of the package to
"encrypt sensitive with userkey"
sis package now runs fine!
April 17, 2014 at 5:21 am
dopydb (4/17/2014)
i logged in on the same account that the sql agent service runs under, changed security of the package to"encrypt sensitive with userkey"
sis package now runs fine!
You should really avoid using EncryptSensitiveWithUserKey. If another developer opens the package and saves it, you'll be having the same issues again.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply