Skip to main content
pshashipreetham
pshashipreetham19-Tanzanite
19-Tanzanite
Oct 12, 2026 12:51 PM UTC
Solved

Kepware 6.15 runtime closes by itself every 3-4 days, then needs a manual reopen

Hi all,

We are supporting a site where Kepware Server 6.15 (drivers V6.15.132.0, Modbus TCP) sends data to ThingWorx 10.2 over the Native Interface. We need some help with the points below.

What is happening
- The customer says Kepware closes by itself about every 3-4 days. Whoever sees it first opens the application again.
- While it is closed, no data from any device reaches ThingWorx. Store and Forward does not help here, as it runs inside Kepware.
- The longest case in the Event Log was on 10 Oct: runtime exit at 3:00:22 AM and next start at 9:04:15 AM (about 6 hours).
- In the log we see 7 runtime exits. Six of them restarted within 1 to 3.5 minutes.

What the Event Log shows
- Each exit is preceded by "Administrator configuration session ended".
- Then: "Runtime performing exit processing."
- On the day of the 6-hour gap, the reopen attempt logged: "Account '<account>' does not have permission to run this application." and then "Timeout waiting for server runtime to start."
- The customer says the application must be run as administrator, otherwise this permission error is logged.
- The same permission error appears on 8 different dates.

    MKhatriAnswer
    Support
    Oct 14, 2026 5:09 PM UTC

    Hello,
     

    Based on the Event Log, the Kepware runtime appears to be shutting down gracefully rather than crashing, as each runtime exit is preceded by "Administrator configuration session ended" followed by "Runtime performing exit processing."

    The repeated "Account '' does not have permission to run this application" messages suggest a Windows user permission or service account issue. This may be preventing Kepware from restarting automatically, which explains the extended downtime observed on October 10.

    Recommendations:

    • Verify which Windows account is being used to launch Kepware.
    • Confirm that the account has local administrator rights and permission to run KEPServerEX.
    • Check whether any scheduled tasks, remote sessions, group policies, or security software could be closing the application.
    • Review Windows Event Viewer logs around the runtime exit timestamps for additional information.

    Regards,
    Mohit

    View in thread

    1 reply

    MKhatriCommunity ManagerAnswer
    Support
    Oct 14, 2026 5:09 PM UTC

    Hello,
     

    Based on the Event Log, the Kepware runtime appears to be shutting down gracefully rather than crashing, as each runtime exit is preceded by "Administrator configuration session ended" followed by "Runtime performing exit processing."

    The repeated "Account '' does not have permission to run this application" messages suggest a Windows user permission or service account issue. This may be preventing Kepware from restarting automatically, which explains the extended downtime observed on October 10.

    Recommendations:

    • Verify which Windows account is being used to launch Kepware.
    • Confirm that the account has local administrator rights and permission to run KEPServerEX.
    • Check whether any scheduled tasks, remote sessions, group policies, or security software could be closing the application.
    • Review Windows Event Viewer logs around the runtime exit timestamps for additional information.

    Regards,
    Mohit

    Translate
    Terms & ConditionsAccessibility statement