Communications with the DLO services are down. Check to see if DLO services are running on server
V-138-57364-16
V-138-52224-270
V-139-57364-16
V-139-52224-270
1. Log onto the DLO server using the DLO service account. If not logged on as the DLO service account, ensure that logged on user has been granted Administration rights in DLO
2. Verify that SQL service for DLO and DLO Administration Service are running.


3. Update the password of DLO Administration Service logon account in services.msc

4. Verify that the following Registry keys contain correct values for Server Name and DB instance name.


5. Ensure that the "DLOAgent" folder is shared.

6. Verify SQL permissions for DLO service account.
Verify if DLO service account has “sysadmin” rights.

Verify if DLO_Administrator role is assigned to DLO service account.

7. Take a backup of DLO and Dedupe databases and run the following scripts.
DLODB Path: C:\Program Files\Veritas\Veritas DLO\Data
DedupeDB Path: C:\Program Files\Veritas\Veritas DLO\Dedupe\Database
-----------------------------------------
DLO Installpath>osql -E -S %COMPUTERNAME%\DLO -d DLO -i DLODBUpgrade20.sql
DLO Installpath>osql -E -S %COMPUTERNAME%\DLO -d DLO -i DLODBUpgrade30.sql
DLO Installpath>osql -E -S %COMPUTERNAME%\DLO -d DLO -i DLODBUpgrade.sql
DLO Installpath>osql -E -S %COMPUTERNAME%\DLO -d DLO -i DLODBInstallXSP.sql
-----------------------------------------
Where,
%COMPUTERNAME% = Name of the server running SQL instance for DLO.
DLO = Name of the SQL instance of DLO database.
Example:

8. Exclude DLO exe files and paths from antivirus scans, as mentioned in the following article :
https://www.veritas.com/support/en_US/article.100047617