Can not add agent 11.5 into AMS

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Messaggi: 3
Commenti: 0

Hi All,

Please help me.. I can't add agent 11.5 into AMS. The error message :

Code: 20,250,646(0x01350016)
LineInfo: 0x8D165E86FB8195FF;

Module: remote_install_command_addon_vs_37975
Message: Failed to add machine 'jan11' to the management server.

Code: 24,641,537(0x01780001)
LineInfo: 0x3EAC2BD32D84C047;

Module: remote_install_command_addon_vs_37975
Message: Failed to add machine 'jan11' to the management server.

Code: 21,430,291(0x01470013)
LineInfo: 0xA76A04993E79384C;

Module: mms_vs_39029
Message: Authentication has failed.

Code: 21,430,292(0x01470014)
LineInfo: 0xA76A04993E793870;

Module: mms_vs_39029
Message: Failed to write the license server configuration.

Code: 11,927,557(0x00B60005)
LineInfo: 0x9BA272E7279B4CE0;

Module: mms_vs_39029
Message: Failed to set the configurations.

Code: 11,927,559(0x00B60007)
LineInfo: 0x6400C1869564B432;

Module: mms_vs_39029
Message: There is a conflict with the value defined by a group policy.

Code: 10,223,617(0x009C0001)
LineInfo: 0xA4ABFCFFC2A95EDC;

Module: mms_vs_39029
Message: The current value differs from that in the registry.

Thanks

Gio, 10/23/2014 - 19:27
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Messaggi: 0
Commenti: 1379

Check if address of license server is specified in Software\Policies\Acronis\MMS\Configuration\License registry branch on machine with agent, and remove it or change to the one specified on the management server. Btw, version of Agent (39029) is higher than that of the Management Server (37975). This is not a supported configuration. All components except agents must be the same version, and version of agents must be the same build or older.

Gio, 10/23/2014 - 20:14
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Messaggi: 1
Commenti: 2

I need help with exactly the same problem. The stated change to the registry did not help in my case.

My error message is the same as above, except that all the version numbers are 39029.

I'm making a cry for help, but not only that, I'm making a cry for better error messages.

1. "There is a conflict with the value defined by a group policy." What are the conflicting values? Is this a group policy that I access with the Windows policy editor, or is it an Acronis group policy?

2. "The current value differs from that in the registry." Well, what are the values? What can I do about that?

These messages tell me nothing useful. And the link to search the knowledge base turns up nothing (which is most often the case with ABR errors).

How do I solve this?

Gio, 01/22/2015 - 21:01
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Messaggi: 1
Commenti: 2

Actually, the stated change to the registry did solve my problem. But it created a new one.

What I failed to notice in the solution above were the words "remove it". I removed the data item "LicenseServerAddress", and now I can add the machine to the AMS.

However, I now wonder what I've done. The item did not get automatically replaced in the registry. So I replaced the item, with the same value.

Then I updated the agent on the machine. The "install component" feature showed that one license was available. And it installed the component.

BUT - it did not assign a license to the machine, and I can't run a backup. The license server still shows one license available.

So, I did the following:
1. I connected to the machine (in the AMS, Connect > New Connection > Manage a Remote Machine > machine-name)
2. Clicked on "Help" and selected "change license"
3. In the section "License for backup of disks", I clicked "Change".
4. It showed me that a license was available, so I clicked "OK".

That allowed the backup to run (finally).

I hope this helps anyone else with this problem.

Gio, 01/22/2015 - 21:00