Page 1 of 1

WAPTUPGRADE update not possible on some machines

Published: October 19, 2020 - 2:03 PM
by Moloc
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.

Re: WAPTUPGRADE update impossible on some machines

Published: November 9, 2020 - 5:00 PM
by Moloc
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.

Re: WAPTUPGRADE update impossible on some machines [Resolved]

Published: May 5, 2021 - 1:43 PM
by Moloc
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.

Re: WAPTUPGRADE update impossible on some machines

Published: May 5, 2021 - 7:31 PM
by vcardon
Also check the antivirus/AV configurations that are installed on your 4 workstations and that may be different from the rest of your network.