Description
This error may be seen in the Windows Application Event log. This article explains how to identify and resolve possible root causes.
Example of error:
Timestamp: 6/9/2009 4:44:13 PM
Message: Failure to complete operation: SUBMIT BATCH, Error BatchTimestamp - Batch time stamp.
Category: Application
EventId: 5367
Severity: Error
Machine: MY-MACHINENAME
OS Version: Microsoft Windows NT 5.2.3790 Service Pack 2
Application Domain: DSI.PVECommon.PVProcWork.exe
Process Id: 5332
Process Name: C:\Program Files\Digitech Systems\PaperVision Capture\DSI.PVECommon.PVProcWork.exe
Win32 Thread Id: 5148
Thread Name:
Summary
This error is usually caused by an interruption to the normal process flow of a particular batch. Essentially, the state of the batch is not in sync with the rest of the system. An example of this is when a batch is manually moved in the process flow but the maintenance queue item that is used to transition the batch to the next step remains in the Maintenance Queue. The error occurs because the system will continue to try and process the abandoned Maintenance Queue item until it is manually removed. For example, if a batch is manually moved from step three to one, and there is a Maintenance Queue item trying to transition the batch to step four, this error will occur.
To resolve this error, follow the steps below:
- Determine if a suspect Maintenance Queue item is out of sync with the state of the corresponding batch.
- This can be done in the Admin Console -> Global -> Maintenance Queue by double-clicking the suspect Maintenance Queue item and comparing identifiers such as its Batch ID or Internal Name with the information found in the Batch Management Console.
- Once it is determined that a Maintenance Queue item is the source of the error, right-click and delete the item.
- Occasionally, it may be necessary to re-submit a batch from a manual step in order to regenerate a proper Maintenance Queue item and thus allow the batch to resume normal process flow.
