Tranquil IT Forum

Hello,

I'm having trouble on a few machines where I installed the Wapt agent. These machines are running Windows 10 (Windows updates are up to date).
The agent installs correctly, both with waptdeploy via GPO and manually. However, the "reachable" status is not available in the console. Upon closer inspection, I see that the Waptservice Windows service is not present on these machines.
I haven't been able to find any installation logs for the agent to check for errors. How can I proceed with my analysis?

Thank you in advance.
William

In my opinion, it's an antivirus program that's been running through there...

Hello,

I did consider that. However, I have all the exclusions I found in another post configured in our antivirus. Windows Defender is disabled.

I just noticed that a version of Python (2.5.2150) is installed on these 9 machines. Could this cause a conflict with WAPT 1.8.1?
I'm specifying the WAPT version because I have one machine that's on 1.7.4, but it also has Python 2.5.2150 installed, and I don't have any problems with it...

Edit: I take back what I said in the last sentence since the WAPT agent was installed before the application that installs Python 2.5.2.
Edit 2: I confirm that it's the fact that Python 2.5.2 is installed on the machine that's causing this problem (tested with a fresh installation), but how can I resolve it?

I've just found the cause of my problem: I have a system environment variable "PYTHONPATH" that points to a business application directory.
If I edit it and replace the path with the WAPT installation path, or if I delete it altogether, the service installs correctly when reinstalling WaptAgent.
I tried adding the WAPT installation path to avoid having to delete the other paths, but the service still doesn't install. (e.g., PYTHONPATH = C:\wapt;C:\S3_exec)

I'll check with the business application vendor to see if the variable is actually necessary.
Does anyone have any other ideas?

We had some issues with this in version 1.8.1, but it seems better in 1.8.2. Could you try it with version 1.8.2?

sfonteneau wrote: ↑June 30, 2020 - 4:15 PM We had some issues with this in 1.8.1 but it seems better in 1.8.2, can you try it with 1.8.2?

Good morning,

Thank you for your feedback.
I just upgraded to version 1.8.2.7267 on both the server and client sides, but the problem remains the same.

Sincerely
William

Can you rename waptguihelper.pyd to waptguihelper.pyd.old?

The problem often comes from waptguihelper.pyd.

You can look for waptguihelper.pyd in the Wapt installation folder (it may be in two places).

sfonteneau wrote: ↑July 1, 2020 - 11:36 AM Can you rename waptguihelper.pyd to waptguihelper.pyd.old?

The problem often comes from waptguihelper.pyd.

You can look for waptguihelper.pyd in the wapt installation folder (it can be in two places).

I didn't understand where you wanted me to modify the file. In the client machine's folder where Wapt is installed? If so, how do I restart the service installation?

You just need to find waptguihelper.pyd and rename the file to waptguihelper.pyd.old

then restart the service

sfonteneau wrote: ↑July 1, 2020 - 12:21 You just need to find waptguihelper.pyd and rename the file to waptguihelper.pyd.old

then restart the service

Code: Select all

net stop waptservice
net start waptservice

As I mentioned in my previous messages, the problem is that the Windows service "waptservice" isn't installing because of the "PYTHONPATH" variable. Therefore, I can't restart it since it doesn't exist.