IDM Provisioning task is stuck

[Former Member]

Hi All,

I have mapped "AD Create user" task in Add event of MX_PERSON. I have written a Job to read from csv and write to IDStore. When I run this job this in turn should trigger "AD Create user" task. My load user Job is running without error but provisioning task is not at all getting triggered. I have checked that dispatcher is working fine and able to execute other jobs successfully.

Is there any way I can check why my provisioning taks are getting stuck?

regards,

Dhiman Paul.

[terovirta · Accepted solution]

I don't think it's a good idea to attach the plugin call to create user event task, rather add the account privilege in that event task and let the provisioning framework do the processing (even it's a lot slower with the dozens of tasks from Provisioning workflow in the queue to be exectuted).

If you decide to continue by calling the plugin directly, check what Dominik already suggested and make also sure that you have the repository selected/hard-coded in the plugin tasks as with direct call the plugin does not inherit the repository from privilege assignment/PVO. The call will fail as the pass refers repository constants.

[Former Member]

Hi Tero and Domink,

Thanks for your suggestions. My problem was related to dispatcher and prov queue. I have created a new dispatcher and made those prov run again. I know this is an work arround, I have to look into more deep. But for time beeing my development can go on.

Thanks again to both of you.

Regards,

Dhiman Paul.

[Former Member]

Hi Dominik,

There lot tasks stuck in the mxp_provision table. few are showing temporary failure.

Can you tell me how I can clear the provisioning queue, so that new prov task can run?

Regards,

Dhiman Paul.

[Former Member]

There is always the possibility to run a query in the SQL studio / developer which deletes the erroneous / unwhished entries from that table: delete from mxp_provision where ...

However, I guess this doesn't solve the problem itself (in most cases). If tasks get stuck there is some deeper problem if suggestions won't work.

If you call the task directly, the AD repository has to be set somewhere in the task chain.

Have you tried out the "normal" way of provisioning like Tero Virta suggested?

[Former Member]

Hi All,

Anyone has any thought ....

Regards,

Dhiman Paul.

[Former Member]

Hello Dhiman Paul,

have you already checked the mxp_provision table / mxpv_provision view?

Some other things I would check:

• Job writes to the correct Identity Store
• The first Job has the flag "Test mode" disabled
• All tasks are enabled
• Job of the task is enabled and has a dispatcher activated

Best regards

Dominik