Emailing a transaction crashes the program

• Damaged custom form
• Damaged *.PTR files
• Damaged *.DDF files
• One or more custom forms are corrupt
• Actian is damaged
• Incorrect security settings for Sage 50 to email or print
• Printer driver-related issues
• Damaged program path
• Recent (Aug 26, 2025 or later) Microsoft Office updates

CAUTION: Sage support can't assist with third-party products, hardware, report customizations, or state and federal tax questions. Refer to our Scope of Support for more info. Contact your Sage business partner, network administrator, or accountant for assistance.

 NOTE: Recent Microsoft Office updates (on or after 8/26/25 Version 2508 Build 19127.20154 and later) cause Sage 50 to crash after sending two or three emails. The current recommendation is to roll back to the 8/19/25 MS Office update - Version 2507 Build 19029.20208. 

Information on how to roll back to prior versions of Microsoft Office can be found here.

Also, the following workarounds have also resolved the issue:

• Removing all embedded images from forms in Sage 50 US
• Using webmail option in Sage 50 US as opposed to default MAPI clients
• Using an alternative MAPI client such as 32-bit editions of Thunderbird

Before that, try running Sage 50 and your email application as administrator:

1. Close Sage 50.
2. Right-click on the Sage 50 Icon.
3. Select Properties, then the Compatibility tab.
4. Check the box next to Run this program as an administrator.
5. Click Apply.
6. Click OK.
7. Follow steps 2 - 6 for the email program you’re using.
   • For Outlook, right-click on the Outlook shortcut, select Properties, click Advanced, and check Run as administrator
8. Test to make sure you can email in Sage 50 without the program crashing.
9. If the program still crashes, disable User Account Control.
10. Verify that you can now email.

Custom forms are missing
Sage 50 E-mail Writer not in Devices and Printers