Tranquil IT Forum

Good morning,

I'm bumping this post because I'm experiencing the same issue after an update from 1.8.2 to 2.2.2.

Users working remotely (on-site) encounter this error message when their machines shut down:
After investigation, it appears that this is caused by waptexit. Indeed, when I disable waptexit from launching when the machine shuts down, the message does not appear.

Otherwise, you must click on abandon in order for the PC to shut down.

I therefore deduce that this error is occurring because it is impossible for it to contact the server (vpn kill process before waptexit launch).

Are there others in this situation?
Is it possible to "bypass" this error pop-up so as not to disable the upgrade when stopped?

I should point out that when the VPN connection is active or when people are on site, the message does not appear.
Thank you in advance for your help.

WAPT Server version: 2.2.3
WAPT Agent version: 2.2.3.12463
WAPT Setup version: 2.2.3.12463
WAPT Deploy version: 2.2.3.12463

Hello,

I'm currently experiencing the same issue across my network.
It only affects users working remotely who are using a VPN.

The network was recently migrated from version 1.8 to the latest version.

Could this be because the 1.8 agent was still installed on the machine when the 2.2 agent was installed?

WAPT Server version: 2.2.3
WAPT Agent version: 2.2.3.12463
WAPT Setup version: 2.2.3.12463
WAPT Deploy version: 2.2.3.12463

Hello,
I'm having the same problem on my control workstation. My latest changes:
- installed the waptupgrade package
- created an agent with the WUA option.
Since then, my computer displays error 408 when I restart/quit...
For your information, I reinstalled my console, but nothing changed... the console works correctly, but the problem persists after restarting.
My other test PC doesn't have this issue, and the wapt client has been updated correctly.
Finally, my wapt server is version 2.2.3 and runs on Debian 11, and my console runs on Windows 10 22H2 (recently updated).

Hoping a solution is forthcoming,
thank you in advance!

Hello everyone,

we've managed to find the problem. It will be fixed in the next version. In the meantime, you can follow the workaround suggested by Amélie in the following post: viewtopic.php?t=3266

Regards,

Denis