Page 1 of 1

WAPT package update

Published: April 1, 2021 - 10:55 AM
by f.belon@aerotec.fr
Hello everyone,

I have a WAPT 1.8.2.7334 server that worked perfectly until the last update. Since version 1.8.2.7334, I've been having trouble updating packages already installed on the machines.

For example, I have version 89.0.4389.72 deployed on my machines, but when I download version 89.0.4389.90, it's in my private repository, but the package doesn't update on the machines where it's installed. Even when I run "Check for Updates" and then "Refresh," the machine is marked as up-to-date, even though the package is still the old version. This behavior affects all the packages already in my private repository that I want to update.

Can anyone point me in the right direction?

WAPT 1.8.2.7334 is installed on a Windows server and administered from a Windows machine.

Sincerely,

Fabrice

Re: WAPT package update

Published: April 1, 2021 - 2:53 PM
by sfonteneau
Has there been a key change on wapt?

Is the wapt agent for the workstations correctly version 1.8.2?

Re: WAPT package update

Published: April 2, 2021 - 5:01 PM
by f.belon@aerotec.fr
Hello,

No WAPT key changes were made during or after the update to version 1.8.2.7334.

Yes, all clients upgraded to version 1.8.2.

Regards,

Re: WAPT package update

Published: April 14, 2021 - 4:31 PM
by f.belon@aerotec.fr
Hello,

after searching for a while, I've finally figured out my mistake:
The WAPT desktop client was reinstalled on my computer because I changed machines at the same time as the WAPT update.

When reconfiguring the client on my computer, I didn't use the same "WAPT Package Prefix" as the one used during the original installation :( . So, for WAPT, the packages weren't the same...

After correcting this, everything is working fine now. :D

In any case, thank you for looking into my problem.

Fabrice