Did you double check and make sure it is set to automatic in services.msc? If so, try stopping the service, disabling it, and restart the machine. Upon that restart, re-enable the service, reboot once more and see if that works.

When in doubt with XP, reboot, reboot, reboot. :-)

Hi Michael,

Is this happening on any specific make of machines ?

Also, is this a fresh deployment or an upgrade from a previous version of SEP ?

Please let me know on the above.

Thanks :-) 

Can I please get a response?  I received no response from Here2Help almost a full week ago after I replied to his question.

Thank you.

Michael R.

I apologize for the delayed response Michael. Do you see any other errors in the event viewer application logs on the machines in question ?

Thanks :-) 

I know I've posted this in more than one location but it seems relevant to this thread as well -

We've also had a problem with 3 out of 19 machines on our network. Hopefully this helps SOMEBODY out there with this problem. Basically what it all boiled down to was an uninstall of SEP on the client machine with a repush of the install. Here's the steps I took to getting my problem client machine working again. All of this was done from the local admin account on a Vista Business 32-bit machine.

1.) Installed MSXML 4.0 SP3, rebooted and no fix

2.) Installed MSXML 6.0 core services, rebooted and no fix

3.) Checked the access permissions for the Symantec install folder and set the folder to be accessed from the local admin account, rebooted and no fix.

4.) Uninstalled from the client machine and rebooted.

5.) Logged back into the machine under the domain username for the machine.

6.) Did an install push from the local server again.

7.) Everything's A-OK.

Sorry for the redundance, but this might work.