Tranquil IT Forum

Good morning

I have a fleet of 60 machines managed by Wapt community 1.8.1-6742 (updated 5 days ago).
My problem already existed in version 1.7.4 before the update
via GPO I push the wapt agent to the Windows machines.
58 machines operate perfectly using this technique.

However, I have 2 Windows 7 - Pro 64-bit PCs that have decided to refuse the deployment.
So I switched to manual mode.
On a virtual machine, I install and configure the URLs, and the machine is referenced. = OK
* on my two grumpy Win7 machines (I disabled the Avast installed on them):
I'm launching the setup as admin = OK
I configure the URLs = OK
I restarted the PC just in case = OK
The Wapt service is not running
If I manually launch c:\program files (x86)\waptrunwaptservice.bat I get a message in the attached file.
"ImportError: Dll load failed"

I tried installing the VC redistributable: it didn't do anything
I tried installing Python 2.7.9 in 64-bit (to get the path I was looking for in the error). The file was there but nothing happened.

(I'll spare you the details of the restarts, multiple uninstalls, and reinstalls)
Has anyone else encountered this situation? I think I've searched the documentation and the forum without finding anything about it, so I'm relying on your experiences.
I suspect a VC++ dependency issue...

Sincerely
Johan

WAPT SERVER COMMUNITY - Version 1.8.1-6742
Server: Debian 9
Admin machine = Win10 - 1909 - 64 bits

Good evening,

WAPT integrates its own Python 2.7 32-bit environment. Regarding the error message, the socket.py file retrieved by the runwaptagent.bat script is incorrect. There's likely an environment variable with a PYTHONPATH or something similar. The WAPTagent service is more careful to protect its PATH, so the error message you displayed in cmd.exe isn't necessarily the same as the one that appears in production. However, if the WAPT service is being interfered with by another Python installation, that's not normal.

Could you uninstall the Python installation(s) outside of WAPT and rerun the runwaptservice.bat script to see if you get a different error message? Do you have any entries in the service logs (usually located in c:\program files (x86)\wapt\log)? Logging has been significantly improved in the latest WAPT version 1.8.1.

Regards,

Denis