cancel
Showing results for 
Search instead for 
Did you mean: 

Failed to display an MTE tree

Former Member
0 Kudos

Hi,

All of sudden the CCMS functionality on Solution Manager has stopped working.

I am getting the following message when I try to open the Operations Monitor in RZ20

Failed to display an MTE tree

Message no. RA025

Diagnosis

Internal error in the monitoring architecture.

Procedure

Contact SAP AG.

I don't see logs in SM21 or ST22. 

Any input would be greatly appreciated.

Thanks.

Adil

Accepted Solutions (1)

Accepted Solutions (1)

former_member185239
Active Contributor
0 Kudos

Hi Adil


Check if CCMSPING is running on the solman server or not.

Also check the remote agents are attached or not.

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Hi Ashutosh,

I checked the CCMSPING RFC Connection on Solman and its working.  Also, I can see the remote system in RZ21,  Choose Technical Infrastructure → Availability Monitoring → Configure CCMSPING Monitoring.  I can ping all the remote systems.

Anymore input would be appreciated.

Thanks

Adil

former_member185239
Active Contributor
0 Kudos

Hi Adil,

Restart the CCMSPING and also paste the logs for ccmsping.

With Regards

Ashutosh Chaturvedi

Former Member
0 Kudos

Hi Ahshutosh,

SAP provided a solution, they have advised me to turn of remote agent on one of the affected application servers and I was able to open the MTE tree.

When I change the status to OFFLINE in the transaction "RZ21>Topology>
Agents for remote systems", our monitor does work again.

Also, after doing some research, I found the following error on the affected  application server CCMS agent log.

INTERNAL ERROR: could not connect to monitoring segment


We are planning to to bounce this server at the Unix level and hopefully this will address the issue, else I will update the message over here.


Thanks


Adil

Former Member
0 Kudos

Hi Everyone,

I just wanted to update that after bouncing the infected system at the OS level resolved this issues and we have closed the message with SAP.

If we encounter the similar problem again, the workaround will be to have the server bounced at the OS level.


Also, I found a note that will be our permanent solution, we will do this as part of upgrade to our systems.


1767151 - CCMS: sapccm4x agent fails after ABAP instance (re-)start


Thanks everybody.


Adil

Answers (0)