Understand error messages associated with automatic and manual ticket starts

Batch Transfer <batchXferName> was not found

The Batch Transfer (batchXfer) record was not found in the system.

Batch Transfer <batchXferName> does not have a pending ticket

There are no tickets pending for this batchXfer record.

Batch Transfer record inhibited

The batchXfer record is inhibited, either manually or through the use of Auto-Inhibit.

Schedule volume has not been specified, ticket cannot be started

The next pending ticket currently has a scheduled Gross Standard Volume (GSV) of less than 1.0 units of volume. The next ticket cannot be started until a valid scheduled GSV has been configured.

No Product type has been specified

The next pending ticket has no product type. The next ticket cannot be started until a product type has been configured.

Exception thrown: <Message> 
Error reading ticket field (or other trapped exception): <Message>

An exception was thrown from one of the modules in batch transfer. There are many possible reasons for an exception, and the error message may give a further indication. There may be an error message in the AVEVA Enterprise SCADA Error Log. This message may require assistance from Support for its interpretation.

Error received back from ticket start function: <code>

A failure code was returned from a manual ticket start. An error message in the AVEVA Enterprise SCADA Error Log should indicate the reason.

Ticket record <ticket slot number> cannot be found.

The ticket record slot number that is referenced in the batchXfer record cannot be found. This indicates a failure in the RealTime database (RTDB) integrity.

Invalid Regex Pattern for name <field>: <regex pattern>

In the user-generated validation, one of the regular expression patterns is invalid in the configuration file LMS.RealTime.Json.

Invalid fieldtype for name <field>: <type>

In the user-generated validation, the fieldtype attribute is invalid in the configuration file LMS.RealTime.Json. Valid field types are string, int, float, double, or bool. If the attribute is omitted, the batchXfer record assumes the field type is a string.

(user error message) 

If a field named in a user specification does not match the regular expression given, a user-defined message will display.

start_ticket(): user criteria failed (<rtncode>) for batch transfer <batchXferName>

This message indicates that one of the user-defined criteria failed on a start.

Not pumping minimum amount of time

This message indicates that the current ticket has not been active for a long enough duration for another ticket start to occur.

Not pumping minimum amount of fluid

This error message is recorded in the AVEVA Enterprise SCADA Error Log in the event that the current ticket has not pumped enough volume for another ticket start to occur.

Execute Action Sequence is enabled for BatchXfer '<BatchXfer Name>', but no action sequence is specified

This error message is recorded in the AVEVA Enterprise SCADA Error Log in the event that the application attempts to execute an action sequence but there is no action sequence defined.

Note: While all attempts are made to correct this situation before it happens through other error-checking mechanisms, sometimes this situation occurs despite the best efforts of the software.

ExecuteActionSequenceIfEnabledExtern(): Execution error: <error message>

This error message is recorded in the AVEVA Enterprise SCADA Error Log in the event that the function used to execute the action sequence (if it is enabled) experiences an unexpected error.

ValidateBatchXferConfigurationExtern(): Execution error: <error message>

This error message is recorded in the AVEVA Enterprise SCADA Error Log in the event that the function used to validate the batch transfer configuration experiences an unexpected error.