Mr. Mth said:

my Sage 50 application seems to not load the MAPI32.DLL driver at start up.

Hi Mathieu,

The tested fix I came up with on a 64 bit OS with a 32 bit Office 2013/2016 click-to-run install, is to check for, and add this missing Registry key if necessary:

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

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 that key is the way it checks for the existence of MAPI.

(used the Support Info from Help | About to find out WHAT, and PROCMON from SysInternals' ProcMon to find out WHY. 

If your system is not 32 bit, then the above fix won't work, and probably won't be necessary, because there is no confusing 32 bit subsystem.

If your Outlook is not 32 bit, there is no fix, because Sage 50 (as of 2019) is 32 bit and can't load a 64 bit DLL.

I hope that helps, please post back!

Randy Wester

Hi Randy,

Thank for your answer.

Unfortunately, the register editor tells me the key is already set to "1"...

Also, FYI, I too am using W7-64 with O365 (Outlook 2016) 32 bits.

I'm sorry that didn't work.  I assumed you tried the other Sage knowledgebase recommendations already?

There are other keys for MAPI under:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Wow6432Node\Microsoft\Windows Messaging Subsystem

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Messaging Subsystem

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Messaging Subsystem

As far as I understand, Windows will read the key from WoW6432Node, then present it to any 32 bit program running inside the 32 bit subsystem as if it was in:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Messaging Subsystem

All I can suggest is to try using PROCMON to find where Sage 50 is trying to load MAPI from, and why it fails. (file not found, key not found, access denied, etc.)

I spent too much of a weekend trying to figure out why it failed to read a key that looked like it was right. there. until I figured out that the key is actually read from Wow6432Node.

If all else fails, it may be possible to email using SMTP, but then of course it won't be in your Outlook sent email.

RandyW said:

I'm sorry that didn't work.  I assumed you tried the other Sage knowledgebase recommendations already

Haha! You assumed right! Spent half of my week reading the forums and KB... Also noticed I'm not the first one you try to help out with this issue! This is very much appreciated! 

RandyW said:

There are other keys for MAPI under:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Wow6432Node\Microsoft\Windows Messaging Subsystem
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Messaging Subsystem
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Messaging Subsystem

Checked all those and they all seem ok... 

RandyW said:

All I can suggest is to try using PROCMON to find where Sage 50 is trying to load MAPI from, and why it fails. (file not found, key not found, access denied, etc.)
I spent too much of a weekend trying to figure out why it failed to read a key that looked like it was right. there. until I figured out that the key is actually read from Wow6432Node.

If all else fails, it may be possible to email using SMTP, but then of course it won't be in your Outlook sent email.

PROCMON seems to be a very usefull tool!! Thanks for pointing this one out! I started playing with it yesterday, but couldn't pinpoint exactly where the exception occurs... I'll be checkin it deeper next week.

As for SMTP, well, I also get an error this solution... My system administrator is actually trying to figure out why the server is refusing the connection when it accepts connexion from other services or application, including Outlook... 

On my side, I'm trying the same configuration on another machine to see if it's my machine that is problematic.

This is all way more complicated than it should be, haha!

Thanks again for your help! I'll keep you posted if I find any solution.

Have a nice week end! 

- Mathieu