Mirth Connect
  1. Mirth Connect
  2. MIRTH-3944

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

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.4.0, 3.3.1, 3.3.2
    • Fix Version/s: None
    • Component/s: Server Manager
    • Labels:
      None
    • Environment:
      Window 7
      Window 2008 R2 Standard
    • Operating System:
      Windows 7, Windows Server 2003

      Description

      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:

      1. From Window Control Panel\All Control Panel Items\Notification Area Icons => "mcmanager.exe" behaviors = Show icon and notifications
      2. Launch Mirth Connect Server Manager
      3. Select "Start" or "Restart"
      1. Error.png
        780 kB
      2. Error Windows10.PNG
        355 kB

        Activity

        Hide
        Khaleshah Shaik added a comment -

        Getting the Error in Windows 10 as well.

        Show
        Khaleshah Shaik added a comment - Getting the Error in Windows 10 as well.
        Hide
        Ben Voytko added a comment -

        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.

        Show
        Ben Voytko added a comment - 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.

          People

          • Assignee:
            Unassigned
            Reporter:
            Minh Tran
          • Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated: