Failing to set a proxy server in Microsoft Azure Recovery Service Agent

Applies to: Azure Backup


When you try to set a proxy by using the Register Server command in the Microsoft Azure Backup snap-in, the server is not registered, and you receive the following error message:

Failed to re-enable existing scheduled backup settings. The server must be registered with Microsoft Azure Backup before this operation can be performed.

Or, you receive the following error message when you set a proxy by using the Change Properties command in the Microsoft Azure Backup snap-in:

Microsoft Azure Recovery Services Agent could not connect to the proxy server.(ID: 280011)
Please check the server settings and verify that the proxy server address is correct.


This problem occurs if the proxy setting is missing in the CBSettings.xml file.


To work around this problem, add the proxy setting to CBSettings.xml, and then restart Microsoft Azure Recovery Service Agent.

CBSettings.xml is stored in the scratch folder that you specified as "Cache Location" during the installation of Microsoft Azure Recovery Service Agent. By default, the scratch folder is located in the following path:

C:\Program Files\Microsoft Azure Recovery Services Agent\Scratch
The current scratch folder path is stored in the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Azure Backup\Config\ScratchLocation

To set a proxy, follow these steps:

  1. Copy the CBSettings.xml file to any folder as a backup.
  2. Close the Microsoft Azure Backup snap-in if it's running.
  3. Open CBSettings.xml.
  4. Update the <ProxySetting> line, and then save the file. If <ProxySetting> is missing in the CBSettings.xml, add it. If <ProxySetting> already exists, replace it. For example, enter the following line in CBSettings.xml Contents:

  5. Open the Services Management console (Services.msc).
  6. Right-click the "Microsoft Azure Recovery Services Agent" service, and then click Restart.
  7. Start the Microsoft Azure Backup snap-in, and then verify that the proxy setting is set correctly by using the Change Properties command.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.