WAPTUPGRADE update not possible on some machines
Published: October 19, 2020 - 2:03 PM
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.
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.