Batch Run-time Errors
- Last UpdatedSep 17, 2021
- 3 minute read
The following errors can appear during batch processing. In all cases, when an error occurs, an error dialog box appears.
|
Error: |
Cannot change mode of <manual operation name> batch! |
|
Reason: Manual Mode is the only valid batch processing mode in a manual operation. |
|
|
Corrective Action: Acknowledge the error message. |
|
|
Error: |
Unexpected phase status of READY! |
|
Error: |
Unexpected phase status of RUN! |
|
Error: |
Unexpected phase status of HELD! |
|
Error: |
Unexpected phase status of DONE/ABORTED! |
|
Error: |
Unexpected phase status of INTERLOCK! |
|
Reason #1: You are trying to run the same phase in parallel in your recipe procedure, or there is a problem with the phase logic. |
|
|
Corrective Action: Correct the recipe procedure or the phase logic. |
|
|
Reason #2: Batch Manager was shut down and phase logic has been left in an improper state. |
|
|
Corrective Action: Manually reset the phase and restart Batch Manager. |
|
|
Error: |
Cannot access material "material id"! - Hold Batch; Correct Problem; Restart. |
|
Reason: Phase is an Automatic Transfer. Batch Manager cannot find the material in the Train assigned to the batch. |
|
|
Corrective Action: Put the batch in Hold, correct the problem, then restart the batch. The problem may require one or both of the following corrections:
|
|
|
Error: |
Cannot access transfer "transfer name"! - Hold Batch; Correct Problem; Restart. |
|
Reason #1: A connection associated with the transfer cannot be found in the train. |
|
|
Corrective Action: Put the batch in Hold. Modify the train to include the appropriate unit that would support the transfer. Restart the batch. |
|
|
Reason #2: The batch is assigned to a train that cannot properly run the recipe. |
|
|
Corrective Action: Make sure the batch is assigned to a train that can properly run the recipe. |
|
|
Reason #3: The connection has not been entered in the process model. |
|
|
Corrective Action: Abort the batch. Stop processing of the AVEVA Batch Management System. Add and assign the connection to the appropriate transfer class using the Process Model Editor. Restart the AVEVA Batch Management System. |
|
|
Error: |
Cannot access process "process name"! - Hold Batch; Correct Problem; Restart. |
|
Reason: A unit associated with the process cannot be found in the train. The unit needed for the process was most likely deleted from the train after the batch was started. |
|
|
Corrective Action: Put the batch in Hold. Modify the train to include the appropriate unit that would support the transfer. Restart the batch. |
|
|
Error: |
Invalid Query Data |
|
Reason: AVEVA Batch Management database is incompatible or corrupt. This error is related to the security system. |
|
|
Corrective Action: Verify and correct the database. |
|
|
Error: |
Phase param tag read timeout (Note: Error is reported in the Batch Logger.) Timeout exceeded allowable value! for param tag read at end of phase - only when using remote I/O server. |
|
Reason: MemTagMngr is local; therefore, the memory tag parameter uses the local server’s time. The phase done tag is a remote tag and may have a different time (perhaps several minutes or more). When BatchMngr compares the time difference between the two, it writes the MemTag time stamp to match that of the remote tag time stamp. |
|
|
Corrective Action: Synchronize the system time settings on the server and the remote system. |