AS ABAP Initial Load fails

[Former Member]

Hi,

We are using IDM 7.0 on SQL 2005. We have connected 2 ABAP systems to the IDM system. Intial Load for System 1 completed successfully. For the second ABAP system, Intial loads fails at 2 passes.

Pass: WriteABAPUsersRolePrivilegeAssigments

Error message:

putNextEntry failed storingADS_AGENT

Exception from Modify operation:com.sap.idm.ic.ToPassException: ToIDStore.modEntry failed modifying entry 'ADS_AGENT'. IDStore returned error message: " User is not allowed to run task:Attribute: MXREF_MX_PRIVILEGE" when storing attribute 'MXREF_MX_PRIVILEGE={ValidFrom=2008-07-29!!ValidTo=9999-12-31}<PRIV:ROLE:FBC010:SAP_BC_FP_ICF>'

Pass: WriteABAPUsersProfilePrivilegeAssigments

Error message:

putNextEntry failed storingALEREMOTE

Exception from Modify operation:com.sap.idm.ic.ToPassException: ToIDStore.modEntry failed modifying entry 'ALEREMOTE'. IDStore returned error message: " User is not allowed to run task:Attribute: MXREF_MX_PRIVILEGE" when storing attribute 'MXREF_MX_PRIVILEGE=<PRIV:PROFILE:FBC010:S_BI-WX_RFC>'

This passes failed for all users. I checked the access of the communication user in the backend and has SAP_ALL. Trace did not show any errors.

I am not sure what is missing?

Looking for some assistance.

Regards

Ramkumar

[Former Member · Accepted solution]

Hello

Compare the two repositories of the systems.

Do they point to the same Provision-Task?

[Former Member · Accepted solution]

Hello Christian,

I did compare both the repositories and both of them point to the same Provisioning task.

Regards

Ramkumar

[Former Member · Accepted solution]

Hi Ramkumar!

Since the errors occur during the InitialLoad I don't think it has something to do with the Provisioning Tasks; especially if you have disabled provisioning during the Initial Load (as proposed in the guides).

It also has nothing to do with your backend-permissions (in your case SAP_ALL) because the Read-Passes were all successful.

The strange thing is that it succeeds for System1...

Some of my thoughts:

Can you please double check that the WriteABAPUsersxxxAssignments-Passes / Destination-Tab are identical in both InitialLoad-Jobs - maybe the reference to the IdentityStore (should be global constant) got lost for the second system?!

What happens if you change the read-order, meaning you first read System2 and afterwards System1? Same errors? Remember to clean the ID-Store before testing again...

What exact version of IdM 7.0 do you use?

Are you using SQLExpress?

Regards

Michael

[Former Member · Accepted solution]

Michael,

Thank You. I ran the provisioning job for the first system and forgot to uncheck the "Run Provisioning jobs" option for the Initial load of the second system. Intial loads ran successfully after I disabled the option.

Regards

Ramkumar