10-24-2008 05:44 AM
I have deployed the System Restore Agent to a server and it worked fine. Suddenly, yesterday, the agent reports back as Unable to get Status and I get a System.Restore.InteropServices.COME exception (0x8000000A) error. I also now get this error when checking the status of the local server where BESRO is installed. I also get a message from the Agent in the system tray of the local server saying that it failed to Reconcile changes last time.
I've uninstalled all Agents and the SR software and rienstalled and all still the same.
Any thoughts on why this is occurring all of a sudden?
Thanks
10-24-2008 08:50 AM
According to the following technote; http://support.veritas.com/docs/302948 this is due to an issue with the .NET framework. Try the steps outlined in the technote, and report back with the results.
I'd suspect that there was an update to .NET or an installation of another product which uses .NET which corrupted the framework.
11-04-2008 06:27 AM
Sorry for the delay in replying, had the luxury of a week off.
I followed the Tech Note 302948 as suggested, by uninstalling BESRO and rebooting, reinstalling .NET 2.0 framework and rebooting, re-installing BESRO and rebooting and then launching the BESR console, but I am in the same boat again, 'unable to get status' and the same error as mentioned in the Tech Note.
Anyone got any further suggestions on a fix?
Cheers.
11-29-2008 02:41 PM
02-09-2009 11:45 AM
I'm having this same exact issue: last Thursday I installed the Agent to a server, and now I am unable to communicate with that agent, with the same error stated above. I've tried the resolution posted in that article you supplied, but this had no effect - still 'Unable to determine status'.
Any ideas?
02-11-2009 08:20 AM
02-11-2009 09:44 AM
The Manager Option is not installed, we don't use it. As a second step to attempt to resolve this, I've installed the full Backup Exec System Recovery to this target machine. It installed fine, but shows the exact same error message: 'Unable to determine status', with the Error details showing the same as the original post with the error code 0x8000000A.
Looking in the event viewer, it shows an application entry with the following three error codes: EC8F1780, EC8F1771, EBAB0013. Doing a search on these errors points to some problem with the hard drives/mbr... but the only solution I haven't tried is reformatting the drive, which on a production machine, isn't possible.
Any other ideas?
02-11-2009 02:32 PM
02-11-2009 02:53 PM
02-11-2009 02:57 PM
02-11-2009 03:22 PM