[BETA] WAPT 1.5

Questions about WAPT Server / Requests and help related to the WAPT server
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
User avatar
guigeek
Messages: 147
Registration: Nov 21, 2017 - 9:21 p.m.

December 11, 2017 - 5:00 PM

guigeek wrote: Dec 11, 2017 - 09:58
guigeek wrote: Dec 6, 2017 - 10:20 AM Thank you,
I ran `wapt-get register` in debug mode and everything went smoothly. It says "success." But on the server side, I still don't have the UUID.wapt...
:(
Apparently, following a server update, the problem seems to be resolved...
Or not...
In fact, other clients installed behind it are experiencing the same problem... :(
User avatar
guigeek
Messages: 147
Registration: Nov 21, 2017 - 9:21 p.m.

December 12, 2017 - 7:42 PM

I feel alone on this thread... :(
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

December 12, 2017 - 10:19 PM

Is your problem still the missing UUID.wapt file?

If so, that's normal; the message will appear as long as the machine package isn't created (from the console).

What are the remaining problems?
User avatar
guigeek
Messages: 147
Registration: Nov 21, 2017 - 9:21 p.m.

December 13, 2017 - 8:36 AM

I found the problem with the websockets... it was due to the server having a completely different time compared to the clients!

However, I have a problem with the create_user_desktop_shortcut function in one of my wapt packages in the session-setup part which causes me the following error:

2017-12-13 08:29:14,720 DEBUG Change current directory to C:\Users\adminstm.
2017-12-13 08:29:14,720 DEBUG DB rollback
2017-12-13 08:29:14,723 DEBUG Error at DB exit (-2147024809, 'Incorrect parameter.', None, None), rollbacking
[' File "C:\\Program Files (x86)\wapt\common.py", line 5019, in session_setup\n raise e\n']
2017-12-13 08:29:14,726 CRITICAL com_error: (-2147024809, 'Param\xe8be incorrect.', None, None)

Any ideas?
User avatar
htouvet
WAPT Expert
Messages: 436
Registration: March 16, 2015 - 10:48
Contact :

December 13, 2017 - 2:43 PM

Synchronizing clocks between machines becomes more critical with this version of Wapt, because actions or the connection of the client to the server are signed, with a timestamp to avoid potential replay attacks.
Tranquil IT
User avatar
guigeek
Messages: 147
Registration: Nov 21, 2017 - 9:21 p.m.

December 15, 2017 - 12:22 AM

Hi,
I still have 2 issues with version 1.5!
The issue I mentioned previously:
with the create_user_desktop_shortcut function in one of my wapt packages in the session-setup part which causes me the following error:

2017-12-13 08:29:14,720 DEBUG Change current directory to C:\Users\adminstm.
2017-12-13 08:29:14,720 DEBUG DB rollback
2017-12-13 08:29:14,723 DEBUG Error at DB exit (-2147024809, 'Param\xe8tre incorrect.', None, None), rollbacking
[' File "C:\\Program Files (x86)\\wapt\\common.py", line 5019, in session_setup\n raise e\n']
2017-12-13 08:29:14,726 CRITICAL com_error: (-2147024809, 'Param\xe8tre incorrect.', None, None)

package that worked in 1.3

And we have an ESET antivirus that detects the nssm.exe file as a potentially dangerous application and deletes it. :(

That's all for the feedback!
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

December 15, 2017 - 9:55 AM

Hello

, nssm is a third-party application: https://nssm.cc/

The executable is not resigned by us, see the conversation:

https://lists.tranquil.it/pipermail/wap ... 02417.html



I'm looking into the create_user_desktop_shortcut.

Simon
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

December 15, 2017 - 1:57 PM

I can't reproduce the bug for create_user_desktop_shortcut. Are you sure the problem is with BETA 1.5?
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

January 3, 2018 - 11:05 AM

For your information, we have just released the nightly version 1.5.1.13:

Two new features in this version:

- Passwords no longer appear in plain text during a build-up from PyScripter.
- We have ensured that the console works correctly with WineHQ (2.0.3) under Linux.
User avatar
agauvrit
WAPT Expert
Messages: 238
Registration: Nov 17, 2016 - 10:25
Location: Nantes
Contact :

January 5, 2018 - 11:33

Good morning
Locked