Runtime errors

Runtime errors are usually displayed without any information about where they have occurred. To obtain the location of the error, use the flag g with the COMPILE, CLOAD, or EXECUTE command.

Initializations

E-30   Duplicate label `label' at line num of file `file' (ignored)

The same label is used repeatedly in a data file.

Example:

 D: [1 2 3]
 D: [1 2 4]

E-31   Error when reading label `label' at (num1,num2) of file `file'

The data entry labeled label has not been read correctly. Usually this message is preceded by a more detailed one, e.g. E-24, E-27 or E-28.

E-32   Error when writing label `label' at (num1,num2) of file `file'

The data entry labeled label has not been written correctly. Usually this message is preceded by a more detailed one, e.g. E-23.

E-33   Initialization with file `file' failed for: list_of_identifier

Summary report at the end of an initializations section. Usually this message is preceded by more detailed ones, e.g. E-27, E-28, E-30, E-31.

General runtime errors

E-6   Number of running concurrent models authorized by license is exceeded

A program or model is trying to use more (sub)models than what is authorized by the licence.

E-51   Division by zero

Division by 0 resulting from the evaluation of an expression.

E-52   Math error performing function `identifier'

For example ln used with inadmissible argument, such as 0 or negative values.

E-72   Not a runnable model (main procedure not found)

Most likely, you are trying to execute a 'package' as if it were a 'model'.

E-1000   Inconsistent range

Typically displayed if the lower bound specified for a range is greater than its upper bound.

Example:

 D:=3..-1

E-1001   Conflicting types in set operation (op)

A set operation can only be carried out between sets of the same type.

Example:

 declarations
  C: set of integer
  D: range
 end-declarations

 C:={5,7}
 D:=C

The inverse, C:=D, is correct because ranges are a special case of sets of integers.

E-1002   An index is out of range

An attempt is being made to access an array entry that lies outside of the index sets of the array.

E-1003   Trying to modify a finalized or fixed set

Occurs, for instance, when it is attempted to re-assign a constant set or to add elements to a fixed set.

E-1004   Trying to access an uninitialized object (type_of_object)

Occurs typically in models that define subroutines.

Example:

type_of_object: array

 forward procedure myprint
 myprint
 declarations
  A:array(1..2,3..4) of integer
 end-declarations

 procedure myprint
  writeln(A(1,2))
 end-procedure

Move the declaration of A before the call of the subroutine

E-1005   Wrong type for ``procedure''

Occurs when procedures settype or getvars are used with incorrect types.

E-1006   Null reference (internal_function)

This error is a special case of E-1004 when the problem is detected on an external type or scalar (e.g. accessing a record field on an object that has not been initialized).

E-1009   Too many initializers

The number of data elements exceeds the maximum size of an array.

Example:

 declarations
  A:array(1..3) of integer
 end-declarations

 A::[1,2,3,4]

E-1010   Trying to extend a unary constraint

Most types of unary constraints cannot be transformed into constraints on several variables.

Example:

 declarations
  x,y: mpvar
 end-declarations

 c:=x is_integer
 c+=y

E-1011   Dense array too big

The model is trying to create a dense array with more than 4 billion cells, typically such an array should have been declared as sparse (dynamic or hashmap). This error will be raised when the array is allocated (after its declaration or when it is first accessed).

E-1013   Infeasible constraint

The simple cases of infeasible unnamed constraints that are detected at run time include:

Example:

 declarations
  x:mpvar
 end-declarations
 i:=-1
 if(i>=0,x,0)>=1

! or:
 x-x>=1

E-1014   Conflicting types in array operation (op)

An array operation (like assignment) can only be carried out between arrays of the same type and structure.

E-1015   Trying to modify a constant list

Occurs, for instance, when it is attempted to apply a destructive operation (like splittail) to a constant list.

E-1016   Trying to get an element in an empty set

The function getfirst or getlast is applied to an empty set.

E-1017   Trying to get an element in an empty list

The function getfirst or getlast is applied to an empty list.

E-1018   Invalid identifier `identifier' for publish

The publish command has received an invalid identifier name (e.g. not a valid Mosel identifier or the name is already in use as Mosel idientifier).

E-1100   Empty problem

We are trying to generate or load an empty problem into a solver (i.e. no constraints; bounds do not count as constraints).

E-1102   Problem capacity of student license exceeded (num1 type_of_object > num2)

The problem is too large to be solved with a student license. Use a smaller data set or try to reformulate the problem to reduce the number of variables, constraints, or global entities.

E-1103   Too many matrix coefficients

Matrix size exceeds machine capacity: for 32bit versions the limit are 2billion (2·10E9) elements.

BIM reader

E-80   `file' is not a BIM file

Trying to load a file that does not have the structure of a BIM file.

E-82   Wrong file version (current:num1/required:num2) for file `file'

A BIM file is loaded with an incompatible version of Mosel: preferably the same versions should be used for generating and running a BIM file.

E-83   Bim file `file' corrupted

A BIM file has been corrupted, e.g. by saving it with a text editor.

E-84   File `file': model cannot be renamed

A model file that is being executed cannot be re-loaded at the same time.

W-85   Trailing data at end of file `file' ignored

At the end of a BIM file additional, unidentifiable data has been found (may be a sign of file corruption).

E-88   Bim file `file' corrupted

Incomplete or otherwise damaged BIM file.

E-90   Signature error (description)

During the generation of a BIM file, a problem with the signature has occurred.

E-91   Signature verification error (description)

While reading a BIM file, a problem with the signature has occurred (e.g. trying to check signature for a file that is not signed; or the keys that have been employed don't match).

E-92   Encryption error (description)

Problem with encryption during the generation of a BIM file (e.g. invalid or missing key).

E-93   Decryption error (description)

Problem with decryption while reading a BIM file (e.g. invalid or missing key).

Module manager errors

E-350   Module `module' not found

A module has not been found in the module path (see section Directive uses for the search rules). This message is also displayed, if a module depends on another library that has not been found (e.g. module mmxprs has been found but Xpress Optimizer has not been installed or cannot be located by the operating system).

E-351   File `file' is not a Mosel DSO

Typically displayed if Mosel cannot find the module initialization function.

E-352   Module `module' requires a more recent version of Mosel (unsupported interface)

A module is not compatible with the Mosel version used to load it.

E-353   Module `module' disabled by restrictions

Module module either does not implement restriction handling at all or it requires features that are not authorized. See section mosel command: restricted mode (restricted mode) and section Configuration file (Remote Launcher configuration) to learn how to relax the restrictions.

Example:

mmxprs will fail with the restriction setting NoTmp

E-354   Error when initializing module `module'

Usually preceded by an error message generated by the module. Please refer to the documentation of the module for further detail.

E-355   Wrong version for module `module'(using:num1.num2.num3/required:num4.num5.num6)

A model is run with a version of a module that is different from the version that has been used to compile the model (trying to run with version num1.num2.num3, required version is num4.num5.num6).

E-358   Error when resetting module `module'

A module cannot be executed (e.g. due to a lack of memory).

E-359   Driver `pkg.driver' rejected (reason)

A module publishes an IO driver which name is invalid or that is missing some mandatory function.

E-360   Control parameter `module.param' unknown (setting ignored)

It is possible to set module parameters when running a model (using the RUN command for instance): in the list of assignments, a control parameter cannot be found in the indicated module.

E-361   Version number truncated (`vernum')

A version number (for module, model or package) consists in three positive numbers a.b.c. This error is raised if one of these numbers is larger than 999.

E-362   The operating system failed to load file `file' (`description')

The module file has been found but cannot be loaded by the system—there will typically be some system error message indicating the exact cause, such as wrong architecture (e.g. using a library compiled for Windows under Linux or bitness mismatch) or missing additional files (e.g. tyring to use module matlab without having previously installed Matlab—see the manual Xpress MATLAB Interface for further detail, or attempting to use mmoci without having installed the Oracle Instant Client—see setup instructions in the whitepaper Using ODBC and other database interfaces with Mosel).