DSXchange

Each instance is logged separately, at least logically (the entries are all in the same table, but each is inspected through its own "view"). You open each instance's log in Director.

Ray,

I can't see the log of the instance that gave mistake, it doesn't appear in the director.
See the log of the sequence. When the job multiple instance is called it begins and it concludes with the status = 99, this provokes the abort of the sequence.

Item #: 4
Event ID: 1011
Timestamp: 2009-03-06 10:30:29
Type: Info
User Name: SERVER85|isadmin
Message Id: IIS-DSTAGE-RUN-I-0019
Message: SeqChamaRTExecJob.SeqDocSiatcProposta.JobControl (DSWaitForJob): Waiting for job SeqDocSiatcProposta to finish

Item #: 5
Event ID: 1012
Timestamp: 2009-03-06 10:30:29
Type: Info
User Name: SERVER85|isadmin
Message Id: IIS-DSTAGE-RUN-I-0019
Message: SeqChamaRTExecJob.SeqDocSiatcProposta.JobControl (DSWaitForJob): Job SeqDocSiatcProposta has finished, status = 99 (Not running)

Where's your InvocationID? It looks to me like you're running your MI job in a non-MI mode as I would think it would say "Waiting for job SeqDocSiatcProposta.??? to finish" otherwise.

Do an exact search on "status = 99 (Not running)". This seems to be a bug related to auto-purge and multi-instance for version 8x.

Mike

Check that you are supplying the invocation ID correctly. There does not appear to be an invocation ID in these messages.

Mike,

I saw that post, but don't solve the problem. I think this is another problem.

Thanks

We think so, too.

Forgive me, in fact, the job that is multiple instance is the sequence and not the job server.

After accomplishing more tests, I noticed that what really happens is the following:

I have two sequences, and the sequence father is not multiple instance, but the son is.
The sequence son, is invoked inside several times of the sequence father.

Usually, the mistake happens when the sequence son is invoked simultaneously at once, in other words, the fact of invoking the multiple instance sequence simultaneously several times is provoking the mistake.
I know this because I change the job father, placing the calls for the sequence son in sequence and the error ended.

But this doesn't solve the problem because sometimes I need to execut in parallel and not in sequence.

Do you have your auto-purge enabled? That has caused some issues for me in the past when multi-instance log details have disappeared on me.

I tured off the auto-purge, however the error persisted.

You do understand that, for any multi-instance job to work "in parallel" that each invocation id must be unique amongst any running invocations, yes?

Yes, for each instance a different id is passed.
The ID is passed though a different parameter for each instance.

Yes, for each instance a different id is passed.
The ID is passed though a different parameter for each instance.

Please verify that this is, in fact, truly happening. The log messages you've posted so far seem to indicate otherwise.

You are correct.

But as I said this morning, the problem is with the sequence (SeqChamaRTExecJob.SeqDocSiatcProposta) and not with the job server (SeqDocSiatcProposta).
The log I posted is the job sequence. The job of multiple instances is the job sequence and it is having problems.