Issue: Unhandled Exception when Opening a Custom Report

Issue: Unhandled Exception when Opening a Custom Report

If you have been working on a custom report and after saving it you get an unhandled exception error when you try to reopen it, you probably want to know if there is a way to fix that error.

The answer to that question depends on whether you know the last few operations before saving the report. In other words, do you have a good idea of what broke the report? If you know the cause of the error, you can fix it. Otherwise, the report may be corrupted and unrecoverable.

If you know what operation broke the report, here is the procedure to get access to the report in the Report Designer.

Open the factory database using the Microvellum SQL CE Viewer. Double click on the ReportTemplates table to open it. In the Name field, find the report that throws the exception. In the field named ReportFile for that row, right-click on the cell containing the "ByteArray" data and click "Save File to Disk." In the Save As dialog box, navigate to where you want to save it, give it a name, and an .MRT file extension and click Save.

Open a known good report in the Report Designer (Toolbox or Production). Click the Open button, as shown in the attached screenshot. Navigate to the location you saved the MRT file, select it, and click Open.

This will open the report in the Designer without any dataset connection. What that means on a practical level is that you won't be able to Preview the results of your work after revising the report. You will need to know what action broke the report, undo that action by setting it back to what it was before, or fix it. Then save the report and continue with the procedure below.

Once the MRT file has been repaired, the next step is to import that file back into the factory database. If the Microvellum SQL CE Viewer is not already open, open it, and double click on the table ReportTemplates to open it. In the Name field, again, find the report that throws the exception. In the field named ReportFile for that report, right-click on the cell containing the "ByteArray" data and click "Import File from Disk." Navigate to the location of the MRT you exported above, select it, and click Open.

If the repair was successful, you will now be able to reopen Toolbox or Production and work with the report.

To prevent this from happening, always be sure to check a report for errors before saving it.
    • Related Articles

    • Understanding Custom Formatting in Report Designer

      The articles in this section of the Knowledge Base involve Text Formatting for display in your reports. To learn more about Text Formatting and how to access this section within the Report Designer, see Understanding Text Formatting in the Report ...
    • Issue: Report Unexpectedly Missing Data

      Some Users tell us that infrequently a report may be displayed that is missing data when previewed. There are various possible reasons for this issue, but one cause may be a defective report dataset definition. This article explains a pre-test to ...
    • Overview: Toolbox Report Designer Access

      Microvellum build 15.5.1415 or higher required.   The Microvellum report suite incorporates reports that are designed to be printed from Toolbox, and other reports that are designed to be printed from the operation modules (Production). All reports ...
    • Report Training Tutorial 1: Report Designer Basics

      This is the first of a series of five Reports Training Tutorial videos.  This video presents some basic concepts that will be useful for first-time users of Report Designer.  By the end of this video, you will have some familiarity with the user ...
    • Working in the Sub Reports Editor of Report Designer

      The articles in this section of the Knowledge Base involve working with Sub Reports for display in your reports. To learn more about Sub Reports, and how to access this section within the Report Designer, see Understanding Sub Reports in Report ...
    • Recent Articles

    • Toolbox Release Notes | Build 24.1.1105.641

      The following release notes apply to Toolbox build 24.1.1105.641 Nesting Fix Fig. 1: The fatal error that would occur during processing. There was reportedly an issue that occurred when clients attempted to process a work order using the nesting ...
    • Microvellum Foundation Library Release Notes | Build 24.1025

      The following release notes apply to Microvellum Foundation Library build 24.1025. Additions Added new global variable “Remove Stop Dado On Bottom Edge” for wood drawer boxes. Check this option to run the dado through at the bottom of the sub front ...
    • Toolbox Release Notes | Build 24.1.1030.641

      The following release notes apply to Toolbox build 24.1.1030.641 Routing and Profile Fixes Several issues were found with routing and polyline paths: Fig. 1: Horizontal routes off of a part disappearing (left) and appearing correctly (right). When ...
    • Toolbox Release Notes | Build 24.1.1010.641

      The following release notes apply to Toolbox build 24.1.1010.641 Biesse Winstore Fix Several issues with the Biesse Winstore plugin have been resolved: There was an issue that would sometimes occur wherein materials that were intended to stack wound ...
    • Toolbox Release Notes | Build 24.1.1001.641

      The following release notes apply to Toolbox build 24.1.1001.641 HBore Toolfile Fix Fig. 1: The location in the Toolfile UI where the error would occur. There was an issue reported with the functionality of the Horizontal Boring Machine setting in ...