Forum Discussion

Jens_J_nsson's avatar
Jens_J_nsson
Level 3
20 years ago

V-79-57344-65247 - A failure occurred reading an object.

I'm getting this error every time I backup Shadow Copy Components on a Windows 2003 server.

When I search http://support.veritas.com I'm pointed to this document: http://seer.support.veritas.com/docs/265282.htm

But I have never moved Event Logs to a different direction and therefor I can't make the suggested solution.

Can anyone help me to solve this problem ?

Thanks in advance,

Jens Jönsson
jcj@itf.dk
10.x and Earlier
Backup and Recovery
Backup Exec

33 Replies

Sort By
Show More
  • Renuka_-'s avatar
    Renuka_-
    Level 6
    19 years ago
    Hello Jens,
    Sine your problem occurs on the BE server itself the solution to reinstall remote agent does not apply for you.On the BE server the remote agent service is installed as part of the BE installation.
    You may nevertheless create a new job, stop all antivirus scans and try the backup.

    NOTE : If we do not receive your reply within two business days, this post would be marked assumed answeredand would be moved toanswered questions pool.
  • Jens_J_nsson's avatar
    Jens_J_nsson
    Level 3
    19 years ago
    This has been solved after applying latest updates from Microsoft including SP1.

    Thanks in advance,

    :-) Jens
  • Marke2112's avatar
    Marke2112
    Level 2
    15 years ago
    I realize that this is an old posting but I was experiencing this exact same issue with BE 11d and couldn’t find any posted solutions.  This was a frustrating situation and perhaps this posting can help someone else resolve it as well.

    The error being reported is below: 

    \ \<SERVER>\System?State
    A failure occurred reading an object.
    WARNING: \\<server>\System?State\SYSVOL\SYSVOL\5d6599af-7dbb-44ff-998a7b28ae354b4b  is a corrupt file.
    This file cannot verify.

    In my potentially unique circumstance, I had upgraded the server (backup client) experiencing the problem from Windows Server 2003 R2 to Windows Server 2008.  To account for all of the old OS path entries in the registry that might still point to the old C:\WINNT rather than the new C:\WINDOWS, Microsoft creates a link in the root of the boot partition called C:\WINNT that points to C:\WINDOWS.  It’s a simple hack to solve many potential path issues stemming from an OS upgrade. 

    It turns out that the key in the registry for the SYSVOL repl entry that was failing (above) still had the old C:\WINNT path.  I changed this path entry to be C:\WINDOWS\... in the registry and it fixed the problem. 

    I DO NOT RECOMMEND OR SUPPORT THIS TYPE OF FIX TO ANYONE AS THE RISKS ARE HIGH.  I AM JUST SHARING MY SOLUTION IN CASE IT MIGHT PROMOTE DISCOVERY OF A POTENTIAL SOLUTION FOR YOUR PARTICULAR SITUATION.  (cma).

    Good luck.

    Mark