Error in RFC: Name of password is incorrect

[Former Member]

Hi All,

I am using GRC AC 10.1 with SP06 and came across with one issue and so need your help to rectify it.

I have created one cross system groups for all deveopement clients (SAP_DEV_CG) and put all the D-clients for all the landscapes.

While running the risk violations reports on user level, i get to see the violations along with an error: "Risk analysis finished with error. Check log for details". SLG1 reports indicates that there is some issue with the RFC: Name or password is incorrect.

The error is quite clear and self explanatory that there is some issue with the RFC; but my concern is that, as I  have put multiple development clients to this group so how would i know for sure that SLG1 indicates the RFC (password/name) issue to exactly what system. It will not be feasible to go and see all the systems one-by-one. I checked the logs in detail, navigated through all the technical information but not really able to see the particular system name where the real issue is there.

Looking forward to your quick and positive response.

Thanks,

Ameet

[FilipGRC]

HI Ameet,

I would recommend to go to GRC/General settings / Workflow / perform automatic workflow customizing and Configure RFC destination to ensure this step is marked as green.

regards,

Filip

[Former Member]

Hi Filip,

Thanks for your time, but this has already been taken care of way back, but still for your acknowledgement,

I would suggest you to kindly go through with my concerns pasted in my original post.

Kindly let me know with your inputs.

Regards,

Ameet

[Former Member]

This message was moderated.

[Former Member]

Hi Yukti,

Thanks for your time, but none of your suggested notes seem to be relevant to my issue.

My concern is to know the particular connector, where the RFC user name/password is incorrect.

I have put multiple connectors in one connector group and whilst running the risk reports on user level, I get the reports but with warning: ""Risk analysis finished with error. Check log for details"

As you can see in my original post with SLG1 snap shots, it says RFC user name/password is not correct.

I need to know that particular connector without digging into each individuals.

Hope you are clear with my concerns now

Regards,

Ameet

[Colleen]

As a quick way to check could you schedule a delta sync for each connector to see which one fails. Run it for all connectors that are assigned to the logical group?

does sm21 logs show the failed rfc connection?

[Former Member]

Hi Colleen,

Thanks for your response and sorry for this delay in responding with your suggestions.

SM21 results are as below, But I don't see any hints on the connector which is causing the error with RFC:

Exeuting the jobs for each connectors or checking for each connectors one-by-one to investigate with the RFC issue is one option as I had already mentioend in my original post, but that would take quality time to come to one conclusion.

Do we have any way out here to get this sorted out for the connector causing the error.

Regards,

Ameet

[Colleen]

HI Ameet

If the connector has a locked user then I'm surprised the object repository synch job does not show it fails to run for a specific connector. Have you already fixed the user?

I suspect you will need to go through and check the satellite system to find the user and fix it up. Once done, it should not occur again if you have the password stored in SM59 or have trusted systems in place.

Possibly, take the time now to find the connector with the issue. Do not fix it and go back to GRC to see if there is a report or something you could have run to find the error (SLG1 logs didn't help so that's why I thought ST22 or SM21 might).

Regards

Colleen

[Former Member]

Hi Colleen,

I have checked for the user in all the connector whether or not this is locked, and it's not locked out to any connector.

From SLG1 reports which I posted in my original msg, it is clear that, there is the RFC issue with some connector and name/password for this user is incorrect either in the connector or in SM59 in GRC system.

We can always go to each individual connectors to see in which system connector is having the issue with the RFC, but I wanted to know, is there any quick way out here to know that particular connector without looking into each connectors individually. This might be helpful in the scenario like mine, where we have multiple connectors mapped to a connector group.

Regards,

Ameet

[Colleen]

Hi Ameet

I get that you are trying to find a quick central way to identify the connector that has the issue. I'm finding it strange that a sync job or something else won't show the error to the specific system

Regards

Colleen