How to enable ZAM Logging and Diagnostic Mode

  • 3564341
  • 28-Jan-2008
  • 30-Apr-2012


Novell ZENworks 7.5 Asset Management - ZAM7.5
Novell ZENworks Asset Management 7 - ZAM7
Novell ZENworks Asset Management 3.3 - ZAM


How to enable the ZAM Logging and Diagnostic Mode


There are a number of logs that are created by default on the Collection Server, Task Server, and Manager. These logs are stored at C:\Program Files\Novell\ZENworks\Asset Management\Logs
ColSrvCoreEvent*.log - Logs the Collection Server
TaskServerCoreEvent*.log - Logs the Task Server.
LoaderEvent*.log - Logs the loading of .WIF files from the Database
UnloaderEvent*.log - Logs the unloading of .WIF files from the Database
NetCMgrEvent*.log - Logs upgrade and PRUs
TSCMgrEvent*.log - Logs the ZAM Manager
Tomcat and WebConsole events are logged to the rtrlet.log at the root of the C: drive on the WebConsole Server. The rtrlet.log can be set to debug level to get a more verbose log. Shut down the Apache Tomcat Service. Use a TXT editor to open C:\Tomcat4\webapps\rtrlet\ and set the logging from INFO to DEBUG so the line looks like this:

log4j.rootCategory=DEBUG, default

Then restart the Apache Tomcat Service.

Once you have recreated the event requiring DEBUG logging, shut down the Apache Tomcat Service. Use a TXT editor to open C:\Tomcat4\webaps\rtrlet\ and set the logging from DEBUG to INFO so the line looks like this:

log4j.rootCategory=INFO, default

To put the Collection Client in Diagnostic Mode open the C:\Program Files\Novell\ZENworks\Asset Management\Bin\cps.ini.
for ZAM 7.0 add this line:
for ZAM 7.5 add this line:
at the end of the file. When restarting the Collection Client Service, an output window will be generated which can be saved to a file.  The cps.ini is not created if the client was installed via the Remote Client Installer.  If the file is not there, you can copy if from another Client machine.
 This log is good for showing the Client connecting to the Collection Server.
To put the Collector (COLW32.EXE) in Diagnostic Mode, create the file C:\Program Files\Novell\ZENworks\Asset Management\Bin\Options.txt on the workstation and add the line Diagnostic. Save the file then restart the Collection Client Service. This will generate another diagnostic window that can be saved to a file. This log is good for showing the actual inventory scan and components being gathered.
NOTE: For Terminal servers, the Collector and Client diagnostic windows will only show up at the Terminal Server console. They do not show up in the RDP session.
Putting the Collector (COLW32) in Diagnostic Mode will also put more information into the .WIF file. The .WIF file can only be used by Novell Support. The location of the .WIF file is in Program Files\Novell\Zenworks\Asset Management\bin\InboxCC.
A Usage log can be created by creating the file C:\tsusagecfg.ini. In the file on the first line write [TSUsage] and underneath that on the second line write Debug=Yes. Save the file and restart the Collection Client. You will get a Usage Diagnostic Window with the usage logging.
For problems with the installation of the Database or File Store there will be a _DBUPGRADE.log created in C:\Program Files\Novell\ZENworks\Asset Management\Bin and a TSCInst.log created in the C:\WINNT or C:\WINDOWS Directory.
A Database Persistor log can be created to log all database activity. This is set on the machine communicating to the database. For example, it can be set on the Collection Server, Manager, or Task Server to show the communication to the database from those components. To enable the Persistor log, create the following registry key:
HKLM\Software\Tally Systems Corp.\TSCensus\Database\DiagnosticLogging=1 (Dword)
The log will be in \Program Files\Novell\ZENworks\Asset Management\Logs\ with the name of the database or the database server. However, the name of the persistor log is different with Oracle databases - the name of the persistor log contains just the ODBC DSN name (ZENworks Dat-xxxxxxxxxx.log), as opposed to the server and db name.
Is the issue that the scan will not happen or the Portable Collector cannot be loaded?  If the Portable Collector was made pointing to one Collection Server but then tried to load to a different Collection Server it will not load.  The TSCMgrEvent log (TSCMgrEvent*.log) and the Collection Server core log (ColSrvCoreEvent*.log) from the time / day the Portable was atteptmed to be loaded are the relevant debug logs.  The options.txt file will not work in this situation because it is not pushed down to the workstation while in portable mode.

Additional Information

Formerly known as TID# 10098082