How to enable verbose Debugging for the Desktop Laptop Option (DLO)

How to enable verbose Debugging for the Desktop Laptop Option (DLO)

Article: 100029177
Last Published: 2021-08-19
Ratings: 1 2
Product(s): Desktop Laptop Option

Problem

How to enable Debugging to troubleshoot Desktop Laptop Option (DLO) issues

 

Solution

  • On the client machine, run the following command from an Administrative CMD prompt from the "C:\Program Files (x86)\veritas\veritas DLO\DLO" or "C:\Program Files (x86)\Veritas\Veritas DLO\DLO  folder":

DLOLoggingu.exe -E dloclientu.exe -L Verbose -LS 500

  • On the DLO Administration Server run the following command from an Administrative CMD prompt from the DLO installation directory; "C:\Program Files\Veritas\Veritas DLO" by default

DLOLoggingu.exe -E DLOAdminsvcu.exe -L Verbose -LS 500    (to Debug issues with the DLO Admin Service)

DLOLoggingu.exe -E DLOConsoleu.exe -L Verbose -LS 500   (to Debug issues with the DLO Admin Console)

DLOLoggingu.exe -E DLORemInstDlgs.dll -L Verbose -LS 500   (to Debug issues with push installs)

*Note*: If the command reports "Failed to find OS bitness. Error=0x5" you have not run this in an Administrative CMD prompt. Correct that and rerun the command.

  • Run the job and reproduce the issue.
    1. ​Select the smallest job that will reproduce the problem.
    2. Run this while no other jobs are running, if possible.
    3. Wait for the error to occur.
  • Collect and send the logs:
    1. Run the DLO Gather Utility.  This utility comes with DLO 7.5x or later and can be downloaded from this article for DLO 7.0  https://www.veritas.com/content/support/en_US/article.100009766
 
  • To disable logging via command line, replace "Verbose" in the above commands, with "Disable" (i.e. DLOloggingu.exe -E dloclientu.exe -L Disable )

 

Warning: The resolution of this issue requires the registry to be edited with the Windows registry editor. Incorrect use of the Windows registry editor can have disastrous results on a server operating system. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
 
 
Manual Registry Debug:
This only needs to be used if the user interface of the Server or Client will not open to be able to perform the normal method listed above.
  1. On the DLO server:
    1. 32 bit server - Goto HKEY_CURRENT_USER\Software\veritas\Components
    2. 64 bit server - Goto HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\veritas\Components   
      1. Create the key Components key if it does not exist
      2. Create a new key called DebugStream
        1. Create a new dword below DebugStream called dloconsoleu.exe
          1. Set the value to 0xFFFFFFFF
        2. Create a new dword called dloadminsvcu.exe
          1. Set the value to 0xFFFFFFFF
        3. Create a new dword called dlomaintsvcu.exe
          1. Set the value to 0xFFFFFFFF
      3. Restart the DLO services
        1. To turn off debug logging the "0xFFFFFFFF" can be changed to a "0"
  2. On the DLO Client 
  • Go to HKEY_CURRENT_USER\Software\veritas\Components

Create the key Components key if it does not exist

Create a new key called DebugStream

Create a new dword below DebugStream called DLOClientu.exe

Set the value to 0xFFFFFFF

  • Go to HKEY_CURRENT_USER\SOFTWARE\Veritas\Veritas DLO\Logger

Create following "String Value" keys:

"ThresholdLevel"="4"
"FileSize"="10"
"BackupFileCount"="50"
"LogCmpression"="1"

  • Restart the client
  • To turn off debug logging the "0xFFFFFFFF" can be changed to a "0"

Notes about the logs: 

The logs are created under -
Client - On Windows 7 and higher: C:\Users\<userName>\AppData\Local\Veritas\DLO\.settings

DLO Server (DLO) - Program Files\Veritas\DLO\Logs
The following logs create a new file each time services restart/debug is turned on:
 
The following logs append (single log file):
DLOClient.log
DLOClient.last.log
DLOadminsvcu.log
DLOadminsvcu.last.log
DLOconsoleu.log
DLOconsoleu.last.log

Was this content helpful?