Status is not OK during IDS Update

[former_member2987]

Hi experts!

Just wondering if anyone has seen this error before. It's occuring during an AD reconciliation process. I've changed the timeout to 600 and cleared the provisioning queue using the SP, but still having trouble.

Messages Warning Status is not OK. Not legal to mark running in this state (2)

Warning MC told us to stop. Status:2 - STOPPING!

Warning Pass stopped by script

Any advice would be appreciated.

Thanks,

Matt

[former_member2987]

Use the Bootstrap job option to increase timeout.

[Former Member]

Hi Matt

We see the same error every now and then, but have found no explanation for it. We do not only see it when running AD jobs though. All we have been able to deduct from it is, that for some reason the MMC detects that something is not right and therefor orders the job to stop.

We have noticed though, that when our system is a bit stressed by a large number of provisionings, it occurs more often.

Kind regards

Heidi Kronvold

[former_member2987]

Heidi,

Same thing here. We found there was a mislinked task being called that did not have a dispatcher (it was the original copy of the framework task) Not sure how it happened, but we relinked to the proper task and all is working now.

Thanks!