Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Directory/file not found - System32\config\COMPONENTS{...}.TxR.0.regtrans-ms

Created: 14 Mar 2014 • Updated: 14 Mar 2014 | 4 comments

I keep getting the following Completed with exceptions but on a sporadic basis

SBE 2012 with all SP's and hotfixes on Server 2008R2 Standard

Server 2008R2 VM on Server 2008R2 Enterprise host

Incremental backup

Job ended: Wednesday, March 12, 2014 at 11:09:22 PM
Completed status: Completed with exceptions

Backup- \\ServerName-01.domain.local\C:
File Windows\System32\config\COMPONENTS{860bd695-f677-11e2-88ae-00155d328b03}.TxR.0.regtrans-ms was not found, or could not be accessed.

File Windows\System32\config\COMPONENTS{860bd695-f677-11e2-88ae-00155d328b03}.TxR.1.regtrans-ms was not found, or could not be accessed.

File Windows\System32\config\COMPONENTS{860bd695-f677-11e2-88ae-00155d328b03}.TxR.2.regtrans-ms was not found, or could not be accessed.

File Windows\System32\config\COMPONENTS{860bd695-f677-11e2-88ae-00155d328b03}.TxR.blf was not found, or could not be accessed.

When I search the config folder I do find COMPONENTS files, but the names are different.  I'm assuming these files change on a continual basis and so more than likely can't exclude them w/out excluding the entire config folder.  I would think that there is a setting required to accomodate these ever changing file names. 

I've done my searching and have not found anything dealing with the above specific issue.  Any ideas as to how to mitigate this problem from continuing? 

thanks,

Operating Systems:

Comments 4 CommentsJump to latest comment

CraigV's picture

Hi,

Do you use Advanced Open File Option in your job? If not, turn it on and check your backups to see if this happens again.

THanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

pkh's picture

If these files/directories do not exists, then these are orphaned entries in the registry from some installation/uninstall.  You either live with the error messages or put a dummy file/directory with the same name in the same location.