[Resolved] Failure to deploy images via SD4 Management Console
Hello All,
I currently have an open support ticket, but while I am waiting on expert center to get back thought it was worth asking the forum community if they have encountered this error before.
==========================================================
Host '192.168.1.128' has failed the deployment.
Additional info:
--------------------
Error code: 1
Module: 52
LineInfo: 9C5A16066A60D4FF
Fields: $module : "C:\Program Files\Common Files\Acronis\Agent\osd_server.dll"
Message: Host '192.168.1.128' has failed the deployment.
--------------------
Error code: 12
Module: 51
LineInfo: 977C1751BBDBA766
Message:
==========================================================
This error occurs during the initial attempt to deploy the image, it fails on the server console and the computer reboots. That's it.
- I'm running a brand new install of ASD4 on a Windows Server 2003 R2 build.
- Trying to deploy via CD Boot media with ASD4 Agent installed on it (Along with Standalone Utility, Master Image Creator and System Report tools)
- The device connects to the server console without issue and is shown in ready state.
- I've created new deployment tasks and schedules
- Tried Multicast and Unicast deployment as well as dropped network speeds
- Tried with and with out Universial deployment
- I've been using new images created with the ASD4 boot media specified above, saved both to external drives and copied to the server, and created over the network and saved directly to the server local drive.
- I'm got Universial Deploy 4.0 and Snap Deploy 4.0 Workstation licenses available (They are upgrades from 3.0 licences, but the 3.0 licenses are available as well).
Acronis support remotely checked my server installation, said everything was good and process being followed is correct. Now I'm waiting on expert center to get back to me after reviewing logs etc.
In the mean time, anyone have any additional ideas for me?

- Anmelden, um Kommentare verfassen zu können

FYI for those who find themselves with a similiar error, after a couple of weeks waiting for a solution from support a colleague recommended checking that the Jumbo Frames property of the local area network connection was disabled. Turns out Jumbo Frames was turned on and set to 16128 bytes. Once disabled no error when trying to deploy or create images from server.
- Anmelden, um Kommentare verfassen zu können

Hello New2SnapDeploy,
Thank you for the follow-up and I am glad to know that the issue has been resolved.
I will forward the information to our Testing Lab so that we can understand what caused it and come up with a solution.
Thank you.
- Anmelden, um Kommentare verfassen zu können