Getting error in SM58 SAP R/3

[Former Member]

Hi All,

I am getting temporary error in SM58 of SAP R/3 system Web AS(6.20) connected to SAP PI 7.31 SP04.This error is intermittent and get resolved automatically sometimes in 2 mins..sometimes take more than that.Error is :

/CPIC-CALL: ThSAPECMINIT' : cmRc = 26 thRc= 665#Unknown.

Please let me know the missing config. SM59 RFC destination,port everything is fine and succesfully connected.

It is connected to java port of SAP PI via idoc_aae.

Thanks,

Rohit

[Former Member]

Thanks Endre and thanks everyone.

Issuse is resolved by deleting and adding again the message server entries for PI system in SAP R/3 in central instance and all application servers.

[Former Member]

Any other pointers ?

Out of 4-5 idocs,1-2 will process immediately while 1-2 will be delayed for 5-10 mins may be more.

[Former Member]

Hi Rohit,

I guess you have more application servers in the R/3 system. Did you run a connection test on all

application servers, or did you test the connection only on one of the application servers?

As already mentioned by Subhro the CPIC 665 means

GW_SERVICE_UNKNOWN            665 Gateway service unknown

(s. note #63347)

This means that on at least one application server the gateway service is not known and - as the

tRFC LUWs will be processed later - there is at least one application server where the gateway service is maintained.

You should check the /etc/service file on the application server where the connection

test on the destination fails.

br, Endre.

[Former Member]

Thanks Endre..

This could be the issue as we have 3 application servers in SAP side.Do we need to do or check anything on PI side or only at SAP R/3 side.

1) Check etc/service file for all three servers ?

2) Anything to do with SM59 connection ?

If there is any document or any blog where we have to take care all the checks for all servers connected to SAP PI,please share.

Thanks,

Rohit

[Former Member]

Hi Rohit,

by the respective syslog (SM21) entry you must have the name of the application server where the error occured.

Run a connection test on this application server in SM59. If the connection test fails you have to

check if the gateway service sapgwXX (where XX is the System Nr.) is attached to the port 33XX.

If the port is maintained correctly you have to check with niping (note #500235) if the gateway service

of the target host can be reached.

niping -c -O -S <sapgwXX> -H <hostname>

(where <sapgXX> has to be replaced by the gateway service, <hostname> has to be replaced by the

gateway host of the target system)

The most related note for this issue is the note #52959.

Regards, Endre.

[Former Member]

Hi Endre,

Connection test is working fine in the application server and also the entries are maintained in the service file.

I will check note 52959.

Thanks,

Rohit

[nipun_shedhani4]

Hi Rohit,

Looks like an intermittent connection error, Check on following steps:

1. Check if sm59 destination for IDOC RFC is working from all application servers.

2. Check NWA if the JCO is running and connects to ECC Client using PI central Server gateway information.

3. Check if ECC IDOC RFC destination is also using the correct Gateway, it should point to PI Central Gateway server if not default.

Regards,

Nipun

[Former Member]

Hi Nipun,

1) Out of three app server,one is giving error while connecting.

2) This is working.

3) Verified.

Now the question is we dont generally configure based on the app servers for RFC connection but we connect with one message server of SAP system to the central gateway server of SAP PI.Why it is failing on the one of app server and how we can rectify it

Thanks,

Rohit

[nipun_shedhani4]

Hi Rohit,

It will be now essential for you to check the gateway setup, because I do not see any issues in your configuration. However your SAP Gateway settings needs to be checked.

Possibly you should ask your Basis team to check if the default port 33XX are allowed from firewall connections, and are properly assigned to Gateway Service.

Regards,

Nipun

[Former Member]

Hi Rohit,

"1) Out of three app server,one is giving error while connecting."

1)  Did you run the niping test

niping -c -O -S <sapgwXX> -H <hostname>

on the application server where the error occurs?

What was the result?

2) Did you check in the /etc/hosts on this machine? Is there any other service using the same 33XX  port as the gateway service?

br, Endre.

[aashish_sinha]

Hi Rohit,

If you have done any recent change in IDOC structure, reimport it and reimport the IDoc Metadata in NWA - SOA -IDOC Meta Data monitor.

For detailed error - you can check NWA logs and traces.

Regards

Aashish Sinha

[Former Member]

Hi Aashish,

There is no change in metadata.All the idocs metadata loaded in PI.

Also there is no NWA trace available for this error.

Thanks,

Rohit

[Former Member]

I checked in NWA ->inboundRA,everything seems perfect there also there are no logs in NWA for this intermittent issue.

Also PI system is connected to one more ECC system where there is no issue.Issue is with R/3 system connected to same PI system.After 5-10 mins automatically message gets processed.

Thanks,

Rohit

[Former Member]

We tried server to server ping and it is going fine.

Also we checked sap service file,all entries are maintained and it is up to dated.

Any more thoughts ?

[Former Member]

In NWA, goto Configuration->Infrastructure->Application Resources->inboundRA

And check whether the property has been set to true. If not, please set it to true and in SM59 modify the gateway settings for the PI's gateway.

This is the recommended configuration for IDOC_AAE sender channels

[subhro_de]

Hi Rohit,

The error code you are getting (665) refers to Gateway service name unknown. Can you check the gateway details on the destination and the corresponding in the inboundRA configurations.

Will advise to also check the NWA logs thoroughly if you are getting this error intermittently.

Regards

Subhro

[former_member223322]

Try to do an SLDCHECK in your system. Also check the AI_RUNTIME_JCOSERVER RFC destination in your PI system.

~Srini

[Former Member]

It's working fine.