5.10 Inventory Report Error Messages

Unable to log into the database. Ensure that the ODBC driver is installed properly

Source: ZENworks Desktop Management; Workstation Inventory; Reporting
Severity: Critical
Explanation: ZENworks Reports uses ODBC for connecting to the Sybase or Oracle inventory database. The ODBC client should be installed on the machine running ConsoleOne.

The error occurs if the specific ODBC client required to connect to the Sybase or Oracle inventory database is not installed.

Action: If your inventory database is running on Sybase or Oracle, you must install the recommended ODBC client on the machine. For more information, see Installing the ODBC Drivers in Post-Installation in the Novell ZENworks 7 Desktop Management Installation Guide.
Action: If your inventory database is running on MS SQL, ignore this message and continue by clicking the Run Selected Report button. If the problem persists, contact Novell Support.

ZENworks Reporting encountered an error because of Crystal Reports. For more information, see the ZENworks error message online documentation at http://www.novell.com/documentation

Source: ZENworks Desktop Management; Workstation Inventory; Reporting
Severity: Critical
Possible Cause: ZENworks Reporting requires Microsoft Data Access Component (MDAC) version 2.6 or later. This error occurs if the recommended MDAC version is not installed on the machine running ConsoleOne.
Action: Install MDAC version 2.6 or later. You can download it from the Microsoft Web site.
Possible Cause: The ZENworks database is not synchronized with the Inventory ConsoleOne snap-ins of ZENworks 7 Desktop Management.
Action: Install and use the Inventory ConsoleOne snap-ins of ZENworks 7 Desktop Management to view the data from the ZENworks database. For more information, see the Novell ZENworks 7 Desktop Management Installation Guide.

Unable to connect to the database. Ensure that the database is up and running

Source: ZENworks Desktop Management; Workstation Inventory; Reporting
Severity: Warning
Possible Cause: The Inventory database is not up and running.
Action: Ensure that the database server is up and the Inventory database on the database server is loaded.
Possible Cause: The network connection is down.
Action: Ensure that the network connection is up.
Possible Cause: Unable to start the Proxy database.
Action: Ensure that ports 2639 and 2640 are not used by any other application.