I’m encountering a frustrating issue after a required downgrade of Mirth Connect for a software integration project. We moved from version 4.4.1 back to 3.6.1.
The problem is specifically related to the Mirth Connect Service startup behavior on our Windows server:
When configured to run as the local SYSTEM account:
The service starts briefly but immediately terminates.
We have checked the Mirth logs and the Windows Event Viewer, but they are not providing a clear reason for the failure.
When configured to run as a local administrator account:
The service starts successfully, remains active, and Mirth Connect functions perfectly.
The client strictly requires the service to run under the SYSTEM account due to specific security and operational policies. The administrator account solution is not acceptable long-term.
Any suggestions on where to check for missing permissions or what logs might provide deeper insight would be greatly appreciated!
