Sssssylw
Sssssylw

Reputation: 11

SSIS package runs well when executed manually, but fails when executed as a Job

As the title says - if I execute the package manually in SSIS it works perfectly, but if it runs as a Job it fails.

Package contains few simple blocks (creating new folder, moving file from one folder to another) and for each loop container. In this container there is a script, which pastes formulas, sorts tables, deletes rows etc. in Excel files.

It is possible that those Excel files do not close properly, but I don't think that this is the case here.

For about 80 excel files, job opens only a half of them (most times, sometimes more sometimes less) and then stops. There are really a lot of jobs on this server and its the first issue like that. Whats the problem?

Upvotes: 0

Views: 1000

Answers (1)

user3224658
user3224658

Reputation: 11

The same problem , we have faced:

Here , what we have done:
Say Package "ABC" has stopped executing in job scheduler.

  1. We have created a new blank SSIS package.
  2. Copy N Pasted all the task and connections from old one.
  3. Rename the new SSIS as "ABC" after taking backup of old "ABC"

and problem was solved.

Some problems, needs non-logic solutions and this is one of them. ;-)

Upvotes: 0

Related Questions