Skip to main content
1-Visitor
September 7, 2025
Question

Tomcat 9.0 service stops after starting

  • September 7, 2025
  • 6 replies
  • 647 views
I am using ThingWorx Platform Release 8.1 and DatecodeSP1

After a problem with the server where the RAM memory was saturated, the server had to be restarted, after this event the Tomcat service starts and stops shortly after.

Here are the errors that I faced
Faulting module name FlxCore64.Dll version 2016.8.0.0 exeption code 0xc0000417

    6 replies

    24-Ruby III
    September 7, 2025
    Rocko
    19-Tanzanite
    September 8, 2025

    8.1? Wow, that's real vintage, when was that released, like 2018? Not sure why you'd want to run a software that old, but if you did nothing else but restarting the server (e.g. updating some component), I would assume some files got corrupted. Do you have a backup?

    You can run a system check for the integrity of the OS files (I guess this is on Windows), also make sure there is no antivirus blocking the application, the error code suggests is could be that.

    Community Manager
    September 12, 2025

    Hello @AU_11025381,

     

    It looks like you have some responses from some community experts. If any of these replies helped you solve your question please mark the appropriate reply as the Accepted Solution. 
    Of course, if you have more to share on your issue, please let the Community know so other community members can continue to help you.

    Thanks,
    Vivek N.
    Community Moderation Team.

    18-Opal
    September 15, 2025

    Few things to try:

    1. Disable Memory Integrity in Windows
    2. Disable the firewall
    3. Check if you have multiple versions of this DLL in your system PATH
    4. Check the Event Viewer for more detailed or related error messages

    / Constantine

    Community Manager
    September 17, 2025

    Hi @AU_11025381 

     

    I saw that you opened a case for this issue.  Once the issue is resolved, I will provide an update here for the benefit of our community members.

     

    Regards.

     

    --Sharon

    Community Manager
    September 29, 2025

    Hi @AU_11025381 

     

    The case has been closed without a solution due to the lack of artifacts needed to investigate the issue.  Were you able to resolve the issue yourself?

     

    Your update on the solution you found would be greatly appreciated.

     

    Regards.

     

    --Sharon