Novell Home

My Favorites

Close

Please to see your favorites.

Enable debug logging in ZDM 6.5 and 7

This document (3112868) is provided subject to the disclaimer at the end of this document.

Environment

Novell ZENworks 7 Desktop Management - ZDM7
Novell ZENworks 6.5 Desktop Management - ZDM6.5
Novell ZENworks Desktop Management Install
Novell ZENworks Desktop Management Agent Install
Novell ZENworks Automatic Workstation Import
Novell ZENworks Automatic Workstation Removal
Novell ZENworks Desktop Management
Novell ZENworks Remote Management
Novell ZENworks Imaging
Novell ZENworks PreBoot Services (PXE)
Novell Application Launcher (NAL)
Novell ZENworks Inventory
Novell ZENworks Middle Tier
Novell ZENworks Wake-On-LAN (WOL)

Situation

Enable debug logging in ZDM 6.5 and 7
Debug registry keys in ZDM 6.5 and 7

Resolution

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
Note: For much greater verbosity during installation of ZFD or ZFD hot patches, use regedit as follows:
  1. Rename "HKEY_CURRENT_USER\Software\Novell\ZENworks\ZWInstal.dll Log" to make a backup.
  2. Create a new "HKEY_CURRENT_USER\Software\Novell\ZENworks\ZWInstal.dll Log" entry defined as a string.
  3. Set the value of the string to "ON" or "1".
  4. Search the log files in \novell\zfdtemp for"entering" and "exiting" to find native function parameters and return information.
  5. Rename the original registry key back to ZWInstal.dll Log to restore the less verbose debugging.
Additionally: You can enable a console install that should show any uncaught exceptions by doing the following:
  1. Create a shortcut to\zenworks\sfiles\bin\setup.exe
  2. Edit the properties of the shortcut and add " ZFD_65 -len installwizard.properties 60 -debug" to the command line
  3. Reproduce the failure and check the console for any exceptions.
Server Install debug loggingfor 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 loggingis 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) Agent loggingis 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 is enabled inside ZENWSIMP.NCF and ZENWSREM.NCF

Location: SYS:\SYSTEM
-Dlogfile=
-Dlogfilelevel=
-Dlogfilelimit=
-Dloglevel=

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

(AWI, AWR) Windows Server debug file loggingis enabled in the registry

Location: HKLM\Software\Novell\ZENworks\AutoWSImport
Name (AWI): zenwsimportCmdLine
Name (AWR): zenwsremovalCmdLine
Type: STRING Value
Data: -Dlogfile= -Dlogfilelevel=

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

(AWI, AWR) Windows Server debug screen loggingis 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= -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 loggingis enabled inside NOVELL-ZDM-AWSI.CONF
Location: /etc/opt/novell/zenworks/zdm
IMPORT_SERVICE_LOGFILE=
REMOVAL_SERVICE_LOGFILE=
loglevel=
logfilelevel=
Output: as specified (default is /var/opt/novell/log/zenworks/AWSI.LOG and /var/opt/novell/log/zenworks/AWSR.LOG)

(Policies) Agent loggingis 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 loggingis 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


(RM) Target Workstation loggingis enabled by default

Location: Program Files\Novell\ZENworks\Remote Management\RMAgent

Output: RMErrorLog*.txt (where * is 0/1/2, etc)

(RM) Remote Management Policy loggingis 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 loggingis enabled by default

Location:

Output: RMErrorLog0.txt


(IMG) NetWare server loggingis enabled at the System Console

PreRequisite: unload IMGSERV.NLM
Console command: IMGSERV -debug

Output: SYS\ZENworks\ZIMGDBG.LOG

(IMG) Windows Server loggingis enabled in the Novell eDirectory Services control panel

PreRequisite: Stop IMGSERV.DLM
Startup Parameter: -debug

Output: C:\ZIMGDBG.LOG
 
(IMG) Linux Server (novell-zmgserv) loggingisalways enabled
 
Output: /var/opt/novell/log/zenworks/preboot/novell-zimgdbg.log
 
(IMG) Workstation loggingis 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 loggingis 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:
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:
(PXE) Windows server logging is enabled in the registry

Location: HKLM\Software\Novell\ZENworks
Name: ZENPXE Log
Type: STRING Value
Data: 1

Output: \system32\ZENPXE.log

(PXE) NetWare server loggingis enabled at the System Console

PreRequisite: unload ZENPXE.NLM
Console command: ZENPXE -debug

Output: SYS\ZENworks\ZENPXE.LOG
(PXE) Linux Server loggingis always enabled

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

(PXE) Windows Transaction Server loggingis enabled in the registry

Logging: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSPService\Parameters
Name: LogLevel
Type: DWORD Value
Data: 80 (Hex)

Output: DTS.LOG

 
Enabling Debug Logging for the Novell Application Launcher
Debug logging for the NovellĀ® Application LauncherTM is enabled in the Windows registry or using the diagnostic tool, naldiag.exe. This section focuses on using the registry to enable debug logging.
NOTE:  The keys in this table are the same as those that are set by nialdiag.exe.
The table below specifies the information you need to edit registry of the workstation where the Application Launcher agent is running:
Registry Key and Hive Location Value Name Value Type Data Notes
HKLM\Software\NetWare\NAL\1.0\Debug Level DWORD 0 (Off) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)



1 (Informational messages only)



2 (Warning messages only)



3 (Informational and Warning messages only)



4 (Critical messages only)



5 (Informational and Critical messages only)



6 (Warning and Critical messages only)



F (All messages)
HKLM\Software\NetWare\NAL\1.0\Debug LogFileLocation STRING location_and_filename_of_output_file Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug Browser
DWORD 0 (Off) Destination: Browser log file as specified



1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug Explorer DWORD 0 (Off) Destination: Application Explorer log file as specified



1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug IPC
DWORD 0 (Off) Destination: IPC log file as specified



1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug Library DWORD 0 (Off) Destination: Library log file specified

 



1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug MUP DWORD 0 (Off) Destination: MUP log file as specified



1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug Reporting DWORD 0 (Off) Destination: Reporting log file as specified



1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug Service DWORD 0 (Off) Destination: NT Services log file as specified



1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug Start DWORD 0 (Off) Destination: Startup log file as specified



1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug Workstation DWORD 0 (Off) Destination: Workstation log file as specified



1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug MSI DWORD 0 (Off) Location: program files\novell\zenworks\
zappmsi.log



1 (On) Alternatively, zappmsi.log is in the path listed in the LogFileLocation string value, if specified



(INV) Scanner logging on the agent workstationis 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: \ZENworks\Inv\server\WmInv\properties\TracerFilter.properties
Data (to enable all debug information): change *default*=BRIEF to *default*=ALL

Output: \ZENworks\Inv\server\WmInv\logs\zenworksinvservice\zenworksinvservice-xxxx.txt

To change the amount of information displayed on the (NetWare) server console, amend
Location: \ZENworks\Inv\server\WmInv\properties\TracerMedia.properties
Data (to enable all debug information): change com.novell.utility.trace.TraceMediumConsole = ON; VERBOSE

Linux:   /var/opt/log/zenworks/inv

(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: \ZENworks\Inv\server\WmInv\logs\Migrationlogs

Output: _migrate.log

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

Location: \1.2\bin\debug.properties
Data (DBexport): DBEXPORT_TRACE=ON
Data (Summary): INVAPI_TRACE=ON
Data (Query): QUERYUI_TRACE=ON

Output: \1.2\bin\DBExportTracer.TXT
Output: \1.2\bin\INVApiTrace.log
Output: \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


(MT) ZENworks Agent logging for communication with the Middle Tier serveris 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 serversis 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 serversis 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
cd software\novell\xtier\configuration\xtlog
mk Log-Informational REG_DWORD 00000001

(MT) ZENworks 7 Middle Tier Server logging on Linux serversis 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 - 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.


(WOL) Details of logging options for Wake-On-LANare covered in TID3004804

Additional Information

Formerly known as TID# 10093312 NOVL97456

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:3112868
  • Creation Date:20-DEC-07
  • Modified Date:30-APR-12
    • NovellZENworks Desktop Management

Did this document solve your problem? Provide Feedback