Hello.
I'm encountering a 404 error ("404 client error: 404 Not Found Resource not found") during the build process when I remove a package from a group.
Current version: 2.4.0.14058 (on Windows).
Apparently, the error wasn't present in version 2.3.
If anyone has any ideas...
Regards
[SOLVED] Error 404 when deleting a packet from a group
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
Good morning,
As discussed over the phone, please run the following cmd command on the server:
Modify the path as needed
Sincerely,
Jimmy
As discussed over the phone, please run the following cmd command on the server:
Code: Select all
wapt-scanpackages "C:\wapt\waptserver\repository\wapt"Sincerely,
Jimmy
Hello and thank you for the information.
Unfortunately, it doesn't change anything.
I created a new group to test, and I can remove a package from it without error. However, this is a group that has never been deployed; perhaps that makes a difference.
In the worst-case scenario, I'll delete the problematic group and replace it with a new one on all machines... hoping the bug doesn't reappear. I admit I'd prefer to be able to fix the problem without having to redo everything.
Sincerely,
Unfortunately, it doesn't change anything.
I created a new group to test, and I can remove a package from it without error. However, this is a group that has never been deployed; perhaps that makes a difference.
In the worst-case scenario, I'll delete the problematic group and replace it with a new one on all machines... hoping the bug doesn't reappear. I admit I'd prefer to be able to fix the problem without having to redo everything.
Sincerely,
