MAPI error 14

Recently been getting MAPI error 14 on some workstations trying to send mail from Sage 50 through Outlook Classic. I have tried the troubleshooting steps listed online (repair office, repair MAPI32.dll, not sure what else to try as it's not happening to all users.

  • 0
    Suggested

    In most cases, problems with emailing between Sage 50 and Outlook Classic can be easily resolved by either running both applications as an Administrator, and with proper settings with Global Options of Sage 50 to allow third-party access. Keep in mind that the System Requirements for Sage 50 mention that 32-bit versions of Office will integrate with Sage 50, we do have clients (including ourselves) who use 64-bit versions of Office with Sage 50 for emailing.

    Our office provides paid support assistance for these types of technical issues and would be happy to assist you. Please reach out if interested in working with us on this.

    Tammi M. Ermerins ([email protected])

    Certified Sage 50/Peachtree Accounting & Crystal Reports Consultant & Trainer

    800-780-0700 / 954-961-0600, Visit Us on the Web at https://pcosupport.com

  • +1
    Verified Answer

    I had this issue too. As an addendum we were able to send emails to our own staff but no outside parties.

    Through a chat with a live agent at Sage 50 Support I found out that a recent Windows update 'broke' the MAPI function between Outlook and Sage 50. The first solution offered was to ensure that I only had one email account set up in Outlook. I had two accounts set up, so I deleted the lesser-used account (leaving only one account set up) and this fixed the issue for me.

    The support agent also said to delete and re-install the email account in Outlook to repair the MAPI function. We didn't need to do this after deleting the second account from Outlook, but this would have been our next step if the issue still persisted.

  • 0 in reply to Don68

    Do you know what update caused the issue?

  • 0 in reply to Don68

    You are correct, removing the second account worked. But once I add the second account back in the issue seems to return. Making a new outlook profile and adding both accounts doesn't seem to solve the issue either. There must be a fix without having to remove the second account.