Good morning,
I'm installing WAPT version 1.38, and I'm stuck during the WAPTAGENT installation from the Windows console. The self-signed certificate is... I'm getting the following error, and I don't know what the problem is. For your information, I'm using Windows 10, and WAPTSERVER is running on a Linux machine.
Thank you for your help, I look forward to using this tool.
Error creating WAPTAGENT
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
Hello everyone,
Has no one else encountered this problem?
Is it due to the new version? This is my first installation, and I've had difficulties installing the console on my Windows 10 machine from the start. The first issue was generating a key; I also got an error.
I had to use the SET PATH command in the command line to point to the openssl.cfg configuration file, which was indeed located in c:/private, as stated in the documentation and offered by default in the key generation field.
Is this version too buggy? Should I install an earlier version, and if so, how can I find the source code?
I welcome your helpful suggestions.
Thank you
Has no one else encountered this problem?
Is it due to the new version? This is my first installation, and I've had difficulties installing the console on my Windows 10 machine from the start. The first issue was generating a key; I also got an error.
I had to use the SET PATH command in the command line to point to the openssl.cfg configuration file, which was indeed located in c:/private, as stated in the documentation and offered by default in the key generation field.
Is this version too buggy? Should I install an earlier version, and if so, how can I find the source code?
I welcome your helpful suggestions.
Thank you
If this is happening on a "clean" Windows machine (one used only for Wapt management and which hasn't seen much use), it looks like an antivirus problem.
The waptagent.exe compiled by the Wapt console isn't digitally "signed," and some antivirus programs delete it immediately after creation.
The waptagent.exe compiled by the Wapt console isn't digitally "signed," and some antivirus programs delete it immediately after creation.
Tranquil IT
Hello,
Could you please try the following:
- Reinstall WAPTSetup on your administrator machine ( http://wapt.tranquil.it/wapt/releases/w ... tsetup.exe )
- Restart WAPTConsole as Administrator
- Restart the agent creation process
These steps are described in our documentation here: http://dev.tranquil.it/scenari/guide_ad ... Setup.html
Please provide as much detail as possible if this fails.
Alexandre
Could you please try the following:
- Reinstall WAPTSetup on your administrator machine ( http://wapt.tranquil.it/wapt/releases/w ... tsetup.exe )
- Restart WAPTConsole as Administrator
- Restart the agent creation process
These steps are described in our documentation here: http://dev.tranquil.it/scenari/guide_ad ... Setup.html
Please provide as much detail as possible if this fails.
Alexandre
This is indeed a bug related to spaces in the Program Files (x86) path.
There are no quotes in the command line for the .iss argument when launching the Innosetup compiler.
A patch is available here: http://wapt.tranquil.it/wapt/nightly/wa ... onsole.exe
(it also fixes the sorting by Windows version in the grid).
Hubert
There are no quotes in the command line for the .iss argument when launching the Innosetup compiler.
A patch is available here: http://wapt.tranquil.it/wapt/nightly/wa ... onsole.exe
(it also fixes the sorting by Windows version in the grid).
Hubert
Tranquil IT
