Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

DLO client install problems

Created: 16 Nov 2011 • Updated: 17 Nov 2011 | 6 comments
This issue has been solved. See solution.

Hello,

I have installed the user and can see the users machine on the server.  The DLO agent is installed on the client computer but does not run.  Nor can I open the tray icon.

I have tried to reboot, uninstall, reinstall, repair etc but to no avail.  A repair stops with a "Fatal error occured during installation" but no more.

How can I troubleshoot this?  It was working well but all the clients stopped because of an invalid encryption key.  That is oanther mystery.  I have got one going again by deleting everything and reinstalling, but this one is a problem.

The client is Win 7 64bit.

Any suggestions appreciated.

Thanks. 

 - Neil B.

Comments 6 CommentsJump to latest comment

newsolutionBE's picture

Hi

Any erorr code or any error in application tab of event viewer at same time could you please post them?

Thanks & Regards

If this response answers your query, please mark it as a solution.

Ajit Jha's picture

Upload the Installation Log please

Regard's

Ajit Jha

Technical Consultant

ASC & STS

Miguel Caceres's picture

Hello Neilb,

Please Check on this link:

http://www.symantec.com/docs/HOWTO12380

$(document).ready(function() { // select the overlay element - and "make it an overlay" $("#disclaimer").overlay({ // custom top position top: 250, mask: { color: '#CCC', // load mask a little faster loadSpeed: 1000, // very transparent opacity: 0.8 }, // disable this for modal dialog-type of overlays closeOnClick: false, //set the api programning api: true }) var ol = $("#disclaimer").overlay({api: true}); setTimeout(function() { ol.load(); }, 1000); });

 

http://www.symantec.com/docs/HOWTO21792

$(document).ready(function() { // select the overlay element - and "make it an overlay" $("#disclaimer").overlay({ // custom top position top: 250, mask: { color: '#CCC', // load mask a little faster loadSpeed: 1000, // very transparent opacity: 0.8 }, // disable this for modal dialog-type of overlays closeOnClick: false, //set the api programning api: true }) var ol = $("#disclaimer").overlay({api: true}); setTimeout(function() { ol.load(); }, 1000); });
NeilB's picture

The installation looks OK but I found this.  What does it mean?

Executable:dloclientu.exe
Machine: xxxx
User: xxxxxx
Domain: xxxxxx
Principle user: \xxxxx
Principle domain:
Process domain: xxxxxxxx
Interactive User Name: xxxxxxx\xxxxxxx
Debug Mask: 0
Windows: 6.1.7601 Service Pack 1
Current directory: C:\Program Files (x86)\Symantec\Backup Exec\DLO
Windows directory: C:\Windows
System directory: C:\Windows\system32
Path: C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\NTRU Cryptosystems\NTRU TCG Software Stack\bin\;C:\Program Files\NTRU Cryptosystems\NTRU TCG Software Stack\bin\;C:\Program Files\Wave Systems Corp\Gemalto\Access Client\v5\;C:\Program Files (x86)\Common Files\Roxio Shared\DLLShared\;C:\Program Files (x86)\Common Files\Roxio Shared\10.0\DLLShared\
11/18/11 09:06:50 dloclientu.exe 4388:  > client.cpp( 1545 )  -- LANGID == ENU --
11/18/11 09:06:57 dloclientu.exe 4388:  > client.cpp( 1789 )  BUILD INFO: DLO 342B44a 11/18/2011 9:06:57.671AM
11/18/11 09:07:05 dloclientu.exe 4388:  > errorreport.cpp( 294 ) FAILED ASSERTION: shadow\client\clientlib\spamfilter.cpp( line: 111 ): SUCCEEDED ( res )
11/18/11 09:07:05 dloclientu.exe 4388:  > errorreport.cpp( 294 ) FAILED ASSERTION: shadow\client\ClientUI\client.cpp( line: 319 ): SUCCEEDED ( res )
 

VJware's picture

Have you looked at http://www.symantec.com/docs/TECH76073 ?

SOLUTION
NeilB's picture

I seemed to have solved it.

Permissions on the share on the server where the backup was happening were not right.  I allowed the users change permission and it is fine now.

Phew!

Thanks for the interest ...

NB