How to enable Debugging for Desktop Laptop Option (DLO)

  • Article ID:100029177
  • Modified Date:
  • Product(s):

Problem

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

 

Solution

Debug Steps for DLO versions 7.x and higher:
 
  1. On the client run the following command from an Admin CMD prompt from the "C:\Program Files (x86)\veritas\veritas DLO\DLO" or "C:\Program Files (x86)\Veritas\Veritas DLO\DLO  folder":
    1. DLOLoggingu.exe -E dloclientu.exe -L Verbose -LS 500
  2. On the DLO Admin Server run the following command from an Admin CMD prompt from "X:\Program Files\veritas\veritas DLO" or "X:\Program Files\Veritas\Veritas DLO"
    1. DLOLoggingu -E DLOAdminsvcu.exe -L Verbose -LS 500   (to Debug issues with the DLO Admin Service)
    2. DLOLoggingu -E DLOConsoleu.exe -L Verbose -LS 500  (to Debug issues with the DLO Admin Console)
    3. DLOLoggingu -E DLORemInstDlgs.dll -L Verbose -LS 500  (to Debug issues with push installs)
  3. 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.
  4. Collect and send the logs:
    1. Run the DLO Gather Utility.  This utility comes with DLO 7.5x and can be downloaded from this article for DLO 7.0. https://www.veritas.com/docs/000018269
 

* To disable logging via command line, replace "verbose" with "disable." (i.e.DLOloggingu.exe -E dloclientu.exe -L Disable)

 

 Debug Steps for Backup Exec DLO versions: 

  1. Set Debug on the DLO server and the DLO Client:
    1. DLO Server
      1. Open the DLO Server User Interface and click on Tools --> Support --> Enable verbose logging
      2. To view the log, click on Tools --> Support --> View Support Log
    2. DLO Client
      1. Open the DLO Client User Interface and click on Tools --> Support --> Enable verbose logging
      2. To view the log, click on Tools --> Support --> View Support Log
  2. 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.
  3. Collect and send the logs:
    1. Run the DLO Gather Utility.  This utility comes with DLO 7.5x and higher and can be downloaded from this article for DLO 7.0. https://www.veritas.com/docs/000018269
  4. Debugs should be turned off after the issue is resolved and the logs can be deleted. Each step of the debugs mentioned above need to be undone.  
     
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 
    1. Goto HKEY_CURRENT_USER\Software\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 DLOClientu.exe
          1. Set the value to 0xFFFFFFFF
      3. Restart the client
        1. 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
Client - On XP: C:\Documents and Settings\<userName>\Local Settings\Application Data\veritas\DLO\.settings 
DLO Server (SDLO) - Program Files\veritas\DLO\Logs
DLO Server (BE-DLO) - Program Files\veritas\Backup Exec\DLO\Logs
The following logs create a new file each time services restart/debug is turned on:
 
The following logs append (single log file):
ServerName-SGMon.log
DLOClient.log
DLOClient.last.log
DLOadminsvcu.log
DLOadminsvcu.last.log
DLOconsoleu.log
DLOconsoleu.last.log

Related Articles

How to Debug Backup Exec - Agent & Options debug log gathering list

Was this content helpful?

Get Support