Hello,
We are using WAPT Enterprise version 2.6.1.17813 on a Linux Ubuntu 22.04.5 server and manage the console via our admin sessions on Windows 11 Professional 25H2 build 26200.8655 machines.
Context:
I am developing a WAPT package to automate the update of the Veeam Agent for Microsoft Windows from version 6.3.2.1302 to 13.0.3.1220 (a major upgrade), using the official Veeam executable in silent mode (/silent /noreboot).
The idea is to be able to modify the package each time a new version is available to automate updates of the Veeam agent deployed on our VIPs' machines.
Problem encountered:
Uninstalling the old version (6.3.2.1302) works correctly. However, the installation of the new version (13.0.3.1220) never completes successfully: the installer consistently returns error code 1002, which in Veeam means "reboot required to complete installation." The Veeam service (VeeamEndpointBackupSvc) is never created after this error, and the software does not appear in the list of installed programs; the installation is therefore blocked, not just waiting for a reboot.
Notably, a manual/interactive installation of the same executable, on the same machine model, completes normally without requiring a reboot. The behavior thus differs significantly between interactive execution (user session) and silent execution via the wapt service (SYSTEM context).
My script handles error code 1002 in setup.py (capturing the exception thrown by run(), returning 3010 to WAPT to schedule a reboot), but I haven't yet been able to confirm that a subsequent reboot will complete the installation, since Veeam 13 currently won't install at all in this context.
Question:
Has anyone encountered this type of blockage with an installer requiring drivers (Veeam, or other products with drivers like antivirus/EDR/CBT) installed silently via WAPT? Is it related to the SYSTEM context of the WAPT service, a residual pending reboot state, or is there a known Veeam flag/parameter to bypass this silent blockage?
Thanks in advance.
Amaël
[RESOLVED] Veeam Agent 13.0.3.1220 return code 1002 (reboot required) silent mode > manual installation does not require it
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
dcardon
- WAPT Expert
- Messages: 1978
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Amaël,
following the uninstallation, is a reboot necessary? Is the service still showing as PENDING_DELETE (or equivalent; I don't remember the exact status Windows returns)?
Does the installation of the new agent work correctly in silent mode under the SYSTEM account (without the update issue from the old version)?
Sincerely,
Denis
following the uninstallation, is a reboot necessary? Is the service still showing as PENDING_DELETE (or equivalent; I don't remember the exact status Windows returns)?
Does the installation of the new agent work correctly in silent mode under the SYSTEM account (without the update issue from the old version)?
Sincerely,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Hello Denis,
Thank you very much for your questions; they did indeed help me move forward in the right direction, even though the initial lead (PENDING_DELETE) wasn't the problem after all. The test allowed me to definitively rule out that hypothesis and investigate elsewhere.
To wrap things up: the blockage actually stemmed from a missing prerequisite, Microsoft ASP.NET Core 8.0 Runtime (x86+x64), which wasn't automatically installed by the Veeam bootstrapper in silent mode. The 1002 return code I was seeing didn't mean "reboot required" as I thought, but rather "installation failed," hence the initial confusion.
It was by testing the executable directly in the SYSTEM context (via PsExec) that the blocking popup mentioning this missing prerequisite finally appeared, whereas it went unnoticed in silent mode.
Incidentally, I also discovered that the /noreboot parameter was no longer valid for the bootstrapper in version 13 ("Invalid command line parameter").
The solution implemented was a separate WAPT package for the ASP.NET Core 8 runtime, declared as a dependency of the Veeam package, plus a corrected installation command with the correct flags (/accepteula /acceptthirdpartylicenses /acceptlicensingpolicy /acceptrequiredsoftware).
Everything now works correctly. Thanks again for the help!
Best regards,
Amaël
Thank you very much for your questions; they did indeed help me move forward in the right direction, even though the initial lead (PENDING_DELETE) wasn't the problem after all. The test allowed me to definitively rule out that hypothesis and investigate elsewhere.
To wrap things up: the blockage actually stemmed from a missing prerequisite, Microsoft ASP.NET Core 8.0 Runtime (x86+x64), which wasn't automatically installed by the Veeam bootstrapper in silent mode. The 1002 return code I was seeing didn't mean "reboot required" as I thought, but rather "installation failed," hence the initial confusion.
It was by testing the executable directly in the SYSTEM context (via PsExec) that the blocking popup mentioning this missing prerequisite finally appeared, whereas it went unnoticed in silent mode.
Incidentally, I also discovered that the /noreboot parameter was no longer valid for the bootstrapper in version 13 ("Invalid command line parameter").
The solution implemented was a separate WAPT package for the ASP.NET Core 8 runtime, declared as a dependency of the Veeam package, plus a corrected installation command with the correct flags (/accepteula /acceptthirdpartylicenses /acceptlicensingpolicy /acceptrequiredsoftware).
Everything now works correctly. Thanks again for the help!
Best regards,
Amaël
