How to resolve WebLogic Managed Server does not start due to incompatible state.

In this article, we will discusses how to resolve WebLogic Managed Server Does Not Start with error incompatible state. If managed server was incorrectly stopped unexpectedly, trying to start it using the node manager could lead to this error:


You cannot start the Weblogic managed server does not start ealier using the admin console because of this. 

managed server does not start
managed server does not start


Error Messages:-

Message icon – Warning The server xxxx  is in an incompatible state.

Message icon – 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.


“The server xxxx is in an incompatible state


The likely cause of this error is that the status of of WL server reflected by node manager, is not correct.


To solve the issue you need to follow the next steps:

Check that the instance is not running using ps -ef. If it is, use kill -9 <pid> to stop the running instance.


Remove the state file:

If the managed server name is “Server-Name”, then go to the managed server machine, delete the following:


<Server-Name>.state is the node manager file containing instance information and status.

After deleting this file, the managed server can be remotely started from the Admin Console.

Once you remove the stat folder, you are able to start the services.

If you feel this is helpful for your issue, you may check another weblogic post.

You may check another post related to same issue.

Leave a Comment