CCMSPING communication error: Cannot access message server

[Former Member]

Hello!

We are trying to set up availability monitoring with CCMSPING agent for several satellite systems.

Therefore we installed the CCMSPING agent centrally on the Server of SAP Solution Manager (OS: Windows).

Now we have several SAP satellite systems on Unix that we access via SAP Router.

The RFC connection via SM59 from SAP Solution Manager to the satellite system works and looks as follows:

RFC-connection with SAP Router: /H/saprout1/H/193.84.171.507

The CCMSPING entry within RZ21 looks as follows:

Connection Data and Monitoring options:

Message server host name: 193.84.171.507

IP Service Name: sapms<sid>

Router String: /H/saprout1/H/

When we test the connection via Test Ping we get the following error:

CCMSPING: Test Results

Available Systems - CCMSPING call successful

Failed CCMSPING Calls

<sid> CCMSPING.solmanserver.00

CCMSPING communication error: Cannot access message server

The content of the file dev_ccmsping looks as follows:

Tue Apr 19 12:26:00 2011

*** ERROR => NiBufIProcMsg: hdl 1 received rc=-94 (NIEROUT_PERM_DENIED) from peer [nibuf.cpp 2125]

*** ERROR => MsINiWrite: NiBufSend (rc=NIEROUT_PERM_DENIED) [msxxi.c 2480]

*** ERROR => MsIAttachEx: MsINiWrite (rc=NIEROUT_PERM_DENIED) [msxxi.c 734]

*** ERROR => LgIAttach: MsAttach (rc=NIEROUT_PERM_DENIED) [lgxx.c 3980]

*** ERROR => comp. = NI (network interface), rc = -94 [alxxping.c 327]

We also add the IP adress of the satellite system into the file "hosts" and the service sapms<sid> with the port 36<xx> into the file "services" on the server of SAP Solution Manager.

Any helpful information will be very appreciated!

Thank you

[Former Member]

Hi

it seems due to firewall, please do ensure your router settings.

Have your admin team added the proper IP address on the saprouttab fie

chk here [http://help.sap.com/SAPhelp_nw70/helpdata/en/4f/992e0b446d11d189700000e8322d00/content.htm|http://help.sap.com/SAPhelp_nw70/helpdata/en/4f/992e0b446d11d189700000e8322d00/content.htm]

and do check your message server port twice?

Thanks

Jansi

[Former Member]

Hello!

Many thanks!

The SAP Router entries should be there, otherwise the RFC connection from SOLMAN to the satellite system would not work...

Any other recommendations?

Thank you!

[jon_friesen2]

Hi there,

CCMSPING first does a connection to the message server (port 36xx) before attempting to connect to the dialog instances (port 32xx). Your saprouter might be permitting connections on the dialog ports 32xx but denying connection to the message server ports on 36xx. When you tested your saprouter in SM59, did you use a load-balanced RFC destination or a direct connection? Try it with a load-balanced connection, which will connect to the messager server and will more closely mimic the kind of connection the ccmsping agent is making.

Jon

[Former Member]

Hello Jon/all,

many thanks for your recommendations.

Our RFC-connection from SOLMAN to the satellite system via SM59 does not use load balancing and looks as follows:

/H/saprout1/H/193.84.171.507

We also allow the connections to the message port (36xx) within SAPROUTTAB.

Colud you kindly explain what are the settings of:

1) RZ21 --> Connection Data and Monitoring options --> Router String

The current CCMSPING entry is:

Connection Data and Monitoring options:

Message server host name: 193.84.171.507

IP Service Name: sapms<sid>

Router String: /H/saprout1/H/

2) The entries within SAPROUTTAB

3) The entries within SERVICES and HOST files

Thank you very much!