https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMDc0IiwiaGFzaCI6ImYwYjFjYmIyLTE5YzMtNDFmZC05YzdkLWRhMjVlMDgxOTJiMCJ9
1-800-691-1991 | 9am - 8pm ET
EN

Remote Registry Inaccessible to 2003 Server

Challenge

VSS fails with the following error:

Starting guest agent
Cannot initialize information about the guest's system. Target host: [xxx.xx.xxx.x].
Cannot collect metrics about the guest's operation system. Cannot open sessions
manager's registry key
. Win32 error:Access is denied. 

Cause

Typically this is simply meaning that the remote registry service is not running on the source guest virtual machine, or it is inaccessible due to firewall restriction.  

Solution

Configure the following permissions on the registry key below:
 
      "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg"
 
Permissions:
 
"Administrators" -  "Full Control"
"Local Service"  -  "Read"
 
Restart "Remote Registry" Service to apply the new settings.
 
http://support.microsoft.com/kb/555335


More information

Make sure to check if remote registry service is running before trying advanced solution.

KB ID:
1074
Product:
Veeam Backup & Replication
Version:
5.x
Published:
2011-07-19
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later