Forum Discussion

Jeff_Anderson_2's avatar
13 years ago

DLO 7.5 Error V-138-52224-20040

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?

7 Replies

  •  

    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?

     

  • 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.

  • 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.

     

  • 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.

  • 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”.

  • 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.