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
WAPT package update
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Has there been a key change on wapt?
Is the wapt agent for the workstations correctly version 1.8.2?
Is the wapt agent for the workstations correctly version 1.8.2?
-
f.belon@aerotec.fr
- Messages: 3
- Registration: Apr 01, 2021 - 10:17
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,
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,
-
f.belon@aerotec.fr
- Messages: 3
- Registration: Apr 01, 2021 - 10:17
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.
In any case, thank you for looking into my problem.
Fabrice
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.
In any case, thank you for looking into my problem.
Fabrice
