Collection Server unavailable

  • 3616609
  • 15-Apr-2007
  • 27-Apr-2012

Environment


Novell ZENworks 7 Asset Management - ZAM7

Situation

After a crash the Collection Server Service recovers however, the Collection Server is listed as unavailable in the Manager.

Resolution

Fixed in ZAM 7.0 IR10 or newer
If downloading the Interim Release manually from https://download.novell.com, the filename is ZAM700SP1IR10.EXE. The Interim releases can also be set up within the ZAM Manager for the Task server to check the site on a scheduled basis, and download and apply them automatically. Please refer to the Help Section for details of how to set up automatic downloads if desired.

Each interim release is cumulative. If Interim Release 10 is not available due to a newer interim release being placed on the website, be assured that the code needed is in the later release.
Restart the Collection Server service.
Once the service is restarted the status shows up correctly as
"Started" in the ZAM Manager.

Additional Information

A scheduled scan for over 2500 machine caused the Collection Service to crash. The problem is related to dropped database connections.

The Collection Server Log shows:


Application Object Error at 8/23/2006 9:18:09 PM on by svczam
Object Store Error
[2.4.104] An error occurred while storing the object.

Class:"Application Error"
Name:"{0ACCE336-4394-4D57-BE75-9EE80041580A}"
Application Object Error at 8/23/2006 9:18:09 PM on LIVONIA-MI-ZAM1 by svczam
Unexpected Exception
[2.4.3] Unexpected exception [2.5.4]... operation failed.
Database Persistence Layer Error in DBOracleErrorHandler::serverError at
8/23/2006 9:18:09 PM
ODBC Manager Error
[2.5.203] An error occurred in the ODBC Manager.
Database Persistence Layer Error in DBOracleErrorHandler::serverError at
8/23/2006 9:18:09 PM
Logon Error
[2.5.4] Failed to Log onto the database.
Database Persistence Layer Error in DBOracleErrorHandler::serverError at
8/23/2006 9:18:09 PM
Database Error
[2.5.3] Error: '[5] SQL call failed.'
Message 1: '[0] S1010'
Message 2: '[1] SQL call failed.'