Novell Home

How to Enable Debug Logging in ZENworks Desktop Management 6.5 and 7

Novell Cool Solutions: Feature

Digg This - Slashdot This

Posted: 2 Aug 2007
 

Check out this very useful reference sheet replete with instructions on how to enable debug logging for the different components of ZENworks Desktop Management, running on various platforms. You should print it and tape it to the wall - no one should be expected to memorize this stuff.

For updates or additional information that may have been added since the date this article was posted, refer to this TID.

Server Install Debug Logging

Server Install debug logging for ZDM on NetWare and Windows is enabled in the registry on the installing workstation.

  • Location: HKCU\Software\Novell\ZENworks
  • Name: ZWInstal.dll Log
  • Type: DWORD Value
  • Data: 0 (Debug log file will NOT be written to)
  • Data: 1 (Debug log file will be written to)

Output: C:\Novell\Zfdtemp\ZENWORKS_DESKTOP_MANAGEMENT_INSTALLLOG.LOG

Server Install debug logging for ZDM on Linux

//Export the variable LAX_DEBUG
export LAX_DEBUG=true
//Run the setup with the following commandline arguments, which are case sensitive
./setup -DLogger.logLevel=FINER

This will output the logfiles in the same locations, but with the specified levels of messages. The JAVA logLevel options are:

  • SEVERE (highest value) *least verbose
  • WARNING
  • INFO
  • CONFIG
  • FINE
  • FINER
  • FINEST (lowest value) *most verbose

Output: /var/log/ZENworks_Desktop_Management_InstallLog.log

Agent Install Debug Logging

Agent Install debug logging is enabled in the registry or through Group Policy

  • Utility: GPEDIT.MSC
  • Location: Computer Configuration / Administrative Templates / Windows Components / Windows Installer
  • Policy: Logging
  • Setting: voicewarmup
  • Reference: Microsoft KB article 314852

Output: %TEMP%\MSIxxxx.log

Note: This will enable logging for all MSI installs.

AWI, AWR Logging

(AWI) Agent Logging

(AWI) Agent logging is enabled in the registry

  • Location: HKLM\Software\Novell\ZENworks\Debug
  • Name: ZENWSREG
  • Type: DWORD Value
  • Data: 0 (Debug log file will NOT be written to)
  • Data: 1 (Debug log file will be overwritten each time)
  • Data: 2 (A new debug log file will be created each time with a unique name)
  • Data: 3 (Debug log will be appended to each time)

Output: Program Files\Novell\ZENworks\DebugLogs\zenwsreg.log

(AWI, AWR) NetWare Server Logging

(AWI, AWR) NetWare Server logging is enabled inside ZENWSIMP.NCF and ZENWSREM.NCF

  • Location: SYS:\SYSTEM
  • -Dlogfile=<location of output file>
  • -Dlogfilelevel=<debug level to control amount of information written to the log file, 1 is the least information and 3 is the most>
  • -Dlogfilelimit=<maximum size (in bytes) for logfile. After limit is reached - the log is maintained on a first in first out basis). N.B. This must be less than or equal to 100000.
  • -Dloglevel=<debug level to control amount of information written to the screen, 1 is the least information and 3 is the most>

Output: as specified (default is SYS\ZENWORKS\ZENWSIMP.LOG and SYS\ZENWORKS\ZENWSREM.LOG)

(AWI, AWR) Windows Server Logging

(AWI, AWR) Windows Server debug file logging is enabled in the registry.

  • Location: HKLM\Software\Novell\ZENworks\AutoWSImport
  • Name (AWI): zenwsimportCmdLine
  • Name (AWR): zenwsremovalCmdLine
  • Type: STRING Value
  • Data: -Dlogfile=<name and location of logfile> -Dlogfilelevel=<debug level to control amount of information written to the log file, 1 is the least information and 3 is the most>

Output: as specified (default is c:\zenwsimp.log and c:\zenwsrem.log)

(AWI, AWR) Windows Server debug screen logging is enabled in the registry and using the command line.

  • Location: HKLM\Software\Novell\ZENworks\AutoWSImport
  • Name (AWI): zenwsimportCmdLine
  • Name (AWR): zenwsremovalCmdLine
  • Type: STRING Value
  • Data: -Dloglevel=<debug level to control amount of information written to the screen, 1 is the least information and 3 is the most> -Dnoauthenticate=true
  • Command Line (AWI): (Must be logged in with admin rights) In a DOS box, "C:\Novell\zenworks\AutoWS\zenwsimport -debug"
  • Command Line (AWR): (Must be logged in with admin rights) In a DOS box, "C:\Novell\zenworks\AutoWS\zenwsremoval -debug"

(AWI, AWR) Linux Server Logging

(AWI, AWR) Linux Server logging is enabled inside NOVELL-ZDM-AWSI.CONF

  • Location: /etc/opt/novell/zenworks/zdm
  • IMPORT_SERVICE_LOGFILE=<location of output file>
  • REMOVAL_SERVICE_LOGFILE=<location of output file>
  • loglevel=<debug level to control amount of information written to the screen, 1 is the least information and 3 is the most>
  • logfilelevel=<debug level to control amount of information written to the log file, 1 is the least information and 3 is the most>

Output: as specified (default is /var/opt/novell/log/zenworks/AWSI.LOG and /var/opt/novell/log/zenworks/AWSR.LOG)

Policies Logging

(Policies) Agent Logging

(Policies) Agent logging is enabled in the registry

  • Location: HKLM\Software\Novell\ZENworks\Debug
  • Name (ALL logs): EnableDebug
  • Name (NWGINA log): NWGINA
  • Name (Workstation Manager log): WM
  • Name (Remote Mgmt Policy log): RMPol
  • Name (Inventory Policy log): InvPol
  • Name (Group Policies log): WMGrpPol
  • Name (User Group Policies log): WMGrpPolUser
  • Name (Wks Group Policies log): WMGrpPolWks
  • Name (iPrint policy log): WMiPrint
  • Name (Desktop Preferences log): WMPM
  • Name (Extensible Policies log): WMPolHlp
  • Name (Queue-based Printer Policy log): WMPrtNT
  • Name (WM helper launch log): WMRUNDLL
  • Name (Mgmt Agent Policy log): WmZenCfg
  • Name (Policy retrieval log): ZenPol
  • Name (Policy retrieval results log): ZenPolStatus
  • Type: DWORD Value
  • Data: 0 (Debug log file will NOT be written to)
  • Data: 1 (Debug log file will be overwritten each time)
  • Data: 2 (A new debug log file will be created each time with a unique name)
  • Data: 3 (Debug log will be appended to each time)
  • Output: Program Files\Novell\ZENworks\DebugLogs\NWGINA.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\WM.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\RMPOL.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\INVPOL.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\WMGRPPOL.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\WMGRPPOLUSERPOL.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\WMGRPPOLWKS.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\WMiPrint.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\WMPM.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\WMPOLHLP.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\WMPRTNT.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\WMRUNDLL.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\WMZENCFG.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\ZENPOL.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\ZENPOLSTATUS.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\ZENPOLSTATUS.LOG

(Policy Tools) ConsoleOne Policy Utility Logging

(Policy Tools) ConsoleOne policy utility logging is enabled in the registry.

  • Location: HKLM\Software\Novell\ZENworks\Debug
  • Name (Policy Reporting log): ReprtPol
  • Name (Policy Migration log): MigrtPol
  • Name (Copy Policy log): CopyPol
  • Type: DWORD Value
  • Data: 0 (Debug log file will NOT be written to)
  • Data: 1 (Debug log file will be overwritten each time)
  • Data: 2 (A new debug log file will be created each time with a unique name)
  • Data: 3 (Debug log will be appended to each time)
  • Output: Program Files\Novell\ZENworks\DebugLogs\REPRTPOL.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\MIGRTPOL.LOG
  • Output: Program Files\Novell\ZENworks\DebugLogs\COPYPOL.LOG

Remote Management Logging

(RM) Target Workstation logging is enabled by default.

  • Location: Program Files\Novell\ZENworks\Remote Management\RMAgent
  • Output: RMErrorLog*.txt (where * is 0/1/2, etc)
  • (RM) Remote Management Policy logging is enabled in the registry

    • Location: HKLM\Software\Novell\ZENworks\Debug
    • Name: RMpol
    • Type: DWORD Value
    • Data: 0 (Debug log file will NOT be written to)
    • Data: 1 (Debug log file will be overwritten each time)
    • Data: 2 (A new debug log file will be created each time with a unique name)
    • Data: 3 (Debug log will be appended to each time)


    • Output: Program Files\Novell\ZENworks\DebugLogs\RMPOL.LOG

    (RM) Console Workstation logging is enabled by default

    • Location: <ConsoleOne directory)\1.2\bin\zen\RcLaunch
    • Output: RMErrorLog0.txt

    IMG Logging

    (IMG) NetWare server logging is enabled at the System Console

    • Pre-requisite: unload IMGSERV.NLM
    • Console command: IMGSERV -debug
  • Output: SYS\ZENworks\ZIMGDBG.LOG
  • (IMG) Windows Server logging is enabled in the Novell eDirectory Services control panel

    • Pre-requisite: Stop IMGSERV.DLM
    • Startup Parameter: -debug
  • Output: C:\ZIMGDBG.LOG
  • (IMG) Workstation logging is enabled from the command line for versions less than 6.5sp2

    Before restoring the image, from the bash prompt:
    Command: export ZENIMGLOG=A

    Output: current directory, named "imglog"

    6.5sp2 and higher versions write to a IMGLOG and IMGLOGR file at the root of the RAM disk by default. To increase the log level written to IMGLOG, export DEVELOPER_LOG=A before using the img engine.

    (IMG) ZISWIN agent logging is enabled in the registry. Alternatively, it can be configured by using the GUI utility ZISWIN.EXE

    • Location: HKLM\Software\Novell\ZENworks
    • Name: ZISWin History Filename (If this Value is non-existent - the default is c:\ziswin.hst)
    • Type: STRING Value
    • Data: <location and filename of output file>
    • Name: ZISWin Log
    • Type: STRING Value
    • Data: 0 (Debug log file will NOT be written to)
    • Data: 1 (Debug log file will be overwritten each time)
    • Data: 2 (A new debug log file will be created each time with a unique name)
    • Name: ZISWin History Log Entries
    • Type: DWORD Value
    • Data: <maximum number of entries to include in the debug log. If this DWORD Value is non-existent - the default is 100) (PXE) Windows server logging is enabled in the registry
    • Location: HKLM\Software\Novell\ZENworks
    • Name: ZENPXE Log
    • Type: STRING Value
    • Data: 1
  • Output: <Windows directory>\system32\ZENPXE.log
  • PXE Logging

    (PXE) NetWare server logging is enabled at the System Console

    • Pre-requisite: unload ZENPXE.NLM
    • Console command: ZENPXE -debug
  • Output: SYS\ZENworks\ZENPXE.LOG
  • (PXE) Linux Server logging is always enabled

    Output: /var/opt/novell/log/zenworks/preboot/novell-zimgdbg.log

    (PXE) Windows Transaction Server logging is enabled in the registry

    • Logging: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSPService\Parameters
    • Name: LogLevel
    • Type: DWORD Value
    • Data: 80 (Hex)
  • Output: DTS.LOG
  • NAL Logging

    (NAL) Agent logging is enabled in the registry. Alternatively, it can be configured using the GUI utility NALDIAG.EXE

    • Location: HKLM\Software\NetWare\NAL\1.0\Debug
    • Name (sets the debug level for any enabled component): Level
    • Type: DWORD Value
    • Data: 0 (Debug log file will NOT be written to)
    • Data: 1 (Informational messages only)
    • Data: 2 (Warning messages only)
    • Data: 3 (Informational and Warning messages only)
    • Data: 4 (Critical messages only)
    • Data: 5 (Informational and Critical messages only)
    • Data: 6 (Warning and Critical messages only)
    • Data: F (All messages)
    • Name: LogFileLocation (If this Value is non-existent - the default is Program Files\Novell\ZENworks\ZFDNAL.CSV)
    • Type: STRING Value
    • Data: <location and filename of output file>
    • Name (MyApps log): Browser
    • Name (NALview log): Explorer
    • Name (Wks comm log): IPC
    • Name (ZENlite log): Library
    • Name (ZENmup log): MUP
    • Name (Reporting log): Reporting
    • Name (NALNTSRV log): Service
    • Name (NALSTART log): Start
    • Name (Wks Helper log): Workstation
    • Type: DWORD Value
    • Data: 0 (Debug logging will NOT be written to the NAL log file for this component)
    • Data: 1 (Debug logging will be written to the NAL log file for this component)

    Output: as specified (if none specified, the default location is Program Files\Novell\ZENworks\ZFDNAL.CSV)

    • Name (NAL MSI log): MSI
    • Type: DWORD Value
    • Data: 0 (Debug logging will NOT be enabled for this component)
    • Data: 1 (Debug logging will be enabled for this component)

    Output: Program Files\Novell\ZENworks\ZAPPMSI.LOG (alternatively, you'll find ZAPPMSI.LOG in the path listed in the LogFileLocation string value, if specified)

    INV Logging

    (INV) Scanner logging on the agent workstation is enabled by default.

    • Location: %SYSTEMDRIVE%\ZENworks

    Output: ZENERRORS.LOG

    (INV) Inventory policy logging is enabled in the registry.

    • Location: HKLM\Software\Novell\ZENworks\Debug
    • Name: InvPol
    • Type: DWORD Value
    • Data: 0 (Debug log file will NOT be written to)
    • Data: 1 (Debug log file will be overwritten each time)
    • Data: 2 (A new debug log file will be created each time with a unique name)
    • Data: 3 (Debug log will be appended to each time)

    Output: Program Files\Novell\ZENworks\DebugLogs\INVPOL.LOG

    (INV) Inventory Service logging on the server is enabled by default, and is also configurable.

  • Location: <inventory volume/share>\ZENworks\Inv\server\WmInv\properties\TracerFilter.properties
  • Data (to enable all debug information): change *default*=BRIEF to *default*=ALL
  • Output: <inventory volume/share>\ZENworks\Inv\server\WmInv\logs\zenworksinvservice\zenworksinvservice-xxxx.txt

    (INV) Inventory Service logging in eDirectory is enabled by default.

    • Location: ConsoleOne, right-click Inventory Service Object, Status Report

    Output: Server Status
    Output: Rollup Status

    (INV) Inventory database migration logging is enabled by default.

    • Location: <inventory volume/share>\ZENworks\Inv\server\WmInv\logs\Migrationlogs

    Output: <timestamp>_migrate.log

    (INV) Inventory reporting logging is enabled on the ConsoleOne workstation.

    • Location: <ConsoleOne install dir>\1.2\bin\debug.properties
    • Data (DBexport): DBEXPORT_TRACE=ON
    • Data (Summary): INVAPI_TRACE=ON
    • Data (Query): QUERYUI_TRACE=ON
    • Output: <ConsoleOne install dir>\1.2\bin\DBExportTracer.TXT
    • Output: <ConsoleOne install dir>\1.2\bin\INVApiTrace.log
    • Output: <ConsoleOne install dir>\1.2\bin\QryUITrace.log

    (INV) Scanner logging in eDirectory is enabled by default.

    • Location: ConsoleOne, properties of Workstation Object, ZENworks Inventory, Scan Status

    Output: Workstation Scan History

    Middle Tier Logging

    (MT) ZENworks Agent logging for communication with the Middle Tier server is enabled in the registry.

    • Location: HKLM\Software\Novell\ZENworks\Debug
    • Name: EnableDebug
    • Type: DWORD Value
    • Data: 0 (Debug log file will NOT be written to)
    • Data: 1 (Debug log file will be overwritten each time)
    • Data: 2 (A new debug log file will be created each time with a unique name)
    • Data: 3 (Debug log will be appended to each time)

    Output: C:\Program Files\Novell\ZENworks\DebugLogs\LGNXTIER.log

    (MT) ZENworks Middle Tier Server logging on Windows servers is enabled in the registry.

    • Location: HKEY_LOCAL_MACHINE\SOFTWARE\Novell\XTier\Configuration\XTLOG
    • Name: Log-Error
    • Name: Log-Warning
    • Name: Log-Informational
    • Name: Log-Success
    • Type: DWORD Value
    • Data: 0 (Debug log file will NOT be written to)
    • Data: 1 (A new debug log file will be created each time with a unique name)

    Output: %System Root%\System32\LogFiles\Xtier

    (MT) ZENworks Middle Tier Server logging on NetWare servers is enabled in the registry.

    • Location: \my server\SOFTWARE\Novell\XTier\Configuration\XTLOG
    • Name: Log-Error
    • Name: Log-Warning
    • Name: Log-Informational
    • Name: Log-Success
    • Type: DWORD Value
    • Data: 0 (Debug log file will NOT be written to)
    • Data: 1 (A new debug log file will be created each time with a unique name)

    Output: SYS:\XTier\LogFiles

    Example: To enable the "Log-Informational" value in the NetWare registry, at the NetWare console type:

    regedit <enter>
    cd software\novell\xtier\configuration\xtlog <enter>
    mk Log-Informational REG_DWORD 00000001 <enter>

    (MT) ZENworks 7 Middle Tier Server logging on Linux servers is enabled in the registry.

    • Location: \my server\SOFTWARE\Novell\XTier\Configuration\XTLOG
    • Name: Log-Error
    • Name: Log-Warning
    • Name: Log-Informational
    • Name: Log-Success
    • Type: DWORD Value
    • Data: 0 (Debug log file will NOT be written to)
    • Data: 1 (A new debug log file will be created each time with a unique name)

    Output: /var/opt/novell/xtier

    Note: To enable xtier debugging on linux, use the xtier regedit utility:

    cd /opt/novell/xtier/bin
    ./regedit

    ls - to list
    ls -l - to get values
    help - for help
    help <function> - for help on function

    For example:

    cd /local_machine/software/Novell/XTier/Configuration/XTLOG
    mkval LOG-Informational REG_UINT32 1

    Restart xtier with /usr/sbin/rcnovell-xsrvd restart
    The log files go to /var/opt/novell/xtier/xterror*.log

    The logs aren't created until the complete initialization, which occurs only after the first request comes in.

    For additional information, check this TID.


    Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

    © 2014 Novell