Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
NOTE: If you see side effects of this workaround such as the filename of the document that you are sending containing the path of the file from the user's TEMP folder (C:\\User\Username…\BlankInvoiceForm.docx), then please remove the MAPIX=1 setting, and properly fix the issue in Outlook itself to prevent that warning by contacting Microsoft Office support.
Are you seeing this message every time you are sending a Template document via E-mail?
Luckily there is a very easy workaround. What is happening is when the user clicks send GP is looking to the Win.ini tile for certain MAPI settings. If they are not there then the user is prompted with this message. You could disable through Programmatic Access on the Trust Center window, but there is an easier fix.
1. Open a Windows Explorer window and go to C:\Windows. 2. Make a backup of the Win.ini
3. Open the WIN.ini file found in this folder.4. Look for the MAPIX setting in the file under the [Mail] section of the file. a. If the MAPIX setting reads MAPIX=0, please change the 0 to a 1 and then save the file. b. If there is not a MAPIX setting under the Mail section, please add the following under the Mail section of the file: i. MAPIX=15. Once you have modified the WIN.ini file, please be sure to save the changes and then close the file.6. Then you can restart both Microsoft Outlook and Dynamics GP to ensure that the changes to the file are picked up.
If you run into trouble with editing the Win.ini you can save this to your desktop and drag and drop it into the C:\Windows folder.
If this still does not work you will need validate your Registry. The document below will walk you through on how to check your Registry for Mail. Go through Steps 1-7 and choose Option A if you are 32-bit or Option B if you are 64-bit.
Regsitry MAPI Fix.docx
*Note: Recently (as of 1/11/18) we found some situations where the Customer did have MAPIX=1 in the Win.ini file and it still did not work. We removed this line in the Win.ini and it started working. Not sure if there was a certain Windows update that is preventing this setting from being used.
The steps above should resolve this error as a workaround. This is an Outlook message, and is occurring based on how your environment is set up and whether Outlook trusts the Microsoft Dynamics GP application to email on your behalf or not automatically.
Sr Support Engineer
I have to say this did the trick! In our terminal server sessions we are on 2013, and for some reason never had this issue.
However, with our users who have Outlook 2016 it seems to be more of an issue.
I first tried changing the settings in the Trust Center in outlook, and no avail.
When I added the MAPIX=1 line, it worked.
Fingers crossed it stays working!
Thanks for the post!
This worked like a charm for me on GP 2015 with Outlook 2013. Didn't need to go in the registry. Just had to make the change to the win.ini file. Thank you!!
Business Applications communities