Skip to Content
0
Former Member
Feb 20, 2007 at 02:39 AM

EOIO - "predecessor not in final state"

1365 Views

We were following Stefan Grube's blog (/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework) to delete an offending message. Of interest is that the first sequential message we can find is numbered "2", and when we try to cancel it we get "Unable to cancel 1 of 1 messages, update the status" and then on detail in the audit log we get the following error:

Admin action: Setting the message status to "failed" failed, due to Predecessor not in final state.

Trouble is, we can't find the predecessor.

Suggestions?