Hello,
I have just upgraded our WAPT server to version 1.8.2 (Community / Debian 4.19.0-6-amd64). The agent and WaptUpgrade update went smoothly on several dozen machines in our network (mostly Windows 10), but four of them (Windows 10 Pro) are stuck on the WaptUpgrade update from version 1.7 to 1.8 with the following message: CalledProcessErrorOutput
: Command 'schtasks /Create /SC ONCE /TN "fullwaptupgrade" /TR "c:\\users\\public\\documents\\wondershare\\creatortemp\\waptdeploy.exe --hash=d86cb1c1032ed801043b0fa16c5696dd2f5e3af48b86cf8889d005bc41d03348 --waptsetupurl=c:\\users\\public\\documents\\wondershare\\creatortemp\\waptagent.exe --wait=15 --temporary --force --minversion=[u\'1.8.2.7267\', u\'24\']" /ST 13:44:03 /RU SYSTEM' returned non-zero exit status -2147467259.
Output: Error: The value for the '/TR' option cannot contain more than 261 characters.
Does anyone have any idea what's causing this problem?
The console is installed on a PC running Windows 10 Pro (1909), but I don't think that's relevant here...
Thanks in advance for your help.
Manuel.
WAPTUPGRADE update not possible on some machines
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
Hello,
my problem persists and only affects 4 workstations out of nearly 200. It seems these 4 workstations are also refusing the deployment of the new agent in version 1.8, which must be installed manually. I'm giving up for now, but if anyone has any ideas or is facing the same problem, I would be happy to discuss it with them...
Manuel.
my problem persists and only affects 4 workstations out of nearly 200. It seems these 4 workstations are also refusing the deployment of the new agent in version 1.8, which must be installed manually. I'm giving up for now, but if anyone has any ideas or is facing the same problem, I would be happy to discuss it with them...
Manuel.
Hello,
I finally managed to resolve this issue simply by uninstalling and reinstalling the agent on the affected machines.
After further consideration, I think the problem stems from the presence of the hash in the command used to create the scheduled task. Perhaps the agent was installed manually, or something caused the WaptDeploy to be unsigned on these machines, resulting in the hash being added to the command, making it longer than 256 characters and preventing execution.
Manu.
I finally managed to resolve this issue simply by uninstalling and reinstalling the agent on the affected machines.
After further consideration, I think the problem stems from the presence of the hash in the command used to create the scheduled task. Perhaps the agent was installed manually, or something caused the WaptDeploy to be unsigned on these machines, resulting in the hash being added to the command, making it longer than 256 characters and preventing execution.
Manu.
