To Identity store doesn't work!!!

[jaisuryan]

Hi Experts,

We have recently patched our Dev environment to 7.2 SP 9 Patch 5. Our dispatcher is in version MxDispatcher v7.2.9.4

Since then, our jobs are always in running state but doesn't modify any data in our IDS. The dispatcher executed all the passes in the job but when it comes to execute "To Identity Store", it doesn't perform any action and remains in that state for days (I started the job on Friday evening, it was in same status till today morning but no user modified). Further to test the issue, I created a job with "to generic" pass to execute a script that calls uIS_SetValue to update attributes for only one user and it behaved in the same way. The job was in running status and doesn't do anything.

In execution log, the last entry was like "Execution of pass started:". no other logs anywhere and no user modified.

I created a job with different types of passes and tested. The dispatcher executed all the passes. Is it a known issue? please advise. Yet to create an Incident to SAP. The same jobs were running fine before patching.

Anything else to test to conclude anything or any screenshots needed, please let me know. Thanks in advance.

Kind regards,

Jaisuryan

[former_member2987 · Accepted solution]

Hi Jaisuryan,

First things first, the final step of any upgrade should be to regenerate your dispatchers.  However before doing that, did you update your DESIGNTIME and RUNTIME components or just the DESIGNTIME?

Thanks,

Matt

[jaisuryan · Accepted solution]

Hi Matt,

Yes, we patched DESIGNTIME, RUNTIME, VDS and portal. Patching was done by server team and I did not know if they regenerated the dispatcher scripts. However, today morning my colleague re-created the dispatcher again and still the same result.

Kind regards,

Jaisuryan

[former_member2987 · Accepted solution]

Please post your connection strings and a screenshot of your IDM setup (click on the top most IDM node, the one below "Standalone Jobs")

Thanks

[jaisuryan · Accepted solution]

Hi Matt,

Please find the requested details below.

The connection string is as below, prefix is removed,

jdbc:sqlserver://localhost\<prefix>:1433;databasename=<prefix>_db;user=<prefix>_rt;password=******

Connection test successful as well.

If any of the above is wrong, we wouldn't have any dispatcher running and couldn't be executing even test jobs. The problem is only "to Identity store" pass and scripts with Identity center user functions are not getting executed.

Kind regards,

Jaisuryan

[former_member2987 · Accepted solution]

Hi there, yes, I expected it to be clean, but I wanted to make sure.  Do you get an error or is it that nothing happens?

Matt

[Steffi_Warnecke]

Hello Jaisuryan,

if you change a user via the UI, are the changes saved to the IC and the dispatchers working for this? You only wrote about jobs, so I just want to make sure, if this also includes tasks.

Also since it seems to at least start the execution of the pass (you wrote, that shows in the log), can you please check via a trace on a user if that gives you more information where it stops exactly (and maybe even why).

I'm not sure if writing to the IC falls under "provisioning" () and therefor is written into the tables for that, but if yes, you could check via the following statement through the SQL developer if the job is just waiting for some other task to finish first:

select * from mxp_provision where msg like 'Wait for%'

Regards,

Steffi.

[jaisuryan]

Hi Steffi,

Thanks for your efforts. our system is back to normal after we patched runtime to SP 9 patch 5 yesterday.

BR, Jaisuryan

[Steffi_Warnecke]

Oh, okay.

But I thought the problems started after you upgraded all components to SP9, patch 5? Did you deployed the patch again or wasn't the runtime upgraded afterall? That would be good to know, if others have the same issue.

But I'm glad, your system is working again like it should!

Regards,

Steffi.

[jaisuryan]

Hi Steffi,

Sorry, I was wrong earlier, it was not patch 5. We had patched to SP9 patch 7, which had below component versions, from SP9 patch 1.

Designtime - 7.2.9.7

Runtime - 7.2.9.4

Since then we had problems with jobs and even our UI tasks were getting timed out. The system became unusable.

Today our team patched the runtime to 7.2.9.5 and everything resolved.

Kind regards,
Jaisuryan

[Steffi_Warnecke]

Ah, thank you for clearing that up! Those patch levels... boy oh boy. *sigh*

Regards,

Steffi.

[former_member2987]

I suspected something like that.  Glad things are working well!

Matt

[jaisuryan]

IDM SP9 Patch 7 had only runtime patch 4. It was just yesterday SAP had released runtime patch 5. So confusing how SAP has decided to name the patches. They said to apply SP9 patch 7 which had designtime patch 7 and runtime still in patch 4.

Many thanks,

Jai

[Steffi_Warnecke]

Hello Jaisuryan,

screenshots of the "Options"- and "Policy"-tabs of the dispatcher would be good.

Regards,

Steffi.

PS: Please don't use exclamation marks in the title. I know it's frustrating and urgent for you, but this always feels like the author is shouting at me.

[jaisuryan]

Hi Steffi,

My apologies for the exclamation

Please find the options and policy tab screenshots below,

I have tried following in our environment:

1. 1)      To run test job with many types of passes: Executes correctly
2. 2)      To run test job with ‘to Identity Store’ pass: Doesn’t execute, hung in running status
3. 3)      To run test job with ‘to generic’ pass to call uIS_SetValue function: Doesn’t execute, hung in running status
4. 4)      To test a provisioning task with ‘to identity store’ pass: Doesn’t execute, hung in running status
5. 5)      To test a provisioning task with ‘to generic’ to call uIS_SetValue function: Doesn’t execute, hung in running status
6. 6)      To test a provisioning task with ‘to generic’ or other types of passes: Executes correctly

Kind regards,

Jaisuryan