x Want to participate? Join the group to interact
  • Replies 16 replies
  • Subscribers 62 subscribers
  • Views 16168 views
  • Users 0 members are here
Browse Forums
Announcements
78
topics
166
replies
General Discussion
5k
topics
16k
replies
Installation and Upgrades
978
topics
2k
replies
Inventory, Projects, and Departments
337
topics
1k
replies
Payables and Receivables
1k
topics
4k
replies
Payroll
1k
topics
3k
replies
Reconciliation and Banking
315
topics
992
replies
Reporting and Analytics
206
topics
397
replies
Soutien Technique - Français
626
topics
1k
replies
Year End Activities
223
topics
595
replies
RandyW

Cannot email from Sage 50 Canadian using Office 365? Poppycock!

Posted By

Hi All,

This April 17, 2015 Sage tech document is a kind of a mashup, so it's difficult to understand from it what can, and cannot be fixed.

https://support.na.sage.com/selfservice/viewContent.do?externalId=12227&sliceId=1

"

Resolution

Workaround:

  1. Install Office 2007, 2010 or 2013 (32-bit) full versions locally.
  2. Verify that you can now email in Sage 50.

Note: Sage 50 does not work with Click-to-run versions of Office. Sage 50 does not work with Office 365.

"

That last statement is badly worded, once the 'Online' is taken off the end it's also wrong - 'Office 365' comes in flavours, the only one(s) that won't work are the 'Online' versions, as stated under 'Cause'.

  • Business and enterprise-oriented plans for Office 365 offer access to cloud hosted versions of Office's server platforms on a software as a service basis.
  • At this time Sage currently does not support interoperability with a locally based installed copy of Sage and a web based version of office.

THAT part makes sense!  Of course my Sage 50 Canadian workstation software can't find MAPI32.DLL if it's off in the @#%$@# cloud!!!

Then there is a link at the bottom of the document to a Microsoft tech article that seems to indicate that it is the 'add-in' developer's responsibility to have their software assess the situation and take action accordingly:

https://msdn.microsoft.com/en-ca/library/office/ff864733.aspx

"Click-to-Run is the default mechanism to deliver Office, and only a subset of Office customers can request physical media to install Office. Add-in developers should determine whether Outlook has been installed, and whether Outlook has been delivered as a Click-to-Run product" 

It turns out that it is not relevant whether Office was installed using click-to-run, a DVD, preloaded, over a LAN, or from an ISO mounted off a memory stick.  If it's installed, MAPI is installed, and it can email from Sage 50 Canadian. 

  • Hey, don't know of any changes in terms of the Outlook compatibility but the specs for the 2016 product haven't been released yet so it is hard to say. Best bet to get this addressed is to go to Help-Contact Sage-Give Us Your Feedback, can do this in any company file. It goes to the dev team and it is really valuable to us in terms of moving the software forward. The more they hear about something the more likely it is to be addressed, or that feature added in.
  • in reply to Erik79

    Thank you for your comments, Erik

    Erik79 said:
    the specs for the 2016 product haven't been released yet

    It's a bug fix.  Yeah, Microsoft made a change that broke it, but they're not changing it back.

    Erik79 said:
    The more they hear about something the more likely it is to be addressed, or that feature added in.

    Sage has created several tech documents to explain when it doesn't work.  You seem to be suggesting that they just need to hear more complaints?  I suppose 'Should Emailing work? with Office 365' could be put to a vote on Ideascale. 

    The Ideascale site seems to be more wishing well than communication tool.   

    Is Sage pre-filtering these items?  Why not just "throw it at the wall and see what sticks?". 

    In the above case, if the 'real answer' is (for whatever reason), there will never be any new 'canned' reports, or fixes to old ones, it would be helpful if Sage would just... say... something. 

    Or there's really no conversation.

  • in reply to RandyW
    Hey, for the idea scale thing there should be no filtering, defeats its purpose for us as a tool for the dev team. If you are having issues with things you are posting there not working properly then please call in at 888-522-2722 or 888-222-8985
  • in reply to Erik79

    Erik79 said:
    Hey, for the idea scale thing there should be no filtering

    ???  The items that are posted are first vetted by someone at Sage, before anyone on this side of the firewall other than the poster can see them.   The process seems to take about a year. 

    Erik79 said:
    If you are having issues with things you are posting there not working properly then please call in

    I think you wildly overestimate the strength of my commitment to helping Sage, or any other vendor.  It's not even always above the 'I told you once' level.   It's rarely been up to the level of  'I'll spend an hour navigating a vendor's voicemail system to find the person responsible for maintaining their website.'

  • in reply to RandyW

    For problems Emailing from Windows 64 bit, and 32 bit office, this registry key may not have been created during installation of Office 2013 or Office 2016:

    Windows Registry Editor Version 5.00

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

    "MAPI"="1"

    ** warning, changing registry settings can affect your computer **

    ** More importantly, Driving in winter on 'all-season' radials can cause serious problems **


    We had trouble with 8 of 10 machines where Office 2007 was previously installed, and upgraded to Office 2013. 

    Office 2013 worked fine on 2 workstations where the user account used for the installation did not have local 'administrator' rights.  Something Goes Wrong with the legacy email settings, so Sage 50 never attempted to load the MAPI32.DLL from c:\windows\SysWOW64. 

    The resulting error message when trying to Email from the afflicted systems was 

    "Sage 50 cannot communicate with your e-mail program.  Please ensure that your e-mail program is MAPI-compatible and that it is the default MAPI client."

    Outlook 2013 is definitely MAPI-Compatible, and it was the default client.  Testing with one of Sage's competitor's software on the non-working system showed that other accounting software could send e-mail, but none of the versions of Sage 50 that once could send e-mail, would work.  

    I finally printed out the list of DLLs from Help | About | Support Info and compared the working / non-working sytems.  The non-working systems didn't have MAPI32.DLL loaded.  

    Now that I knew that the issue happened at startup, instead of when Emailing, another few runs with SysInternals' program PROCMON gave the final clue.  On 64 bit workstations, Windows only shows 32 bit applications the 'WOW6432Node' 32 bit registry keys, since they're running inside a 32 bit emulator, on 64 bit Windows.   It's the same sort of thing that we would run into back in the Windows 3.1 / windows 95 days, only instead of 16 bit / 32 bit, now it was 32 bit / 64 bit. 

    Once the missing registry key was exported from one of the 'working' units and imported to the 'non-working' ones, the issue was resolved.

    I hope the above helps anyone who has been getting that error message.   The only outside help (Sage 50, Microsoft, a local consultant) we ever were able to get seemed focused on fixing blame, not fixing computer software.  

    Randy

  • in reply to RandyW
    When contacting Sage about this email issue I was given a solution which I qualify of "crutch solution". I asked if a fix was being looked at by the IT's, I cannot get a straight answer from Sage. I tried to go back to Office 2013, I contacted Microsoft, I contacted Sage and finally I had to go to the caveman solution and print my statements and invoices to be able to send them to my customers. The only other way is to print to PDF and send from PDF. I spent hours on the phone and on installing and re-installing to no avail, finally I just went back to my original Office 2016. I am the owner of a small business and I just cannot afford to spend more money on getting a program that will work with modern software, I was recently invoiced for the 2016 version of Sage.
  • in reply to Normand
    The cause of this problem is that modern computers are 64 bit, but most applications are still 32 bit, and their installation / uninstallation programs don't always work properly on operating systems that didn't exist when they were built.

    The computer market used to be driven by accounting and business, now it isn't, so what you get is more or less an Xbox and access to an 'App Store', and while problems are fewer, the ones that do occur are blessed complicated and subtle.

    Fortunately, for this particular problem you can:

    1 - Start Sage 50 and check in Help | About to see whether MAPI32.DLL is in the list of loaded modules (click on 'name' to sort them by name).

    If that DLL is not on the list, it is because Sage 50 did not load it, and email cannot possibly work. If that's the case, close Sage 50 again.

    2 - Start the Registry Editor and add the key as in the screenshot in the previous post.

    3 - Try step 1 again.

    ************************************************************************************************************

    As to whose 'fault' this problem is, I would say it's mostly Microsoft, but could be any MAPI compliant email program that has ever been installed.

    A little bit of blame should splash onto the Sage programmers. If the email menus were disabled when the DLL didn't load, it would be pretty obvious that SOMETHING HAD GONE WRONG AT PROGRAM STARTUP, and I wouldn't have had to look as long to find the cause.

    For us, the wording of Sage's tech document was a major contributor to our consultant leading us down a ten thousand dollar rabbit hole to the wrong fix.
  • in reply to RandyW
    This did not work
    My operating system is Windows 10. My Office 365 is 32 bits, my Outlook 2016 is 32 bits. My Sage 50 still does not email as it used to. We tried every possible solutions suggested on Sage City. Nothing works, I still have the warning that my mail should be MAPI compatible, MAPI32.dll is on my computer
  • in reply to RandyW
    Tried it, does not work. The latest answer I had from Sage HELP is that I will have to wait for the next upgrade which could be as far as 6 months down the road. thanks anyway for the info. By the way Quick Books advertises their connectivity to Outlook.
    Could you enlighten me about the IT's at Sage, I cannot get an straight answer on a fix, are they working on it ?
  • in reply to Normand

    Normand said:
    The latest answer I had from Sage HELP is that I will have to wait for the next upgrade which could be as far as 6 months down the road.

    Normand said:
    I cannot get an straight answer on a fix, are they working on it ?

    They're building a 'connector', which will connect to Outlook on the Web, Hotmail on the Web, etc.  

    Normand said:
    By the way Quick Books advertises their connectivity to Outlook.

    On a 64 bit workstation with 32 bit email, if Outlook is installed, and the proper registry entry for the WOW6432 subsystem's NT Messaging subsystem exists, Sage 50 will load the MAPI32.DLL stub, and email will work. 

    No amount of messing with uninstall and reinstall is likely to add the missing registry key as described in this thread, and the web connector that's coming out in June or July is a totally separate, different thing for web-based email that has nothing to do with Outlook installed on the computer.

    Normand said:
    Could you enlighten me about the IT's at Sage, I cannot get an straight answer on a fix

    Could you please post the exact, full product name of the 'Office 365' that they sold you?   You haven't mentioned it on this forum, and if you did not tell Sage Support, they also would not be able to give you a meaningful answer.

  • Hi there,

    I have identified the problem, and found a solution.

    Here's the solution steps:

    1. Google/Bing search Bullzip PDF Printer. Download the free PDF Printer.

    2. Install PDF Printer with the GhostScript Writer option checked. Uncheck the other two options during the install.

    3. Finish the install and close the installer.

    4. Open Devices and Printers > Right click Sage 50 E-mail Writer > select PRINTER Properties

    5. Click the Advanced Tab > Driver Dropdown > Select "Bullzip PDF Printer"
    - Be sure "Print Directly to the Printer" is selected. Some of you may have changed that while trying to troubleshoot.

    6. Click OK. Test Emailing from Peachtree. You DO NOT need to reboot or restart Peachtree. It's fixed.

    SIDENOTE: IF the stuff on the advanced tab is greyed out, click the Sharing Tab and click "Share this printer" and enter in the administrator username and password. Then go back to step 5.


    Has nothing to do with Sage 50's compatibility with Outlook and everything to do with the "amyuni document converter 300" PDF printer driver being used for this version of the software. Would be GREAT if sage would release to people the newest release of the PDF driver so it has no problems with Outlook 2013/Outlook 2016.

    I have this exact solution implemented on 3 computers all running completely fine with emailing now. ZERO errors no matter how many you try to do in a row.
  • in reply to Paul - Celera Network Senior Network Engineer
    Sage 50 US (PeachTree) and Sage 50 CA (Simply Accounting) are different programs. May work for Peachtree does not mean it will work with Simply, it may I don't know
  • in reply to Paul - Celera Network Senior Network Engineer
    Paul,

    Thanks for the info, but I am not sure it has the same relevance with the Canadian version of Sage 50, though for those with the same problem, they might wish to test this. You might want to post this solution in the US forums so others there can benefit.
  • in reply to Paul - Celera Network Senior Network Engineer

    Paul - Celera Network Senior Network Engineer said:
    ZERO errors no matter how many you try to do in a row.

    The problem that a lot of Sage 50 Canadian users are experiencing is due to a missing registry key for 32 bit NT messaging.   If it's missing, MAPI32.DLL will not load in Sage 50 Canadian, but no error message will appear until the user clicks 'send'.

    Paul - Celera Network Senior Network Engineer said:
    Has nothing to do with Sage 50's compatibility with Outlook and everything to do with the "amyuni document converter 300" PDF printer driver being used for this version of the software

    Sage 50 Canadian does not use that PDF driver.  It has its own.

    In saying that the Canadian and U.S. software packages are different, I don't mean slightly.  I believe they use different codebases, different back end databases, possibly different compilers, with perhaps a little shared interface code - they're more different than WordPerfect and Microsoft Word.  

  • in reply to Paul - Celera Network Senior Network Engineer

    HUGE thanks for this solution! Working great for me so far.
    Windows 7 Pro x64, Office 2016, Sage 50 Premium Accounting 2016 23.2.00.0184

  • in reply to cavsim
    Perhaps the moderator can move the Sage 50 U.S. software related posts to the U.S. software related forum.

    Paul's post appears to be as helpful to the U.S. software users, as it is irrelevant to Canadian software users.

    Between the different country editions of completely different 'Sage 50', and the different flavours of desktop and online 'Office 365', it's no wonder there's confusion.

*Community Hub is the new name for Sage City