Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

DLO 7.5 Error V-138-52224-20040

Created: 16 Jan 2013 | 7 comments

I have a test environment with DLO 7.5 there are 67 users on the testing server.  Most of the users are working fine, however there are 10 that are getting this error message a lot V-138-52224-2004 "Failed to copy to the desktop user data folder.  Dedupe engine offline.".  I could not find any documentation on what this error is.  What is this error, and how do get these users backing up properly?

Comments 7 CommentsJump to latest comment

eavinash's picture

 

These issues occur when

·         There is a network connection failure between the agent and the dedupe server.

·         The user backing up the data may not have sufficient privileges to write data to the chunk store.

Could you please verify the above?

 

Jeff Anderson 2's picture

None of the users have rights to the dedup storage location.  Most of the users work without having rights to the dedup area.  In the DLO Admin Guide for 7.5 on page 129, it explains why the users do not need rights to this area.

NIzk99's picture

I've also experienced this for 1 user out of the 10 I've tested with dedupe.  9000+ errors every 7 minutes, all linked to a non-existent web site http://www.symantec.com/business/support/index?page=answers&startover=y&question_box=V-138-52224-20040

Switching the profile back to one without dedupe active fixes the backups, but would like to know how to get this fixed before I start rolling out the dedupe feature to everyone.

 

 

Santhosh_Bhanda's picture

The reason might be agent is unable to communicate to the dedupe server, so please type the following URLs in your browser on agent machine where issue seen.
http://<dedupeserver_ip_or_hostname>:8080
https://<dedupeserver_ip_or_hostname>:8443

Ex: https://172.28.16.122:8443
If the Dedupe Server is active, then the following message is displayed: Dedupe Server Status: (20159) Active.

If there is no response from Dedupe Server, then it indicates that the Dedupe Server is not initialized, and one of the reasons could be that the database connection is down.

 

Jeff Anderson 2's picture

That may be an issue.  I cannot access the Dedupe server by name or IP addess in this way.  I know the dedupe server is running since I see space being used on the Dedupe storage area, so something is wrong.

Santhosh_Bhanda's picture

Can you please check all the firewall ports have been added properly, if you enabled firewall in your environment.To know what all ports need to be enabled, refer page no 143 in SDLO Admin guide 7.5 under section “Symantec DLO Firewall Ports”.

Jeff Anderson 2's picture

The Fix for us was to enable "Log information messages for backup".  In the profile, on the "Options" tab, make sure that this is enabled.