Outlook 2013 mapi

 From what i've read there are components missing from Office 365 C2R.

There are no components missing from C2R that would affect Sage.

There are things missing from the outlook that comes with the Home subscription - features that are used only by Exchange server, such as support for Online Archives, but Sage doesn't use those features or work with the proplus subscription (a C2R build which has the missing features).

I had this same problem with a 32bit app that stopped working when I uninstalled Office 2010.

I was just cleaning up, figured I didn't need it as I had installed Office 2013.

I confirmed it was 32bit Office 2013/Outlook. And the app using MAPI is an old 32bit app.

After lots of stressful reading and testing I came across this recommendation...

   http://www.slipstick.com/outlook/outlook-not-recognized-default-email-client/

...which says to go to the control panel and select "Quick Repair" for Office 2013.

That took about 5 minutes, and magically everything works again.

My old app using MAPI happily sends email again.

I think 32bit Outlook2013 is indeed MAPI compliant but something got messed up in the registry when uninstalling the older Outlook2010. Anyhow, all is working now, no idea whether this will fix Sage problems, but may be worth a try.

Trying to get my reports to email from Sage and this worked!!

As per the article in the link I went to the control panel and set Outlook as my default email client.  I had already thought it was set as my default but this has definitely made a difference.  All my reports now pop nicely into my inbox (used to be Drafts folder but never mind) ready for sending.  

After lots of stressful reading and testing I came across this recommendation...

   http://www.slipstick.com/outlook/outlook-not-recognized-default-email-client/

...which says to go to the control panel and select "Quick Repair" for Office 2013.

That took about 5 minutes, and magically everything works again.

My old app using MAPI happily sends email again.

I've got two Dell Windows 7, 64 bit workstations on my desk.   From one of them, I can send Emails through Click-To-Run Office 2013 or 2016 from Sage 50.   From the other, I can't.  

I have tried every fix that a web search could turn up, even some of the wing-nutty ones, and every conceivable combination of removal and re-installs of Office and Sage 50, SFC /SCANNOW, all the Office cleanup / removal tools, etc.    I've run side-by-side procmon traces to see where the one (working) workstation finds and loads MAPI on startup, and the other one doesn't appear to try.  

The results of MFCMAPI are identical, the file sizes / versions / registry entries / configuration files appear to be identical.

The one that *works* shows that it has loaded c:\windows\system32\MAPI32.DLL (under help | About | Support Info), however the reported file size matches the one on disk under c:\windows\SysWOW64.

The workstation that does NOT work, does not show MAPI32.DLL on the dependency list.

If Sage would deign to publish whatever secret method they are using to 'discover' whether MAPI is available (or not), it might help solve this.   I'm so far down the rabbit hole on this that it has gone from an issue to a task to a project to a quest. 

There are other things that Sage could do, such as if the relied upon DLL doesn't load at startup, disable the 'email' button.   Or at install, a warning that the installation couldn't find an email profile.   Or a test utility.   Or sod it all and make SMTP an option.   Or, instead of posting a link to where Microsoft explains how MAPI has changed, change the Sage software to recognize the change.

Back-and-forth finger-pointing and lame work-arounds make both Microsoft and Sage look like greedy jerks. 

...came across this recommendation...

   http://www.slipstick.com/outlook/outlook-not-recognized-default-email-client/

...which says to go to the control panel and select "Quick Repair" for Office 2013.

I have tried that fix as well.   Quick repair, online repair, uninstalled, Office 2013 and 2016 32 bit,  Office clean-up utility, installed Thunderbird, removed it, etc...  

Can email from QuickBooks all day long, but still can't send email from Sage 50 2015.3 (using Office 2013 Home ClickToRun, 32 bit, on one of two Win 7/64 bit workstations.   The other workstation taunts me by loading mapi32.dll and sending email with no problem)

I'm testing at home, but really would like to fix this for 9 of 10 workstations at our office that are stuck with Office 2007 because of Sage 50, until we get a resolution.  

A backup, FDISK /MBR and reinstall Windows would have been SO much faster, but I have stubbornly looked for a fix instead of repaving.  

Its clearly a Microsoft problem.  From what i've read there are components missing from Office 365 C2R. How is this sages problem?

Well... Sage development and support are way confused on the distinction between Office click-to-run, the web application, and Office click-to-run, the installation method for the full local installation. 

As another example of keeping up with technology: For the '2008' release in late 2007, Sage completely changed their back-end data storage - from an Access file database to a MySQL daemon that communicated over TCP/IP.

But it took until the recent '2016' release SEVEN YEARS LATER for them to remove some of these dead menu options:

Maintenance | Database Utilities | Compact Database   (does absolutely nothing but open and close the MySQL database)

File | Backup | [ ] Compact data before backing up to save disk space  (adds '1', '2', etc. to the backup filenames, otherwise does absolutely nothing.  May have once been used for backing up to multiple floppy disks, or for choosing compressed / uncompressed output.)

And rather than fix the ratio calculations in the 'Daily Business Manager', they just removed them.

Years ago, worked for a bureaucratic software company (not Sage) through the transition from a startup to when it was run by MBAs and CAs 'Down East'.   Every change had to bring in money or it couldn't be made.   No refactoring, no non-crash bug fixes, the only interface changes allowed were fixing typos, no new features whatsoever.  

I remember going from being a progressive, customer focused company on the leading edge, to vainly trying to slow the inevitable grinding downward spiral of budget and staff cuts, to just... leaving the sinking ship.

So... I blame Sage.   There evidence strongly suggests that someone wrote Email as a cheap hack long, long ago, and they haven't the skills or the staff to do a proper job of it now, or perhaps even the wit to understand the need.  

Diane, your theory that stupidity at Sage is the root cause, has not been disproved by any of their 'technical bulletins' that recommend that I buy 32 bit 'emaling software'.   Yes, they almost certainly are doing something deeply, thoroughly stoopid.  

Sage is a huge corporation run by people that have no clue that small business (virtually the only customers for their 'Sage 50' product) are not scaled-down big businesses.  

Typically they have no access to support staff or even installation media.   They buy a laptop at Wal-mart and pick Sage 50 off the next shelf, and then try to use the Office 2013 that came with the laptop to send Email.  

I'm in the unique position of having access to Microsoft Certified Professionals that charge a hefty monthly fee to provide 'support' for our company.  

That support consisted of a quick Google search, then when they found the confused drivel that Sage vomited forth they decided they had done their job by passing us the link.   'See? can't be fixed!' when what 'Not Supported' from Sage really means 'We in Tech Support have no idea how to fix this'.

As customers of both Sage and Microsoft, we're stuck in the middle, doing internet searches, posting questions on forums where everyone is as stuck as we are, then reading the great works of Chen and Russinovich by the light of an old CRT monitor, and running various diagnostic utilities in a vain hope of stumbling across the secret decoder ring that would disclose the particulars of the now-stupid thing that some long-gone Sage programmer did during a summer internship, in 1998.

So, eventually...  Mark's trusty old SysInternals came through...

Procmon showed that when Sage 50 Canadian 2015.3 'Quantum' loads on a system where Email works, it does, indeed, look for:

HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows Messaging Subsystem

HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows Messaging Subsystem\MAPI

If the result is 'SUCCESS', it calls 'CreateFile' for MAPI32.DLL in the local directory, then locates:

C:\windows\SysWow64\MAPI32.DLL

On the broken workstation, the result from RegQueryValue for

HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows Messaging Subsystem\MAPI

is

'NAME NOT FOUND'.

and the Sage software never even attempts to find MAPI32.DLL or Outlook.

So it would seem that copying the Registry keys has a good chance of making it work, although it's like having to make 3 left turns because our Sage car's broken steering can't turn right.

Hi Stephen,

After a number of unbillable hours that doesn't bear thinking about, I have discovered this difference:

On Windows 7 64 bit with installed Outlook 2013 'click-to-run' 32 bit, and Sage 50 2015.3 Canadian Quantum Edition:

Save this and run it, or manually add this key:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows Messaging Subsystem]
"MAPI"="1"

This key was already there, but is either hidden by the operating system (most likely) or ignored by Sage 50 (possibly) on 64 Bit Windows 7:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Messaging Subsystem]
"MAPI"="1"

Since Microsoft has cancelled their old MSDN software program that let me test under various operating systems, and I no longer pay Sage to be their 'Partner' because I am but a humble millionaire, I have only verified this fix (remove it, the problem appears, put it back, it goes away) on 64 bit Windows 7.

So, shame on the Microsoft for not making a 32 bit software run seamlessly under a 64 bit OS, and double shame on Sage for not knowing how to grep their source code for 'MAPI32', or not caring enough to try, in the past three years.   (during which we've paid them twelve thousand dollars for the use of their **** software.  Canadian dollars, but still...)

So, I happened to fix one problem while fixing another regarding Office 2013 MAPI errors and I wanted to share with everyone.

I'm just an IT guy in Texas and I've been scouring the web for some answers, and I happened to stumble upon this thread.  I've been having a few problems with Office 2013 (installed from the Office 365 Portal) namely with the dreaded MAPI problems you all have been/are experiencing with your 3rd party application.

And as people in my office have started to complain about it, there has been another issue with Skype for Business 2015 where it likes to randomly crash and restart.  So after researching for a long time with no real results, I finally created a MS Support case and potentially fixed the Skype for Business thing.  Which is awesome since it's been crashing 4-5 times a day on each computer I've installed Office 365 on.

How does this fit in with what you're talking about?  Well, it just so happens that after applying this fix, it solved the problem with some of my 3rd party applications calling Outlook 2013 using the MAPI profile and now attaches the files to an outbound message.  I'm not sure how or why, but this registry fix got me working 100% in many different areas of difficulty.

https://support.microsoft.com/en-us/kb/3118497

With all Office programs closed, open Regedit and browse to HKCU, Software, Microsoft, Exchange.  Add a D-Word String in "Exchange" named MsoAuthDisabled and give it a value of 1.

Open Outlook.  Try to use your software to attach a file to a new message in Outlook.  I've provided the link to the KB Article from Microsoft with more detailed instructions.

I hope from the bottom of my heart that this fix works for you.  I know the feeling of searching for a solution with finding little to no help, or the fixes you do find don't help at all.

Good luck!!

Rob Fassett - Texas

Thank you Rob,

We had never tried Skype, the problem we were having was that we could not email from our accounting application *at all* once we upgraded from Office 2007 to Office 2013.

Except for two of them, where the user had full local administrator rights.   Even though the installation was run as 'administrator' on all 10 of them, the secret, hidden light switch of 'MAPI=1' was never installed.

The problem with these online forums is that in this unstructured data there is no way to be specific enough about error messages, file versions, OS versions, etc.   So when searching for 'MAPI error' there's a needle-in-a-haystack problem.