Unhandled exception occurred during FW Upgrade to 2.7
-
- Posts: 4
- Joined: Sun Nov 27, 2022 3:12 pm
Unhandled exception occurred during FW Upgrade to 2.7
System.Threading.Tasks.TaskCanceledException: A task was canceled.
at Peg.UI.RJesHttpClient.BaseHttpClient.<RequestAsync>d__10`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Peg.UI.RJesHttpClient.BaseHttpClient.<RJesRequestAsync>d__12`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Peg.UI.RJesHttpClient.FirmwareUpdateHttpClient.<UpdateDeviceAsync>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Peg.UI.View.FirmwareUpdate.FirmwareUpdateView.<UpdateDeviceFirmwareAsync>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Peg.UI.View.FirmwareUpdate.FirmwareUpdateView.<Ribtne_Update_ButtonClick>d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
Re: Unhandled exception occurred during FW Upgrade to 2.7
Thank you for reporting this.
We are investigating what is the cause of this error.
We are investigating what is the cause of this error.
-
- Posts: 4
- Joined: Sun Nov 27, 2022 3:12 pm
Re: Unhandled exception occurred during FW Upgrade to 2.7
Thanks Evan. If it helps I got the same issue on two different computers, and also tried uninstalling and reinstalling the Unity app. Both computers were on Windows 11 BTW.
-
- Posts: 4
- Joined: Sun Nov 27, 2022 3:12 pm
Re: Unhandled exception occurred during FW Upgrade to 2.7
Hi Evans.
Is there any update on this issue yet?
Further testing on the Quad 12V Output ports not staying ON shows that if I turn to On, save it using the icon, and save the profile, close the Unity App and then re-open the App, the Output Ports are still ON, BUT if I attempt to reboot the device, it defaults back to OFF. If I power off the device, and then power back on and reopen Unity it also defaults back to OFF. This means before each session using the device on my scope I will need to connect it to my laptop, change the setting and then close the app, but power will have to stay on at all times, else I will lose the setting. This is obviously not acceptable.
-
- Posts: 4
- Joined: Sun Nov 27, 2022 3:12 pm
Re: Unhandled exception occurred during FW Upgrade to 2.7
The problem turned out to be a Windows OS issue. Upgrade fails on multiple Windows 11 computers but succeeds on Windows 10.
Thanks for the excellent support.
Thanks for the excellent support.
Re: Unhandled exception occurred during FW Upgrade to 2.7
Thank you for the feedback.
I check with latest Windows 11 which is working fine.
We have seen issues when customer that use KMS pico (serial activator) in Windows which modifies lots of system variables and crashes the update process.
Will continue to investigate the issue.
I check with latest Windows 11 which is working fine.
We have seen issues when customer that use KMS pico (serial activator) in Windows which modifies lots of system variables and crashes the update process.
Will continue to investigate the issue.