Trusted RFC issue, while implementing SAP FIORI

[Former Member]

Hi Experts,

We are in process of implemented FIORI,(a Central HUB installation).

We deployed, 1)Create sales order, 2)Change sales order and 3)tracking sales order Apps.

Everything went smooth, till the Trusted RFC part.

We are facing issues with Trusted RFC. we are able to execute authorization test successfully form SMT1 of ECC to Gateway server, but unable to get successful authorization test form Gateway server to ECC.

We are getting the below error, while testing  form SMT1.

we maintained Message server port entries in both systems services file, and also assigned the required Authorization to the RFC user(S_RFCACL)but still some this is fishy in the setup.

Thank you.

[former_member214119]

Hi,

I have faced the same issue and it got resolved now.

Please update the services file with below entries in both trusted and trusty system

sapms<SID>    36NN/tcp

Please let me know if you need any further details.

Thanks,

Bikshamaiah.G

[michael_albrecht]

Hi Sreekanth,

Can you copy the error message to to a reply. I'm not able to read it.

Check if the blog SAP Fiori LL05 - Common mistake for setting trusted RFC can help you.

Best regards,

Michael

SCN Moderator

[Former Member]

Hi Michael,

while performing the Authorization test, we are getting the below RFC errors in SMT1 transaction.

"Error when opening an RFC connection (LB: Hostname or service of the message ser "

Thanks

[patriciamaria_cano]

Hi Sreekanth,

I am Patricia, from the BC-CST-GW team. Have you configured load balancing properly for this RFC? This error means that either the hostname where the message server is running or the logon group couldn't be reached.

You should perform the following checks:

• is the ECC message server reachable from the host from which you execute the connection test?  Please execute the following command from the gateway server:

        niping -v -H <hostname message server> -S sapms<SID>

• is the logon group available?  lgtst -H <hostname message server> -S sapms<SID>

• the trace file of the message server (dev_ms) may also give further details if there is any problem with this process

Best regards

Patricia Cano

SAP Active Global Support