This is is usually seen with a System State Backup and is not caused by Backup Exec it is caused by individual software vendors not correctly registering critical components that are then linked to the System State. (because it is System State backup CraigV's answer above will not help)
As such there is no single fix as it is unique to the individual files. We have seen his caused by both using unix style path statments in the Windows Registry or uninstall routines not removing their registry information correctly.
Typically the routine is
a) If file name is unqiue to a software vendor contact that softwre vendor to get assistance with cleaning up the registry - as a lsat resort try san find the registry entry yourself - would recommend starting in area of resgitry relating to services as a first place to look.)
b) If the file name is generic and does not exist in the specified path then either try to find the registry entry yourself OR create a dummy file in same path with same name
c) if the fiel name is generic and does exist then it is probably a unix style path statement somewhere (typically the / character may have been used instead of the \ character in a path)
