Open rbeckman-nextgen opened 4 years ago
Understandably, this has been a painful and long standing issue for some. This and various other improvements to the Server Manager are currently slated for 3.4
Imported Comment. Original Details: Author: wayneh Created: 2014-12-15T06:34:30.000-0800
I think I experienced this issue when installing 4.4.0 on a Windows machine that already had 4.3.0 installed. (The two were installed in different directories.) "Mirth Connect Service" was modified to reference the 4.4.0 installation, leaving no service for 4.3.0.
In the class com.mirth.connect.manager.WindowsServiceController, WINDOWS_SERVICE_NAME is hard-coded. So, when several Mirth services are installed on the same server, the manager cannot be used.
Imported Issue. Original Details: Jira Issue Key: MIRTH-2112 Reporter: dbe Created: 2012-03-08T00:56:52.000-0800