Weblogic 12c and Managed Server in incompatible state

Oracle WebLogic application server (WLS) is quite a behemoth and usually works much better than e.g. OC4J which we previously had to use. But sometimes things don’t go as they should and it gets stuck. Some time ago my managed Server was in “FORCE_SHUTTING_DOWN” state and when trying to restart it I got an error message.

“The server myServer is in an incompatible state.

Warning All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.”

Seems that this is a “common” problem with WebLogic Server and happens at least with 12c version which was also my case. The solution is to delete the “managed_server.state” file under your domain in “servers/managed_server/data/nodemanager/” where managed_server is your managed server’s name.

So, stop everything, delete managed_server.state from your managed server folder and start everything (go to console to start your managed sever as it is SHUTDOWN).





25 responses to “Weblogic 12c and Managed Server in incompatible state”

  1. Sharath Avatar

    Any similar troubleshooting steps for WLS 14C?

  2. Jagan Avatar

    Worked for me, thank you

  3. Jeff Avatar

    No luck. got the state files but renaming them didn’t help.

  4. muja Avatar

    worked, yes, thx

  5. Krishnakumar Avatar

    It works most of the time, but it is not the solution. Oracle guys should have come with a bug fix

  6. khasim Avatar

    Thanks a lot!

  7. Rajasekharbabu Medarametla Avatar
    Rajasekharbabu Medarametla

    thanks its worked for me…But is this a temp solution or perminent fix?

  8. sourav Avatar

    Thanks ..Its working

  9. Siva Boppana Avatar
    Siva Boppana

    Thanks for the solution. It worked.

  10. Sundar Avatar

    Thanks it works exactly as explained.

  11. andik Avatar

    thanks a lot

  12. Nadal Avatar

    Thank you !! quite simple yet very frustrating if you do know this solution.

  13. Arun Avatar

    Thanks!! This worked

  14. Mohammed Avatar

    Thank you very much. solution worked for me

  15. ThangNM Avatar

    Thanks alot, quite simple after try some way (ldap..)

  16. Punit Avatar

    Thanks for solution

  17. Hitesh Avatar

    What if managed_server.state file is not present in this folder?

    1. Marko Avatar

      Then there shouldn’t be any problem with the state.

      1. Onkar Avatar

        This file is not present in my server directory and still I am getting this issue while starting the managed server.

        1. Andrew Avatar

          Same – no Java process for the managed servers, no .state file but still stuck in STARTING

  18. José Avatar

    Thanks a lot!

  19. ramakrishna vishwanath Avatar
    ramakrishna vishwanath

    When i got this issue where the managed server was stuck in FORCED_SHUTTING_DOWN state, the owner of managed_server.state file in servers/managed_server/data/nodemanager/ was root(or different user other than the one that starts weblogic server). I must have started nodemanager logged in as root by mistake. I just changed the owner ship of the file and restarted admin server and nodemanager. The issue was fixed.

    Hope this helps.

  20. Margaret Avatar

    thank you thank you thank you! such a simple solution which I hadn’t found until today!

  21. Kris Reese Avatar

    Worked for me — thanks!!

  22. Victor Avatar

    Thanks for the help, it works!!

Leave a Reply

Your email address will not be published. Required fields are marked *