Norton's Common Client Fiasco

CoolBeans2665 · Corporal Joined: Jul 19, 2003 Posts: 55 Location: USA

My nomination goes to Symantic Corp. for this gem:

Errors when installing the Symantec Common Client program update via LiveUpdate

Situation:
When you run LiveUpdate and download the Symantec Common Client Update you see the error message "LiveUpdate was unable to complete this update. Please contact Technical Support and provide all information displayed on this screen." The error lists various file names. When you close the error message, you see the error message "LU1806: LiveUpdate was not able to install any of the <number> updates that you selected."

You may also see a Runtime error message on the Windows task bar. If you open the error message, you see the Microsoft Visual C++ Runtime Library error message "Runtime Error!...Program: ...APPLIC~1\Symantec\LIVUP~1\DOWNLO~1\EXITEM~1.3_E\spa.exe...abnormal program termination."

Solution:
This problem should be fixed by a Symantec Common Client program update. Do the following to run LiveUpdate and download the latest program updates

1. Start Norton AntiVirus (NAV). If NAV is installed as part of Norton Internet Security (NIS) or Norton SystemWorks (NSW), then start NIS or NSW.
2. Click LiveUpdate.
3. Download all available updates, and restart the computer when prompted.
4. Start NAV (or NIS or NSW), and then run LiveUpdate again. Download all available updates, and then restart the computer again if prompted.
5. Repeat steps one though four until you see the message "Thank you for using LiveUpdate. All of the Symantec products and components installed on your computer are currently up-to-date. Remember to check for new updates frequently."

DarkWinG · Guest

ok, that's clever Razz

but how r u supposed to update the common client if that's realy the prob!!!

the prob is that you cannot update the common client, and there is an error report for that....

Guest · Posted: Fri Oct 10, 2003 4:14 pm Post subject:

When it fails to update the common client, it gives a list of files (with path)that it can't update. Go through each one and rename them to something - e.g. prepend them with 'old' for example. Re-run live update and it will 'install' the common client update successfully.

Then go back to the files and rename them back - because you followed my instructions you can sort alphabetically in details view and make sure you rename them all back.

Don't thank me, I read it somewhere else and am merely a relay.

CoolBeans2665 · Corporal Joined: Jul 19, 2003 Posts: 55 Location: USA

guest · Guest

When I try to rename the files, it says that some of the files are protected operating system files. I am so fed up with this liveupdate crap. I have tried everything in the KB article for error LU1806 and nothing is working.
Here is the error report:

Windows 2000 5.0.2195 Service Pack 4

Common Client Core 1.0.2

LiveUpdate was not able to complete this update.

Please contact Technical Support and provide all information displayed on this screen.
For contact information, go to Help->Technical Support from your Symantec product.

The files below could not be updated by LiveUpdate:
-----------------------------------
File: C:\WINNT\system32\ccPasswd.dl^
99576 Bytes 7/17/2003 10:05:14 v1.0.8.1.
File: C:\WINNT\system32\ccTrust.dl^
95480 Bytes 7/17/2003 10:05:14 v1.0.8.1.
File: C:\PROGRA~1\COMMON~1\SYMANT~1\ccApp.ex^
54520 Bytes 7/17/2003 10:05:14 v1.0.8.1.
File: C:\PROGRA~1\COMMON~1\SYMANT~1\ccEmlPxy.dl^
152824 Bytes 7/17/2003 10:05:14 v1.0.8.1.
File: C:\PROGRA~1\COMMON~1\SYMANT~1\ccEmlUI.dl^
75000 Bytes 7/17/2003 10:05:14 v1.0.8.1.
File: C:\PROGRA~1\COMMON~1\SYMANT~1\ccErrDsp.dl^
120056 Bytes 7/17/2003 10:05:14 v1.0.8.1.
File: C:\PROGRA~1\COMMON~1\SYMANT~1\ccEvt.dl^
185592 Bytes 7/17/2003 10:05:14 v1.0.8.1.
File: C:\PROGRA~1\COMMON~1\SYMANT~1\ccLgView.ex^
144632 Bytes 7/17/2003 10:05:14 v1.0.8.1.
File: C:\PROGRA~1\COMMON~1\SYMANT~1\ccPwdSvc.ex^
99576 Bytes 7/17/2003 10:05:14 v1.0.8.1.
File: C:\PROGRA~1\COMMON~1\SYMANT~1\ccRegMon.dl^
95480 Bytes 7/17/2003 10:05:14 v1.0.8.1.
File: C:\PROGRA~1\COMMON~1\SYMANT~1\ccRegVfy.ex^
58616 Bytes 7/17/2003 10:05:14 v1.0.8.1.
File: C:\PROGRA~1\COMMON~1\SYMANT~1\ccShtDwn.ex^
25848 Bytes 7/17/2003 10:05:14 v1.0.8.1.
File: C:\PROGRA~1\COMMON~1\SYMANT~1\ccWebWnd.dl^
169208 Bytes 7/17/2003 10:05:14 v1.0.8.1.
File: C:\PROGRA~1\COMMON~1\SYMANT~1\SRNew.dl^
107680 Bytes 7/17/2003 10:05:14 v1.0.8.1.
File: C:\PROGRA~1\COMMON~1\SYMANT~1\SROld.dl^
107680 Bytes 7/17/2003 10:05:14 v1.0.8.1.

Guest · Posted: Sat Oct 25, 2003 5:53 am Post subject:

NOTE: this is in response to the post by Jimbo40
Re: NIS 2003 Two Problems
This happens because LiveUpdate is attempting to rewrite files that are already current, and the product catalog file for LiveUpdate does not reflect that they have been updated, which is causing the LiveUpdate to fail.

For example, LiveUpdate installs a Common Client update. The Common Client core gets updated, but the product catalog file shows that they are an earlier version. In this case, 1.0 is listed in Product.Catalog.LiveUpdate, when the version on the computer is actually 1.0.8.1

To fix this, the Product.Catalog.LiveUpdate file must be modified to reflect that the current version is installed on the computer.

To modify the Product.Catalog.LiveUpdate file
Locate the Product.Catalog.LiveUpdate file. (Make sure that you locate the file that begins with "Product" and not a file that begins with a number in front of "Product." The files location varies with the operating system.
Windows 98/Me: C:\Windows\All Users\Application Data\Symantec\LiveUpdate
Windows 2000/XP: C:\Documents And Settings\All Users\Application Data\Symantec\Liveupdate

Right-click the file, click Properties, remove the Read Only attribute, and apply the change.
Open the Product.Catalog.LiveUpdate file in Notepad or similar text editor.
Locate the product that you are having the problem with. In this example, the product is the common client core:

PRODUCT=COMMON CLIENT CORE
PRODUCT DESCRIPTION=COMMON CLIENT CORE

Locate the Version line. This example is a version for the common client core:

VERSION=1.0

Append the correct version number to the end of the version number. For example:

VERSION=1.0.8

Save the file and exit Notepad.
Right-click the Product.Catalog.Liveupdate file and click properties. Change the attributes to Read Only.

Guest · Posted: Sun Nov 09, 2003 1:05 pm Post subject: Thanks!!!!

Well, that worked like a champ. Thanks to the anonymous helper! Glad I stubbornly refused to reinstall as Symantec was insisting I should.

Guest · Guest

Hello

that worked Very Happy

great for me as well.
But initially I only changed the first Version line to 1.0.8.1
instead of 1.0
It did not work....then this morning I thought to myself
let's go with search and replace and replace all
"version" lines, that I did and I went did the update
and it worked great!

Thanks heaps this post is the best one I ever read on internet
to help in dire straits!

ibi
Italy

Guest · Guest

I have the same problem.
My common client updates version number is 1.0.3
I changed it to 1.0.8 // I have version 8.07.17c

Question 1: Was this the right thing to do?

Now When I run the update it doesn't try to update the common client again, but the Norton Internet Security cannot be updated now because it expects the common client to be updated first. Like I said earlier the common client thinks he is up to date now so it will not be updated.

Question 2: How can I solve this problem?

Question 3: Aren't we just faking Norton when we adjust the version numbers? Doesn't this now mean that we think we are up to date, but we aren't?

Thanks for the help, Marco

Guest · Guest

Symantec's solution of uninstalling SystemWorks 2003, deleting items from the Registry, etc., was so extreme, when just editing the Product.Catalog.LiveUpdate file to the current version was the simple solution.

Many thanks for saving me lots and lots of time and frustration.

Acheton · Posted: Mon Nov 17, 2003 3:06 pm Post subject:

Hi all guests, it would be really great if you could register, it's free and makes it far easier to keep track of conversations. Which in turn makes it far easier for us to help you Wink

Remember if you have a problem, regardless of whether it is the same as one for which a thread is already started please start a new thread by clicking on "New Topic".

Thanks.

Ach

esacnitsuj · Posted: Mon Nov 17, 2003 4:21 pm Post subject:

Hi Y'all

I uninstalled & re-installed NAV 2003 & that seemed
to rectify the problem with CCApp Smile

Regards,
esacnitsuj

phoenix22 · Posted: Mon Nov 17, 2003 5:14 pm Post subject:

so did I.........uninstall that is...........then i decided that this was my opportunity to grab some memory....so i went back to syswrks 2k2 pro.....quickly picked up 20mg ram...and this was ram i use here in the boards.....so now i happy........this weekend i am gonna go down for my dlink 624 and firewall fixer upper......plus all the memory i can swallow and another hd..........for back up.....and i have three sys's to do........


	Home ˇ Topics ˇ Submit News ˇ Top 10 This entire site, Cops Themes, and Computer Cops are Š 2002 - 2004 Computer Cops, LLC. All rights reserved. You can syndicate our news using the file RSS 0.91, ultramode.txt, or RSS 1.0. Acceptable Use Policy. Use signifies your agreement. Engine Copyright Š 2002 by PHP-Nuke, GNU/GPL Licensed. ICRA Member. Paul Laudanski, Member of Computer Cops, LLC Server Load: 1026 pages served in previous 5 minutes. Page Rendered: 0.720 seconds.