Job Fails on one SSIS Package - Password is not correct

Question

Post reply

Job Fails on one SSIS Package - Password is not correct

Welsh Corgi

SSC Guru

Points: 116520
More actions
March 26, 2012 at 12:44 pm

#255391

When I run a package as a Job I get the following error:
Password for user XYZ989 on system AS400.CORP.MYDOMAIN.COM is not correct
It works finne in BIDS and I just dfeployed it this afternoon
Any thoughts or ideas?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 1

Need details on how you deployed the package, specifically what type of security you used.

Looks like the password was not saved with the package.

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 2

I did not save sensitive Data.

There are 4 packages in the Job.

I deleted the deployment folder, tested the connection with the password, etc. Job still fails.

I'm running it from BIDS on the Server then deploing it using a Deployment Manifest.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 3

I did not save sensitive Data.

This means the package does not have the password to connect. Are you passing this in via a package configuration?

sqlserver8650 Ten Centuries Points: 1121 More actions · Answer 4

Hi,

Click the check box(Save password) in connection managers of corrsponding connection

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 5

Lynn Pettis (3/26/2012)
I did not save sensitive Data.
This means the package does not have the password to connect. Are you passing this in via a package configuration?

Just got out of a metting.

I saved it in MSDB.

I still don't know the basic syntax to execute the package using DTExec.

I Googled it, read several articles but could not find what I needed.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 6

sqlserver8650 (3/26/2012)
Hi,
Click the check box(Save password) in connection managers of corrsponding connection

That's odd, I wonder why it saved the PW for the other 3 packages in the job.

I will try it.

Thanks.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 7

sqlserver8650 (3/26/2012)
Hi,
Click the check box(Save password) in connection managers of corrsponding connection

I did not see a check box (Save password).

I checked alllow saving password, redeployed and the job failed.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/