Tranquil IT Forum

Hello,

WAPT version: 1.4.3.2.

On approximately 2000 workstations with the WAPT agent installed, an increasing number of computers are finding themselves with an empty package list (suddenly, I might add).

The method I use to solve this problem is a complete uninstallation (normal uninstallation + deletion of the c:\wapt directory) and reinstallation of the agent.

A simple uninstallation is not enough to restore everything to normal. You will understand that in the case of a mass application deployment, there are many computers on which it does not work. Therefore, a case-by-case approach is necessary.

How can this problem be explained? What is causing the issue? And how can this problem be resolved without having to delete the local WAPT database, which is responsible for future updates to the workstation?

Thank you in advance.

Patrice

Perhaps Office 2016... and its excessively long list of uninstallation keys.

On the server (if Debian):

Hi Hubert,

Actually, this is independent of Office 2016. It's been happening for many months now, and our user support team frequently encounters this recurring problem.

A few weeks ago, I came across a machine where everything was working fine. The package list was available on the web interface. Then, for no apparent reason, a few days later the list was empty, even though no WAPT installation had been performed.

What does the command you mentioned do?

The command increases the size of the `uninstall_key` field in the database (Wapt >= 1.6).
This field is declared as a `varcha(255)` and should be a list.
In Wapt 1.7, it is now a list.
However, in the meantime, you can work around the problem by increasing the field size.

This can generate the bug described in your case, as it prevents the list of deployed packages from being updated in the server's database.

Thanks so much!

I'm on CentOS 7. I imagine the principle is the same as on Debian!

However, I have version 1.4.3.2. So the command you wrote probably won't work?

I'm using MongoDB, right?

You are using PostgreSQL but in version 1.4, this field does not exist, so it is not the source of your problem.

Hello,

I have the same problem, so I'm taking the liberty of reviving this thread.
However, I'm on a Windows server (Version 1.8.2.72.65)
and ALL workstations have an empty package list.

PS: The workstations are on their second WAPT server (formerly server 2008, now server 2019).