SAP Knowledge Base Article - Preview

1576264 - CMS Failover Delay in a Clustered Environment


What could be the cause of a long delay in failover to a different CMS?

  • When connected to a specific CMS and that CMS is shut down, the Enterprise session failover occurs within seconds.
  • If instead the entire machine hosting the CMS is shut down, or made unavailable through other means the failover can take minutes.

Why is there such a big difference in the length of time taken to re-establish the Enterprise session on a different CMS in the cluster?



  • Business Objects XI R2.x
  • BusinessObjects Enterprise XI 3.1
  • SAP BusinessObjects Business Intelligence Platform 4.x


SAP BusinessObjects Business Intelligence platform 4.1 ; SAP BusinessObjects Business Intelligence platform 4.2


boe enterprise cluster clustered failover switch timeout network disabled failed gone missing off cms hanging logon SDK request port cms name port firewall request dispatched dispatch working slow BI cms clustering , KBA , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , Problem

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.