Symantec/XP Norton Antivirus conflicts

  • Thread starter Thread starter I approved this message
  • Start date Start date
I

I approved this message

Hi All,

I know this is a Microsoft group, but Symantec's Mr. Padmasumbava in India
couldn't help me. Maybe one of you can.

Got a brand new Norton SystemWorks 2005, which includes Antivirus. It
simply will not work on my XP computer. I followed the instructions to the
letter, several times through repeated install/uninstall cycles. I am 100%
certain that I purged all traces of SystemWorks 2003 from my computer before
installing 2005. Between install/uninstalls of 2005, I did the same. Even
reinstalled SP2 (twice).

The error message I get is: "3029,27. Internal program error, uninstall and
reinstall Norton Antivirus."

Naturally, the discussion in the Symantec group blames XP SP2 for the
problem. I find that hard to believe, given Symantec's track record of
installation problems.

Thank you ANY help.
 
I have XP SP2 am still using Norton 2003, with virus updates. However, I
recall having to wait for a patch from Symantec before installing SP2. So,
one possibility is to remove SP2, install version 2003, do the Norton Live
Update to get the pre-SP2 patch, as well as new virus definitions, then
install SP2.

Another possibility is to try remove SP2, installing 2005, Live Update it,
then install SP2.

A couple of other random thoughts:

I assume the Norton (2003 or 2005) is the only antivirus software on your
computer? Running multiple antivirus software is probably not a good idea.
Be aware that some firewalls also include antivirus oftware.

I once had trouble installing an earlier System Works, and solved the
problem by first copying the whole CD to a dummy directory, then performed
the install from there. I never did learn why it refused to install from
the CD.

When installing fundamental software, be sure that no other application
software is running. For example, something like the GOBACK or TAKETWO
could interfer with an installation.

Finally, as painful as it will be, try Symantec support, politely stress
that followed the advice of Mr. S, and request new advice. The odds of
getting the same support person are close to zero, and not all support folks
are equally qualified. If the advice of the second Mr. S does not solve the
problem, call back and continue to be polite (no matter how you really feel)
and firmly request to speak to a supervisor.

Finally, check the support website for install issues and solutions.
Symantec is NOT good about admiting they have a problem and do not know the
answer, but when they find the soloution they will post it.
 
Thanks.

This whole mess started because our NAVE 2003 subscription was coming to an
end, and we figured why not buy the new software? Big mistake.

Maybe I'll just purge all 2005 from my system and go back to 2003.

I also was unable to install SystemWorks 2003. Finally gave up and ran all
utilities from the CD.

Not sure I want to tackle uninstalling SP2. I think going back to NAV 2003
is the sure thing. Christ, it's not like SP2 is "new" software. There are
only about 1 billion copies out there.

I just don't see how Symantec hasn't been hit with a class action consumer
fraud suit.
 
The error message I get is: "3029,27. Internal program error, uninstall and
reinstall Norton Antivirus."

Naturally, the discussion in the Symantec group blames XP SP2 for the
problem. I find that hard to believe, given Symantec's track record of
installation problems.
Click to expand...

I don't know how to fix your installation issue but "Internal program
error" is coming directly from the Symantec software. Apparently this is a
common enough problem that Symantec has an article on this error in their
Knowledge Base:

Error: "Norton AntiVirus 2005 has encountered an internal program error . . . " (3029,27)
http://service1.symantec.com/SUPPOR...mWorks&ver=2005&src=sg&pcode=nsys&svy=&csm=no

If you have a problem with that ridiculously long URL, go to the online
Symantec support site http://www.symantec.com/techsupp/support_options.html

and select free support. Enter Norton System Works in product field and
2005 for the version. On the next page, elect to search their Knowledge
Base and type the following into the search box: internal program error
3209,27

You'll get two links in the search results: one for System Works 2004 and
another for System Works 2005.
 
Thanks, but I know about the Symantec link. The proposed fix is worthless.
Symantec says the same thing for every problem: Uninstall and re-install,
as if that's magic.
 
Symantec has (or used to anyway) a small utility (symcln.exe) that cleans
all references to its software from your system if its regular uninstall
routine leaves things behind. I don't know if this would help in your case,
but you might want to check it out. I don't have a link, but if you do a
search on Symantec's site, hopefully you can find it.

Bruce
 
Thanks, but I know about the Symantec link. The proposed fix is worthless.
Symantec says the same thing for every problem: Uninstall and re-install,
as if that's magic.
Click to expand...

I understand your frustration but the point is that this error has been
reported enough times to Symantec's tech support (and through two
versions), that it is documented in their knowledge base. Problems of this
type and the Symantec provided "solutions" are why I no longer recommend or
use their products.
 
Thanks, but I tried it.

Bruce Phillips said:
Symantec has (or used to anyway) a small utility (symcln.exe) that cleans
all references to its software from your system if its regular uninstall
routine leaves things behind. I don't know if this would help in your
case,
but you might want to check it out. I don't have a link, but if you do a
search on Symantec's site, hopefully you can find it.

Bruce
Click to expand...
 
As I've said before, sooner or later Symantec is going to get hit was a
major consumer fraud, class-action lawsuit. I've been scouring the 'net
looking for solutions. As you suggested, I'm not the only one who had this
problem.
 
To be honest I don't see where there is any fraud being committed. But maybe
trying a custom install of SystemWorks without NAV and doing a live update,
reboot and then trying an install of NAV.
I approved this message said:
As I've said before, sooner or later Symantec is going to get hit was a
major consumer fraud, class-action lawsuit. I've been scouring the 'net
looking for solutions. As you suggested, I'm not the only one who had
this problem.
Click to expand...
 
To be honest I don't see where there is any fraud being committed.

Knowingly selling a defective product = fraud.


Michael said:
To be honest I don't see where there is any fraud being committed. But
maybe trying a custom install of SystemWorks without NAV and doing a live
update, reboot and then trying an install of NAV.
Click to expand...
 
Just because something does not work for you does not mean it is fraud. Both
SystemWorks and Internet Security 2005 on my system work fine. I downloaded
the SP2 patch before I installed.
 
Knowingly selling a defective product = fraud
If this was truly defective then it should not work for anyone. Since it
works for some and not others I believe there are issues that Symantec needs
to get answers for but I believe the word "fraud" is not the correct term
here.
I am fully aware of the problems with Symantec just peruse this newsgroup
daily and it is apparent. I believe Symantec is in the same category as
Microsoft good intentions but no contingencies for problems.
 
Hope you don't mind my twopenneth, but I presume you are putting SP2 on
before the Norton stuff? Just a thought. I have System Works 2005 ( which
is supposed to SP2 compliant - as I'm sure you know), and although I didn't
have your problem, I sympathise. I'm finding some of Norton's features, and
notions of customer support, ridiculous. As someone recently said, one of
the biggest mistakes in consumer history was for people, including
governments, to have allowed the current situation to exisit, namely, that of
software being licenced, rather than sold. What else could you buy that
refused to promise to be fit for anything, and took zero responsibility for
whatever happened as a result of its use?
 
Back
Top