Microsoft Dynamics GP crashes/closes when emailing after Office Update
July 2022 UPDATE: We have just published the following article with a possible workaround for compatibility issues between Microsoft Dynamics GP's implementation of VBA and Microsoft Office and Windows Server 2019:
VBA causing issues in Dynamics GP? Here's a possible solution.
March 11, 2019 update:
After communicating with the Office team it sounds like the redistributable version of VBA that is packaged with Microsoft Dynamics GP has reached end-of-life, which means it is no longer tested for compatibility with the monthly Office 365 releases. Such a compatibility issue was found in build 1811 and later versions of Office 365. It does not appear that there is a newer VBA redistributable that we could package with the Microsoft Dynamics GP installer that would address this issue. Since there are likely ISV products and customizations that require VBA and we want to maintain their functionality we’ve decided that the current VBA build will still be packaged with future installation media.
After weighing our options to move forward we’ve identified three workarounds to consider that you can read about in Lucas' blog post, Microsoft Dynamics GP and VBA: Future Considerations.
Microsoft Dynamics GP and VBA: Future Considerations
--------------------------
Dec 14, 2018 update:
After further testing, we have narrowed the issue to Any Custom VBA code installed on Dynamics GP. If you remove all VBA code, this will remove the issue with GP Crashing when emailing. See below for how to check if you have VBA code installed. We cannot guarantee that removing the VBA won't have any side effects. You will have to know what your VBA contains.
----------------------------
We have seen a few cases around the topic of Dynamics GP crashing or closing when accessing any email/outlook functionality for any Microsoft Office version newer than 1810.
Affected GP Versions: 2013, 2013R2, 2015, 2015R2, 2016, 2016R2, 2018, 2018R2, 18.2, 18.3, 18.4+
Common Errors:
- Closing with no error
- Not Responding with no error
- APPCRASH ilmapi32.dll
- APPCRASH olmapi32.dll
- APPCRASH MSO.dll
You have 3 options to resolve. You should only have to apply 1 of these options, not all of them.
- Backup & Remove all VBA code you have in Dynamics GP.
- Revert/Rollback Microsoft Office to the 1810 build
- Rename Dynamics GP Code folder and run a Repair (this will remove 3rd Parties)
How to check if you have VBA code?
(We cannot guarantee that removing the VBA won't have any side effects. You will have to know what your VBA contains.)
- Open the GP20XX folder
- Sort by TYPE
- Look to see if you have any files that are VBA File TYPE
- If you have such files, back them up and remove them or move them to another folder.
- Now reopen Dynamics GP and Test Email functionality.
To check what version of Microsoft Office that you have:
- Open an Office application (outlook, word, etc)
- You should see About Outlook if you go to File -> Office Account
-
- Office 365 - Version 1811 (Build 11029.20079) or newer - Standard
- Office 365 - Version 1811 (Build 11029.20045) or newer - Insider Edition
- Office 2019 - Version 1811 (Build 11029.20079) or newer
How to Rollback Microsoft Office?
- Disable office updates **
File-> Office Account-> Update Options-> Disable Updates
- Open an elevated command prompt:
- Start-> type: cmd
- Right click on: Command Prompt
- Choose: Run as administrator
- Provide your administrator credentials or confirm the User Account Control dialog when prompted.
- Type: cd %programfiles%\Common Files\Microsoft Shared\ClickToRun\
- You can specify the built number to return to in the following way:
O365 Standard use: OfficeC2RClient.exe /update user updatetoversion=16.0.11001.20074
O365 Insiders use: OfficeC2RClient.exe /update user updatetoversion=16.0.11001.20038
Office 2019: OfficeC2RClient.exe /update user updatetoversion=16.0.11001.20108 - Replace <build number> with the build number that you want to return to.
- Here are the links to find update builds for Office 2016, Office 2019, Office 365
- After pressing ENTER, a “Checking for updates” dialog will open shortly followed by a “Downloading Office updates” dialog. Once this dialog closes, the rollback has been completed.
- Open Outlook and go back to: File-> Office Account
- In the Office Updates section, it should now list the version that you specified.
Rename Dynamics GP Code folder and run a Repair (this will remove 3rd Parties)
- Rename the GP20XX folder to bakGP20XX.
- The run a repair on Dynamics GP (this creates a clean install of Dynamics GP)
- Run Dynamics Utilities.
- Run Dynamics GP.
- Reinstall 3rd Party apps one at a time, testing GP after each to see if GP still works with Email.
** We do not know if the next release of Office will fix this issue.
** Based on current cadence of releases, we estimate the next release of Office will be in January.
** At that time, I would recommend testing on one machine to see if resolves the issue.
Comments
-
Has anyone heard if the January Office release is available and can confirm GP no longer as an as the issue after the Office update?
-
Thank you sir! Rolling back Office365 standard use to 16.0.11001.20074 fixed this issue for us, just waiting on the Office fix now...
-
Thank you, we found rolling back the patch worked and were hoping a fix was on the way. For GP 2010 users - We use GP 2010 and some users have office 2016. I know GP 2010 and office 2016 is not supported, but we have a lot of custom and cannot update GP yet. The "rename GP code folder" option fixes the problem until I add our VBA files back or create new VBA files. Rolling back the patch does work.
*This post is locked for comments