Terminal Server: Dynamics.exe encountered a problem and needed to close
Just recently I assisted a partner with an issue they were having on a Terminal Server environment, after upgrading from Microsoft Dynamics GP 9.0 to Microsoft Dynamics GP 2010.
Upon launching Microsoft Dynamics GP, an end-user was receiving the error shown below:
Clicking on the hyperlink for the error detail showed the following:
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:
The Event Viewer information was in effect confirming that the faulting application was indeed the Runtime Engine, Dynamics.exe. However, interestingly enough, it was showing that the faulting module was the msvcr90.dll.
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/
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/
Comments
Glad I could help!
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.