Hello,
since the update we've been encountering this error when editing packages, and we no longer see the local repository in the console.
Before uploading to the server, we had a section in the console to edit a package; now we no longer have the "
Windows Environment version 3505"
TZipRead ERROR
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
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
exact version 3505 -> 2.3.0.13505? Enterprise/Discovery?Geoffroy wrote: ↑Feb 15, 2023 - 12:04 PM Hello,
Since the update, we've been encountering this error when editing packages, and we no longer see the local repository in the console.
Before uploading to the server, we had a section in the console to edit a package; we no longer have the "
Windows Environment version 3505"
For the package editing tab integrated into the console, you need to check "show developer features" in the view/preferences menu.
Are you experiencing this problem only with this software, or with other .exe files as well? What is the size of the .exe file?
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
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
Hello,
Thank you for your initial response; that's exactly what I wanted.
Regarding the other issue, it occurs with all large packages under 2GB.
We are using Windows Server 2019 for the server and Windows 10 version 2.3.0.13505 for the console (Enterprise edition).
Thank you for your feedback.
Thank you for your initial response; that's exactly what I wanted.
Regarding the other issue, it occurs with all large packages under 2GB.
We are using Windows Server 2019 for the server and Windows 10 version 2.3.0.13505 for the console (Enterprise edition).
Thank you for your feedback.
Server: WAPT Enterprise 2.6.0.17226 on Debian 12;
Consoles: Windows 11
; Infrastructure: Windows
Consoles: Windows 11
; Infrastructure: Windows
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello,
following debugging with Geoffroy, there is indeed an issue with some large packages. The problem seems to stem from a compatibility issue with a file that was generated in zip64 format using Python (which was used in version 2.2 to generate WAPT packages), and then reopened using FPC/Lazarus (the console language, which is now also used in version 2.3 for generating WAPT packages). We are currently looking into how to address this issue.
If you need to make a change quickly, a workaround is to download the WAPT file using a browser and unzip it with 7-Zip (which is more tolerant of the format), then re-import the unzipped package directory into the console.*
Sincerely,
Denis
following debugging with Geoffroy, there is indeed an issue with some large packages. The problem seems to stem from a compatibility issue with a file that was generated in zip64 format using Python (which was used in version 2.2 to generate WAPT packages), and then reopened using FPC/Lazarus (the console language, which is now also used in version 2.3 for generating WAPT packages). We are currently looking into how to address this issue.
If you need to make a change quickly, a workaround is to download the WAPT file using a browser and unzip it with 7-Zip (which is more tolerant of the format), then re-import the unzipped package directory into the console.*
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
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
