Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
We've seen a few cases and even some forums questions regarding the "Either there is no default mail client or the current mail client cannot fulfill the message request. Please run Microsoft Outlook and set it as the default mail client." or "Connection to the MAPI server not available. Unable to send e-mail or select addresses." when users attempt to use the e-mail functionality within Microsoft Dynamics GP 2013.
The resolution to these errors as we've frequently seen is done in two parts:
A. On the machine(s) that Microsoft Dynamics GP 2013 and Outlook is installed onto, under Control Panel, and under User Accounts and then when you click on Mail, there should be a mail profile needs to be setup and selected to be used as the default.
B. As mentioned in the System Requirements for Microsoft Dynamics GP 2013 page:
1. If you're using a 64-bit version of Office/Outlook, in Microsoft Dynamics GP 2013, in the System Preferences window (Microsoft Dynamics GP > Setup > System Preferences), the Server Type needs to be set to 'Exchange'.
2. If you're using a 32-bit version of Office/Outlook, in Microsoft Dynamics GP 2013, in the System Preferences window, the Server Type can be set to either MAPI or Exchange.
If the Server Type is set to 'Exchange', users may see a Exchange login window appear when they click on the Send To and then Mail Recipient(Text) buttons when emailing a report or document from within the Dynamics GP 2013 application. Once they enter their credentials, an Compose email window will appear:
--If the Server Type is set to 'MAPI', an Outlook email window will appear as if a new email window was opened within Outlook itself.
-- Microsoft Dynamics GP 2013 is supported on both Office 2010 and Office 2013, 32 bit and 64 bit.
--The 'Exchange' server type only supports XPS and DOCX, PDF is not supported.
If after making the above changes, the email functionality still doesn't work in Microsoft Dynamics GP 2013 or you're still getting the same errors, you can also try the following that we've seen resolve email issues in the application:
1) First, log into the workstation where you're seeing these email functionality issues in Dynamics GP 2013, as an Administrator account.
2) Go to Start > Run, type REGEDIT and click OK to open the Registry Editor
3) You will want to backup the HKEY_LOCAL_MACHINE keys by right-clicking on that node, selecting Export and saving the keys to a location you can restore from later if necessary
4) Once that is done you'll want to expand HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\win.ini
5) If you look in the right-hand pane when win.ini is highlighted you'll likely not see a MAIL string key. Right-click on win.ini and select New > String Value. Name this new value: MAIL
6) Double-click on the MAIL key and set its value to the following:
7) You then need to create the key(s) that the MAIL key refers to. If this is a 32-bit machine you'd need to use option A below. If this is 64-bit use option B:
a) Expand HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
b) Right-click on CurrentVersion and select New > Key
c) Name this new key: MAIL
d) Right-click on the new MAIL key and select New > String Value.
e) Name this new string value: MAPIX
f) Double-click on MAPIX and set the value to 1.
a) Expand HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion
c) Name this new key: MAIL
8) You must restart the machine after making any Windows Registry changes, for the changes to then take effect.
While there could be other issues causing email functionality not to work in Microsoft Dynamics GP 2013, the above would be the first items we would begin looking at to rule those out.
Hopefully this information will help everyone that runs into these type of errors or email issues as I know I've seen them a few times on my own systems. Thank you.
The registry entry did the trick (option B). I was facing this issue on my 64-bit environment and could not figure out for the life in me what would be the cause. I will broadcast this on my FB blog page.
Mariano Gomez, MVP
This is very helpful. However, I would like to know how does it work if the client is connecting to a Terminal Server. They have Outlook 2007 installed and configured on their local computer but GP 2013 is installed on the TS. What configurations do I have to have on TS and local computer. They will use MAPI not exchange. I appreciate your answer.
I have the same question as Andreaies.....We cannot get Gp to recognize the user.
GP and OUtlook 64-bit are installed on a terminal server. We have Exchange selected...but when the user tries to even open the Purchasing Series window it always asks for username and password. When the users enter their username and password it tells them it is incorrect.
Auto-Discover is on in Exchange.
What else can we test?
What we've mostly seen in cases as you mentioned is that when the customer has their email setup as 'Exchange' in Dynamics GP, due to how Exchange is setup, they need to click the advanced option which then shows a third field, Login ID, on the Exchange Log On window. Once they entered that information: Email Address, Password, Login ID, then they were able to get the functionality working within Dynamics GP, such as opening windows or emailing.
Hopefully this will help.....