Tranquil IT Forum

Hello,

after several searches, I haven't found anything on this topic, so here's my problem:

The WAPT agent was successfully deployed via GPO, no issues there.
However, some agents don't start when the computer boots. We have to start this agent manually using the `runwaptservice` command line.

Do you know why this agent doesn't start automatically when the session is opened?

Thank you in advance for your help.

Never encountered this issue.

Is the waptservice running?

Is the service paused?

Is the service set to automatic?

Is the file C:\Program Files (x86)\wapt\waptservice\win32\nssm.exe present?

Hello,

I had this problem and it was caused by the "tis-schedule-wapt-upgrade-on-boot" package.
Once the task was removed, the problem was solved.

Hi Simon,

Yes, the Wapt Service agent is installed.

How can I tell if the service is paused? And in automatic mode?
Is the file C:\Program Files (x86)\wapt\waptservice\win32\nssm.exe present? YES.

Thanks @smandel, I'll look into that, but I don't know if the "tis-schedule-wapt-upgrade-on-boot" package is running.

I have to start the service from the command line for the agent to start.

Thanks in advance for your help.

admgautier wrote: ↑June 2, 2022 - 4:27 PM How can I tell if the service is paused? And in automatic mode?

In services.msc

The agent isn't showing up in services.msc... so it hasn't started, which is normal since that was my initial problem.

On the old machines, there's no problem; the agent starts up correctly on startup. Not on the new ones, even though it's enabled in the "Startup" service in Task Manager.

This means that when the WaptAgent installed, the "WaptService" failed to install.

I've seen this before when antivirus software blocks the nssm.exe file.

Nssm is a service manager in Windows.

nssm.exe has been used by viruses in the past, and as a result, some antivirus programs don't question this and block it.

However, nssm is not inherently dangerous; it all depends on what you run it.

What's strange is that nssm.exe is indeed present in the folder C:\Program Files (x86)\wapt\waptservice\win32\nssm.exe... so it must have installed correctly.

When Simon talks about installation, he means that the service is properly registered

Does it work if you launch the service from the command line (with elevated privileges)? What's in the event viewer?

Denis

Hi Denis,

When I run `net start waptservice`, I get the message: "The service name is not valid" (see attached image).

To start the WAPT agent via cmd, I usually use `runwaptservice`, and I get the same error message, but the service starts.

I don't see anything unusual in the Event Viewer. Where should I look for any information?

Thanks for your help.

Anthony