Tranquil IT Forum

Hello,

Following an update of my server to version 2.2.3.12481 (previously 2.2.1...), I started installing my agents on the same version. I'm getting a persistent warning message that I can't seem to clear: "

Auditing prod-waptupgrade.
The installed version of the WAPT agent and the version of the package are not corresponding. The installation may have just finished. If this warning persists one day after installation, please take this into consideration."

prod-waptupgrade is the name of the package I used to upgrade the agent. I've checked on the affected machines, and the version is indeed 2.2.3.12481. Not only can I not clear this warning in the console under audit status, but I'm also experiencing errors with installation packages, particularly the wapt conf package, which refuses to update.

Windows Server 2016 /
Wapt Enterprise Server 2.2.3.12481 /
Windows 10 client workstation (minimum 21hH2) / agent 2.2.3.12481 /
Windows 10 workstation in console/package creation

. Thank you in advance.
Sincerely,

Michel Merle

Hello Michel,

right after installing the package, the waptagent isn't updated yet. The waptupgrade package installs a scheduled agent update task that runs a few minutes after the package installation, because the update needs to stop and then restart the agent, so it can't be done like a standard package installation. Therefore, it's normal for the audit warning to appear immediately after the agent installation.

However, it should disappear during the next audit. If you force an audit on the machine, does the audit warning disappear?

Regards,

Denis

Hello,

I tried forcing an audit on all the affected machines.
The warning is still present, but without success.

In the package status summary, I even see packages that I've uninstalled but are still showing up in the audit.

Regards

Hello,

I confirm what you're both saying.

It is indeed a bit strange to see this warning on all the workstations. But in the next audit cycle (without forcing it), the warnings disappear.

Regards

Hello David,

x-davidl wrote: ↑Jan 24, 2023 - 10:49 AM I confirm what you're both saying.

It is indeed a bit strange to see this warning on all the workstations. But in the next audit cycle (without forcing it), the warnings disappear.

It's a chicken-and-egg problem. Waptsetup.exe cannot be launched directly by the WAPT agent because of exclusive locks on the files opened by the service that need updating. Therefore, a scheduled task is created to update it a few minutes after the package is installed. Since the audit is launched immediately after installation, it shows a "not OK" status because the package version doesn't match the installed version. After the scheduled task has run and the agent has been updated, the audit should show an "OK" status.

Sincerely,

Denis

Hello Michel,

michel.merle wrote: ↑Jan 23, 2023 - 9:25 AM I tried forcing an audit on all the affected machines.
The warning is still there, but without success.

In the package status summary, I even see packages that I've supposedly uninstalled but that are still showing up in the audit.

Can you check the status locally on the machine (see online documentation) and force an inventory update (see online documentation)? If the status doesn't update, there might be a problem with the inventory reported by the machine.

Sincerely,

Denis