[RESOLVED] Agent error after upgrade from 2.2.2 to 2.3; unable to generate the new agent

[Welsh]

Hello,

I followed the usual recommendations for upgrading WAPT from version 2.2.2 to 2.3.
The server is working perfectly and I have the following status:
WAPT Server Version: 2.3.0.13516
WAPT Agent Version: 2.2.2.12388
WAPT Setup Version: 2.3.0.13516
WAPT Deploy Version: 2.3.0.13516
Database Status: OK

I retrieved the waptsetup.exe file to update my console on a Windows Server 2019 Terminal Server.
Everything went smoothly.
The problem appears when opening the console. During the WAPTAgent check, I have to generate a new agent (which seems logical), but once everything is filled in (nothing is actually changed, just the DEV field instead of PROD initially ), a window appears with the following error message:
(title) waptconsole
(content) Error creating waptagent.exe: Stuff should be pure Text for
C:\Users\MONUSER\AppData\Local\waptco..\waptsetup.exe.
I haven't found any information about this type of error on the forum. Can you help me?
Thank you in advance.
Baptiste

[dcardon]

Hi Baptiste,

I think there must be a non-ASCII character in the agent's description or configuration.

In WAPT versions 2.2 and earlier, the WAPT agent was regenerated using innosetup (the executable installer creator), incorporating the agent's parameters specific to your network installation (server URL, certificate, configuration, etc.). This had the disadvantage of removing the cryptographic signature of waptsetup.exe and generating false positives with antivirus software.

To avoid this issue, in version 2.3, the agent parameters (server URL, certificate, configuration, etc.) are stored in the executable's certificate area to prevent modifying the signature during agent regeneration.

However, there are some restrictions on what can be placed in this area. We would need to identify the problematic character(s).

Best regards,

Denis

[htouvet]

The executable file used to distribute the agent configuration is limited to 32KB.
The error message may indicate that this limit has been exceeded.

Typically, this occurs if you are verifying HTTPS certificates with a large bundle (for example, the path to the complete CA bundle cacert.pem) and not just the CA that signed your HTTPS server certificate.

If this is the case, when generating the agent, you can replace the "Path to certificate authority files for HTTPS servers" with simply the number 1, which means verifying with the system CAs.

[Welsh]

Hi Denis,
I just opened a support ticket, sorry.
I've just looked again and I don't see any non-ASCII characters, nor any spaces at the beginning or end of entries in the configuration window.
Yes, I understand from another thread that the configuration of the agent to be deployed has changed.
In the agent configuration interface, I have the impression that I've done everything "properly," unless it's directly related to the "Issuer DN" of the certificates, where there's an @ for the email field, = signs for each field value, and commas to separate the fields?
I don't know where else to look.
Baptiste

[Welsh]

Thank you Mr. Touvet,
I will try that.

[Welsh]

Re,
Ah yes, that was it, the generation just completed correctly without any errors.
I'll test it right away on my DEV machines.
I'll give you feedback so I can close the ticket then.
:cross_finger:

[dcardon]

Thanks for the feedback . I'm closing the topic,
Denis.