Forum Discussion

Artegic's avatar
Level 6
11 years ago

V-79-57344-33967 on ProgramData\Symantec\CRF

The last run of the self-backup job for my BackupExec 2012 media server produced a bunch of error messages like this:

Datei ProgramData\Symantec\CRF\4f5ea992a6d24e92b9873a39bda85b5f\bin\App_Web_l2vxmiah.dll wurde nicht gefunden, oder es war kein Zugriff möglich.
V-79-57344-33967 - Das Verzeichnis bzw. die Datei wurde nicht gefunden, oder der Zugriff ist nicht möglich.
Element \\GOLGI.artegic.local\C:\ProgramData\Symantec\CRF\4f5ea992a6d24e92b9873a39bda85b5f\bin\App_Web_l2vxmiah.dll wird gerade benutzt - übersprungen.

English translation:

File ProgramData\Symantec\CRF\4f5ea992a6d24e92b9873a39bda85b5f\bin\App_Web_l2vxmiah.dll wasn't found, or no access was possible.
V-79-57344-33967 - The folder or file wasn't found, or the access wasn't possible.
Element \\GOLGI.artegic.local\C:\ProgramData\Symantec\CRF\4f5ea992a6d24e92b9873a39bda85b5f\bin\App_Web_l2vxmiah.dll is currently in use - skipped.

All reported files are within the folder "ProgramData\Symantec\CRF", so apparently they belong to BackupExec itself.

What's happening there? Shouldn't Backup Exec be able to access its own files? Should I worry?

  • Hopefully final update: The support engineer asked me to add the folders

    C:\Program Files\Symantec

    to the exclusion list of Kaspersky Anti-Virus' real time protection. Since then, the continuous recreation of files and directories has stopped and the error message during incremental self backup does not occur anymore.

    So lmosla's first hunch was right. The problem was with the virus scanner.

    Seems the case is finally solved. Sure, it does make me somewhat uneasy to exclude parts of the filesystem from virus protection. But this machine runs nothing else but Backup Exec and has no users except administrators and backup operators, so I guess the risk is acceptable.

17 Replies