Finance | Project Operations, Human Resources, ...

GP (2019) VBA Compatibility Issue on Windows server 2019

(1) Share

Report

Posted on by Deepak T

We have almost completed a test upgrade from GP 2018 to GP 2019(18.2.1100). GP is running normally until any VBA code is run. GP is installed on Windows Server 2019 with SQL 2019. We have quite a few customization in GP2018 using VBA. The project files imported without errors and all VBA code looks normal in the Editor. But GP crashes anytime VBA code is run.

Need help with figuring out solution to work VBA package in GP 2019(18.2.1100) on Windows Server 2019.

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (13)

Answers (0)

Suggested answer

Justin Sutton on at

Like (2)

Report

Hello Deepak,

Dynamics GP does not support VBA on Server 2019.

More information on this can be found here:

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

There are a few different tools to move away from VBA, some of which is held on that page. We also know the community has even more options, so you may be even more feedback on this thread.

Was this reply helpful? Yes No
David Musgrave MVP ... 14,093 Most Valuable Professional on at

Like (3)

Report

I would suggest replacing your VBA code with GP Power Tools - Developer Tools module.

See why here: winthropdc.wordpress.com/.../

Regards

David

Was this reply helpful? Yes No
Almas Mahfooz 11,009 User Group Leader on at

Like (0)

Report

Deepak , you already have good responses just want to add that you can also hire freelancers to convert your vba code to dexterity. :-)

Was this reply helpful? Yes No
mnola 72 on at

Like (1)

Report

Hi Justin,

Have a client that is in the same boat in that they are in process of upgrading all their Servers to Windows 2019 and eventually upgrading GP as well. They have an extensive amount of VBA (that needs to be converted) and ran into the same GP Crashing issue anytime VBA code was touched on.

However, one of the client's techs found that replacing the VBE6.dll with a later version got them past the crashing issue. Albeit, this is a temporary workaround, as there is no guarantee that there won't be a Security Update that breaks things again (like the Office Suite security update that broke DOCX files that you so kindly posted about in another link). Not sure where they found the newer VBE6.DLL file, but the version information that was able to find is below:

Crashing version ==> 6.5.10.32

Working version ==> 6.5.10.53

Location C:\Program Files (x86)\Common Files\microsoft shared\VBA\VBA6

When searching the internet and other sites such as this, haven't found any mention of the temporary workaround mentioned above. Wondering what it is with Windows 2019 that stops GP/VBA combo from working? As noted, this temporary workaround resolves the GP crashing issue, but does not fix the GP/VBA/Outlook (Email) crashing issue, which requires an earlier version of Office, no VBA or switching from MAPI to Exchange.

So, wondering what your thoughts are on this?

Regards,

Michael.

Was this reply helpful? Yes No
Terry R Heley Microsoft Employee on at

Like (0)

Report

Michael, can you provide the link from the customer for the 6.5.10.53 so it can be reviewed as a future consideration of what they did to get this working, thanks

Terry

Microsoft

Was this reply helpful? Yes No
Suggested answer

mnola 72 on at

Like (1)

Report

Hi Terry,

As noted in my post "Not sure where they found the newer VBE6.DLL file". However, a Google Search points to 6.5.10.53 as being a security fix, which the client must have applied on one of their older Servers.

The following link (www.microsoft.com/.../details.aspx looks like it might do the job.

Regardless of this, do you know the underlying cause to why VBA stops working on Windows 2019?

Expect the above will only be a temporary workaround and that there is no guarantee that a new Windows 2019 security update won't break things again. And, yes, we need to get the client off of VBA sooner than later, but that is going to take quite a bit of time/resources due to the volume of modifications made using VBA through the years in their environment.

Was this reply helpful? Yes No
EnriqueGarcia 113 on at

Like (0)

Report

Glad to learn about this option as it buys us some time to communicate to the customer and get approval to re-develop these customizations.

Was this reply helpful? Yes No
mnola 72 on at

Like (1)

Report

Hi Enrique,

Noting that the link on the page that I posted isn't working. What you want to look for is "www.microsoft.com/.../details.aspx. In case this link doesn't work either, then look for "Visual Basic for Applications Runtime Security Update", Knowledge Base Article KB974945.

I personally haven't tried downloading/installing the update, as my client that I was working with already had the DLL available, but can clearly see "Vbe6.dll 6.5.10.53" listed at the bottom of the KB article's Additional Information page.

We are definitely pushing to get all our clients off of VBA, but even with a workaround, you never know what might break it next! Just went through the process of changing DOCX to PDF to get around the new MS Security Update that breaks DOCX documents generated from GP Templates and switching from MAPI to Exchange to get around the Outlook/GP/VBA crashing issue.

Was this reply helpful? Yes No
EnriqueGarcia 113 on at

Like (0)

Report

Thanks, Deepak.

I did notice the link placed a quote " after the address and had figured that out. However do thank you for the heads up.

Was this reply helpful? Yes No
mnola 72 on at

Like (1)

Report

Hi Enrique,

Actually it is Michael, not Deepak (guess I should remember to sign my posts. Believe Deepak originated this BLOG chain. Had added my question to Justin, who also placed a response to this chain, wondering about what the true underlying cause is with the Windows 2019 O/S and GP/VBA.

Take care,

Michael J. Nola.

Was this reply helpful? Yes No