Hi,

The tested fix on a 64 bit OS with a 32 bit Office 2013/2016 click-to-run install of Outlook, is to add this missing Registry key:

----------------------------------------------------------------------------------------------------------------------------

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows Messaging Subsystem]

"MAPI"="1"

-----------------------------------------------------------------------------------------------------------------------------

If that key is missing from the 32 bit subsystem on a 64 bit workstation, Sage 50 will not load MAPI32.DLL, because of the way it checks for the existence of MAPI.

This has been tested by me on Windows 7, 8, 8.1, and 10  with 32 bit Outlook 2013, and with 32 bit Outlook, 2016.

If your Outlook is 64 bit, then there's no hope of making it work, because Sage 50 is 32 bit.  If you have the non-installed, web-only email agreement with Microsoft, then you don't have Outllook.

I hope that helps, please post back!

Randy

Roger L said:

find mapi32.dll, mine is version 1.00.2536.0000 date stamped 2014.10.28 size 89600

On a 64 bit workstation, if MAPI32.DLL is not in the list of DLLs loaded on startup, it is likely because the registry key is missing from the 32 bit subsystem.  

On startup, Sage 50 queries the Registry to ask if MAPI is installed in the 'Windows Messaging Sybsystem'.   Since Sage 50 is a 32 bit program, it is redirected to the 32 bit part of the Registry (Wow6432Node):

From what I've seen, this key sometimes is deleted when a workstation is upgraded from older versions of Office.  Removing Office / Outlook and reinstalling a dozen times did not fix it.   Installing, removing, and reinstalling Thunderbird and Outlook in various combinations did not fix it.

To add the registry key, paste everything between the two lines below into Notepad, and save as (all files) MAPIKEY.REG and then merge it.  Of course, if 32 bit MAPI really isn't installed (64 bit version of Outlook, for example), this won't help.

----------------------------------------------------------------------------------------------------------------------------

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows Messaging Subsystem]

"MAPI"="1"

-----------------------------------------------------------------------------------------------------------------------------

vicktoriacameron said:

This post made me realize my computer is running Windows 7 64-Bit.

Your post sounds like you think this can't be fixed because Windows 7 is 64 bit.  Not at all - e-mail from Sage will work with all versions of the operating system (Windows 7, Windows 8, Windows 10) regardless of whether they are 32 or 64 bit.

And, the Outlook (and therefore Office) has to be 32 bit, and installed on the workstation (not a 'Cloud' version like 'Business Essentials).

vicktoriacameron said:

I wonder why it worked before my install of Microsoft 2016 Business

Microsoft 2013 and 2016 business sometimes do not properly install overtop an old installation of Office (2007, 2010, 2013), even when the original installation worked fine. 

So that's why it worked before you installed Office 2016.  My earlier post re the Registry key is commonly the fix to get Office 2013 or Office 2016 working with Sage 50, with Windows 7, 8, or 10 64 bit, with Outlook 2013 32 bit or Outlook 2016 32 bit.  

Hi vicktoriacameron, you can try Article 76977 see if it resolve your issue.

Still waiting for a fix also. 

How about you print to pdf and send those files?

I might have to, thou it would have been nice to do it in one step.

Can you suggest a good FREE PDF printer?

Sage automatically exports to pdf for free

adobe has a free reader

try running thunderbird app and you will be able to send straight from sage.  I dont know how it works but it works. Thats above my paygrade knowing technical stuff I just know how to run it and get around it.