Error "The Mirth Connect Service could not be started."

rbeckman-nextgen commented 4 years ago

What is the issue: Getting Error in Window Notification Area for MC server manager even though MC services started Is the Issue Consistent (list details):

stop services would show successful notification
start or restart services would show Error notification

Steps to Reproduce:

From Window Control Panel\All Control Panel Items\Notification Area Icons => "mcmanager.exe" behaviors = Show icon and notifications
Launch Mirth Connect Server Manager
Select "Start" or "Restart"

Imported Issue. Original Details: Jira Issue Key: MIRTH-3944 Reporter: minht Created: 2016-04-26T11:53:24.000-0700

rbeckman-nextgen commented 4 years ago

Getting the Error in Windows 10 as well.

Imported Comment. Original Details: Author: khaleshahs Created: 2018-07-06T10:25:10.000-0700

rbeckman-nextgen commented 4 years ago

I appear to get this issue when NOT running on Derby. It was typically not an issue when running on Derby as the database solution. When I switch to Postgres or SQL server the issue begins to manifest on Windows Server 2016, even on a clean database with no channels installed.

Service appears to actually start succesfully, but the error message appears any time I start service with Mirth Connect Service Manager. No errors when starting with Windows "Services" control panel applet.

Imported Comment. Original Details: Author: vlight Created: 2020-01-23T06:32:50.000-0800

rbeckman-nextgen / test-mc4

Error "The Mirth Connect Service could not be started." #3800