All Collections
Webgility Desktop
Advice & troubleshooting
Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. - Webgility Desktop
Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. - Webgility Desktop

Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue.

David Pond avatar
Written by David Pond
Updated over a week ago

An unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately. Exception of type 'System OutofMemoryException' was thrown. - Webgility Desktop

Reason:

This is a generic error message that indicates that an exception (an unexpected error) has occurred in the Microsoft .NET Framework application, but there is no specific error handling code to handle the exception. This message is often displayed in a dialog box when the Webgility Desktop encounters an unhandled exception, and it may include additional details about the exception.

Steps to rectify this error for Webgility Desktop:

  1. Close Webgility Desktop and Scheduler(if running) on all the Webgility machines.

  2. Now on the primary Webgility Database machine perform database upgrade (UnifyDBUpgrade) with the help of the steps mentioned in the help article (LINK)

  3. If the issue persists then on the same machine restart the SQL Services for Webgility Database.

  • Open Windows Explorer.

  • Navigate to the "Services" section.

  • Search for the SQL Server service corresponding to your database name (WEBGILITY/UNIFY).

  • Right-click on the SQL Server service.

  • Select "Restart" from the context menu that appears.

  • Once done then check again.

  1. If the issue persists then try to perform a clean reboot of the Webgility database machine and then check again.

If you are unable to resolve this issue or need assistance please contact Webgility Support.

Did this answer your question?