Unable to subscribe to guest processing components

[scidoner]

Hi!

Did some google digging, couldn't find anything for this specific one. The exact error is:

Code: Select all

28/11/2013 2:01:04 AM :: Unable to subscribe to guest processing components: Cannot initialize information about the guest's system. Target host: [10.0.0.24].
Cannot collect metrics about the guest's operation system.
Cannot connect to the remote registry.
Win32 error:The network path was not found.
 Code: 53.

That's great and all, but what network path exactly is it referring to? I just upgraded this VM in question to from Windows 8 to Windows 8.1. It is running on Windows Server 2012 R2 Hyper-V with Veeam 7.0 R2 installed.

Does anyone know what might have caused this to start happening after the upgrade?

Thanks!

[veremin]

Have you had a chance to contact our support team with this issue? Thanks.

[scidoner]

Hi!

All fixed up - the remote registry service decided to disable itself during the upgrade, re-enabled it and working now!

Thanks

[foggy]

Thanks for coming back to update the thread, Michael.

[CS-JS]

Hi everyone!

we're actually experiencing something quite similar to the error described here.
The error we're getting is:

20.04.2015 18:00:49 :: Processing SRV05 Error: Failed to prepare guests for volume snapshot.

SRV05 is the name of the faulting machine. We already figured out, re-enabling and starting the remote-registry service does the trick for this error, but I'd like to ask if anyone else is experiencing some similar errors. From time to time the remote registry service on SRV05 decides to disable itself and let Veeam be running into the error posted above. This happens about every 3-4 weeks. My Case file number is 00884175.

Any advice much appreciated

Kind regards,
Johannes

[foggy]

The best advice is to continue working with technical support on logs review. Any related messages in the Windows Event log on the affected VM?

[CS-JS]

Just that the service stopped, and in best cases started again, but no hint to what script oder task is causing this. Does Veeam B&R itself stop and start this service? Whenever I find a corresponding entry in the event log, it is roughly a few minutes after the backup job is sheduled.

[foggy]

Veeam B&R itself does not stops/start this service, but just queries the guest OS type from the registry. So most likely the issue is somewhere outside its responsibility. Have you tried to contact MS regarding that?