From: Darryl Champagne [dgc03052@adelphia.net]
Sent: Friday, August 11, 2006 9:11 PM
To: 'Symantec Technical Support'
Subject: RE: 'Case=002-372-278'
OK, I followed both processes, which takes a huge amount of time.
The autofix tool in the steps to remove and replace... could never succeed at removing the temp files, enabling seeing system directories and such (although they were already enabled, along with show all files and such), but I manually cleaned out the temp directories, internet caches and so on, rebooted, and continued.  Running the intelligent updater did nothing, because I had previously run LiveUpdate, which found nothing to update.
With a fresh directory for LiveUpdate, there was all of a 2 handle change - the first time after reboot Symlcsvc.exe starts with 88 handles, then you see the Rules created for LiveUpdate dialog, and the handles used goes up to 136.  Running LiveUpdate found nothing to update, and raised the number of handles to 176 (leaked 40 handles).  Running LU again leaked the regular 42 handles, raising the number in use to 218, then 260, then 302 in subsequent runs.
 
So, the issue is not resolved.  As before, I should be able to run my system for 2 weeks or so before it starts getting unstable, and must be rebooted.  I have gone and reconfigured the default time interval to run LiveUpdate (via the control panel for LiveUpdate) from the default 2 hours to 12, which should at least keep my system stable for a Month, but the License manager is still clearly leaking handles, which eventually leads to system instability (and probably causes performance problems well before that).
 
dgc


From: Symantec Technical Support [mailto:technicalsupport@symantec.iseva.net]
Sent: Friday, August 11, 2006 5:40 PM
To: Darryl G. Champagne
Subject: RE:'Case=002-372-278'

Greetings Darryl,
 
We welcome you back to our Symantec Online Technical Support, your customer service at all times.
 
Darryl, I acknowledge your inconvenience and will do my best to resolve the issue that you are encountering. I need your cooperation and patience in resolving this issue.
Darryl, this issue can be caused by damaged LiveUpdate files. In order to fix this issue, you will need to follow the steps provided below:
 
-- Remove damaged LiveUpdate files
-- Replace damaged LiveUpdate files
 
For instructions on how to perform these steps, please refer the article in the link provided below:
 
Title: 'How to remove and replace damaged LiveUpdate files'
Document ID: 2004030908410213
> Web URL:
http://service1.symantec.com/Support/sharedtech.nsf/docid/2004030908410213?Open&src=con_ols_nam
 
In the mean time to download the latest virus definitions, I would suggest that you run Intelligent Updater. Please refer to the link below for detailed instructions:
 
Title: 'How to update virus definition files using the Intelligent Updater'
Document ID: 1998082013035306
> Web URL:
 
Please let me know if the issue has been resolved.
 
Regards,
 
Navin Singh
Symantec Authorized Technical Support

Prev Next