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

[Jens_J_nsson]

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

[uz]

the following forum entry had similar problems and were solved after applying anonymus support - as mentioned by VERITAS "Renuk a":

http://forums.veritas.com/discussions/thread.jspa?forumID=103&threadID=49092

Don't know whether this will fix your problem to, but give it a try:

http://support.veritas.com/docs/238618

regards

uz

[Renuka_-]

Hello,

Uninstall and reinstall of the remote agent may also help. Also you could check if the device is installed on a RAID controller if so you need to change it to scsi.

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.

[Rob_de_Vries]

Sorry, problem does not comply wit server2003.

Problem still exsist, still can't backup system stateMessage was edited by:
Rob de Vries

[Jens_J_nsson]

Can you please tell me how to re-install the remote agent ?
In my case Backup Exec is installed on the server which it has problem backing System State up on.

Backup drive is installed on a separate SCSI-controller, not on the RAID-controller.

Still, there's no problem backing System State up from NT backup.

:) Jens

[Renuka_-]

Hello Jens,
The remote agent can be uninstalled from add/remove programs, to re-install the remote agent please follow this technote:

http://support.veritas.com/docs/265736

Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm

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]

I'll try your suggestion and get back to this thread with the result.
I'm quite busy here at the moment and going on holiday soon, so maybe it will be August before I get to work with this issue again. Just to let you know why you don't hear anything....

:) Jens

[Rob_de_Vries]

Jens, I hope this works for you too !

The problem is solved over here (in a test run), Hope it works as good in the schedule
Thnx for that Veritas. It took a while but now i can sleep well again.

:) Rob

[Sharvari_Deshmu]

Hello,

Please update us once you are back.


Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm


NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.


Thanks,

[Jens_J_nsson]

Sorry Renuk,

> The remote agent can be uninstalled from add/remove programs

No, I can't find the remote agent in "Add/Remove programs".
There's only listed the following:

VERITAS Backup Exec for Windows Servers
VERITAS Device Driver Install
VERITAS Update

So how can I un-install the Remote Agent ?

Re-installing the remote agent doesn't help at all....

Thanks in advance,

:) Jens

[Amruta_Purandar]

Hello,

Are you trying to uninstall Remote Agent from the same server where Backup Exec is installed? If yes, then this is not possible.

Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Jens_J_nsson]

Yes I am....

How do I solve the problem then ?
When I installed build 5520 I also did a completely uninstall of the former build.

So how do I solve the problem if I can't uninstall the Remote Agent ?

Help me please! Customer is really pissed now that his expensive backup software that we recommended him doesn't work....

:) Jens

[Renuka_-]

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]

This has been solved after applying latest updates from Microsoft including SP1.

Thanks in advance,

:) Jens

[Marke2112]

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