Summary of common Batch Transfer messages

Batch Transfer <Batch Transfer Name> was not found.

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

Batch Transfer <Batch Transfer Name> does not have a pending ticket.

There are no tickets pending for this batchXfer.

Batch Transfer record inhibited.

The Batch Transfer 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 the batchXfer record. There are multiple possible reasons for an exception; the 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 AVEVA 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 that there is a failure of the integrity of the RealTime database (RTDB).

Invalid Regex Pattern for name <Field>: <Regular Expression Pattern>.

One of the regular expression patterns used in the LMS.RealTime.Json file is invalid. Navigate to %DNAInstallRoot%\RealTime\config\Settings\LMS.RealTime.Json to correct the issue.

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 the following:

• string

• int

• float

• double

• bool

If the attribute is omitted, batch transfer 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 error message will be displayed.