Tranquil IT Forum

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...

I feel alone on this thread...

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?

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?

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.

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!

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

I can't reproduce the bug for create_user_desktop_shortcut. Are you sure the problem is with BETA 1.5?

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.

Good morning

• Online documentation updated : https://www.wapt.fr/fr/doc-1.5/index.html
• Explicit and differentiated update procedure (minor/major)
• upgrade minimum from WAPT Server Windows 1.3 to WAPT Server Windows 1.5 is documented.
• For a complete migration, consider migrating to WAPT Linux Server (CentOS or Debian): https://www.wapt.fr/fr/doc-1.5/migratio ... e-complete