Reports not working after upgrading Everest


This article outlines the solution when some reports cannot be generated after upgrading Everest to a newer version.

The following error messages can be encountered when generating some reports after an upgrade:

Error in Reports, Error Number: 588
  • Error Message: Error: 723 Error in File <path to tmp file>: Failed to retrieve data from the database.
  • Error Message: Error: 722 Error in File <path to tmp file>: The rowset column could not be found.
  • Error Message: Error: 530 Error in File <path to tmp file>: File I/O error.
  • Error Message: Error: 524 Error in File: Print job busy.


The above errors can occur when the stored procedures that are invoked when reports are generated fail to properly update automatically during the upgrade process.

The solution when this happens is to review all SQL Server stored procedures and manually correct errors in any invalid stored procedures.

This external article provides a quick way to check if your SQL database has any invalid objects, including stored procedures.

You can modify stored procedures accordingly from SQL Server Management Studio to correct any invalid references such as the one shown in the example below:


For more information on how to modify stored procedures and save the modifications, see Error in Reports when printing or emailing invoices with tracking number

Review the following articles for additional solution steps if users are still unable to run reports after validating the stored procedures:


Ensure you have no invalid stored procedures then run the failing reports to confirm that the reports can be generated successfully. If the errors persist, submit a support request for further troubleshooting.

Back to top



Please sign in to leave a comment.