Show TOC

 Error Analysis: CCMS AgentsLocate this document in the navigation structure

Caution

CCMS agents are no longer required for purely SAP NetWeaver 7.1 landscapes; their functions are performed by SAP NetWeaver Management Agents. For information about when you still require CCMS agents for SAP NetWeaver 7.1, see CCMS Agents: Central Monitoring for Components up to SAP NetWeaver 7.0.

SAP has possible solutions to the following errors that can occur when you are using the CCMS agents:

General

  • Logon to the central monitoring system does not work during registration of the agent.

    This is usually due to incorrect configuration that applies to all RFC client programs, irrespective of the agent.

    Therefore, you should first test the RFC connection to the central monitoring system. To do this, use the test program SAPINFO, which is part of the Remote Function Call Development Kit (RFC SDK). This package is on every presentation CD. You can use this program to check the connection to the central monitoring system without logon and password (see also SAP Note 42692).

  • The agent registers error-free as a service. However, the service does not start or terminates immediately (Microsoft Windows).

    A service under Microsoft Windows always starts in the System32 directory. So that the system can find any existing profile files, you must always specify these with a full path.

    Deregister the service (for example, with sapccm4x -U), and reregister it, specifying the profile with the complete path.

  • Although a template for log file monitoring exists and is entered in SAPCCMSR.INI, the system does not display any subtrees for log files in transaction RZ20 of the central system.

    You must end the LOGFILE_TEMPLATE with a period (.). The line containing the period must contain no other characters. You should also check in the log file of the agent which files it is actually monitoring.

  • During the installation of the SAPCCMSR agent, you receive an error message saying that the system cannot access a directory or that it does not exist (Microsoft Windows).

    You must have created the working directory \\<host>\saploc\prfclog\sapccmsr and have released the directory saploc, before you install SAPCCMSR.

  • After a restart, the agent is not used to collect data.
    • Check in the operating system whether the process is active.
    • Check the RFC destination SAPCCM4X.<host>.<no> in transaction SM59 of the central system. Perform a connection test in the transaction.
    • Check the log file of the CCMS agent in its working directory.
  • The service cannot be started during the registration of the agents (Microsoft Windows only)

    Ensure that the Services window is not open during the registration.

  • If you cannot solve a problem, we recommend the following procedure:
    • Check the log files in the working directory of the CCMS agent for possible error causes.
    • Restart the service (Microsoft Windows).
    • If the problem persists, uninstall the CCMS agent and reinstall it.
    • Check the RFC destination of the CCMS agent in transaction SM59 in the central system.
    • Load the newest version of the CCMS agent.
    • When sending problem messages and queries to SAP, always send all log files and configuration files from the working directory of the CCMS agent.

SAPCCMSR/SAPCM3X

  • Where is the working directory for sapccmsr.ini and the log files?

    $DIR_PERF/sapccmsr

    Under UNIX: /usr/sap/tmp/sapccmsr

    Under Microsoft Windows: \\<host>\saploc\prfclog\sapccmsr

    Example                C:\usr\sap\prfclog\sapccmsr(sap must be released as the share saploc)

SAPCCMSR -j2ee

SAPCCM4X

  • Where is the working directory for sapccmsr.ini and the log files?

    $DIR_LOGGING/sapccm4x

    Example (UNIX):/usr/sap/C11/D01/log/sapccm4x

  • How can you display when the monitored instance was available?

    In the working directory of the agent, there is the log file available.logcontaining the following information:

    • Periods when the agent is connected to a shared memory segment
    • Periods when the monitored instance is available

    Example (the instance was started after the agent and was then restarted again):

Unavailable        uw1042_C11_01, agent not attached   05.04.2002 10:50:14 - 05.04.2002 10:50:55Available          uw1042_ C11_01, agent not attached   05.04.2002 10:51:05 - 05.04.2002 10:51:05Available          uw1042_ C11_01, agent attached to key 13 (pool 10)   05.04.2002 10:51:25 - 05.04.2002 10:52:46Unavailable        uw1042_ C11_01, agent attached to key 13 (pool 10)   05.04.2002 10:52:56 - 05.04.2002 10:52:56Unavailable        uw1042_ C11_01, agent not attached   05.04.2002 10:53:18 - 05.04.2002 10:56:19Available          uw1042_ C11_01, agent not attached   05.04.2002 10:56:29 - 05.04.2002 10:56:29Available          uw1042_ C11_01, agent attached to key 13 (pool 10)   05.04.2002 10:56:50 - 05.04.2002 11:16:20

 CCMS Agents start page