Resolve Sage 50 Error A Managed Exception was Caught

Sage 50 clicking maintain .NET Framework is on, uninstall/reinstall Sage 50 to a new Program Path.

The exact error message is shown…

Error: “A managed exception was caught”

Causes for Sage 50 Managed Exception Error

The cause for the Sage 50 error was a managed exception was caught due to blank fields in the Pay Levels/Pay Info area, before converting your data to the Sage 50 2021.1

• Microsoft .NET Framework is disabled or damaged
• NET errors in Event Viewer
• Data is damaged
• Company damaged by Crypto Wall virus
• Backup files damaged by Crypto Wall virus
• The company data folder is damaged
• Damaged DDF files
• Damaged DDF.zip content.

Solution for Sage 50 Error A Managed Exception was Caught

To fix the Sage 50 error regarding managed exceptions during payroll setup in releases 2021.1 or 2022.0, revert to version 2021.0, restore a prior backup, and update pay type names and GL account numbers. After completing the payroll setup, upgrade Sage 50 to the latest version to resolve the issue.

Step 1: Damaged DDF Files in Company Directory

• Go to the top to File then down to Open Company
• Note the Directory listed next to the company name.
• Browse to this location in Windows File Explorer
• Select all DDF files.
• Right-click, and then click Delete.
• Delete ATMNTBDL.DAT, ATTCHMNT.DAT, ALARM.DAT, ALERT.DAT, UserPref.DAT, and COSESS.DAT.
• Open Sage and your company.
• Click Yes when prompted to recreate the deleted files.
• Reopen Sage and verify that you can now open a maintenance window.

Step 2: If the issue occurs in a Sample Company

• Damaged DDF.zip content
  • Browse to the company data location. See Article ID 10165: How to find data path and program path
  • Rename the Reports folder to Old Reports.
  • Repair the installation.
• Damaged .NET framework
  • Verify that Microsoft .NET Framework is on in Windows Features
  • If the Microsoft .NET Framework is off, turn it on.
  • Open Sage 50 and verify that can click Maintain.
  • If Microsoft .NET Framework is on, uninstall/reinstall Sage 50 to a new Program Path.

Step 3: If not happening in a Sample Company

• Run Data Verification on the machine that hosts the data.
• If Data Verification does not resolve the issue and the error does not occur in a sample company, create a clean data folder.
• Open the version of the company with the directory you just created and verify that the maintenance windows are open.

Step 4: Uninstall / Reinstall Microsoft .NET Framework

• Uninstall .NET 4.5 in Windows Features.
• Reboot the computer.
• Install .NET 4.5 in Windows Features. Allow Windows to download the installation files and install them.
• Reboot the computer.
• Open Sage and verify that you can now open a maintenance window.

 Note: If the computer was infected by the Crypto Wall virus, the backup files may also have been damaged. Restore a backup that was stored on a device that was not infected.