Forum Discussion
All,
I think I have identified the root cause of this issue.
Using Sysinternals' Process Monitor and KDiff3, I found out that when running Symantec DLO Agent as administrator (in which case it works), dloclientu.exe reads registry keys from
HKLM\SOFTWARE\Wow6432Node\Symantec\Symantec DLO\Client
and several subkeys, including those that contain the info about the location of the DB and NUDF.
However, when running as standard user (same user account, just not elevated), Windows redirects that registry access to the VirtualStore, e.g.
HKCU\Software\Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node\Symantec
That node does not exist because the installer ran with administrative privileges and that was not redirected.
So, I exported the registry key HKLM\SOFTWARE\Wow6432Node\Symantec to a .reg file. I then replaced all occurrences of HKLM\SOFTWARE\Wow6432Node with HKCU\Software\Classes\VirtualStore\MACHINE\SOFTWARE\Wow6432Node (using a standard text editor). Now, I am able to run the DLO agent normally. I have not been able to confirm if it really runs 100%. There may also be file redirection taking place that doesn't cause the agent to fail, but just causes files not to get backed up.
This does not explain why, for me, on Windows 8, it appears to work for several days after installation and fails suddenly.
Maybe this will help someone else,
SA.
- Seco_Tools_UK_L7 years agoLevel 0
I have been trying to sort this out for ages. I just stumbled across this post and it has worked a treat for one user. I would like to have this option so it can be more generic, so that I don't have to change it for every user, but this is way, way further than I have gotten before. Many thanks SA.
Related Content
- 6 months ago
- 12 years ago
- 10 years ago