Upon launching Microsoft Dynamics GP, an end-user was receiving the error shown below:
![]() |
Dynamics.exe Error |
Clicking on the hyperlink for the error detail showed the following:
![]() |
Error Signature |
I have faced a number of issues of this type in the past and typically they are all narrowed down to corrupt forms and/or reports dictionaries - both Dynamics and third-parties. However, this seemed different, since other Terminal Server users were not experiencing the same issue.
The Event Viewer, however, showed a bit more details about the issue:
![]() |
Event Viewer |
In doing some search, I confirmed that the component in question was a part of the Microsoft Visual C++ 2008 SP1 Redistributable Package (x86).
The Microsoft Visual C++ 2008 SP1 Redistributable Package (x86) installs runtime components of Visual C++ Libraries required to run applications developed with Visual C++ SP1 on a computer that does not have Visual C++ 2008 SP1 installed.
This package installs runtime components of C Runtime (CRT), Standard C++, ATL, MFC, OpenMP and MSDIA libraries. For libraries that support side-by-side deployment model (CRT, SCL, ATL, MFC, OpenMP) they are installed into the native assembly cache, also called WinSxS folder, on versions of Windows operating system that support side-by-side assemblies.
The Microsoft Dynamics GP Runtime Engine (Dynamics.exe), was originally developed in C++ and has since evolved to include interoperability with the .NET Framework, needed to develop some of the most advanced aspects of the application.
I had the partner download and reinstall the Microsoft Visual C++ 2008 SP1 Redistributable Package (x86), found at the Microsoft Download Center.
http://www.microsoft.com/download/en/details.aspx?id=5582
After a couple hours, the partner confirmed that the issue was solved... another one bites the dust!
Until next post!
MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/
3 comments:
You are god, this has been annoying me for months on all of our citrix boxes.
Arthur,
Glad I could help!
here is a crazy one... we were getting the same error when printing some reports. It turned out to be a data issue where the screen generator and also the print job caused a dynamics.exe crash referring to this MSVCR90.dll.
We found the ` character ( not the ', but the ` which is under the tilda typically). Once we removed the character from the docnumbr...error gone. Fun 2 days.
Post a Comment