SAP Knowledge Base Article - Preview

1709483 - Some servers stay in Stopping/Starting status if using -managedstop/-managedstart command to stop/start servers repeatedly in a clustered environment

Symptom

Some servers stay in Stopping/Starting status if using -managedstop/-managedstart command to stop/start servers repeatedly

Command example:

ccm.exe -cms <ServerName>:6400 -username Administrator -authentication secEnterprise -managedstop <NodeName>.DestinationJobServer <NodeName>.EventServer <NodeName>.ProgramJobServer <NodeName>.PublicationJobServer <NodeName>.AdaptiveJobServer <NodeName>.CrystalReportsJobServer <NodeName>.ListOfValuesJobServer

ccm.exe -cms <ServerName>:6400 -username Administrator -authentication secEnterprise -managedstart <NodeName>.DestinationJobServer <NodeName>.EventServer <NodeName>.ProgramJobServer <NodeName>.PublicationJobServer <NodeName>.AdaptiveJobServer <NodeName>.CrystalReportsJobServer <NodeName>.ListOfValuesJobServer


Read more...

Environment

  • BusinessObjects Enterprise XI 3.1 Service Pack 4 (SP4)
  • Cluster
  • Windows Server 2008 R2

Product

SAP BusinessObjects Enterprise XI 3.1

Keywords

ccm, cluster, clustering, commandline, hanging, hang, ADAPT01635929, 01635929, 1635929 , KBA , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.