cancel
Showing results for 
Search instead for 
Did you mean: 

MX dispatcher exception

Former Member
0 Kudos

Hi,

we are running idm 7.2 sp5 and i am facing trouble in debugging. I have a system log that repeats itself but i can't figure out wich task is sending  it.

I tried mxp_audit table, mc_syslog, mcmv_tasks..

The error message i have is

MxDispatcher - SWITCH      - Exception: sendSelectResult: invalid parameter value, strRes=-999:Invalid query - multiple entries returned

I tried to go into every procedure used in my switch task but didn't find anywhere where this message could be sent from.

I queried mc_syslog and had the attached result. As you can see, no jobid is given which makes it difficult to debug. Any idea how to retrieve it? it came to a point where i can barely query this table and when i click on System logs it goes into timeout so it's kind of critical.

Thanks a lot for your help,

Clotilde

Accepted Solutions (0)

Answers (4)

Answers (4)

former_member2987
Active Contributor
0 Kudos

Does this happen on all dispatchers or just one?  Also have you checked that the housekeeping options for the dispatchers are turned on?

Matt

Former Member
0 Kudos

Hi,

@Chris : I didn't try it yet, but from what i recall from yesterday i haven't been able to figure out which user was affected by this error.

@Thomas : That is what i intend to do as soon as i fix my first problem which is figuring out which task goes into error. As you can see on the logs i posted, there is no jobid linked to this log, do you know a way to find out which one it is?

Best Regards,

Clotilde

thomas_groth2
Explorer
0 Kudos

What i mean is that maybe the problem is the switch task itself. What select statement does it have under "options --> sql query" ?

thomas_groth2
Explorer
0 Kudos

Hello,

i would start analysing the select inside the switch task. Maybe it returns more than one result in a certain situation. I had a likewise problem myself.

Best regards,

Thomas

Former Member
0 Kudos

You may want to try tracing this problem.  To do this, go to the admin UI - ~ /idm/admin and go to the Trace tab.  Here you will be able to trace the actions performed on the user.  This might show you where the problem might be.