Optimizer Error and Warning Messages

Following a premature exit, the Optimizer can be interrogated as necessary to obtain more information about the specific error or warning which occurred. Library users may return a description of errors or warnings as they are encountered using the function XPRSgetlasterror. This function returns information related to the error code, held in the problem attribute ERRORCODE. For Console users the value of this attribute is output to the screen as errors or warnings are encountered. For Library users it must be retrieved using:

XPRSgetintattrib(prob,XPRS_ERRORCODE,&errorcode);

The following list contains values of ERRORCODE and a possible resolution of the error or warning.

3 Extension not allowed - ignored.: The specified extension is not allowed. The Optimizer ignores the extension and truncates the filename.
4 Column <col> has no upper bound.: Column <col> cannot be at its upper bound in the supplied basis since it does not have one. A new basis will be created internally where column <col> will be at its lower bound while the rest of the columns and rows maintain their basic/non-basic status.
5 Error on .<ext> file.: An error has occurred on the . <ext> file. Please make sure that there is adequate disk space for the file and that it has not become corrupted.
6 No match for column <col> in matrix.: Column <col> has not been defined in the COLUMNS section of the matrix and cannot be used in subsequent sections. Please check that the spelling of <col> is correct and that it is not written outside the field reserved for column names.
7 Empty matrix. Please increase EXTRAROWS.: There are too few rows or columns. Please increase EXTRAROWS before input, or make sure there is at least one row in your matrix and try to read it again.
9 Error on read of basis file.: The basis file .BSS is corrupt. Please make sure that there is adequate disk space for the file and that it has not been corrupted.
11 Not allowed - solution not optimal.: The operation you are trying to perform is not allowed unless the solution is optimal. Please call XPRSmaxim (MAXIM) or XPRSminim (MINIM) to optimize the problem and make sure the process is completed. If the control LPITERLIMIT has been set, make sure that the optimal solution can be found within the maximum number of iterations allowed.
18 Bound conflict for column <col>.: Specified upper bound for column <col> is smaller that the specified lower bound. Please change one or both bounds to solve the conflict and try again.
19 Eta overflow straight after invert - unrecoverable.: There is not enough memory for eta arrays. Either increase the virtual paging space or the physical memory.
20 Insufficient memory for array <array>.: There is not enough memory for an internal data structure. Either increase the virtual paging space or the physical memory.
21 Unidentified section The command is not recognized by the Optimizer.: Please check the spelling and try again. Please refer to the Reference Manual for a list of valid commands.
29 Input aborted.: Input has encountered too many problems in reading your matrix and it has been aborted. This message will be preceded by other error messages whose error numbers will give information about the nature of each of the problems. Please correct all errors and try again.
36 Linear Optimizer only: You are only authorized to use the Linear Optimizer. Please contact your local sales office to discuss upgrading to the IP Optimizer if you wish to use this command.
38 Invalid option.: One of the options you have specified is incorrect. Please check the input option and retype the command. A list of valid options for each command can be found in Console and Library Functions.
41 Global error - contact the Xpress support team.: Internal error. Please contact your local support office.
45 Failure to open global file - aborting. (Perhaps disk is full).: The Optimizer cannot open the .GLB file. This usually occurs when your disk is full. If this is not the case it means that the .GLB file has been corrupted.
50 Inconsistent basis.: Internal basis held in memory has been corrupted. Please contact your local support office.
52 Too many nonzero elements.: The number of matrix elements exceeds the maximum allowed. If you have the Hyper version then increase your virtual page space or physical memory. If you have purchased any other version of the software please contact your local sales office to discuss upgrading if you wish to read matrices with this number of elements.
56 Reference row entries too close for set <set> member <col>.: The coefficient of column <col> in the constraint being used as reference row for set <set> is too close to the coefficient of some other column in the reference row. Please make sure the coefficients in the reference row differ enough from one another. One way of doing this is to create a non computational constraint (N type) that contains all the variables members of the set <set> and then assign coefficients whose distance from each other is of at least 1 unit.
58 Duplicate element for column <col> row <row>.: The coefficient for column <col> appears more than once in row <row>. The elements are added together but please make sure column <col> only has one coefficient in <row> to avoid this warning message.
61 Unexpected EOF on workfile.: An internal workfile has been corrupted. Please make sure that there is adequate disk space and try again. If the problem persists please contact your local support office.
64 Error closing file <file>.: The Optimizer could not close file <file>. Please make sure that the file exists and that it is not being used by another application.
65 Fatal error on read from workfile <file> - program aborted.: An internal workfile has been corrupted. Please make sure that your disk has enough space and try again. If the problem persists please contact your local support office.
66 Unable to open file <file>.: The Optimizer has failed to open the file <file>. Please make sure that the file exists and there is adequate disk space.
67 Error on read of file <file>.: The Optimizer has failed to read the file <file>. Please make sure that the file exists and that it has not been corrupted.
71 Not a basic vector: <vector>.: Dual value of row or column <vector> cannot be analyzed because the vector is not basic.
72 Not a non-basic vector: <vector>.: Activity of row or column <vector> cannot be analyzed because the vector is basic.
73 Problem has too many rows. The maximum is <num>.: The Optimizer cannot input your problem since the number of rows exceeds <num>, the maximum allowed. If you have purchased any other than the Hyper version of the software please contact your local sales office to discuss upgrading it to solve larger problems.
76 Illegal priority: entity <ent> value <num>.: Entity <ent> has been assigned an invalid priority value of <num> in the directives files and this priority will be ignored. Please make sure that the priority value lies between 0 and 1000 and that it is written inside the corresponding field in the .DIR file.
77 Illegal set card <line>.: The set definition in line <line> of the .MAT or .MPS file creates a conflict. Please make sure that the set has a correct type and has not been already defined. Please refer to the Reference Manual for a list of valid set types.
80 File creation error.: The Optimizer cannot create a file. Please make sure that these is adequate disk space and that the volume is not corrupt.
81 Fatal error on write to workfile <file> - program aborted.: The Optimizer cannot write to the file <file>. Please make sure that there is adequate disk space and that the volume is not corrupt.
83 Fatal error on write to file - program aborted.: The Optimizer cannot write to an internal file. Please make sure that there is adequate disk space and that the volume is not corrupt.
84 Input line too long. Maximum line length is <num>: A line in the .MAT or .MPS file has been found to be too long. Please reduce the length to be less or equal than <num> and input again.
85 File not found: <file>.: The Optimizer cannot find the file <file>. Please check the spelling and that the file exists. If this file has to be created by the Optimizer, make sure that the process which creates the file has been performed.
89 No optimization has been attempted.: The operation you are trying to perform is not allowed unless the solution is optimal. Please call XPRSmaxim (MAXIM) or XPRSminim (MINIM) to optimize the problem and make sure the process is completed. If you have set the control LPITERLIMIT make sure that the optimal solution can be found within the maximum number of iterations allowed.
91 No problem has been input.: An operation has been attempted that requires a problem to have been input. Please make sure that XPRSreadprob (READPROB) is called and that the problem has been loaded successfully before trying again.
97 Split vector <vector>.: The declaration of column <vector> in the COLUMN section of the .MAT or .MPS file must be done in contiguous line. It is not possible to interrupt the declaration of a column with lines corresponding to a different vector.
98 At line <num> no match for row <row>.: A non existing row <row> is being used at line number <num> of the .MAT or .MPS file. Please check spelling and make sure that <row> is defined in the ROWS section.
102 Eta file space exceeded - optimization aborted.: The Optimizer requires more memory. Please increase your virtual paging space or physical memory and try to optimize again.
107 Too many global entities at column <col>.: The Optimizer cannot input your problem since the number of global entities exceeds the maximum allowed. If you have the Hyper version then increase your virtual page space or physical memory. If you have purchased any other version of the software please contact your local sales office to discuss upgrading it to solve larger problems.
111 Duplicate row <row> - ignored.: Row <row> is used more than once in the same section. Only the first use is kept and subsequent ones are ignored.
112 Postoptimal analysis not permitted on presolved problems.: Re-optimize with PRESOLVE = 0. An operation has been attempted on the presolved problem. Please optimize again calling XPRSmaxim (MAXIM), XPRSminim (MINIM) with the l flag or turning presolve off by setting PRESOLVE to 0.
113 Unable to restore version <ver> save files.: The svf file was created by a different version of the Optimizer and cannot be restored with this version.
114 Fatal error - pool hash table full at vector <vector>.: Internal error. Please contact your local support office.
120 Problem has too many rows and columns. The maximum is <num>: The Optimizer cannot input your problem since the number of rows plus columns exceeds the maximum allowed. If you have purchased any other than the Hyper version of the software please contact your local sales office to discuss upgrading it to solver larger problems.
122 Corrupt solution file.: Solution file .SOL could not be accessed. Please make sure that there is adequate disk space and that the file is not being used by another process.
124 Invalid parameter value passed to <function>. Parameter value <param_name> is not allowed: A parameter lookup by name has failed. The provided parameter name does not match any parameters in Xpress.
127 Not found: <vector>.: An attempt has been made to use a row or column <vector> that cannot be found in the problem. Please check spelling and try again.
128 Cannot load directives for problem with no global entities.: The problem does not have global entities and so directives cannot be loaded.
129 Access denied to problem state : '<name>' (<routine>).: The user is not licensed to have set or get access to problem control (or attribute) <name>. The routine used for access was <routine>.
130 Bound type illegal <type>.: Illegal bound type <type> has been used in the basis file .BSS. A new basis will be created internally where the column with the illegal bound type will be at its lower bound and the rest of the columns and rows will maintain their basic/non-basic status. Please check that you are using XPRSreadbasis (READBASIS) with the t flag to read compact format basis.
131 No column: <col>.: Column <col> used in basis file .BSS does not exist in the problem. A new basis will be created internally from where column <col> will have been removed and the rest of columns and rows will maintain their basic/non-basic status.
132 No row: <row>.: Row <row> used in basis file .BSS does not exist in the problem. A new basis will be created internally from where row <row> will have been removed and the rest of columns and rows will maintain their basic/non-basic status.
136 Cannot access control <control_name> via attribute routine <function>: When accessing controls and attributes, the API function called must be matched appropriately to the type (double, int, string) and access type (control / attribute) of the parameter.
137 Bad internal state found in `Struct' lookup : <parameter_table> (<parameter_name>): A parameter provided could not be found in the parameters table. This is an internal error, please contact FICO support.
140 Basis lost - recovering.: The number of rows in the problem is not equal to the number of basic rows + columns in the problem, which means that the existing basis is no longer valid. This will be detected when re-optimizing a problem that has been altered in some way since it was last optimized (see below). A correct basis is generated automatically and no action needs to be taken. The basis can be lost in two ways: (1) if a row is deleted for which the slack is non-basic: the number of rows will decrease by one, but the number of basic rows + columns will be unchanged. (2) if a basic column is deleted: the number of basic rows + columns will decrease by one, but the number of rows will be unchanged. You can avoid losing the basis by only deleting rows for which the slack is basic, and columns which are non-basic. (The XPRSgetbasis function can be used to determine the basis status.) To delete a non-basic row without losing the basis, bring it into the basis first, and to delete a basic column without losing the basis, take it out of the basis first - the functions XPRSgetpivots and XPRSpivot may be useful here. However, remember that the message is only a warning and the Optimizer will generate a new basis automatically if necessary.
142 Type illegal <type>.: An illegal priority type <type> has been found in the directives file .DIR and will be ignored. Please refer to Appendix Log and File Formats for a description of valid priority types.
143 No entity <ent>.: Entity <ent> used in directives file .DIR cannot be found in the problem and its corresponding priority will be ignored. Please check spelling and that the column <ent> is actually declared as an entity in the BOUNDS section or is a set member.
151 Illegal MARKER.: The line marking the start of a set of integer columns or a set of columns belonging to a Special Ordered Set in the .MPS file is incorrect.
152 Unexpected EOF.: The Optimizer has found an unexpected EOF marker character. Please check that the input file is correct and input again.
153 Illegal card at line <line>.: Line <line> of the .MPS file could not be interpreted. Please refer to the Reference Manual for information about the valid MPS format.
155 Cannot access control '<id>' via attribute routine <routine>.: Controls cannot be accessed from attribute access routines.
156 Cannot access attribute '<id>' via control routine <routine>.: Attributes cannot be accessed from control access routines.
157 Cannot access attribute <attribute_name> via control routine <routine>.: Attributes cannot be accessed from control access routines.
158 Unrecognized callback name <callback> (<function>): The callback name provided to the API function is not recognized.
159 Failed to set default controls.: Attempt failed to set controls to their defaults.
160 Cannot access <typename> type '<id>' via routine <routine>.: Accessing an attribute or control requires using a routine with matching type.
161 Cannot access <typename> type '<name>' via routine <routine>.: Accessing an attribute or control requires using a routine with matching type.
162 Recording and playback error : <info>.: An error occurred in the recording and playback tool.
163 Failed to copy controls.: Attempt failed to copy controls defined for one problem to another.
164 Problem is not presolved.: Action requires problem to be presolved and the problem is not presolved.
167 Failed to allocate memory of size <bytes> bytes.: The Optimizer failed to allocate required memory of size <bytes>.
168 Required resource not currently available : '<name>'.: The resource <name> is required by an action but is unavailable.
169 Failed to create resource : '<name>'.: The resource <name> failed to create.
170 Corrupt global file.: Global file .GLB cannot be accessed. Please make sure that there is adequate disk space and that the file is not being used by another process.
171 Invalid row type for row <row>.: XPRSalter (ALTER) cannot change the row type of <row> because the new type is invalid. Please correct and try again.
173 Name not recognized : <name>.: The control name cannot be recognized.
178 Not enough spare rows to remove all violations.: The Optimizer could not add more cuts to the matrix because there is not enough space. Please increase EXTRAROWS before input to improve performance.
179 Load MIP solution failed : '<status description>'.: Attempt failed to load MIP solution into the Optimizer. See <status description>> for details of the failure.
180 No change to this control allowed.: The Optimizer does not allow changes to this control. If you have the student version, please contact your local sales office to discuss upgrading if you wish to change the value of controls. Otherwise check that the Optimizer was initialized properly and did not revert to student mode because of a security problem.
181 Cannot alter bound on BV, SC, UI, PI, or set member.: XPRSalter (ALTER) cannot be used to change the upper or lower bound of a variable if its variable type is binary, semi-continuous, integer, partial integer, semi-continuous integer, or if it is a set member.
186 Inconsistent number of variables in problem.: A compact format basis is being read into a problem with a different number of variables than the one for which the basis was created.
187 Unable to restore alternative system <system> save files.: The svf file was created on a different operating system and cannot be restored on the current system.
191 Solution in file '<file>' (rows:<nrow>, cols:<ncol>) not compatible with problem.: The size of the loaded problem is not compatible with problem size from the solution file.
192 Bad flags <flag string>.: A flag string passed into a command line call is invalid.
193 Possible unexpected results from XPRSreadbinsol (READBINSOL) : <message>.: A call to the XPRSreadbinsol (READBINSOL) may produce unexpected results. See <message> for details.
194 Failure writing to range file.: Failure writing to range file.
195 Cannot read LP solution into presolved problem.: An LP solution cannot be read into a problem in a presolved state.
197 Failed to register callback for event : '<event>'.: Registering callback for an event failed.
199 Network simplex not authorized: The Optimizer cannot use the network algorithm. Please contact your local sales office to upgrade your authorization if you wish to use it.
202 Control parser: <error>.: A generic control parser error, for example a memory allocation failure.
243 The Optimizer requires a newer version of the XPRL library.: You are using the XPRS library from one Xpress distribution and the XPRS library from a previous Xpress distribution. You should remove all other Xpress distributions from your system library path environment variable.
245 Not enough memory to presolve matrix.: The Optimizer required more memory to presolve the matrix. Please increase your virtual paging space or physical memory. If this is not possible try setting PRESOLVE to 0 before optimizing, so that the presolve procedure is not performed.
247 Directive on non-global entity not allowed: <col>.: Column <col> used in directives file .DIR is not a global entity and its corresponding priority will be ignored. A variable is a 'global entity' it is type is not continuous or if it is a set member. Please refer to Appendix Log and File Formats for details about valid entities and set types.
249 Insufficient improvement found.: Insufficient improvement was found between barrier iterations which has caused the barrier algorithm to terminate.
250 Too many numerical errors.: Too many numerical errors have been encountered by the barrier algorithm and this has caused the barrier algorithm to terminate.
251 Out of memory.: There is not enough memory for the barrier algorithm to continue.
256 Simplex Optimizer only: The Optimizer can only use the simplex algorithm. Please contact your local sales office to upgrade your authorization if you wish to use this command.
257 Simplex Optimizer only: The Optimizer can only use the simplex algorithm. Please contact your local sales office to upgrade your authorization if you wish to use this command.
259 Warning: The Q matrix may not be semi-definite.: The Q matrix must be positive (negative) semi-definite for a minimization (maximization) problem in order for the problem to be convex. The barrier algorithm has encountered numerical problems which indicate that the problem is not convex.
261 <ent> already declared as a global entity - old declaration ignored.: Entity <ent> has already been declared as global entity. The new declaration prevails and the old declaration prevails and the old declaration will be disregarded.
262 Unable to remove shift infeasibilities of &.: Perturbations to the right hand side of the constraints which have been applied to enable problem to be solved cannot be removed. It may be due to round off errors in the input data or to the problem being badly scaled.
263 The problem has been presolved.: The problem in memory is the presolved one. An operation has been attempted on the presolved problem. Please optimize again calling XPRSmaxim (MAXIM), XPRSminim (MINIM) with the l flag or tuning presolve off by setting PRESOLVE to 0. If the operation does not need to be performed on an optimized problem just load the problem again.
264 Not enough spare matrix elements to remove all violations.: The Optimizer could not add more cuts to the matrix because there is not enough space. Please increase EXTRAELEMS before input to improve performance.
266 Cannot read basis for presolved problem. Re-input matrix.: The basis cannot be read because the problem in memory is the presolved one. Please reload the problem with XPRSreadprob (READPROB) and try to read the basis again.
268 Cannot perform operation on presolved matrix. Please postsolve or re-input matrix.: The problem in memory is the presolved one. Please postsolve or reload the problem and try the operation again.
279 The Optimizer has not been initialized.: The Optimizer could not be initialized successfully. Please initialize it before attempting any operation and try again.
287 Cannot read in directives after the problem has been presolved.: Directives cannot be read if the problem in memory is the presolved one. Please reload the problem and read the directives file .DIR before optimizing. Alternatively, re-optimize using the -l flag or set PRESOLVE to 0 and try again.
293 This license file does not specify the permitted problem size. Contact your vendor to obtain a valid license.: The license file is invalid as it doesn't specify the permitted problem size. Please contact your local sales office.
302 Option must be C/c or O/o.: The only valid options for the type of goals are C, c, O and o. Any other answer will be ignored.
305 Row <row> (number <num>) is an N row.: Only restrictive rows, i.e. G, L, R or E type, can be used in this type of goal programming. Please choose goal programming for objective functions when using N rows as goals.
306 Option must be MAX/max or MIN/min.: The only valid options for the optimization sense are MAX, max, MIN and min. Any other answer will be ignored.
307 Option must be P/p or D/d.: The only valid options for the type of relaxation on a goal are P, p, D and d. Any other answer will be ignored.
308 Row <row> (number <num>) is an unbounded goal.: Goal programming has found goal <row> to be unbounded and it will stop at this point. All goals with a lower priority than <row> will be ignored.
309 Row <row> (number <num>) is not an N row.: Only N type rows can be selected as goals for this goal programming type. Please use goal programming for constraints when using rows whose type is not N.
310 Option must be A/a or P/p.: The only valid options for the type of goal programming are A, a, P and p. Any other answer will be ignored.
314 Invalid number.: The input is not a number. Please check spelling and try again.
316 Not enough space to add deviational variables.: Increase EXTRACOLS before input. The Optimizer cannot find spare columns to spare deviational variables. Please try increasing EXTRACOLS before input to at least twice the number of constraint goals and try again.
318 Maximum number of allowed goals is 100.: Goal programming does not support more than 100 goals and will be interrupted.
319 No Optimizer license found. Please contact your vendor to obtain a license.: Your license does not authorize the direct use of the Optimizer. You probably have a license that authorizes other Xpress products, for example Mosel or BCL.
320 An internal error has occured. Please report to " SUPPORT_CONTACT_NAME " the circumstances under which this happened.: An internal error has occured. Please report to " SUPPORT_CONTACT_NAME " the circumstances under which this happened.
324 Not enough extra matrix elements to complete elimination phase.: Increase EXTRAPRESOLVE before input to improve performance. The elimination phase performed by the presolve procedure created extra matrix elements. If the number of such elements is larger than allowed by the EXTRAPRESOLVE parameter, the elimination phase will stop. Please increase EXTRAPRESOLVE before loading the problem to improve performance.
326 Linear Optimizer only: You are not authorized to use the Quadratic Programming Optimizer. Please contact your local sales office to discuss upgrading to the QP Optimizer if you wish to use this command.
352 Command not authorized in this version.: There has been an attempt to use a command for which your Optimizer is not authorized. Please contact your local sales office to upgrade your authorization if you wish to use this command.
361 QMATRIX or QUADOBJ section must be after COLUMN section.: Error in matrix file. Please make sure that the QMATRIX or QUADOBJ sections are after the COLUMNS section and try again.
362 Duplicate elements not allowed in QUADOBJ section.: The coefficient of a column appears more than once in the QUADOBJ section. Please make sure all columns have only one coefficient in this section.
363 Quadratic matrix must be symmetric in QMATRIX section.: Only symmetric matrices can be input in the QMATRIX section of the .MAT or .MPS file. Please correct and try again.
368 QSECTION second element in line ignored: <line>.: The second element in line <line> will be ignored.
381 Bug in lifting of cover inequalities.: Internal error. Please contact you local support office.
386 This version is not authorized to run Goal Programming.: The Optimizer you are using is not authorized to run Goal Programming. Please contact you local sales office to upgrade your authorization if you wish to use this command.
392 This version is not authorized to be called from BCL.: This version of the Optimizer cannot be called from the subroutine library BCL. Please contact your local sales office to upgrade your authorization if you wish to run the Optimizer from BCL.
394 Fatal communications error.: There has been a communication error between the master and the slave processes. Please check the network and try again.
395 This version is not authorized to be called from the Optimizer library.: This version of the Optimizer cannot be called from the Optimizer library. Please contact your local sales office to upgrade your authorization if you wish to run the Optimizer using the libraries.
401 Invalid row type passed to <function>.: Elements <num> of your array has invalid row type <type>. There has been an error in one of the arguments of function <function>. The row type corresponding to element <num> of the array is invalid. Please refer to the section corresponding to function <function> in Console and Library Functions for further information about the row types that can be used.
402 Invalid row number passed to <function>.: Row number <num> is invalid. There has been an error in one of the arguments of function <function>. The row number corresponding to element <num> of the array is invalid. Please make sure that the row numbers are not smaller than 0 and not larger than the total number of rows in the problem.
403 Invalid global entity passed to <function>.: Element <num> of your array has invalid entity type <type>. There has been an error in one of the arguments of function <function>. The column type <type> corresponding to element <num> of the array is invalid for a global entity.
404 Invalid set type passed to <function>.: Element <num> of your array has invalid set type <type>. There has been an error in one of the arguments of function <function>. The set type <type> corresponding to element <num> of the array is invalid for a set entity.
405 Invalid column number passed to <function>.: Column number <num> is invalid. There has been an error in one of the arguments of function <function>. The column number corresponding to element <num> of the array is invalid. Please make sure that the column numbers are not smaller than 0 and not larger than the total number of columns in the problem, COLS, minus 1. If the function being called is XPRSgetobj or XPRSchgobj a column number of -1 is valid and refers to the constant in the objective function.
406 Invalid row range passed to <function>.: Limit <lim> is out of range. There has been an error in one of the arguments of function <function>. The row numbers lie between 0 and the total number of rows of the problem. Limit <lim> is outside this range and therefore is not valid.
407 Invalid column range passed to <function>.: Limit <lim> is out of range. There has been an error in one of the arguments of function <function>. The column numbers lie between 0 and the total number of columns of the problem. Limit <lim> is outside this range and therefore is not valid.
409 Invalid directive passed to <function>.: Element <num> of your array has invalid directive <type>. There has been an error in one of the arguments of function <function>. The directive type <type> corresponding to element <num> of the array is invalid. Please refer to the Reference Manual for a list of valid directive types.
410 Invalid row basis type passed to <function>.: Element <num> of your array has invalid row basis type <type>. There has been an error in one of the arguments of function <function>. The row basis type corresponding to element <num> of the array is invalid.
411 Invalid column basis type passed to <function>.: Element <num> of your array has invalid column basis type <type>. There has been an error in one of the arguments of function <function>. The column basis type corresponding to element <num> of the array is invalid.
412 Invalid parameter number passed to <function>.: Parameter number <num> is out of range. LP or MIP parameters and controls can be used in functions by passing the parameter or control name as the first argument or by passing an associated number. In this case number <num> is an invalid argument for function <function> because it does not correspond to an existing parameter or control. If you are passing a number as the first argument, please substitute it with the name of the parameter or control whose value you wish to set or get. If you are already passing the parameter or control name, please check Console and Library Functions to make sure that is valid for function <function>.
413 Not enough spare rows in <function>.: Increase EXTRAROWS before input. There are not enough spare rows to complete function <function> successfully. Please increase EXTRAROWS before XPRSreadprob (READPROB) and try again.
414 Not enough spare columns in <function>.: Increase EXTRACOLS before input. There are not enough spare columns to complete function <function> successfully. Please increase EXTRACOLS before XPRSreadprob (READPROB) and try again.
415 Not enough spare matrix elements in <function>.: Increase EXTRAELEMS before input. There are not enough spare matrix elements to complete function <function> successfully. Please increase EXTRAELEMS before XPRSreadprob (READPROB) and try again.
416 Invalid bound type passed to <function>.: Element <elem> of your array has invalid bound type <type>. There has been an error in one of the arguments of function <function>. The bound type <type> of element number <num> of the array is invalid.
417 Invalid complement flag passed to <function>. Element <elem> of your array has invalid complement flag <flag>.: Element <elem> of your array has an invalid complement flag <flag>. There has been an error in one of the arguments of function <function>. The complement flag corresponding to indicator constraint <num> of the array is invalid.
418 Invalid cut number passed to <function>.: Element <num1> of your array has invalid cut number <num2>. Element number <num1> of your array contains a cut which is not stored in the cut pool. Please check that <num2> is a valid cut number.
419 Not enough space to store cuts in <function>.: There is not enough space to complete function <function> successfully.
420 Too many saved matrices in savmat: Version 12 compatibility interface only. There is a hard limit of at most 64 matrices that can be saved with savmat or cpymat
421 Matrix no. <mat> has not been saved. Cannot restore in resmat: Version 12 compatibility interface only. No matrix with number <mat> has been saved with savmat or cpymat.
422 Solution is not available.: There is no solution available. This could be because the problem in memory has been changed or optimization has not been performed. Please optimize and try again.
423 Duplicate rows/columns passed to <function>.: Element <elem> of your array has duplicate row/col number <num>. There has been an error in one of the arguments of function <function>. The element number <elem> of the argument array is a row or column whose sequence number <num> is repeated.
424 Not enough space to store cuts in <function>.: There is not enough space to complete function <function> successfully.
425 Column already basic.: The column cannot be pivoted into the basis since it is already basic. Please make sure the variable is non-basic before pivoting it into the basis.
426 Column not eligible to leave basis.: The column cannot be chosen to leave the basis since it is already non-basic. Please make sure the variable is basic before forcing it to leave the basis.
427 Invalid column type passed to <function>.: Element <num> of your array has invalid column type <type>. There has been an error in one of the arguments of function <function>. The column type <type> corresponding to element <num> of the array is invalid.
429 No basis is available.: No basis is available.
430 Column types cannot be changed during the global search.: The Optimizer does not allow changes to the column type while the global search is in progress. Please call this function before starting the global search or after the global search has been completed. You can call XPRSmaxim (MAXIM) or XPRSminim (MINIM) with the l flag if you do not want to start the global search automatically after finding the LP solution of a problem with global entities.
434 Invalid name passed to XPRSgetindex.: A name has been passed to XPRSgetindex which is not the name of a row or column in the matrix.
436 Cannot trace infeasibilities when integer presolve is turned on.: Try XPRSmaxim (XPRSmaxim) / XPRSminim (MINIM) with the l flag. Integer presolve can set upper or lower bounds imposed by the column type as well as those created by the interaction of the problem constraints. The infeasibility tracing facility can only explain infeasibilities due to problem constraints.
459 Not enough memory for branch and bound tree Not enough resources for branch and bound tree (<type>) Failure locking branch and bound tree (probably out of memory) Failure in handling of branch and bound tree (<type>): Functions to signal that an unexpected error happened during the management of the branch-and-bound tree for storing information from a global solve. The string <type> will provide more information about the particular failure. These errors are typical of running out of memory.
473 Row classification not available.
474 Column passed to <routine> has inconsistent bounds. See column <index> of <count>.: The bounds are inconsistent for column <index> of the <count> columns passed into routine <routine>.
475 Inconsistent bounds [<lb>,<ub>] for column <column name> in call to <routine>.: The lower bound <lb> is greater than the upper bound <ub> in the bound pair given for column <column name> passed into routine <routine>.
476 Unable to round bounds [<lb>,<ub>] for integral column <column name> in call to <routine>.: Either the lower bound <lb> is greater than the upper bound <ub> in the bound pair given for the integer column <column name> passed into routine <routine> or the interval defined by <lb> and <ub> does not contain an integer value.
501 Error at <line> Empty file.: Read aborted. The Optimizer cannot read the problem because the file is empty.
502 Warning: 'min' or 'max' not found at <line.col>. No objective assumed.: An objective function specifier has not been found at column <col>, line <line> of the LP file. If you wish to specify an objective function please make sure that 'max', 'maximize', 'maximum', 'min', 'minimize' or 'minimum' appear.
503 Objective not correctly formed at <line.col>. Aborting.: The Optimizer has aborted the reading of the problem because the objective specified at line <line> of the LP file is incorrect.
504 No keyword or empty problem at <line.col>.: There is an error in column <col> at line <line> of the LP file. Neither 'Subject to', 'subject to:', 'subject to', 'such that' 's.t.', or 'st' can be found. Please correct and try again.
505 A keyword was expected at <line.col>.: A keyword was expected in column <col> at line <line> pf the LP file. Please correct and try again.
506 The constraint at <line.col> has no term.: A variable name is expected at line <line> column <col>: either an invalid character (like '+' or a digit) was encountered or the identifier provided is unknown (new variable names are declared in constraint section only).
507 RHS at <line.col> is not a constant number.: Line <line> of the LP file will be ignored since the right hand side is not a constant.
508 The constraint at <line> has no term.: The LP file contains a constraint with no terms.
509 The type of the constraint at <line.col> has not been specified.: The constraint defined in column <col> at line <line> of the LP file is not a constant and will be ignored.
510 Upper bound at <line.col> is not a numeric constant.: The upper bound declared in column <col> at line <line> of the LP file is not a constant and will be ignored.
511 Bound at <line.col> is not a numeric constant.: The bound declared in column <col> at line <line> of the LP file is not a constant and will be ignored.
512 Unknown word starting with an 'f' at <line.col>. Treated as 'free'.: A word starting with an 'f' and not known to the Optimizer has been found in column <col> at line <line> of the LP file. The word will be read into the Optimizer as 'free'.
513 Wrong bound statement at <line.col>.: The bound statement in column <col> at line <line> is invalid and will be ignored.
514 Lower bound at <line.col> is not a numeric constant. Treated as -inf.: The lower bound declared in column <col> at line <line> of the LP file is not a constant. It will be translated into the Optimizer as the lowest possible bound.
515 Sign '<' expected at <line.col>.: A character other than the expected sign '<' has been found in column <col> at line <line> of the LP file. This line will be ignored.
516 Problem has not been loaded.: The problem could not be loaded into the Optimizer. Please check the other error messages appearing with this message for more information.
517 Row names have not been loaded.: The name of the rows could not be loaded into the Optimizer. Please check the other error messages appearing with this message for more information.
518 Column names have not been loaded.: The name of the columns could not be loaded into the Optimizer. Please check the other error messages appearing with this message for more information.
519 Not enough memory at <line.col>.: The information in column <col> at line <line> of the LP file cannot be read because all the allocated memory has already been used. Please increase your virtual page space or physical memory and try again.
520 Unexpected EOF at <line.col>.: An unexpected EOF marker character has been found at line <line> of the LP file and the loading of the problem into the Optimizer has been aborted. Please correct and try again.
521 Number expected for exponent at <line.col>.: The entry in column <col> at line <line> of the LP file is not a properly expressed real number and will be ignored.
522 Line <line> too long (length>255).: Line <line> of the LP file is too long and the loading of the problem into the Optimizer has been aborted. Please check that the length of the lines is less than 255 and try again.
523 The Optimizer cannot reach line <line.col>.: The reading of the LP file has failed due to an internal problem. Please contact your local support office.
524 Constraints could not be read into the Optimizer. Error found at <line.col>.: The reading of the LP constraints has failed due to an internal problem. Please contact your local support office.
525 Bounds could not be set into the Optimizer. Error found at <line.col>.: The setting of the LP bounds has failed due to an internal problem. Please contact your local support office.
526 LP problem could not be loaded into the Optimizer. Error found at <line.col>.: The reading of the LP file has failed due to an internal problem. Please contact your local support office.
527 Copying of rows unsuccessful.: The copying of the LP rows has failed due to an internal problem. Please contact your local support office.
528 Copying of columns unsuccessful.: The copying of the LP columns has failed due to an internal problem. Please contact your local support office.
529 Redefinition of constraint at <line.col>.: A constraint is redefined in column <col> at line <line> of the LP file. This repeated definition is ignored.
530 Name too long. Truncating it.: The LP file contains an identifier longer than 64 characters: it will be truncated to respect the maximum size.
531 Sign '>' expected here <line>.: A greater than sign was expected in the LP file.
532 Quadratic term expected here <pos>: The LP file reader expected to read a quadratic term at position <pos>: a variable name and '^2' or the product of two variables. Please check the quadratic part of the objective in the LP file.
533 Wrong exponent value. Treated as 2 <pos>: The LP file reader encountered an exponent different than 2 at position <pos>. Such exponents are automatically replaced by 2.
535 A constraint name was expected here.: The LP file reader expected to read a row name in the ranges section.
536 Wrong range statement at <pos>.: The LP file reader expected to read a range type in the ranges section.
538 Error when loading the SOS names: The LP format file reader failed to create the SOS names. The previous error should explain why this failed.
539 Invalid indicator constraint condition at <line.col>: The condition part in column <col> of the indicator constraint at line <line> is invalid.
545 A variable name was found but ignored at <pos> due to not appearing before.: The LP file reader read a variable in bounds or integer type sections that does not appear in the matrix.
552 'S1|2:' expected here. Skipping <pos>: Unknown set type read while reading the LP file at position <pos>. Please use set type 'S1' or 'S2'.
553 This set has no member. Ignoring it <pos>: An empty set encountered while reading the LP file at position <pos>. The set has been ignored.
554 Weight expected here. Skipping <pos>: A missing weight encountered while reading sets in the LP file at position <pos>. Please check definitions of the sets in the file.
555 Cannot presolve cut with PRESOLVEOPS bits 0, 5 or 8 set or bit 11 cleared.: Can not presolve cut with PRESOLVEOPS bits 0, 5 or 8 set or bit 11 cleared.
No cuts can be presolved if the following presolve options are turned on:
bit 0: singleton column removal,
bit 5: duplicate column removal,
bit 8: variable eliminations
or if the option
bit 11: No advanced IP reductions is turned off. Please check the presolve settings.
557 Integer solution is not available: Failed to retrieve an integer solution because no integer solution has been identified yet.
558 Column <col> duplicated in basis file - new entry ignored.: Column <col> is defined in the basis file more than once. Any repeated definitions are ignored.
559 The old feature <feature> is no longer supported: The feature <feature> is no longer supported and has been removed. Please contact Xpress support for help about replacement functionality.
602 Values must be specified for all columns when column indices are not provided.: In a call to XPRSaddmipsol the column index array is optional. When this argument is omitted (given as NULL), the length of the solution value array must match ORIGINALCOLS.
604 String passed as parameter is too long: The file name passed to XPRSsetlogfile can be at most 200 characters long.
606 Failed to parse list of diving heuristic strategies at position <pos>: Invalid diving heuristic strategy number provided in position <pos> of the string controls HEURDIVEUSE or HEURDIVETEST. Please check control HEURDIVESTRATEGY for valid strategy numbers.
706 Not enough memory to add sets.: Insufficient memory while allocating memory for the new sets. Please free up some memory, and try again.
707 Function can not be called during the global search: The function being called cannot be used during the global search. Please call the function before starting the global search.
708 Invalid input passed to <function> Must specify mstart or mnel when creating matrix with columns: No column information is available when calling function <function>. If no columns were meant to be passed to the function, then please set the column number to zero. Note, that mstart and mnel should be set up for empty columns as well.
710 MIPTOL <val1> must not be less than FEASTOL <val2>: The integer tolerance MIPTOL (val1) should not be set tighter than the feasibility tolerance FEASTOL (val2). Please increase MIPTOL or decrease FEASTOL.
711 MIPTOL <val1> must not be less than FEASTOL <val2>. Adjusting MIPTOL: The integer tolerance MIPTOL (val1) must not be tighter than the feasibility tolerance FEASTOL (val2). The value of MIPTOL has been increased to (val2) for the global search.
712 Function not permitted when problem is presolved: <func>%s: The problem is currently in a presolved state and the function <func> can only be called when the problem is in its original state. XPRSpostsolve can be called to return the problem to its original state.
713 <row/column> index out of bounds calling <function>. <index1> is '<' or '>' <bound>: An index is out of its bounds when calling function <function>. Please check the indices.
715 Invalid objective sense passed to <function>. Must be XPRS_OBJ_MINIMIZE or XPRS_OBJ_MAXIMIZE.: Invalid objective sense was passed to function <function>. Please use either XPRS_OBJ_MINIMIZE or XPRS_OBJ_MAXIMIZE.
716 Invalid names type passed to XPRSgetnamelist. Type code <num> is unrecognized.: An invalid name type was passed to XPRSgetnamelist.
717 Generic error.: Used to promote license manager errors.
721 No IIS has been identified yet: No irreducible infeasible set (IIS) has been found yet. Before running the function, please use IIS -f, IIS -n or IIS -a to identify an IIS.
722 IIS number <num> is not yet identified: Irreducible infeasible set (IIS) with number <num> is not available. The number <num> stands for the ordinal number of the IIS. The value of <num> should not be larger than NUMIIS.
723 Unable to create an IIS sub-problem: The irreducible infeasible set (IIS) procedure is unable to create the IIS approximation. Please check that there is enough free memory.
724 Error while optimizing the IIS sub-problem: An error occurred while minimizing an irreducible infeasible set (IIS) sub-problem. Please check the return code set by the Optimizer.
725 Problems with variables for which shift infeasibilities cannot be removed are considered infeasible in the IIS: The irreducible infeasible set (IIS) sub-problem being solved by the IIS procedure is on the boundary of being feasible or infeasible. For problems that are only very slightly infeasible, the Optimizer applies a technique called infeasibility shifting to produce a solution. Such solutions are considered feasible, although if solved as a separate problem, a warning message is given. For consistency reasons however, in the case of the IIS procedure such problems are treated as being infeasible.
726 This function is not valid for the IIS approximation. Please specify an IIS with count number > 0: Irreducible infeasible set (IIS) number 0 (the ordinal number of the IIS) refers to the IIS approximation, but the functionality called is not available for the IIS approximation. Please use an IIS number between 1 and NUMIIS.
727 Bound conflict on column <col>; IIS will not continue: There is a bound conflict on column <col>. Please check the bounds on the column, and remove any conflicts before running the irreducible infeasible set (IIS) procedure again (bound conflicts are trivial IISs by themselves).
728 Unknown file type specification <type>: Unknown file type was passed to the irreducible infeasible set (IIS) sub-problem writer. Please refer to XPRSiiswrite for the valid file types.
729 Writing the IIS failed: Failed to write the irreducible infeasible set (IIS) sub-problem or the comma separated file (.csv) containing the IIS information to disk. Please check access permissions.
730 Failed to retrieve data for IIS <num>: The irreducible infeasible set (IIS) procedure failed to retrieve the internal description for IIS number <num>. This may be an internal error, please contact your local support office.
731 IIS stability error: reduced or modified problem appears feasible: Some problems are on the boundary of being feasible or infeasible. For such problems, it may happen that the irreducible infeasible set (IIS) working problem becomes feasible unexpectedly. If the problem persists, please contact your local support office.
732 Unknown parameter or wrong parameter combination: The wrong parameter or parameter combination was used when calling the irreducible infeasible set (IIS) console command. Please refer to the IIS command documentation for possible combinations.
733 Filename parameter missing: No filename is provided for the IIS -w or IIS -e console command. Please provide a file name that should contain the irreducible infeasible set (IIS) information.
734 Problem data relevant to IISs is changed: This failure is due to the problem being changed between iterative calls to IIS functions. Please start the IIS analysis from the beginning.
735 IIS function aborted: The irreducible infeasible set (IIS) procedure was aborted by either hitting CTRL-C or by reaching a time limit.
736 Initial infeasible subproblem is not available. Run IIS -f to set it up: The initial infeasible subproblem requested is not available. Please use the IIS -f function to generate it.
738 The approximation may be inaccurate. Please use IIS or IIS -n instead.: The irreducible infeasible set (IIS) procedure was run with the option of generating the approximation of an IIS only. However, ambiguous duals or reduces costs are present in the initial infeasible subproblem. This message is always preceded by warning 737. Please continue with generating IISs to resolve the ambiguities.
739 Bound conflict on column <col>; Repairinfeas will not continue: There is a bound conflict on column <col>. Please check the bounds on the column, and remove any conflicts before running the XPRSrepairinfeas procedure again (bound conflicts are trivial causes of infeasibility).
740 Unable to create relaxed problem: The Optimizer is unable to create the relaxed problem. The relaxed problem may require significantly more memory than the base problem if many of the preferences are set to a positive value. Please check that there is enough free memory.
741 Relaxed problem is infeasible. Please increase freedom by introducing new nonzero preferences: The relaxed problem remains infeasible. Zero preference values indicate constraints (or bounds) that will not be relaxed. Try introducing new nonzero preferences to allow the problem to become feasible.
742 Repairinfeas stability error: relaxed problem is infeasible. You may want to increase the value of delta: The relaxed problem is reported to be infeasible by the Optimizer in the second phase of the repairinfeas procedure. Try increasing the value of the parameter delta to improve stability.
743 Optimization aborted, repairinfeas unfinished: The optimization was aborted by CTRL-C or by hitting a time limit. The relaxed solution is not available.
744 Optimization aborted, MIP solution may be sub-optimal: The MIP optimization was aborted by either CTRL-C or by hitting a time limit. The relaxed solution may not be optimal.
745 Optimization of the relaxed problem is sub-optimal: The relaxed solution may not be optimal due to early termination.
746 All preferences are zero, repairinfeas will not continue Use options -a -b -r -lbp -ubp -lrp or -grp to add nonzero preferences: Zero preference values indicate constraints (or bounds) that will not be relaxed. In case when all preferences are zero, the problem cannot be relaxed at all. Try introducing nonzero preferences and run XPRSrepairinfeas again.
748 Negative preference given for a <sense> bound on <row/column> <name>: A negative preference value is set for constraint or bound <name>. Preference values should be non-negative. The preferences describe the modeler's willingness to relax a given constraint or bound, with zero preferences interpreted as the corresponding constraints or bounds not being allowed to be relaxed. Please provide a zero preference if the constraint or bound is not meant to be relaxed. Also note, that very small preferences lead to very large penalty values, and thus may increase the numerical difficulty of the problem.
749 Relaxed problem is infeasible due to cutoff: A user defined cutoff value makes the relaxed problem infeasible. Please check the cutoff value CURRMIPCUTOFF.
750 Empty matrix file : <name>: The MPS file <name> is empty. Please check the name of the file and the file itself.
751 Invalid column marker type found : <text>: The marker type <text> is not supported by the MPS reader. Please refer to the Appendix XMPS Matrix Files for supported marker types.
752 Invalid floating point value : <text>: The reader is unable to interpret the string <text> as a numerical value.
753 <num> lines ignored: The MPS reader has ignored <num> number of lines. This may happen for example if an unidentified section was found (in which case warning 785 is also invoked).
754 Insufficient memory: Insufficient memory was available while reading in an MPS file.
755 Column name is missing: A column name field was expected while reading an mps file. Please add a column name to the row. If the MPSFORMAT control is set to 0 (fixed format) then please check that the name field contains a column name, and is positioned correctly.
756 Row name is missing in section OBJNAME: No row name is provided in the OBJNAME section. If no user defined objective name is provided, the reader uses the first neutral row (if any) as the objective row. However, to avoid ambiguity, if no user defined objective row was meant to be supplied, then please exclude the OBJNAME section from the MPS file.
757 Missing objective sense in section OBJSENSE: No objective sense is provided in section OBJSENSE. If no user defined objective sense is provided, the reader sets the objective sense to minimization by default. However, to avoid ambiguity, if no user defined objective sense was meant to be supplied, then please exclude the OBJSENSE section from the MPS file.
758 No SETS and SOS sections are allowed in the same file: The Optimizer expects special order sets to be defined in the SETS section. However, for compatibility considerations, the Optimizer can also interpret the SOS section. The two formats differ only in syntax, and feature the same expressive power. Both a SETS and a SOS section are not expected to be present in the same matrix file.
759 File not in fixed format : <file>: The Optimizer control MPSFORMAT was set to 0 to indicate that the mps file <file> being read is in fixed format, but it violates the MPS field specifications.
760 Objective row <row> defined in section OBJNAME or in MPSOBJNAME was not found: The user supplied objective row <row> is not found in the MPS file. If the MPS file contains an OBJNAME section please check the row name provided, otherwise please check the value of the control MPSOBJNAME.
761 Problem name is not provided: The NAME section is present in the MPS file, but contains no problem name (not even blanks), and the MPSFORMAT control is set to 0 (fixed format) preventing the reader to look for the problem name in the next line. Please make sure that a problem name is present, or if it's positioned in the next line (in which case the first column in the line should be a whitespace) then please set MPSFORMAT to 1 (free format) or -1 (autodetect format).
762 Missing problem name in section NAME: Unexpected end of file while looking for the problem name in section NAME. The file is likely to be corrupted. Please check the file.
763 Ignoring range value for free row : <row>: A range value is defined for free row <row>. Range values have no effect on free rows. Please make sure that the type of the row in the ROWS section and the row name in the RANGE section are both correct.
764 <sec> section is not yet supported in an MPS file, skipping section: The section <sec> is not allowed in an MPS file. Sections like "SOLUTION" and "BASIS" must appear in separate ".slx" and ".bas" files.
765 Ignoring repeated specification for column : <col>: Column <col> is defined more than once in the MPS file. Any repeated definitions are ignored. Please make sure to use unique column names. If the column names are unique, then please make sure that the COLUMNS section is organized in a contiguous order.
766 Ignoring repeated coefficients for row <row> found in RANGE <range>: The range value for row <row> in range vector <range> in the RANGE section is defined more than once. Any repeated definitions are ignored. Please make sure that the row names in the RANGE section are correct.
767 Ignoring repeated coefficients for row <row> found in RHS <rhs>: The value for row <row> in right hand side vector <rhs> is defined more than once in the RHS section. Any repeated definitions are ignored. Please make sure that the row names in the RHS section are correct.
768 Ignoring repeated specification for row : lt;rowgt;: Row <row> is defined more than once in the MPS file. Any repeated definitions are ignored. Please make sure to use unique row names.
770 Missing prerequisite section <sec1> for section <sec2>: Section <sec2> must be defined before section <sec1> in the MPS file being read. Please check the order of the sections.
771 Unable to open file : <file>: Please make sure that file <file> exists and is not locked.
772 Unexpected column type : <type> : <column>: The COLUMNS section contains the unknown column type <type>. If the MPSFORMAT control is set to 0 (fixed format) then please make sure that the type of the column is correct and positioned properly.
773 Unexpected number of fields in section : <sec>: Unexpected number of fields was read by the reader in section <sec>. Please check the format of the line. If the MPSFORMAT control is set to 0 (fixed format) then please make sure that the fields are positioned correctly. This error is often caused by names containing spaces in free format, or by name containing spaces in fixed format but positioned incorrectly.
774 Unexpected row type : <type>: The ROWS section contains the unknown row type <type>. If the MPSFORMAT control is set to 0 (fixed format) then please make sure that the type of the row is correct and positioned properly.
775 Unexpected set type : <type>: The SETS or SOS section contains the unknown set type <type>. If the MPSFORMAT control is set to 0 (fixed format) then please make sure that the type of the row is correct and positioned properly.
776 Ignoring unknown column name <col> found in BOUNDS: Column <col> found in the BOUNDS section is not defined in the COLUMNS section. Please check the name of the column.
777 Ignoring quadratic coefficient for unknown column : <col>: Column <col> found in the QUADOBJ section is not defined in the COLUMNS section. Please check the name of the column.
778 Ignoring unknown column name <col> found in set <set>: Column <col> found in the definition of set <set> in the SETS or SOS section is not defined in the COLUMNS section. Please check the name of the column.
779 Wrong objective sense: <sense>: The reader is unable to interpret the string <sense> in the OBJSENSE section as a valid objective sense. The objective sense should be either MAXIMIZE or MINIMIZE. The reader accepts sub-strings of these if they uniquely define the objective sense and are at least 3 characters long. Note that if no OBJSENSE section is present, the sense of the objective is set to minimization by default. Please provide a valid objective sense.
780 Ignoring unknown row name <row> found in column <column>: Row <row> found in the column <column> in the COLUMNS section is not defined in the ROWS section. Please check the name of the row.
781 Ignoring unknown row name <row> found in RANGE: Row <row> found in the RANGE section is not defined in the ROWS section. Please check the name of the row.
782 Ignoring unknown row name <row> found in RHS: Row <row> found in the RHS section is not defined in the ROWS section. Please check the name of the row.
783 Expecting numerical value: A numerical value field was expected while reading an MPS file. Please add the missing numerical entry. If the MPSFORMAT control is set to 0 (fixed format) then please check that the value field contains a numerical value and is positioned correctly.
784 Null char in text file: A null char ('\0') encountered in the MPS file. An MPS file is designed to be a text file and a null char indicates possible errors. Null chars are treated as spaces ' ' by the reader, but please check the origin of the null char.
785 Unrecognized section <sec> skipped: The section <sec> is not recognized as an MPS section. Please check the section identifier string in the MPS file. In such cases, the reader skips the whole section and continues reading.
786 Variable fixed above infinite tolerance limit <tol>. Bound ignored: A variable is marked as fixed in the MPS above (its absolute value) the tolerance limit of <tol>. The bound is ignored. Please check the bound and either remove it, or scale the corresponding column. Note that values close to the tolerance are accepted but may introduce numerical difficulties while solving the problem.
787 Empty set: <set>: No set members are defined for set <set> in the MPS file. Please check if the set is empty by intention.
788 Repeated definition of section <sec> ignored: Section <sec> is defined more than once in the mps file. Any repeated definitions are ignored. Many sections may include various versions of the described part if the problem (like different RHS values, BOUNDS or RANGES), but please include those in the same section.
790 Wrong section in the basis file: <section>: Unrecognized section <section> found in the basis file. Please check the format of the file.
791 ENDATA is missing. File is possibly corrupted: The ENDATA section is missing from the end of the file. This possible indicates that part of the file is missing. Please check the file.
792 Ignoring BS field: BS fields are not supported by the Optimizer, and are ignored. Basis files containing BS fields may be created by external software. Please convert BS fields to either XU or XL fields.
793 Superbasic variable outside bounds. Value moved to closest bound: A superbasic variable in the basis file are outside its bounds. The value of the variable has been modified to satisfy its bounds. Please check that the value in the basis file is correct. In case the variable should be set to the value given by the basis file, please modify the bounds on the variable.
794 Value of fixed binary column <col> changed to <val>: The lower and upper bound for binary variable <col> was to <val>. Binaries may only be fixed at level 0 or 1.
795 Xpress/Mosel extensions: number of opening and closing brackets mismatch: The LP file appears to be created by Mosel, using the Xpress MPS extensions to include variable names with whitespaces, however the file seems to be broken due to a mismatch in opening and closing brackets.
796 Char <c> is not supported in a name by file format. It may not be possible to read such files back correctly. Please set FORCEOUTPUT to 1 to write the file anyway, or use scrambled names.: Certain names in the problem object may be incompatible with different file formats (like names containing spaces for LP files). If the Optimizer might be unable to read back a problem because of non-standard names, it will give an error message and won't create the file. However, you may force output using control FORCEOUTPUT or change the names by using scrambled names (-s option for XPRSwriteprob).
797 Wrong section in the solution file: <sec>: Section <sec> is not supported in .slx MPS solution files.
798 Empty <type> file : <file>: File <file> of type <type> is empty.
799 Ignoring quadratic coefficients for unknown row name <row>: No row with name <row> was defined in the ROWS sections. All rows having a QCMATRIX section must be defined as a row with type 'L' or 'G' in the ROWS section.
835 Given solution column count does not match given problem: The given solution contains a different column count compared to the loaded problem.
843 Delayed row (lazy constraint) <row> is not allowed to be of type 'N'. Row ignored: Delayed rows cannot be neutral. Please define all neutral rows as ordinary ones in the ROWS section.
847 Model cut (user cut) <row> is not allowed to be of type 'N'. Row ignored: Model cuts cannot be neutral. Please define all neutral rows as ordinary ones in the ROWS section.
862 Quadratic constraint rows must be of type 'L' or 'G'. Wrong row type for row <row>: All quadratic rows must be of type 'L' or 'G' in the ROWS section of the MPS file (and the corresponding quadratic matrix be positive semi-definite).
863 The current version of the Optimizer does not yet support MIQCQP problems: The current version of the Optimizer does not yet support mixed integer quadratically constrained problems.
864 Quadratic constraint rows must be of type 'L' or 'G'. Wrong row type for row <row>: A library function was trying to define (or change to) a row with type 'L' having quadratic coefficients. All quadratic rows are required to be of type 'L' (and the corresponding quadratic matrix be positive semi-definite).
865 Row <row> is already quadratic: Cannot add quadratic constraint matrices together. To change an already existing matrix, either use the XPRSchgqrowcoeff library function, or delete the old matrix first.
866 The divider of the quadratic objective at <pos> must be 2 or omitted: The LP file format expects, tough may be omitted, an "/2" after the each quadratic objective term defined between square brackets. No other divider is accepted. The role of the "/2" is to notify the user of the implied division in the quadratic objective (that does not apply to quadratic constraints).
867 Not enough memory for tree search: There is not enough memory for one of the nodes in the tree search.
884 Fatal user error detected in callback: An error occurred during a user callback.
898 Cannot define range for quadratic rows. Range for row <row> ignored: Quadratic constraints are required to be convex, and thus it is not allowed to set a range on quadratic rows. Each quadratic row should have a type of 'L' or 'G'.
899 The quadratic objective is not convex. Set IFCHECKCONVEXITY=0 to disable check: The quadratic objective is not convex. Please check that the proper sense of optimization (minimization or maximization) is used.
900 The quadratic part of row <row> defines a non-convex region. Set IFCHECKCONVEXITY=0 to disable check.: The quadratic in <row> is not convex. Please check that the proper sense of constraint is defined (less or equal or greater or equal constraint).
901 901 Duplicated QCMATRIX section for row <row> ignored.: The MPS file may contain one Q matrix for each row. In case of duplicates, only the first is loaded into the matrix
902 Calling function <func> is not supported from the current context.: This XPRS function cannot be called from this callback.
903 Row <row> with right hand side value larger than infinity ignored.: The matrix file being read contains a right hand side that is larger than the predefined infinity constant XPRS_PLUSINFINITY. Row is made neutral.
904 Function is not allowed outside optnode callback.: The used function of the branching manager is not allowed to call outside optnode.
905 Bad index passed to function.: The index passed to function is not in range of the attribute.
906 Global entity cannot be branched further.: The selected global entity is fixed and cannot be branched further.
907 Column is continuous and cannot be branched.: The given column is of continuous type. The used function does not support branching on continuous columns.
909 Limit exceeded.: The limit of a certain object is exceeded.
910 Empty branch or branching object.: The given branch or branching object is empty.
911 Invalid information provided for branching object.: The given branching object contains invalid information.
912 Branching object(s) cannot be changed/used at this time.: The branching object is not fix yet. Hence, it cannot be changed/used.
913 Required data missing in function call for branching object.: Data is missing in function call for branching object.
914 Unexpected error triggered for branching object.: Unexpected error happened on a branching object.
915 Branching object (ID=<id>) rejected because it is empty or contains empty branches.: Improper branching object.
918 Module error.: Model can not be modified.
919 Column must be of type semi-continuous, semi-integer or partial integer to change its global bound.: The global bound can be modified only for semi-continuous, semi-integer or partial integer column.
920 Semi-continuous lower bound for column <column> must be non-negative.: Only non-negative lower bounds can be specified for semi-continuos columns.
921 Partial integer limit for column <column> is outside the allowed range of 0 to 2^28-1.: The give limit for the column is out of the allowed range.
932 Unknown column name <column> found in piecewise linear term.: One of the columns given in the PWLOBJ or PWLCON section of the MPS file was not defined in the COLUMNS section.
933 Breakpoints for piecewise linear constraint <index> not sorted and contradicting points (<x>,<y1>) and (<x>,<y2>) given.: The breakpoints for this piecewise linear function were not given as a sorted list, and due to contradicting points this cannot be fixed by sorting (since it is unclear what the left- and right-limit of the discontinuity would be).
934 Breakpoints for piecewise linear constraint <index> not sorted, will be sorted internally.: The breakpoints for the piecewise linear function were not given as a sorted list, these will be reordered internally.
935 Piecewise linear breakpoints not given consecutively for variable <column>, will reorder them.: The breakpoints for this column were not given consecutively but with breakpoints for another variable in between, will be fixed internally.
936 Ignoring duplicate piecewise linear breakpoint (<x>,<y>) for piecewise linear constraint <index>.: The same breakpoint was given twice for this piecewise linear constrant, the second one will be dropped.
937 Piecewise linear section for column <column> contained at most one breakpoint.: The piecewise linear function over this column only contained a single breakpoint or no breakpoints at all, which is not enough to define the function.
938 Discontinuity at the <beginning/end> of piecewise linear constraint <index> without a matching bound.: The first or last two breakpoints of the piecewise linear function shared the same value for the input variable. While this is allowed to model discontinuous functions, it is only allowed for the first or last points if they match the corresponding bound and do not leave the function undefined before or after them.
939 Non-convex piecewise linear function with unbounded domain for column <column>, may lead to unbounded LP relaxation for reformulation even if MIP is bounded.: The piecewise linear function over the unbounded variable was non-convex and the sum of slopes for the lower and upper limit is negative, potentially leading to an unbounded LP relaxation for the reformulation even though the MIP might be bounded. Consider giving explicit bounds for this variable if possible.
940 General constraint type <type> for constraint <name> not supported, should be one of MAX, MIN, AND, OR, ABS, PWL: The general constraint <name> was assigned the type <type>, which is not supported. The type should be "MAX", "MIN", "AND", "OR", "ABS", or "PWL".
941 Entry <entry> of general constraint <name> neither a column nor a constant: One of the lines in general constraints section for constraint <name> consisted of <entry>, which is neither a column name nor a valid constant (and in case of free-format MPS-format also not a GENCONS-type).
942 <type> constraint <index> includes non-binary variable <name>. Only binaries allowed in AND/OR general constraints.: The <index>-th general constraint, which is either an "AND" or an "OR" constraint, includes variable <name> which is not binary.
943 The absolute value constraint <index> includes <number> variables. ABS-constraints should consist of exactly 2 variables.: The <index>-th general constraint, which is an "ABS" constraint, includes more than two variables.
944 The general constraint <index> consists of <number> elements. General constraints need to have at least two elements.: The <index>-th general constraint consists of less than two elements. All general constraints must include at least two elements ("abs" exactly two).
945 Error when loading the piecewise linear constraint names.: The LP format file reader failed to create the piecewise linear constraint names. The previous error should explain why this failed.
946 Error when loading the general constraint names.: The LP format file reader failed to create the general constraint names. The previous error should explain why this failed.
947 PWLCON section refers to piecewise linear constraint <name>, which was not defined in the PWLNAM section.: In the MPS format, all piecewise linear constraints must first be defined in the PWLNAM section before adding extreme points in the PWLCON section.
948 Missing bracket or comma in piecewise linear function or general constraint: Piecewise linear functions should be given as (<val1>, <val2>), general constraints as <keyword> (<col1>, <col2>, ..., <colk>). In this case one of the commas or brackets was missing.
949 Invalid piecewise linear constraint number passed to <function>.Piecewise linear constraint number <val1> is invalid <val2>: There has been an error in one of the arguments of function <function>. The <val1>th given piecewise linear constraint number <val2> is invalid. Please make sure that the piecewise linear constraint numbers are not smaller than 0 and not larger than the total number of piecewise linear constraints in the current problem, given by attribute PWLCONS.
950 Invalid general constraint number passed to <function>. <val1>-th General constraint number <val2> is invalid: There has been an error in one of the arguments of function <function>. The <val1>-th given general constraint number <val2> is invalid. Please make sure that the general constraint numbers are not smaller than 0 and not larger than the total number of general constraints in the current problem, given by attribute GENCONS.
951 Input column or resultant of <name> deleted, piecewise linear constraint is also dropped: An <XPRSdelcols> call left the piecewise linear constraint <name> without input column or without resultant. Thus the piecewise linear constraint is dropped.
952 Column deletion left <name> with no resultant or no inputs, general constraint is also dropped: An <XPRSdelcols> call left the general constraint <name> without resultant or without any inputs (either columns or constant values in case of <MIN>/<MAX>). Thus the general constraint is dropped.
953 Column <index> appears as both resultant and input variable in piecewise linear/general constraint <index>.: The resultant of the piecewise linear or general constraint is equal to one of the input columns. These need to be distinct.
953 __pwlobj() appearing outside of objective.: The keyword __pwlobj(<col>) may be used inside the linear objective function to declare that the objective contribution of this variable will later be defined in the pwlobj section, but it should never appear in any other section.
1001 Solution value redefined for column: <col>: <val1> -> <val2>: Multiple definition of variable <col> is not allowed. Please use separate SOLUTION sections to define multiple solutions.
1002 Missing solution values in section <sec>. Only <val1> of <val2> defined: Not all values were defined in the SOLUTIONS section. Variables with undefined values are set to 0.
1003 Please postsolve the problem first with XPRSpostsolve (postsolve).: Not all values were defined in the SOLUTIONS section. Variables with undefined values are set to 0.
1004 Negative semi-continuous lower bound (<val>) for column <col> replaced with zero: Wrong input parameter for the lower bound of a semi-continuous variable was modified to 0.
1005 Unrecognized column name : <col>: No column with name <col> is present in the problem object while loading solution.
1006 Failed to capture solution information.: Solution information is not available.
1020 Function <function> cannot be called here.: The specified function can not be called.
1022 Error (<error>) while trying to run branching script.: Branching script error.
1028 Unable to keep branch and bound tree memory usage below <val>Gb - currently using <val>Gb;: The Optimizer was unable to keep the tree memory usage below the limit defined by the TREEMEMORYLIMIT control - the solve will continue but performance will be impaired.
1030 Duplicate names are not allowed - row/column/set/constraint <row1> would have same name as row/column/set/constraint <row2>.: Each row, column, special ordered set, piecewise linear constraint and general constraint should have unique name.
1034 Unknown column name <col> found in indicators: Columns <col> found in the INDICATORS section is not defined in the COLUMNS section. Please check the name of the column.
1035 Unknown row name <row> found in indicators: Row <row> found in the INDICATORS section is not defined in the ROWS section. Please check the name of the row.
1036 Unexpected indicator type : <type>: Indicator type <type> found in the INDICATORS section is invalid. The type should be 'IF'.
1037 Unexpected indicator active value : <value> for row <row>: The value <value> found in the INDICATORS section is invalid. Values in this section should be either 0 and 1.
1038 Unsupported row type for indicator constraint <row>: Rows configured as indicator constraints should have a type of 'L' or 'G'.
1039 Non-binary variable <col> used as an indicator binary: The variable used in the condition part of an indicator constraint should be of type binary.
1054 Please use the FICO-SLP solver for general nonlinear problems. Contact " LICENSING_CONTACT_NAME " for a license.: To solve general nonlinear problems the FICO-SLP solver can be used.
1055 Can not resume global search - not currently solving a MIP.: The global search can not be resumed, the current problem is not mixed integer optimization.
1059 Unrecognized string identifier <id> passed to function <func>: The string <id> given as input to the function <func> does not match any expected identifiers. Double-check spelling of <id> and consult documentation of function <func>, if available.
1071 Unable to dualize problems with quadratic coefficients: The current version of the Optimizer only supports dualization of linear problems. Remove quadratic terms.
1074 Could not write tree to global file.: Branch-and-bound tree memory saving is disabled; re-enable this feature to allow the tree to be compressed and saved to the global file.
1075 Message too long: message <mes> must be shorter than <maxlen> characters: Could not write an error/info/warning message, due to a problem, row, column or set name being too long. Shorten all names s.t. they consist of at most <maxlen> characters.
1082 Tree heap create failed.: Failed to create private heap for branch-and-bound tree; probably due to insufficient memory. If possible, try to free up memory on your system, reduce the problem size or set appropriate working limits.
1090 No license capacity.: The FICO Xpress license file does not specify an Optimizer capacity; license has been incorrectly generated, please contact support@fico.com .
1091 User cuts not allowed: User cuts are not accessible in the tree when in-tree presolving is turned on. Deactivate in-tree presolving by setting TREEPRESOLVE to 0.
1092 Invalid scale factor: An invalid scale factor was given for a row or a column. Scale factors are provided as the exponents of powers of two, and must be between 0 and MAXSCALEFACTOR
1093 Column scaling not allowed.: Scaling of binary, integer and partial integer columns is not allowed.
1094 Invalid SOCP constraint detected.: The Optimizer has detected an invalid SOCP constraint: a quadratic row has incorrectly been identified as a second order cone. Please contact support.
1097 The dependent variable of row (e.g. variable z in z²≥x² + y²) must be defined non-negative, otherwise the constraint is non-convex.: The problem is not formulated in a standard second order conic formulation.
1098 Both dependent variables of row (e.g. variables u and v in u*v≥x²+y²) must be defined non-negative.: The problem is not formulated in a standard second order conic formulation.
1100 Cut limit reached: Failed to create cut, since the limit of storable cuts was reached. Please restart your solve with a less aggressive cutting strategy.
1101 Cannot call optimization routine recursively: You cannot call XPRSglobal, XPRSminim or XPRSmaxim within a call of XPRSglobal, XPRSminim or XPRSmaxim on the same problem pointer. Either terminate the running optimization process or use a separate problem pointer. See also error code 1101.
1102 Presolve detected infeasibility on non-convex quadratic row: All quadratic matrices in the quadratic constraints must be positive semi-definite or a second-order cone.
1103 Insufficient name buffer: The supplied name buffer is too small. Allocate more memory for the buffer or use shorter names.
1104 No row/column/set names: Tried to access a group of names that do not exist. Provide names to columns/rows/sets before doing so.
9999 Generic error message: Please contact support@fico.com.

© 2001-2020 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.

Contents

Index

Glossary

Search Results

Optimizer Error and Warning Messages