SOLMAN: CCMS "SID_RZ20_COLLECT_103617Error when opening an RFC connection "

[former_member554823]

Hi,

During CCMS configuration i am facing below issue in SOLMAN system

a:) After basic prerequistes check & setup when trying to Add component

to monitoring via rz21.

Selected ABAP in component type to be monitored

Got below error.

-

---

SID_RZ20_COLLECT_103617Error when opening an RFC connection

Error during remote call of SAL_MS_GET_LOCAL_MS_INFO function: Error

when opening an RFC connection

Error during remote call of SALC function: Error when opening an RFC

connection

Error during remote call of RFC1 function: Error when opening an RFC

connection

________________________________________________

b:) we followed note 987166 & Monitored guide

https://websmp102.sap-ag.de/~form/sapnet?

SCENARIO=01100035870000000202&SHORTKEY=01100035870000659947&_OBJECT=011000358700001444802008E

and created user CSMREG but user is getting locked automaticaly within

5 min.

System detail:

SID: 300

SAP_BASIS: 701

SP-Levle: 5

Support package: SAPKB70105

For more detail about error please refer attachment screen.

Please provide a solution

Thanks&Regards,

Vyash

[Paul_Babier · Accepted solution]

Hello Vyash,

It looks like Raghavendra has provided the answer this this query however this will only work if the SID is not conencted to the CEN.

You should check in transaction RZ21

RZ21>Topology>System overview

to see if the system is already connected, and if it is you will se a line like:

<SID> SM_<SID>CLNT115_READ SM_<SID>CLNT115_TRUSTED ONLINE USERNAME DATE

If this is the case then please first check if the SAP CCMS agent for this system was not started

by another user than the ddradm user. You would also want to check for a shared memory key 13 error.

If the shared memory key was created by another user then you have to stop the system and also the SAP CCMS agent and execute the command "cleanipc xx remove" by using the root user (xx is instance number) and

after this you can start the <SID>system.

Regards,

Paul

[raghavendra_bdeshpande]

Hello Vyash,

Please perform this.

The RFC destination will be created based on load balancing and for this the sapmsXXX must be defined in the services file of the central monitoring system, like: C:\Windows\System32\drivers\etc

You can do 2 things now:

1.) Define the correct sapmsXXX TCP/IP port name for each system which you want to add to the central monitoring system in the services file

2.) blank the field 'Logon group' and this will create the RFC destination based on load balancing but without a logon group.

Hope this helps.

Thanks,

Raghavendra.

[former_member554823]

Hi,

In My landscape Centarl & chiled system messageing sever TCP/IP port number is same.

3601/tcp # SAP System Messaging Service Port

So as per above suggession

1.) Define the correct sapmsXXX TCP/IP port name for each system which you want to add to the central monitoring system in the services file

can we define same portnumber entry for sapmsxxx TCP/IP portnumber in services file or we would have to use duplicate portnumber there?

Please suggest.

Regards,

Vyash

[Former Member]

Hi vyashmishra,

We face the same problem. Did you resolved this issue.

My error is

Error during remote call of SAL_MS_GET_LOCAL_MS_INFO function: Name or password is incorrect (repeat logon).

Regards

[former_member554823]

Hi,

As per above issue i followed the thred

And made entry with new TCP- Port for satelite system but still facing and then try to register system monitoring agent as per guide

but still facing same issue.

Error during remote call of SAL_MS_GET_LOCAL_MS_INFO function: Error when opening an RFC connection

Error during remote call of SALC function: Error when opening an RFC connection

Error during remote call of RFC1 function: Error when opening an RFC connection

_________________________________________________________________________________________________________

Regards,

Vyash

[nirmal_konchada]

What error are u getting in the RFC check??

Nirmal.K

[former_member554823]

Hi,

There are no error in RFC chckes.

only below warnings are coming.

-

---

Connection Test SID_RZ20_COLLECT

Connection Type SAP Connection

On HP multiprocessor machines, the specified time values may be incorrect.

-

---

Logon 10 msec

Transfer of 0 KB 2 msec

Transfer of 10 KB 3 msec

Transfer of 20 KB 5 msec

Transfer of 30 KB 6 msec

But whenevr we unlock the CSMREG user in central monitring clinet user gets lock with 5 min with below error

Password logon not possible (too many incorrect attempts)

Followed below solution:

Set password as per SAP note:987166

deleted user CSMREG from central monitoring system and created again via RZ21 as per guide in Service market place.

but still facing the same user lock issue.

Now how we can resoulve this issue.

due to this user lock issue i am not able to create remote monitoring entry for ABAP stack always geting below error.

SID_RZ20_COLLECT_121023Error when opening an RFC connection

Error during remote call of SAL_MS_GET_LOCAL_MS_INFO function: Error when opening an RFC connection

Error during remote call of SALC function: Error when opening an RFC connection

Error during remote call of RFC1 function: Error when opening an RFC connection

Regards,

Vyash

[former_member554823]

Hi,

For above issue i folowed

Note 1453112 - CCMS agent and kernel: patches 2010

and souved few problems

i.e:

a:) User CSMREG lock frequently issue got soulve.

b:) Now SAPCCM4X agent is running smoothly without any error on central system.

But the issue is i m still getting below error when trying to create remote monitoing entry in SOLMAN Live system.

Error during remote call of SAL_MS_GET_LOCAL_MS_INFO function: Error when opening an RFC connection

Error during remote call of SALC function: Error when opening an RFC connection

Error during remote call of RFC1 function: Error when opening an RFC connection

Please someone suggest what action need to taken here.

Regards,

Vyash

[former_member554823]

Dear All,

Issue has been fixed after following

SAP Note 1453112 - CCMS agent and kernel: patches 2010

1:) Here we first performed kernel upgrade then re register agents as per note.

2:) While for mentioned error during remote monitoring entry we checked in path

Tcode-> sm59-> TCP/IP connectiones -> then in RFC destination SAPCCM4X.<SID>.<instance no> and found destination information was not correct so we corrected as

SAPCCM4X.<monitoring system id>.<instance no> then

then perform remote monitoring entrory steps via RZ21 and issue got resoulved

Regards,

Vyash Mishra