Previous Topic: CA Business Intelligence: I Cannot Choose an Existing Database ServerNext Topic: BusinessObjects Enterprise: CMC Cannot Connect to BusinessObjects Database


BusinessObjects Enterprise: Users Cannot Run Reports or Connect to CMC

Symptom:

Reviewers and administrators cannot access BusinessObjects Enterprise. For example:

Solution:

Required BusinessObjects Enterprise services are not running.

  1. Use the BusinessObjects Diagnostic Tool to identify which services are down and which are running.
  2. Use the CMC to verify that services identified by the Diagnostic Tool as running are actually running.
  3. Restart any services that are not running. Also, restart any services that the Diagnostic Tool identified as down.
  4. If the CMS service does not restart:
    1. Stop the Server Intelligence Agent (SIA).

      Note: You specified the SIA node when you ran the CA Business Intelligence installer.

    2. Stop the web application server.

      Typically, this is the Tomcat web application server included with BusinessObjects Enterprise.

    3. Stop the web service associated with the web application server (for example, the World Wide Web Publishing Service).
    4. Restart these components in in reverse order.

    Note: The 'CMS' in these instructions is the BusinessObjects Central Management Server, which manages the entire BusinessObjects Enterprise system. Do not confuse this BusinessObjects CMS with the CA Data Protection Central Management Server.

  5. If the CMS service still does not restart, reboot your reports server (that is, the server hosting BusinessObjects Enterprise).