Mirth Connect 4.3.0 Released!

Mirth Connect 4.3.0 is now available as an appliance update and on our GitHub page.

This is a major release containing new features like adding new functionality to the Mirth Connect Setup Wizard, adding the ability for resource and channel-specific classloaders to load child-first or parent-first, and added a default implementation of the getObjectsForSwaggerExamples() method in the ServicePlugin class. This release also contains enhancements for the Mirth Connect Administrator Launcher, the Mirth Connect Docker images, and several bug fixes and security improvements.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

NTVDM error during installation

  • Filter
  • Time
  • Show
Clear All
new posts

  • NTVDM error during installation

    I'm working with a client to install Mirth 1.7. In going through the install process he is getting a "NTVDM encountered a hard error" error.
    Has anyone seen this and how did you get around it? I have sent him some links on the problem from the Microsoft MSDN site, but of course I've never had an install problem,so haven't seen this before.

    Post edited by: dugjohnson, at: 02/05/2008 10:48

  • #2
    Re:NTVDM error during installation

    I just heard back from the client. I had told him to just download it again in case there was a problem with the download. That worked.
    However, I am not convinced from my research that that is what fixed it. According to what I saw, the fact that he started out by installing it from a Terminal Services session caused the problem. And when he first switched out of that, ntvdm.exe was still in a bad way from the first install attempt.
    Downloading a new installation gave the ntvdm.exe time to clear itself, and installing properly made it all work.
    That's my theory, not fact. If it helps someone who gets this error in the future, should it happen, great. If not, sorry.


    • #3
      Re:NTVDM error during installation

      Thanks for your research and follow-up Doug - we appreciate it here!
      Chris Lang