We need to be able to export invoices using MAPI, rather than copying the invoice to a shared drive and then using email on personal workstation to access shared drive and attach that invoice. We used MAPI frequently before upgrading from Sage 2014 to Sage 2019. With Sage 2014 we had desktop client installed one each user's workstation. With Sage 2019 we've switched to having the Sage desktop hosted on a Citrix server.
MAPI export now fails with error "There is no email program associated to perform the requested action.".
The SMTP is set up correctly on the Citrix server. This was verified by Sage Support.
Sage support reports: "...this is an issue where it’s a problem with Crystal and not Sage 500. The MAPI option was never part of Sage’s design. Crystal is the one that basically uses the MAPI option. Unfortunately the Crystal reports we have and is used has never been redesigned for quite a number of years. Thus we never needed to use any other versions of Crystal for Sage 500.
Based on our research it seems that the MAPI issue that you’re experiencing is more than likely due to the incompatibility of the Crystal version with Office. Thus it would stem outside of our support scope."
Sage support further says this is an enhancement request rather than a bug.
by: Craig R. | over a year ago | 6 - General Enhancements
Comments
From what I recall, the configuration of SMTP in Set Up CI Options is used for functions like Alerts, which originate at the server and MAPI is client-based. I think if SMTP is configured then the client application will default to that, so maybe try changing CI Options from SMTP to none and test, or try mailing from one of the newer pieces of code like in SO. Either way, it would be odd that an incompatibility would be introduced in Crystal by MS Office. There are other document management methods to send documents as well.
Another option is to install Crystal on a test host along with Sage 500 client. Try a separate host first because there is also an acknowledged problem with loading a more current version of Crystal (run-time or otherwise) on the same host as Sage 500. KB on that should be: 94251, 89183, 94339. There is an associated fix that adds a config file for affected older reports.
The invoice print engine is one of the oldest in the code base but the mail function should be part of the common code. There are a couple of other ways to test it if you have Customizer by calling a method of the CEMail class (from what I recall) directly. Also, the Crystal object Support was referring to might be either CRPE32.dll or U2LSOTA.dll. I don't know which of the older report engine builds are still in the code base.