I believe what you'll need to do is rebuild the state.xml using the DBUtil tool found on the server; it's in the bin directory on Windows servers; not sure about the location for Linux. That rebuilds the state.xml according to the XML files it finds and the XMLDB.
will rebuild the whole thing - it takes a while, depending on your server.
dbutil -s Protocols
will just rebuild the protocols tab. So if you know which state.xml is corrupt, you can rebuild just that one. It can still take a while of course. If it's the Components tab, then replace Protocols in the above command with Components.
But, I think this will sort your problem out.
Apologies, I forgot that there's another step you need to do when using DBUtil (and other tools in the bin directory I believe), which is to set up variables. I found this in the help:
On Linux servers, first execute the command "
source ppvars.sh" (if using the bash shell), or "
source ppvars.csh" (if using the C shell). This sets environment variables required for successful execution of DbUtil (see below).
Hopefully that helps you.
That's my pleasure. I had the same thing happen to me a few weeks back (for completely unknown reasons) and this command saved me - so I know how you feel!