Tranquil IT Forum

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.

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

Well, that's a shame, I'm going to drop WAPT, which seemed nice...
I'm going to switch to FusionInventory with GLPI.

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.

Hello,
The problem is that the agent creation doesn't even start, and with the antivirus disabled.

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

Hello,
I reinstalled and restarted the creation of an agent, without antivirus or anything that could potentially block it, and I get exactly the same error message.

To add to my previous message, it looks like an incorrect path, but I don't know which file to check.
I installed Wapt in C:\Program Files (x86)\wapt.
Is there a configuration file I need to edit manually?
Thanks

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

Hi Hubert,
great, the situation is resolved, I was able to create the WaptAgent.
I'll continue...
Thanks again
Alain