![]() I can change the registry key ImagePath to point to the correct location, however I am unsure of the exact path that it should be point too. ![]() However, there are multiple files named with eectrl64.sys. File c:\program files (x86)\common files\symantec shared\eengine\eectrl64.sys is not present on the snapshot.Ī registry Key HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\eeCtrl\ ![]() How do I correct this so that there are no longer exemptions to the Backup Exec 2010 R3 jobs. It appears that the latest version of Symantec Endpoint Protection 12 and Backup Exec 2010 R3 do not play well together? I researched this error message and supposedly it indicates that the files are not present, but that there are registry entries. File c:\program files (x86)\common files\symantec shared\eengine\eectrl64.sys. Backup- \\ SERVERNAME \System?State VSS Snapshot warning. ![]() Unable to open the item \\ SERVERNAME\C:\ProgramData\Symantec\Symantec Endpoint Protection\CurrentVer. īackup- \\ SERVERNAME \C: Unable to open the item \\ SERVERNAME\C:\ProgramData\Symantec\Symantec Endpoint Protection\CurrentVer. ![]() Unable to open the item \\ SERVERNAME\C:\ProgramData\Symantec\Symantec Endpoint Protection\CurrentVer.īackup- \\ SERVERNAME \System?State VSS Snapshot warning. Over the weekend, after upgrading to the latest release of Symantec Endpoint Protection V12, I got several errors' on my backups.īackup- \\SERVERNAME\C: Unable to open the item \\ SERVERNAME\C:\ProgramData\Symantec\Symantec Endpoint Protection\CurrentVer. I am running the latest release of Backup Exec 2010 R3, and just upgraded to the latest release of Symantec Endpoint Protection V12. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |