ISD jobs are not running

BuddingDev · Post by **BuddingDev** » Thu Feb 09, 2012 1:00 pm

Hello,
I have four ISD jobs in one quality stage project. After compiling each one of them using designer. I deployed this project using Information Server console. I see only two jobs turned to RUNNING status right after deployment but two of them stays in COMPILED status in director. When the request was sent to standardize, source system are not getting failed error at their side.

These same jobs are successfully running in other environments. I tried exporting same jobs from those environment, complied them and deployed the project. But still two of them are in Compiled status.

PaulVL · Post by **PaulVL** » Thu Feb 09, 2012 4:24 pm

Are those "Multi Instance" jobs?

The base job in a Multi Instance job would show up like that, but the invocation of an instance would be a different entry in director.

BuddingDev · Post by **BuddingDev** » Fri Feb 10, 2012 6:42 am

Yes, all of them are Multi instance jobs. But I don't see any instances being created for these two specific jobs.
Rest of the two successful jobs have their own instances created which are in RUNNING mode.

qt_ky · Post by **qt_ky** » Fri Feb 10, 2012 11:16 am

In ISD if you create a new operation and navigate to the server / project / folder containing the jobs in question, do you see the 2 jobs listed and are you able to add each of them, one at a time?

When you deploy in ISD do you see any status bar at the bottom that you can expand or click to get details and see an error message?

You can also search the SystemOut.log and SystemErr.log WAS log files on the server.

eostic · Post by **eostic** » Sat Feb 11, 2012 9:36 am

This assumes that these two Jobs are indeed designed to be "always on".....not every ISD enabled Job will be "running".....if it begins with an ISDInput Stage, then yes, it should end up running.

...check again the deployments and the log, as suggested by other posters.

...what is odd is that it isn't aborting (a common symptom when there are environment issues in the job, such as wrong filenames, conflicts with other jobs, or credential issues)...the job will start/abort/start/abort, etc.

Ernie

BuddingDev · Post by **BuddingDev** » Fri Feb 17, 2012 2:35 pm

I found the solution for this.
One of the job got corrupted. So I had to delete it entirely and bring a fresh copy form other environment.

One job was just pointing to a wrong job name in QS. So I made the change and thankfully all of them are in RUNNING status now.

Thank you all for your attention and suggestions!