E0033001D: Failed to connect to Acronis Snap Deploy 4 OS Server
After upgrading from 4.0.268 to 4.0.540 to fix the issue with the NICs being recognized on Dell Optiplex 390s we have been unable to connect to the Server. When loading up the Agent it will not connect and gives the error code E0033001D, however this is only if Agent version is 4.0.540. When using an Agent with version 4.0.268 it connects without issue like it once did, which means all the machines except the Optiplex 390s we need it for currently. I thought it might be the media or the ISO so I’ve burned a new disc and created a bootable USB flash drive from the ISO downloaded from my accounts page but I am getting the same error code. The only thing changed was the upgrade from Snap Deploy 4 4.0.268 to 4.0.540. Any ideas?
Thank you,
Brian Anderson

- Se connecter pour poster des commentaires

Morning Andrey,
Thank you for responding. In regards to the issue I don't believe that drivers are the culprit because I can create a master image from the Optiplex 390 with a bootable media (4.0.540) but if I restart and select the Agent from the same media it will not connect to the server. What further leads me to believe it isn't driver related is when the Agent loads up on the PC and I go into the settings it lists the NIC which it didn't before using the 4.0.268 Agent. At any rate I tried to get a report and it says it saves it but I'm not seeing it on the USB thumb drive or on the HDD so I'm not sure what is happening there.
Thank you,
Brian Anderson
Fichier attaché | Taille |
---|---|
152696-110587.png | 1.14 Mo |
152696-110590.png | 1.15 Mo |
- Se connecter pour poster des commentaires

According to pictures that does not look like a driver problem indeed.
I advise you to contact our support because the problem requires investigation and there is no quick answer to it.
- Se connecter pour poster des commentaires

I was able to create a safe report using the Acronis System Report Linux.
Fichier attaché | Taille |
---|---|
152746-110596.txt | 102.77 Ko |
- Se connecter pour poster des commentaires

Sorry, just saw your response after I uploaded the report. We will do that.
Thank you,
Brian Anderson
- Se connecter pour poster des commentaires

I am having same error using HP Elitedesk 800 model PC's and it is very frustrating. Did you ever get resolution on this??
Thanks,
Dan
- Se connecter pour poster des commentaires

Stark County & Danel
Did you get the matter resolved?
We have been getting a similar with HP ELite Desktops and ProBooks. This is with CDs that were created recently that worked until a week or so ago and older versions of the CD that worked with those models.
- Se connecter pour poster des commentaires

CDFA, I was having the exact same issue. I had to manually put the IP address of the server in during the boot even though I had done so when I created the bootable media. Like most of Acronis products, they have a newer version to fix some issues but cause others.
- Se connecter pour poster des commentaires

Just started getting this error. Has anyone found a solution?
- Se connecter pour poster des commentaires

I never come and post comments but after what I went through I figured I would share. I consider this SOLVED.
The original poster was encountering the exact same issue I was and it IS A DRIVER problem. The solution was to build a PE "4.0" deployment image.
If you load a stock PE 2.0/3.0 disk and look at your available adapters it will show none. You load a PE 4.0 disk and the adapter is ready to go. This means.. it's a driver issue. Because your adapter requires chip-set dependencies it will not load the appropriate driver period. Tried driver packs, manufacture .ini injection, even extracted the drivers from the host machine manually with no go.
Solution:
Installed Windows 8.1
Installed WAIK for Windows 8.1
Installed Snap Deploy 4 VR 540
Created PE 4.0 Menu
Enjoy
Hope this helped!
- Se connecter pour poster des commentaires

Thank you for sharing, Robert!
- Se connecter pour poster des commentaires