Finance | Project Operations, Human Resources, ...

SEND TO MAIL RECIPIENT (PDF) in Great Plains Crashes

(0) Share

Report

Posted on by Brian Wolters

340

I have a user, our office Manager/VP, who just got a new PC yesterday. It is fully updated and we use Great Plains 2018.

Her preferred method of sending a report from Great Plains is to use the SEND TO MAIL RECIPIENT (PDF).

When she goes to do that, it crashes Great Plains completely and kicks her out.

I tried the same on my PC and same...crashes.

Faulting application name: Dynamics.exe, version: 18.0.21.0, time stamp: 0x5d8138e8
Faulting module name: MSO.DLL, version: 11.0.8117.0, time stamp: 0x45602fcc
Exception code: 0xc0000005
Fault offset: 0x0032fc57
Faulting process id: 0x4ac
Faulting application start time: 0x01d5d83d731d18f4
Faulting application path: C:\Program Files (x86)\Microsoft Dynamics\GP\Dynamics.exe
Faulting module path: C:\PROGRA~2\COMMON~1\MICROS~1\OFFICE11\MSO.DLL
Report Id: b04a1f2c-4809-4f74-8bec-eb2e7ba732c3
Faulting package full name: 
Faulting package-relative application ID:

I tried 3 other GP users and it works fine. And we have multiple versions of Adobe Acrobat floating around and that doesn't seem to be a problem. And it isn't an adobe problem as (TEXT) also crashes it. So it seems to be an issue between GP and Outlook.

I offered to present a workaround and she refused to learn it.

The one common thing I've found is her PC (and mine) is on Windows 10 Update 1909 whereas the 3 users I tested where it worked is 1903. Could that be the cause? And if so, is there a fix that won't require removing 1909 as it will eventually need to be applied.

Thanks...

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (8)

Answers (0)

Suggested answer

Hokuminaria 2,950 on at

Like (0)

Report

Hello Brian,

Thank you for posting your question on the GP Forums. My name is Brandon and i am an engineer on the Microsoft GP Team.

There are a few things that can cause this that we have seen. i will provide these below. However, without having a Fiddler Trace and Script log, it will be hard to tell where it is failing and causing GP to crash.

The first thing i would look at is if the machines having an issue have any VBA Modifications installed and have Microsoft Office version later than 1810.

The solution to this is to remove VBA or revert your version of office prior to 1810. Alternatively, you can switch to using Exchange instead of MAPI in the GP Email Setup. You can read about this more in the links below.

community.dynamics.com/.../dynamics-gp-crashes-closes-when-emailing-after-office-update

community.dynamics.com/.../dynamics-gp-and-vba-future-considerations

The other issue we have seen with Adobe. They had pushed an update out and need to change a few security settings. This is covered in the article below.

https://helpx.adobe.com/acrobat/kb/security-warning-postscript-pdf.html

If neither of these options help resolve your issue, i would recommend you create a support case so we can take a further look and capture logs to see where we are crashing at.

I hope this helps!

Thank you!

Was this reply helpful? Yes No
Brian Wolters 340 on at

Like (0)

Report

This was helpful. We do have one, single VBA module for a payroll screen. We need that but I also don't want to digress back to an older Office. So, at this time, I need to see what we can do to make this module/screen work in a different language.

Was this reply helpful? Yes No
Hokuminaria 2,950 on at

Like (0)

Report

Hello Brian,

Thank you for your response!

Hopefully one of the options below will be valid for your environment.

Microsoft Dynamics GP, VBA and Windows Server 2019

If you've launched Microsoft Dynamics GP on a Windows Server 2019 machine any implementation of VBA will cause the GP application to close. This does not seem to be isolated to e-mailing, but rather any time a VBA customization is present on a window or report. This is not an issue on earlier versions of Windows Server or any client OS. If you need to use VBA in Dynamics GP you will need to have it installed on one of those previous operating systems.

After weighing our options to move forward we’ve identified the three following workarounds for you to consider:

1) First, since the Web Client was initially introduced in Microsoft Dynamics GP 2013 we’ve heard of a push from many partners and ISVs to port their VBA customizations to another solution since VBA is not compatible with the Web Client. Similarly, if you were to migrate your VBA customizations to Dexterity or Visual Studio Tools there are no known compatibility issues with those solutions. You can use either C#.NET or VB.NET with VSTools, so you may already have someone in your organization with that knowledge. Several members of the community, including partners and MVPs, have published articles on this process. I’ve linked to an example of such an article below:

Migrating VBA Customizations to VS Tools for Dynamics GP

2) The second option would be to maintain two different Dynamics GP client’s (installs/code folder): one with VBA customizations loaded and a second without any VBA. In this scenario when you need to perform an e-mail operation you will need to do so while logged into the VBA-free client. This would introduce some additional administration for the extra clients and depending on the nature of the VBA customizations it may not be possible to split the processes efficiently.

3) Finally, the issue only occurs when you have VBA customization enabled and you’re using the MAPI Server Type. This is because when you send an e-mail using MAPI the Outlook application itself is used to compose and send the e-mail message. If you switch to the Exchange server type (as found in the System Preferences window under Microsoft Dynamics GP > Tools > Setup > System > System Preferences) you should still be able to use VBA along with e-mail. The main limitation that could apply to this option is that you will need to be using Exchange for e-mail server rather than another solution.

Microsoft Support Engineer | Brandon Jarrett

Was this reply helpful? Yes No
Brian Wolters 340 on at

Like (0)

Report

Thank you...I think we will go with option 1. Being the solo and Jack of all IT Trades IT Director, I find little time to not only dabble in development, but also learn it. The workaround right now is easy but the VP doesn't want to use it and wants this fixed ASAP. So going to seek out a reasonable development contractor.

Was this reply helpful? Yes No
Brian Wolters 340 on at

Like (0)

Report

Good Morning...

I have an update on this.

We did hire a developer to convert the old VBA to a newer customization and had them go ahead and convert all 5 even if we may only use 1 or 2 of them.

After removing VBA and adding in these customizations, sadly, it didn't fix the problem. Choosing SEND TO MAIL RECIPIENT (PDF) still causes GP to completely crash.

So, I tried some other approaches. It had nothing to do with PDF printers as SEND TO MAIL RECIPIENT (TEXT) caused the same problem.

I made a copy of my GP folder and copied over a folder from a Purchasing Agent. SEND TO MAIL RECIPIENT (PDF) works on that copy. It also works on several other installs of GP except for this VP (and mine when I worked off her copy of it on my PC.)

So, if I am correct in this assessment, it has nothing to do with VBA or the latest Office 365 copy of the Office (Outlook in this case).

The VP in which SEND TO MAIL RECIPIENT (PDF) is crashing does have a customized REPORTS.DIC and the aforementioned VBA (which now has been converted.) I had thought about using the copy of the Purchasing Agent on the VP's Machine and copy over the REPORTS.DIC. Is there anything else that might be customized that could lead to these crashes?

Or any other insights? We are close to getting this fixed.

Was this reply helpful? Yes No
Hokuminaria 2,950 on at

Like (1)

Report

Hello Brian,

I suspect you are using Adobe. Adobe had a change and could be the cause of the issue. Please take a look at the Adobe link below.

helpx.adobe.com/.../security-warning-postscript-pdf.html

This has to be done for both Adobe Acrobat and Adobe Acrobat Distiller.

Hope this help!

Microsoft Support Engineer | Brandon Jarrett

Was this reply helpful? Yes No
Brian Wolters 340 on at

Like (0)

Report

We are but it doesn't seem to be the cause of the problem. I've performed the above and it still crashes.

Was this reply helpful? Yes No
leeg 20 on at

Like (0)

Report

No solution yet I'm afraid but I'm also in the same boat
I'm thinking the presence of any VBA may be the cause here even if it is not referenced

We have 3 regional GP application folders
1 has a teensy bit of VBA (will have to try and switch over to VS tools method as outlined previously)
the other 2 do not

The one with the VBA just terminates the GP client as soon as you try to email text or PDF
the other two work correctly

I'll update as I discover more.

Switching over to Exchange O365 (EWS) is essentially a non starter if you also use MFA (even with basic auth enabled in active directory)
as basic auth for EWS is going away from 13 October 2020
https://techcommunity.microsoft.com/t5/exchange-team-blog/upcoming-changes-to-exchange-web-services-ews-api-for-office-365/ba-p/608055

Which is why I'm now looking back at MAPI

Was this reply helpful? Yes No

Join the conversation

Community site session details

SEND TO MAIL RECIPIENT (PDF) in Great Plains Crashes

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

SEND TO MAIL RECIPIENT (PDF) in Great Plains Crashes

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates