Changed SSIS now won't run in a job

  • I had a SSIS package running fine for months through a SQL Agent job. Then ... I deleted a task and re-saved to MSDB now the job just hangs and never finishes. I can run the actual package and all runs fine, I can execute the package in SSMS - using the Integration Services connection and it runs fine. I did not change anything in the job itself. Can someone give me some suggestions on how to trouble shoot this? I'm pretty much a beginner and any help would be appreciated!! TIA!

  • Are there any saved / protected login credentials in the package? The protectionLevel might be set to EncryptSensitiveWithUserKey, which is why it works for you and not the SQL Agent account.

    Add some logging to the package and check where it's hanging. Or run a SQL trace and check what's happening during the agent execution.

  • Ahh … password!

    I initially had a password on the package, however when I made changes to the package I changed the security setting to ServerStorage and saved it to MSDB. The job then stopped working. After your posting I have now gone back and resaved the package with EncryptAllWithPassword and entered the old password but it still will not run through a job (runs fine in bids).

Viewing 3 posts - 1 through 2 (of 2 total)

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