Skip to main content

License Server

Thread needs solution
Beginner
Posts: 1
Comments: 0

Trying to deploy an image across a network, 192.168.100.x where the console, deploy and license servers are at 192.168.100.153. Snap Deploy Agent on 192.168.100.168 starts and is able to see the deploy server: "Connected to Acronis Snap Deploy 4 OS Server" 192.168.100.153. The Agent system shows as Ready before running the deployment task but the task immediately ends and and the State reverts to Not Ready with Deployment Failed. The Agent system then reboots

This appears in the log:

--------------------
Error code: 2
Module: 100
LineInfo: 876D9AA543F78D10
Message: No Acronis Snap Deploy 4 License Server installed on ''.

For some reason the License Server cannot be contacted. We have 5 WorkStation Trial licenses, none in use per the license server.

I can ping both Snap Deploy Agent system and Deploy Server using IP or DNS name.

Firewall on Win 7 Enterprise (servers) has inbound rules provided by Acronis for its components; for the Domain location the Acronis related ports allow about everyone (all addresses) in.

What am I missing?
Thanks,
-ba

0 Users found this helpful
Beginner
Posts: 0
Comments: 2

SAME PROBLEM!
ANY IDEAS!
Thank you!

Regular Poster
Posts: 0
Comments: 132

Hello Burt, Udo

Can you please open C:\ProgramData\Acronis\DeployServer\Configs folder and check the template XML file that was failing? There should be a line with license server address like the following:

{DeployServer}

Recently we encountered one case when this xml file was corrupt and the License server address tag was empty. Please check if you have "{DeployServer}" in the template file and add it if it's missing. Then check the deployment again. We still investigating the case why it gets corrupt and your help is appreciated.

If the xml file is okay, please attach a System information file (from Snap Deploy Management console go to Help -> Collect system information) to this thread and I'll check the other possible reasons of the problem you experienced.

Thank you.

Beginner
Posts: 0
Comments: 2

I tried to fix it by inserting the value:{DeployServer}
Maybe at the wrong line.
No success.

Attachment Size
134183-108406.zip 2.44 MB
134183-108409.txt 3.53 KB
Beginner
Posts: 0
Comments: 1

I have the same issue. 

replacing
<license-server-addr />

to

<license-server-addr>
            {DeployServer}
</license-server-addr>

both times in config helped. Thank you!

Forum Moderator
Posts: 113
Comments: 4341

Александр Абраменко wrote:

I have the same issue. 

replacing
<license-server-addr />

to

<license-server-addr>
            {DeployServer}
</license-server-addr>

both times in config helped. Thank you!

Thank for taking the time to confirm the solution, Alexander!