Wapt Agent launch error

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
Locked
jdevelon
Messages: 1
Registration: February 18, 2020 - 3:42 PM

February 18, 2020 - 3:54 PM

error with runwaptservice.bat
error with runwaptservice.bat
Screenshot.jpg (74.08 KB) Viewed 2171 times
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
High
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :
Contact dcardon

February 19, 2020 - 8:33 PM

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
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
High
Locked

Return to "WAPT usage (Console, Agent) / WAPT usage (Console, Agent)"


  • To go further with WAPT