• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 907
  • Last Modified:

"Error Code: 0x80004005” error message on XP SP2 client every time we install corporate Symantec Antivirus - URGENT - THX

Greetings One and All,

I am hoping that someone here can help us out on a truly perplexing issue. We recently installed a new dedicated Antivirus server (W 2003 Enterprise SP2) running Symantec Antivirus Corporate This is exactly the same version we had on the older server (no longer available) and we never had any issues. The new server also runs smoothly, does all tasks that you request from the console (e.g. scan and update clients, etc...) and we had no problems with it until I tried to install the client on a newly imaged (Ghost 8) system. Then the issues started. Initially the client went into a reboot loop after the antivirus was installed. This happened to every image we have (numerous different HP hardware platforms, including DC7800 and DC5800). I then rebuilt the images from scratch (using new CD's) and everything works until I install the antivirus and it then gives me this error ""Error Code: 0x80004005” (http://support.microsoft.com/kb/306081) error message after it informs me that there are not sufficient resources to log on the account. It does this for all images and all hardware types. The system logs the account off after that and you cannot get in at all (safe mode works but I cannot remove the antivirus that way). Which means that I have to re-image every time I test again. I have tried logging in locally vs domain and same error. I have tried stopping the Symantec services (set to manual in safe mode) and still same error. We have tried using a variety of o/s installations, including images, original HP CD's and also the pre-installed o/s and all with the same result after the antivirus is installed. We have tried installing the antivirus through the server (vphome), from the cd locally and over the network and we still get the bloody error. We have installed the antivirus before and after joining the domain (2003 AD mixed). We have tried exluding recent MS updates (no change). I did notice that the error happens after I do the live update, i.e. the XP SP3 systems we use are okay until the reboot after live update. I did manage to get two machines to work, but cannot replicate the success for other machines with the same hardware and o/s image following the same process. I highly suspect that it is the antivirus server or the install on it that is causing the issue, but there is nothing in the event logs that suggests a problem. Our next step is to install the anti virus server on another machine and to test XP SP3 clients against it. Any idea's, thoughts... Any and all help is greatly appreciated and I thank you all in advance.
Laszlo Denes
Laszlo Denes
  • 2
2 Solutions
u will try to change ur ram,and hard disk data cabel, and incrage the capecity of ram,
 just try it.and also chk proper installed media ( xp sp2,)
Laszlo DenesAuthor Commented:
It happens on 30+ different brand new systems and their o/s (SP3 as noted) + everything else is okay until we install the Antivirus (same version we have used for years but on a new server). It only happens after the antivirus. Please read the question before responding. Thanks.
you do realize that product is no longer supported by symantec right?
So you are going to fix a product that is downloading revised virus definitions (that protect you against virus whos behaviour has change) rather than download full defitions that will protect your client from new viruses.
Im just saying dont waste your time trying to fix this issue go to sep11ru6mp1 otherwise you are looking at installing sav 10.1.9 which is almost at the end of life.
Laszlo DenesAuthor Commented:
This is the version that we use and I cannot just switch it over. However, I have resolved the problem. The issue was a small switch (between the imaged systems and the network) that we use in our lab. :-)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now