Salta al contenuto principale

Acronis Snap Deploy Fails

Thread needs solution

Hello everyone,

 

After PXE booting a laptops recently, I've stopped being able to get to the Snap Deploy interface. The laptop gets assigned an IP address, and the NBP file gets downloaded, the the laptop fails out and goes to the onboard diagnostics. Here's the text the appears before it fails out:

 

>>Start PXE over IPv4

After a few seconds, it adds the following lines

Station IP address is 172.25.1.12

Server IP address is 172.25.0.13

NBP filename is bootwiz.cfg

NBP filesize is 191 Bytes

Downloading NBP file...

 

NBP file downloaded successfully

 

Any help or ideas would be greatly appreciated. Thanks!

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 2
Commenti: 1727

Hello James.

Welcome to the forum!

From your description it's complicated to provide you a solution because we need the logs to investigate the issue.

Here are a few troubleshooting steps you can try to resolve the issue:

  1. Please check the following KB and apply the solutions: https://kb.acronis.com/content/47134

  2. Check NBP Configuration: Review the configuration of the NBP file (bootwiz.cfg) on the server side. Ensure that the settings are correct and compatible with the laptop's hardware. https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/os-deploym…

  3. Check Firewall and Security Software: Verify that there are no firewalls or security software on either the laptop or server that might be blocking the communication.

  4. Check Laptop Hardware Compatibility: Ensure that the laptop hardware is compatible with Acronis Snap Deploy. Check the system requirements and verify if the laptop's hardware is supported.

  5. Update Acronis Snap Deploy: If you are not using the latest version of Acronis Snap Deploy, consider updating to the latest release. Newer versions often include bug fixes and improvements.

  6. Review Logs: Check the server logs and event viewer for any error messages or warnings related to the PXE boot process. This might provide additional insights into the issue.

  7. If the issue persists, please contact our support at: https://support.acronis.com/

Thanks in advance!

Hello Jose,

Thanks for your response.

1. I was looking at this article earlier, but wasn't able to find much. I'll have to go back to it and try to mess around with wireshark some more.

2. I don't think it can be the NBP file, since we haven't had any issues imaging these models in the past.

3. I check the Firewall and Security settings againt our other sites (we have six working sites, and the one that isn't). Also, our imaging servers are created from templates, so the settings should all be the same, but I doubled checked just to make sure.

4.I don't believe there should be any compatiblity issues, since we have imaged these in the past. All we ever had to do was change the storage type to AHCI or make sure that the BIOs are up-to-date.

5.I have checked for updates. Unfortunately, we were already up-to-date.

6. I wasn't aware that PXE boot issues were logged in Event Viewer. I'll have to take a look through that.

7. I think our support has expire.

 

Thanks again for your help. I had run out of ideas, but you've given me a few other places to look.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 2
Commenti: 1727

James Lance wrote:

Hello Jose,

Thanks for your response.

1. I was looking at this article earlier, but wasn't able to find much. I'll have to go back to it and try to mess around with wireshark some more.

2. I don't think it can be the NBP file, since we haven't had any issues imaging these models in the past.

3. I check the Firewall and Security settings againt our other sites (we have six working sites, and the one that isn't). Also, our imaging servers are created from templates, so the settings should all be the same, but I doubled checked just to make sure.

4.I don't believe there should be any compatiblity issues, since we have imaged these in the past. All we ever had to do was change the storage type to AHCI or make sure that the BIOs are up-to-date.

5.I have checked for updates. Unfortunately, we were already up-to-date.

6. I wasn't aware that PXE boot issues were logged in Event Viewer. I'll have to take a look through that.

7. I think our support has expire.

 

Thanks again for your help. I had run out of ideas, but you've given me a few other places to look.

Hello!

After checking the logs, please let us know what's the feedback.

Thanks in advance! 

I tried looking through the logs in the folders in C:\ProgramData\Acronis, but nothing really stood out to me as the problem, but I guess I'm not really sure what I'm looking for. I assumed it would be in either the AgentService, PXEServer, or SnapDeploy logs, or is there somewhere else I should be looking?

Thanks again.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 2
Commenti: 1727

James Lance wrote:

I tried looking through the logs in the folders in C:\ProgramData\Acronis, but nothing really stood out to me as the problem, but I guess I'm not really sure what I'm looking for. I assumed it would be in either the AgentService, PXEServer, or SnapDeploy logs, or is there somewhere else I should be looking?

Thanks again.

Hello James,

In order to locate errors within the folder, you need to enable the option in the Bootable Media settings. You can find the instructions here: https://www.acronis.com/en-us/support/documentation/ASD6/#cshid=13484. Please ensure that the "Place the agent's logs on the deployment server" option is selected. Once you've reproduced the issue, the logs will be stored in the designated folder.

You can also collect the system report after reproducing the issue: https://www.acronis.com/en-us/support/documentation/ASD6/#cshid=15577

Thank you in advance!

If we boot from a USB, the process works fine. Not sure if that helps narrow down the issue.

We tried PXE booting today, and that made logs in the AgentService, FileServer, PXEServer, and SnapAPILogs folders. Nothing in the DeployServer logs.

 

****AgentService****

<?xml version="1.0" encoding="UTF-8" ?>
<log uuid="" product="Acronis Test Program" version="41.0" build="76" >
 

 

****FileServer****

<?xml version="1.0" encoding="UTF-8" ?>
<log uuid="" product="Acronis File Server" version="41.0" build="1184" >
    <event id="1" level="1" module="100" code="0" time="1691587848" message="OnServiceMainStart: Start listening on '24001'" />
    <event id="2" level="2" module="100" code="0" time="1691587848" message="Open Unicast Session 172.25.0.13:69 with root C:\Program Files\Acronis\PXEServer" />
    <event id="3" level="1" module="100" code="0" time="1691587848" message="Remove all files from session 172.25.0.13:69" />
    <event id="4" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\F02410F4A to session 172.25.0.13:69 by name f02410f4a" />
    <event id="5" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\F07610F49 to session 172.25.0.13:69 by name f07610f49" />
    <event id="6" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\F5CA20D0E to session 172.25.0.13:69 by name f5ca20d0e" />
    <event id="7" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\F6EB80D51 to session 172.25.0.13:69 by name f6eb80d51" />
    <event id="8" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\F73E20D50 to session 172.25.0.13:69 by name f73e20d50" />
    <event id="9" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\F78CE0D78 to session 172.25.0.13:69 by name f78ce0d78" />
    <event id="10" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\F79340D87 to session 172.25.0.13:69 by name f79340d87" />
    <event id="11" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\F8B6A0DBB to session 172.25.0.13:69 by name f8b6a0dbb" />
    <event id="12" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\F8BD00DCA to session 172.25.0.13:69 by name f8bd00dca" />
    <event id="13" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\F90920DBA to session 172.25.0.13:69 by name f90920dba" />
    <event id="14" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\F90F80DC9 to session 172.25.0.13:69 by name f90f80dc9" />
    <event id="15" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\FC8910AF7 to session 172.25.0.13:69 by name fc8910af7" />
    <event id="16" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\FD7830B3A to session 172.25.0.13:69 by name fd7830b3a" />
    <event id="17" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\FDCB90B39 to session 172.25.0.13:69 by name fdcb90b39" />
    <event id="18" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\FED7E0F07 to session 172.25.0.13:69 by name fed7e0f07" />
    <event id="19" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\bootia32.xml to session 172.25.0.13:69 by name bootia32.xml" />
    <event id="20" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\bootmenu.exe to session 172.25.0.13:69 by name bootmenu.exe" />
    <event id="21" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\bootwiz.cfg to session 172.25.0.13:69 by name bootwiz.cfg" />
    <event id="22" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\bootx64.xml to session 172.25.0.13:69 by name bootx64.xml" />
    <event id="23" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\cpp.so to session 172.25.0.13:69 by name cpp.so" />
    <event id="24" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\fox.so to session 172.25.0.13:69 by name fox.so" />
    <event id="25" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\graphapi.so to session 172.25.0.13:69 by name graphapi.so" />
    <event id="26" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\icu38.so to session 172.25.0.13:69 by name icu38.so" />
    <event id="27" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\icudt38.so to session 172.25.0.13:69 by name icudt38.so" />
    <event id="28" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\libc.so to session 172.25.0.13:69 by name libc.so" />
    <event id="29" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\libgcc_s.so to session 172.25.0.13:69 by name libgcc_s.so" />
    <event id="30" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\osfiles.so to session 172.25.0.13:69 by name osfiles.so" />
    <event id="31" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\pxe_boot.so to session 172.25.0.13:69 by name pxe_boot.so" />
    <event id="32" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\resource.so to session 172.25.0.13:69 by name resource.so" />
    <event id="33" level="1" module="100" code="0" time="1691587848" message="Add file C:\ProgramData\Acronis\PXEServer\Bootmenu\threads.so to session 172.25.0.13:69 by name threads.so" />
 

 

****PXEServer****

<?xml version="1.0" encoding="UTF-8" ?>
<log uuid="" product="Acronis PXE Server" version="41.0" build="1184" >
    <event id="1" level="2" module="100" code="0" time="1691587848" message="Loading IP addresses from all installed Ethernet adapters." />
    <event id="2" level="2" module="100" code="0" time="1691587848" message="A session associated with address '172.25.0.13' has been successfully created." />

 

****SnapAPI****

 

[20230809-133530-620][SnapAPI][T] build: 4038, process: 6444, 'C:\Program Files\Common Files\Acronis\SnapDeployConsole\AdvReport\systeminfo.exe'
[20230809-133530-620][SnapAPI][T] 2023.08.09 13:35:30 UTC
[20230809-133530-620][SnapAPI][T] 2023.08.09 09:35:30 LOCAL
[20230809-133530-620][SnapAPI][T] Initialize DLL 4.7.4038 (64 bit)
[20230809-133530-620][SnapAPI][T] Machine Computername.Domain.com
[20230809-133530-620][SnapAPI][T] Process 6444
  C:\Program Files\Common Files\Acronis\SnapDeployConsole\AdvReport\systeminfo.exe