Invalid state file format. State file contents Invalid state file format. State file contents

Weblogic managed Servers cannot be started via the WLS console as Node Manager is not reachable.
Also, the nodemanager.log file is showing the following messages:
The error “ Invalid state file format. State file contents” was coming for only one machines in a cluster.


<Feb 9, 2011 11:06:01 AM> <WARNING> <There was a problem initializing the domain ‘steffworld’ at ‘$domains\domainName’. Please make sure that this domainName: ‘domainName’ is registered and is fully enrolled for this nodemanager at: ‘$domains\domainName’.>
<Feb 9, 2011 11:06:01 AM> <WARNING> <I/O error while reading domain directory> Invalid state file format. State file contents:
at weblogic.nodemanager.common.StateInfo.load(
at weblogic.nodemanager.server.ServerMonitor.loadStateInfo(
at weblogic.nodemanager.server.ServerMonitor.isCleanupAfterCrashNeeded(
at weblogic.nodemanager.server.ServerManager.recoverServer(
at weblogic.nodemanager.server.DomainManager.initialize(
at weblogic.nodemanager.server.DomainManager.<init>(
at weblogic.nodemanager.server.NMServer.getDomainManager(
at weblogic.nodemanager.server.Handler.handleDomain(
at weblogic.nodemanager.server.Handler.handleCommand(


The state file of the managed server is in an invalid state: for example, it may be empty. Under each managed server directory, there is a NodeManager directory containing a state file <managed_server_name>.state. If this file is empty or corrupt, then the described errors occur.
For example, under $domains\domainName\domainName\servers\<serverName>\data\nodemanager, the <serverName>.state file is empty.
The cause of the empty file could be one of the following:

⦁ When the computer crash occurred, this particular state file was may have been in the process of being updated, For instance it may have been changing from “RUNNING:Y:N” to “SHUTTING_DOWN:Y:N” but did not have time to write the new line before the machine actually shutdown. This could have caused a empty file.
⦁ A file corruption issue at the ⦁ OS level.
In both the above cases, WebLogic Server cannot control the cause, so cannot avoid it. Thus, we have to execute a solution after the problem occurs to recover the environment, instead of preventing the problem occurrence.


We have two options to recover the environment.


Edit the state file so that it contains a valid line, such as:
⦁ Please insert the above line into your <managed_server_name>.state file and save it. Then restart Node Manager. Finally, in the WLS console, the Node Manager Status will show:
⦁ Status: Reachable
⦁ Please, perform the above step for all managed servers in the domain.


Stop the managed server if it is RUNNING.
⦁ Stop the Admin Server.
⦁ Stop Node Manager.
⦁ Delete the following ⦁ files:
⦁ Start Node Manager again.
⦁ Start the Admin Server again.
⦁ Start the managed server using the Admin Console.

For more Weblogic Issues check here.