10-09-2013 06:24 AM
I have added dummy files in the path but still receiving error. I have also added a global exclusion for EENGINE folder on any server.
10-09-2013 07:04 AM
Have you tried rebooting the server on which you performed the upgrade.
10-09-2013 08:33 AM
Yes, the server was rebooted.
10-16-2013 05:32 AM
Our weekly full job ran this weekend with the same results....the job completed successfully except for the SEP files. Anyone have any idea how I can get a clean SystemState backup?
10-16-2013 07:14 AM
Unfortunately this is probably another manifestation of a regular issue coverd in
http://www.symantec.com/business/support/index?page=content&id=TECH126412
http://www.symantec.com/business/support/index?page=content&id=TECH126412
and
http://support.microsoft.com/kb/955078
Mind you I am not sure why creating a dummy file has not resolved it, however somewhere in the registry is likely to be references to
c:\program files (x86)\common files\symantec shared\eengine\eectrl64.sys
Although you may need to either post on the SEP forum, OR log a support case against SEP to find out where in the registry the problem lies. Please be aware that if you try to find this yourself, then editing the registry is at your own risk and we would recommend you export the registy (or at least that area of the registry) before you make any changes.