[SOLVED] Update package error

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
Locked
thomas789
Messages: 95
Registration: May 31, 2021 - 3:44 p.m.

December 11, 2023 - 3:46 PM

Hello,

I'm using a WAPT 2.4.0 agent on Windows 11, with
a WAPT console (version 2.4.0.14058)
and a WAPT server (version 2.4.0)

. I'm experiencing package update problems (when I click "Launch package update") for no apparent reason; there are no logs on the console, only the error message. I've reinstalled the console, but that hasn't fixed the problem.

Sincerely, Thomas.
Attachments
image.png
image.png (37.71 KB) Viewed 4009 times
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

December 11, 2023 - 3:59 PM

That's strange, it crashes during the package upload.

Does this happen every time?
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

December 11, 2023 - 4:17 PM

Hello Thomas,

are you getting the same error when you run the update with a recently downloaded update_package from the store (i.e., downloading the tis-chrome package from the store to get the latest update_package)?

Website developers modify their sites from time to time, and sometimes it's necessary to update the update_package function.

Regards,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
thomas789
Messages: 95
Registration: May 31, 2021 - 3:44 p.m.

December 11, 2023 - 5:34 PM

I just tried with three example packages:
- In Adobe, the error message appears instantly when I click "Upload selected packages."
- In Teams, it appears after the "Downloading:" message (even though I cleaned the %TEMP% folder).
- In Chrome, whether it's the Linux or Windows version, I get the same error message.

What's surprising is that you haven't offered any new versions of these packages to potentially fix these update problems.

However, I was able to update Firefox on Windows, so I think the issue stems from these packages and not from my console.

Sincerely.
Attachments
Screenshot 2023-12-11 172821.jpg
Screenshot 2023-12-11 172821.jpg (92.46 KB) Viewed 4001 times
Screenshot 2023-12-11 164343(1).jpg
Screenshot 2023-12-11 164343(1).jpg (88.32 KB) Viewed 4001 times
Screenshot 2023-12-11 164534.png
Screenshot 2023-12-11 164534.png (235.68 KB) Viewed 4001 times
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

December 11, 2023 - 5:50 PM

Chrome is displaying a different message than before; it's trying to access the API, so it's using the old package (the API is no longer working).

For Teams, it uses "os.rename," which has been removed from our internal package, so you're using the version from 8 months ago.

With the update package, you don't benefit from the new setup.py file we provide.

For Adobe Reader, the upload to the server failed.
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

December 11, 2023 - 5:51 PM

Hello Thomas,
thomas789 wrote: Dec 11, 2023 - 5:34 PM ...
What's surprising is that you haven't offered me any new versions of these packages to potentially fix these update problems.
...
If you have updated the package locally to such a recent version, the console will not offer the one from our store. However, you can retrieve it by disabling "newer version only" or by accessing the store's webpage.

You can then check the differences in the update_package() functions

Sincerely,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Locked