Job fails to deploy from Package

danddmrs · Post by **danddmrs** » Thu Jan 15, 2015 11:02 am

When deploying a package with multiple jobs one of the jobs fails every time. To get around this the job was moved in a dsx.

The message from the compile listing is:
Failed: Unexpected error importing design. See the log in the Web Console for more details.

What Web Console has the log? Nothing was found in ISS or ISM.

This is the second time this has happened using packages to promote code. Previously there were problems with a Server job and a Parallel job, both of which were moved using a dsx (a separate package containing just these jobs also failed).

DS Admin is opening a ticket with IBM but thought I'd ask the guru's too!

PaulVL · Post by **PaulVL** » Thu Jan 15, 2015 11:31 am

Hard to guess from way out here...

Your admins could try the cleanup_abadoned_locks.sh script, or reindex the project.

Does any error pop up when trying to log in to director for that job folder?

your admin could rename the job in that project and you could try to reimport (thus it would obtain job id).

danddmrs · Post by **danddmrs** » Thu Jan 15, 2015 11:38 am

Thanks for the reply.

The deployment fails in all environments for the same jobs but I'll ask the Admin about the script and re-indexing. Also wouldn't the dsx import also fail if there was a lock on the job?

No errors pop up when accessing to logs.

PaulVL · Post by **PaulVL** » Thu Jan 15, 2015 1:40 pm

The "all environment fails" is new info. That helps rule out a corrupted target system.

is recompiling the offending code and rebuilding the package an option?

danddmrs · Post by **danddmrs** » Thu Jan 15, 2015 1:48 pm

We've tried that several times. For a workaround we use a dsx for those jobs that fail in the Package. The export of the single job to a dsx took several minutes, like more than 5. Perhaps there is a timeout limit with a package element that causes the failure? Just a thought.