sapccmsr did not respond to start in a timely fashion

[former_member211576]

Hi experts,

   I install SAP on Windows server 2012 cluster and I succeed install sapccmsr in the first node for monitoring OS performance. However, when I install sapccmsr in the second node, I get an error "

ERROR: Failed to start the service SAPCCMSR.99

        Windows message: The service did not respond to the start or control req

uest in a timely fashion.

         Error number: 1053".

Should I reboot OS?

------

      starttype of service:             manual/[auto] :

     ---

      password                            : ********INFO: Windows Service alread

y exists and will be updated.

INFO: Agent status is NOT_ACTIVE (10), monitoring segment type HOST (2). Info re

ad from up-to-date pid file.

INFO: Attached to a monitoring segment type HOST (2), running in shared memory.

INFO: Agent status in the created monitoring segment is NOT_ACTIVE (10).

INFO: trying to start Windows service SAPCCMSR.99 ...

ERROR: Failed to start the service SAPCCMSR.99

        Windows message: The service did not respond to the start or control req

uest in a timely fashion.

        Error number: 1053

WARNING: The following service is registered but could not be started

  SAPCCMSR.99   (command ["C:\usr\sap\PRFCLOG\sapccmsr\sapccmsr.exe" -Service pf

="c:\usr\sap\prfclog\sapccmsr\sapccmsr.pfl"]   user ---)

INFO: Updated config file c:\usr\sap\prfclog\sapccmsr\csmconf.

INFO: dsr: dsrlib unloaded.

EXITING with code 0

[sunny_pahuja2 · Accepted solution]

Hello,

When you install SAPCCMSR in clustered environment then this service will be controlled by cluster. So, this service will be part of cluster and will be started by cluster. At a particular time, this service will run only on one node. As soon as failover happens, cluster will move resources on other node and will start SAPCCMSR service on another node. That is the reason, this service is not getting started on 2nd node.

Please refer to SAP note 536954 for more information.

Thanks,

Sunny

[former_member211576 · Accepted solution]

Hi sunny,

   If I am wrong, please correct me. I think sapccmsr can be installed as a cluster generic service or standalone service on two physical nodes. It depends on SAPLOCALHOST=<hostname> in sapccmsr.pfl. I always install as a standalone service so I can monitor two nodes and it did not failover sapccmsr when I failover SAP ASCS.

[sunny_pahuja2 · Accepted solution]

Hello,

I don't think so. If you will install it on physical hostname then how will you monitor DB instance which is installed on virtual hostname?  SAPLOCALHOST is always point to DB host in case of sapccmsr agent.

Thanks,

Sunny

[Sriram2009 · Accepted solution]

Hi

Kindly refer the SAP Note 1898440 - Failed to start CCMS agent as WinNT service: Error
1053

Regards

Ram

[former_member211576 · Accepted solution]

Hi Sunny,

   DB instance is just the second hostname for me. If SQL runs on node 1, I monitor node 1 in OS07. If SQL runs on node 2, I monitor node 2 in OS07.

   SAPLOCALHOST in sapccmsr.pfl can be physical node or virtual hostname. I use this since Windows server 2008.

[former_member211576 · Accepted solution]

Hi SS,

    Great help. I run sapccmsr and find there is no -noservice parameter but -DCCMS is probably the same as -noservice. Before I try that, I find there is another parameter -initshm and it works. Now sapccmsr in both nodes are running normally.

----

  Usage: sapccmsr -r [-f CSMCONF] | -Service | -DCCMS | -u [-f CSMCONF] | -stop | -initshm | -status | -v | -VERSION |

                  -MONITORING_OFF -level <LEVEL> [-initiator <TEXT>] [-info <TEXT>]

                  | -MONITORING_ON [-initiator <TEXT>] [-info <TEXT>] |

                  -shmdump | -dump

                  [pf=FILE] [-j2ee]

                  [-standalone] [-nosema] [-debug]

  Operation mode parameters (you must specify the one):

     -r

         Install the CCMS Agent as an NT Service SAPCCMSR.<nr>, register

         it at the Central System in dialog mode, create the configuration files and start.

     -r -f <path\to\csmconf>

         Unattended registration of CCMS agent on the Central System using CSMCONF file,

         that has been generated in Central System and has maintained CEN_ADMIN_PASSWORD

         and CEN_CSMREG_PASSWORD parameters. Relative path to csmconf can be used.

         If the path contains blank spaces, enclose it with double quotes (").

     -u

         Stop the CCMS Agent, unregister it from the Central System, remove

         the NT Service SAPCCMSR.<nr> and delete configuration files.

     -u -f <path\to\csmconf>

         Unattended deregistration of CCMS agent on the Central System using CSMCONF file,

         that has been generated in Central System and has maintained CEN_ADMIN_PASSWORD

         and CEN_CSMREG_PASSWORD parameters. Relative path to csmconf cqan be used.

         If the path contains blank spaces, enclose it with double quotes (").

     -Service

         Start the CCMS Agent as an NT Service. This option is only used by

         the service controller of the operating system. Case sensitive.

     -DCCMS

         Start the CCMS Agent in the normal operation mode and stay attached

         to the console. Case sensitive.

     -stop

         Stop the CCMS Agent.

     -initshm

         Re-initialize agent runtime flags in the Monitoring Segment, delete the current PID file

         and delete agent lock file to be able to start the agent after an unexpected termination.

         It must be called with sapadm user. If there is "-j2ee" option specified, then it is

         supposed to be running for a Java instance and it must be started with <sid>adm user.

     -report

         Report the status of the CCMS Agent.

     -MONITORING_OFF -level <LEVEL>

         Activate the monitoring pause of the specified level for the Monitored

         Segment managed by this CCMS Agent. The mandatory parameter -level take

         the values NO_ALERT or NO_VALUES.

     -MONITORING_ON

         Resume a regular collection of the monitoring data for the

         controlled Monitoring Segment.

     -shmdump

         Dump the content of the Monitored Segment in a binary format to

         the file shm13.bin of the working directory.

     -dump

         Dump the content of the Monitored Segment in a human readeable format

         to the file  CcmsSegmentDump.txt of the working directory.

      pf=<full\path\to\profile>

         If there is "-j2ee" parameter set, then set the complete path to the start profile

         of the managed Java instance, otherwise set the complete path to a host profile,

         if you want to customize default profile parameters DIR_CCMS, DIR_PERF.

         The parameter "pf=" must be specified together with each operation mode option.

         If the profile path contains blank spaces, enclose the path in double quotes (").

         Relative path form (.\<profile>) cannot be used - not supported by service controller.

         Note: Directory paths containing blank spaces in values of parameters in profile

               do not need to be enclosed in quotes.

  Optional parameters:

     -j2ee

         Enable the monitoring of a standalone J2EE instance.

     -standalone

         Run the CCMS Agent in a stand alone mode, when it does not report

         to any Central System.

     -nosema

         Do not use semaphores to protect an access to the Monitoring Segment.

         Incorrect usage of this option can corrupt the monitoring data.

     -v

         Show the version information and exit.

     -info <TEXT>

         Specify the cause of activating or deactivating of the monitoring pause.

     -initiator <TEXT>

         Specify the name of the user, who has activated or deactivated the monitoring

         pause.

     -debug

         Write developer traces to the file dev_sapccmsr and stay attached

         to the console (equivalent of -t and -nodaemon options at Unix OS).

     -t

         Activate debug trace level and write developer traces to dev_sapccmsr.

     -VERSION

         Show the patch number and patch history.