How to enable Debugging for Desktop Laptop Option (DLO)
| Article:TECH51435 | | | Created: 2007-01-21 | | | Updated: 2013-04-04 | | | Article URL http://www.symantec.com/docs/TECH51435 |
Problem
How to enable Debugging to troubleshoot Desktop Laptop Option (DLO) issues
Solution
Debug Steps:
- Set Debug on the DLO server and the DLO Client:
- DLO Server
- Open the DLO Server User Interface and click on Tools --> Support --> Enable verbose logging
- To view the log, click on Tools --> Support --> View Support Log
- DLO Client
- Open the DLO Client User Interface and click on Tools --> Support --> Enable verbose logging
- To view the log, click on Tools --> Support --> View Support Log
- DLO Server
- Run the job and reproduce the issue.
- Select the smallest job that will reproduce the problem.
- Run this while no other jobs are running, if possible.
- Wait for the error to occur.
- Collect and send the logs:
- Run the SymHelp Tool (formerly the BE Support Tool) on each server to collect and send logs. More detail on this tool can be found in http://www.symantec.com/docs/TECH126539
- Be sure to select Full logs for support
- After the Tool has completed the upload of logs from each server to the FTP site, Save and send the Job Log of the job by replying to the Symantec Technician Email or posting it to the case at www.MySymantec.com
- 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.
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.
- On the DLO server:
- 32 bit server - Goto HKEY_CURRENT_USER\Software\Symantec\Components
- 64 bit server - Goto HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Symantec\Components
- Create the key Components key if it does not exist
- Create a new key called DebugStream
- Create a new dword below DebugStream called dloconsoleu.exe
- Set the value to 0xEFFFFFFF
- Create a new dword called dloadminsvcu.exe
- Set the value to 0xEFFFFFFF
- Create a new dword called dlomaintsvcu.exe
- Set the value to 0xEFFFFFFF
- Create a new dword below DebugStream called dloconsoleu.exe
- Restart the DLO services
- To turn off debug logging the "0xFFFFFFFF" can be changed to a "0"
- On the DLO Client
- Goto HKEY_CURRENT_USER\Software\Symantec\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 0xEFFFFFFF
- Create a new dword below DebugStream called DLOClientu.exe
- Restart the client
- To turn off debug logging the "0xFFFFFFFF" can be changed to a "0"
- Goto HKEY_CURRENT_USER\Software\Symantec\Components
Notes about the logs:
The logs are created under -
Client - On Windows 7 and higher: C:\Users\<userName>\AppData\Local\Symantec\DLO\.settings
Client - On XP: C:\Documents and Settings\<userName>\Local Settings\Application Data\Symantec\DLO\.settings
DLO Server (SDLO) - Program Files\Symantec\DLO\Logs
DLO Server (BE-DLO) - Program Files\Symantec\Backup Exec\DLO\Logs
Client - On XP: C:\Documents and Settings\<userName>\Local Settings\Application Data\Symantec\DLO\.settings
DLO Server (SDLO) - Program Files\Symantec\DLO\Logs
DLO Server (BE-DLO) - Program Files\Symantec\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
DLOClient.log
DLOClient.last.log
DLOadminsvcu.log
DLOadminsvcu.last.log
DLOconsoleu.log
DLOconsoleu.last.log
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.
|
|
Related Articles
Legacy ID
288399
Article URL http://www.symantec.com/docs/TECH51435
Terms of use for this information are found in Legal Notices









Thank you.