Rule of Tech

technology shall have no dominion

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).

Posted

in

by

Marko

Tags:

, ,

Comments

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

  1. Jagan Avatar
    Jagan

    Worked for me, thank you

    Reply
  2. Jeff Avatar
    Jeff

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

    Reply
  3. muja Avatar
    muja

    worked, yes, thx

    Reply
  4. Krishnakumar Avatar
    Krishnakumar

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

    Reply
  5. khasim Avatar
    khasim

    Thanks a lot!

    Reply
  6. Rajasekharbabu Medarametla Avatar
    Rajasekharbabu Medarametla

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

    Reply
  7. sourav Avatar
    sourav

    Thanks ..Its working

    Reply
  8. Siva Boppana Avatar
    Siva Boppana

    Thanks for the solution. It worked.

    Reply
  9. Sundar Avatar
    Sundar

    Thanks it works exactly as explained.

    Reply
  10. andik Avatar
    andik

    thanks a lot

    Reply
  11. Nadal Avatar
    Nadal

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

    Reply
  12. Arun Avatar
    Arun

    Thanks!! This worked

    Reply
  13. Mohammed Avatar
    Mohammed

    Thank you very much. solution worked for me

    Reply
  14. ThangNM Avatar
    ThangNM

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

    Reply
  15. Punit Avatar
    Punit

    Thanks for solution

    Reply
  16. Hitesh Avatar
    Hitesh

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

    Reply
    1. Marko Avatar
      Marko

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

      Reply
      1. Onkar Avatar
        Onkar

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

        Reply
        1. Andrew Avatar
          Andrew

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

          Reply
  17. José Avatar
    José

    Thanks a lot!

    Reply
  18. 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.

    Reply
  19. Margaret Avatar
    Margaret

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

    Reply
  20. Kris Reese Avatar
    Kris Reese

    Worked for me — thanks!!

    Reply
  21. Victor Avatar
    Victor

    Thanks for the help, it works!!

    Reply

Leave a Reply

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