Error found in RFC (target) and respective logon\logons are disabled.

[Former Member]

Hi All,

So we have a requirement to use trusted connections for our EAM configuration and after setting up FFUser when the user login in to the system and execute GRAC_SPM we automatically get the message "Error found in RFC (Plugin System) and respective logon\logons are disabled."  We saw note 1777094 that suggest to update validity and password of RFC user, but because this is a trusted connection there is no "RFC User" or in other words the user is the "Current user" of the session and note 1652880 is suggested as a possible fix for Non trusted RFC.  Can anyone point me in the direction of what the issue is here?
we automatically get the message

[mamoonr · Accepted solution]

Hi Jonathan,

Please run connection and authorization for that RFC connection to see the issue, Your Basis team may be of help here.

Thanks,

Mamoon

[santosh_krishnan2 · Accepted solution]

Jonathan,

Were you ever able to solve this issue?  We are seeing this issue today, but last week, it was working fine.  Since no one on our GRC team made changes, we are asking BASIS if they did, to which they're saying they have not.

So we're stumped - the user ID used for the RFC connection is within validity date and isn't locked, and is properly configured, and yet we are seeing this error.

Let me know.

Thanks,

Santosh

[Former Member · Accepted solution]

Hi Santosh,

Our problem was a mixture of not understanding correctly RFC objects and also when to use trusted vs standard connections.  As shown in this link http://help.sap.com/saphelp_nw70/helpdata/en/6b/af429b12e9214d9a2d6cba921b162f/content.htm auth objects related to RFC are actually not included on the SAP profile (that was one of our problems) so our configuration for S_RFC was incorrect.  Also using trusted connections is not mandatory any more to use EAM so at the end using Standard connections was a better approach.  Hope that helps.

[naveen_alluru · Accepted solution]

Hi Santosh,

Try with SAP_ALL to RFC .....could be authorisation issue