Not able to modify Dispatchers

[former_member190695]

Hi All,

I am having an issue with a new installation of SAP IdM 7.2 SP09 DT.

I am able to perform almost every activity in IdM ecxept when I try to create a new dispatcher.

The dispatcher will be created but nothing will be filled-in and I am not able to change anything.

Error:

Overflow

Method: EmcDispatcher.ShowDispatcher

Error: 6h

Description: Overflow

Anyone an idea?

Thanks very much.

Regards,

Ridouan

[terovirta · Accepted solution]

What happens if you refresh the dispatchers leaf in MMC? Can you delete the dispatcher? Or did you try to delete and recreate already?

(I manage to get the same "invalid property array index" time to time when configuring new workflow tasks.. I guess somehow the task is not really saved and then editing the properties fail.)

regards, Tero

[former_member190695 · Accepted solution]

Hi Tero,

I am getting the error message when trying to add a dispatcher as well.

I can remove the dispatcher but I am not able to save it.

Regards,

Ridouan

[Former Member · Accepted solution]

Can you verify that the version of the management console and db schema are in sync? Things like this can happen if you use an old MMC with a new version of the DB where the schema might have changed slightly.

Br,

Chris

[former_member190695 · Accepted solution]

Hi Per,

Latest schema update is 1129.

I admit it's not a new server so a previous release of SAP IdM DT was installed.

I have removed old MMC, restarted the server and installed the new version.

I can browse and create attributes but just not able to generate dispatcher scripts,modify dispatcher properties.

All dropdownlist for example Log Level are not set by default.

This is the error message when I try to set it: Invalid property array index.

Method: EmcDispatcher.SaveChanges

Error: 17Dh

Is a table/view missing?

Regards,

Ridouan

[former_member2987 · Accepted solution]

Ridouan,

I'd recommend the following to remove all doubt:

1. Stop all dispatchers and event agents
2. Uninstall the dispatcher / event agent services via MMC (VERY IMPORTANT)
3. Uninstall the Designtime and Runtime from the system.
4. Re-install the Designtime
5. Run the MXMC_UPDATE script (unless of course you have a custom name)
6. Re-install the Runtime
7. Regenerate your dispatchers and event agents
8. Install dispatcher / event agent services
9. Optional: Run Dispatcher in Test Mode
10. Start Dispatcher service

Of course some of this might be slightly different if you are working in a *NIX environment.  In this case also make sure all permissions are properly set.

Good luck!

Matt

[former_member190695 · Accepted solution]

Thanks Matt.

I have already tried many of you suggestions.

The problem I am facing is that I have never been able to create any dispatchers because when I select 'Create Dispatcher Scripts' MMC crashes with the following message: Run-time error '381' Invalid property array index.

The same server was used before to install IdM 7.1 and 7.2 SP0.

Regards,

Ridouan

[Former Member · Accepted solution]

If all else fails, download debugview from Microsoft. It will trace the communication between MMC and the database and could provide hints for us or the support team about what is going wrong.

Br,

Chris

[former_member190695]

Thanks very much  Guy's. My issue was related to OLE DB Provider.

[Former Member]

Hello Ridouan,

can you please let me know what was the solution for this issue, i am also getting the same error.

i have installed oracle provided OLE DB

[former_member190695]

Hi Prashanth,

I was using Microsoft OLE DB Provider instead of Oracle Provider OLE DB.

I was using Oracle as Database.

Regards,

Ridouan

[Former Member]

Hello Ridouan,

we are using the Oracle Provider OLE DB itself, we have raised the OSS message for the support.

In our case issue is the time difference, here is the reply from SAP.

====================

The problem seems that currently the system where you have Identity Center installed and the system where you have Oracle database installed, have time difference bigger than 10 hours.

===================

After changing the timezones issue solved.

Regards,

Prashanth