Known Issues › Known Reporting Issues › Central Management Server (CMS) Not Starting

Central Management Server (CMS) Not Starting

Valid on all operating systems with a CA Business Intelligence installation

Symptom:

When you start the BusinessObjects server and use the Central Configuration Manager to verify that all servers have successfully started, the Central Management Server (CMS) can unexpectedly stop.

Solution:

Your CMS database is located on the same server and the database service has not yet started.

To start the CMS

1. On the CMS properties Dependency tab, add the database service according to the database you are using (for example, Microsoft SQL Server).
2. In the Central Configuration Manager, right-click Central Management Server.

   The pop-up menu appears.

3. Select Start.

   The CMS starts.

Unable to Generate Reports for the CIs that contain dot (.) in the CI names

Valid on MS SQL

The following reports (to find the relationship between the CIs) are not generated for the CIs containing dot (.) in the CI name:

• All Change Impact Report
• CIs Relationship Report
• CIs Root Cause Analysis Report
• Direct Change Impact Report