Navigate
Wasp Helpdesk
  • Register

  • or
  • Login
    Need a password reminder?
or
Contact Us
  • Get in touch

    Send us an email

  • Start a chat session

  • Knowledgebase Read help articles
  • News News & updates
  • Contact Us We are here to help
  • Training View our options
  • Product Sunsets Non-Supported Products
Barcode System Consult
Barcode Printer Consult
Barcode Label Consult
  • Portal
  • Knowledgebase
  • Software
  • Labeler
  • Version 7
  • Labeler v7.1.5: At quit, Unhandled Error appears, on Windows 10 v1803 or Windows Server 2016 v1607
Subscribe Download PDF

Labeler v7.1.5: At quit, Unhandled Error appears, on Windows 10 v1803 or Windows Server 2016 v1607

Scott Leonard
2025-01-07
in Version 7

On Windows 10 v1803 or Windows Server 2016 v1607, when Labeler v7.1.5 is quit normally (X out of application window, File tab, Exit), a message appears:

Unhandled Error
An error occurred in the application. For more information, please check the log file WaspLabelerV7.log
OK

L7-unhandled-error.png

At this time, the cause is unknown other than a change introduced in Windows.

This error can be ignored. If there are unsaved changes when quitting, Labeler will prompt and allow saving changes before throwing the error.

Wasp is investigating and will update this article if any workaround or fix is found.

More information:

Error verbiage from WaspLabelerV7.log:

2018-06-07 15:34:08.198          2 ERROR       | ------------------------------ Unhandled Exception Information ------------------------------
2018-06-07 15:34:08.198          2 ERROR       | ------Exception Message-------
2018-06-07 15:34:08.198          2 ERROR       | A task was canceled.
2018-06-07 15:34:08.198          2 ERROR       | ------------------------------
2018-06-07 15:34:08.198          2 ERROR       | ------------Source------------
2018-06-07 15:34:08.198          2 ERROR       | mscorlib
2018-06-07 15:34:08.198          2 ERROR       | ------------------------------
2018-06-07 15:34:08.198          2 ERROR       | ------- Stack Trace-----------
2018-06-07 15:34:08.198          2 ERROR       |    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
                                    |    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
                                    |    at System.Windows.Threading.DispatcherOperation.Wait(TimeSpan timeout)
                                    |    at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherOperation operation, CancellationToken cancellationToken, TimeSpan timeout)
                                    |    at System.Windows.Threading.Dispatcher.Invoke(Action callback, DispatcherPriority priority, CancellationToken cancellationToken, TimeSpan timeout)
                                    |    at MS.Internal.WeakEventTable.OnShutDown()
                                    |    at MS.Internal.WeakEventTable.WeakEventTableShutDownListener.OnShutDown(Object target, Object sender, EventArgs e)
                                    |    at MS.Internal.ShutDownListener.HandleShutDown(Object sender, EventArgs e)

Rate the quality of this page

This page was helpful :) :( This page was not helpful

27 of 62 people found this page helpful


Quick Jump
  • Wasp Helpdesk
  • Knowledgebase
  • News
  • Contact Us
Top
Helpdesk software provided by Deskpro