4.1 System Reporting Error Messages

This section contains detailed explanations of the error messages you might encounter using System Reporting.

An error has occurred: Batch state is unknown

Source: ZENworks 10 Configuration Management SP3; System Reporting.
Explanation: In the ZENworks Reporting Server InfoView, you might encounter this error if you access the parent reporting folder after generating the reports.
Action: After generating the reports, log out of the ZENworks Reporting Server and log in again to the ZENworks Reporting Server InfoView.

30270: An internal error occurred while calling the 'processDPCommands' API. (Error: WIS 30270) BOException caught:RESULT=80004005;WHAT=RefreshBatch failed

Source: ZENworks 10 Configuration Management SP3; System Reporting.
Explanation: If you schedule a Predefined report or a Web Intelligence report published by using the report-deploy command, you might encounter this error.
Possible Cause: The report-deploy command publishes *.wid files into the BusinessObjects File repository, opens the document, refreshes it, then saves it again. If it fails to refresh for reasons such as the database connectivity timing out, it leaves the document in a invalid state. The report is deployed to the ZENworks Reporting Server but fails when it is scheduled.
Action: Do the following.

  1. Open the report that you want to schedule in the ZENworks Reporting Server InfoView.

  2. Click Refresh Data.

  3. Save the report.

  4. Schedule the report. For more information on how to schedule a report, see Section 3.0, Creating and Managing Reports.

There are no ZENworks Reporting Servers configured in the Management Zone

Source: ZENworks 10 Configuration Management SP3; System Reporting.
Explanation: In a management zone, if the Primary Server is a a SLES 10 64-bit device, and ZENworks Reporting is installed on a Windows Secondary ZENworks Server, then you might encounter this error when you try to launch Reporting from the Secondary Server. The Reporting options might be disabled in the Reporting tab of ZENworks Control Center.
Possible Cause: The ZENworks Configuration Management post-installation tasks have not been successfully completed on the Secondary Server.
Action: Launch Reporting from the SLES 10 Primary Server.

You do not have the rights to save in this folder or edit categories. If you require these rights, see your BusinessObjects administrator

Source: ZENworks 10 Configuration Management SP3; System Reporting.
Explanation: You might encounter this error when you try to save a template to My InfoView in the ZENworks Reporting Server InfoView.
Possible Cause: You do not have rights to save reports or data to the My Favorites folder.
Action: Get Create/Delete Report rights for the Favorites folder from the Administrator.

Unable to reconnect to the CMS <server-name>:6400. The session has been logged off or has expired. (FWM 01002)

Source: ZENworks 10 Configuration Management SP3; System Reporting.
Explanation: You might encounter this error if the ZENworks Reporting Server InfoView session has expired, and you are trying to launch it again.
Action: Do the following:

  1. Delete the cookies from your browser.

  2. Close all browser instances.

  3. Log in to the ZENworks Control Center, and launch the ZENworks Reporting Server InfoView.

Cannot initialize Report Engine server. (Error: RWI 00226) (Error: INF)

Source: ZENworks 10 Configuration Management SP3; System Reporting
Possible Cause: This problem might occur if the Report Engine Server is not running, and you are trying to create or access the reports.
Action: On Windows, do the following:

  1. From the desktop Start menu, click Programs > ZENworks Reporting Server > ZENworks Reporting Server > Central Configuration Manager > Server Intelligence Agent to display the Central Configuration Manager window.

  2. Click Restart.

  3. Wait 2 to 3 minutes for the services to restart.

  4. Launch the ZENworks Reporting Server InfoView.

On Linux, do the following:

  1. Stop the BusinessObjects Enterprise services by running the following command as a root user:

    /etc/init.d/BobjEnterprise120 stop

  2. Wait 2 to 3 minutes for all the services to stop.

  3. Start the BusinessObjects Enterprise services by running the following command as a root user:

    /etc/init.d/BobjEnterprise120 start

  4. Wait 2 to 3 minutes for all the services to start.