Good morning,
We are having problems with the OS deployment; the installation is stuck on the waptagent.
We have the latest version:
WAPT Server version: 2.6.0.17392
WAPT Agent version: 2.6.0.17392
WAPT Setup version: 2.6.0.17392
WAPT Deploy version: 2.6.0.17392
DB status: OK
Have you ever had this problem?
Thank you for your feedback
OS Deployment Problem - WADS
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
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Good morning
You'll find our code here:
This would mean that the download of waptdeploy failed. Is it present and downloadable on the wapt server's web interface?
And in the correct version for the server?
You'll find our code here:
Code: Select all
if not WadsWget(MakeUrlPath([RepoUrl,'wapt','waptagent','waptdeploy.exe']),
MakePath([DefaultInstallDir,'waptdeploy.exe']), WaptData^.S['waptdeploy.exe'], 4000, 'Wapt Deploy Download') then
begin
UpdateWadsStatus('The waptdeploy.exe can not be found on the machine.', True, True);
Exit(Result);
end;
This would mean that the download of waptdeploy failed. Is it present and downloadable on the wapt server's web interface?
And in the correct version for the server?
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Thanks for the feedback. Could you check the hash of waptdeploy on your WAPT server? (
https://srvwapt.mydomain.lan/wads/hash.json)
and the hash of waptagent:
(https://srvwapt.mydomain.lan/wapt/waptagent.exe)
Do you have a secondary repository?
https://srvwapt.mydomain.lan/wads/hash.json)
and the hash of waptagent:
(https://srvwapt.mydomain.lan/wapt/waptagent.exe)
Do you have a secondary repository?
Hello,
I just checked //srvwapt.mydomain.lan/wapt/waptagent.exe the hash of https: retrieved from the webpage https://srvwapt.mydomain.lan/ in the file https://srvwapt.mydomain.lan/ .
There is no matching hash in the JSON file.
We are currently deploying secondary repositories (39) with rules, so it's quite possible the problem arose at that time. But where is the problem coming from?
I just checked //srvwapt.mydomain.lan/wapt/waptagent.exe the hash of https: retrieved from the webpage https://srvwapt.mydomain.lan/ in the file https://srvwapt.mydomain.lan/ .
There is no matching hash in the JSON file.
We are currently deploying secondary repositories (39) with rules, so it's quite possible the problem arose at that time. But where is the problem coming from?
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
I don't understand, you don't have waptagent.exe in this file at all???Serv_info wrote: ↑August 7, 2025 - 9:40 AM I just checked the file https://srvwapt.mydomain.lan/wads/hash.json
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
That's strange; it's as if the agent generation didn't work.
You can try going to "Tools" -> "Sign executables" in the console and try again.
You can try going to "Tools" -> "Sign executables" in the console and try again.
