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).
worked, yes, thx
Thanks..
It works most of the time, but it is not the solution. Oracle guys should have come with a bug fix
Thanks a lot!
thanks its worked for me…But is this a temp solution or perminent fix?
Thanks ..Its working
Thanks for the solution. It worked.
Thanks it works exactly as explained.
thanks a lot
Thank you !! quite simple yet very frustrating if you do know this solution.
Thanks!! This worked
Thank you very much. solution worked for me
Thanks alot, quite simple after try some way (ldap..)
Thanks for solution
What if managed_server.state file is not present in this folder?
Then there shouldn’t be any problem with the state.
This file is not present in my server directory and still I am getting this issue while starting the managed server.
Same – no Java process for the managed servers, no .state file but still stuck in STARTING
Thanks a lot!
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.
thank you thank you thank you! such a simple solution which I hadn’t found until today!
Worked for me — thanks!!
Thanks for the help, it works!!