I recently had a partner contact me when they were doing an upgrade and Microsoft Dynamics GP was crashing upon launching the application. As Winthrop products were installed, we were looking initially to see if the problem was caused by GP Power Tools or Visual Studio Integration Toolkit.
Short Answer: Removing the Winthrop products did not fix the problem …
Long Answer: The Windows Event Log entry related to the crashing Dynamics.exe showed the following information:
Exception Info: System.AccessViolationException
at <Module>.TNTsend_message(HWND__*, EV7ENT*)
at <Module>.dtw_powerup(HINSTANCE__*, Byte*)
Because of the mention of WinMainCRTStartup, I did think that could be related to the use of Bitmap Scaling which is automatically enabled with GP Power Tools build 29 or later, but removing the Dynamics.exe.manifest file to disable the Bitmap Scaling did not stop the crashing.
Eventually, the partner came back to me and confirmed the cause of the problem …
It was being caused by the custom reports dictionary (REPORTS.DIC) becoming corrupted during the upgrade process.
Moral of the Story: If you ever get unexplained crashing of Microsoft Dynamics GP on launch, start by renaming any custom forms and reports dictionary to test the application without the custom dictionaries.
Hope this information helps save you some time.
This article was originally posted on http://www.winthropdc.com/blog.
2 thoughts on “#MSDynGP Microsoft Dynamics GP Crashing on Launch”
David, we had a similar thing happen we found it after installing GP Power tools we has one third party that was not updated. once we updated it all went well. Note we also had a problem with the print server it needed clean up as they had never removed old printers that were no-longer on there network
I am assuming that GP Power Tools’ Product Version Validation highlighted the product dictionary version mismatch for you. That’s exactly what it was designed to do. Glad it helped resolve your issue.