Initializing help system before first use

# Error codes

Topics covered in this chapter:

- MIP Solution Pool errors
- MIP Solution Enumerator errors

Following an error exit from a function call to the MIP solution pool or the MIP solution enumerator library users may access the error code and a short string description of the error using the functions XPRS_msp_getlasterror or XPRS_mse_getlasterror. The following sections list the error codes returned by calls to the MIP solution pool and MIP solution enumerator functions. The main Optimizer Reference manual contains the list of error codes returned by the rest of the API.

## MIP Solution Pool errors

800 First index outside bounds: <col_index> not in [0,<num_cols> - 1]

  The index col_index of the first column passed to XPRS_msp_getsol is outside the range [0, <num_cols> - 1]

801 First index greater than last

  The index of the first column passed to XPRS_msp_getsol is greater than the index of the last column.

802 Attempt to attach problem more than one XPRSmipsolpool: Attach failed

  A problem cannot be attached to more than one MIP solution pool.

804 Unable to check if loaded sol is dupld: No MIP model avail

  A check if the solution being loaded is a duplicate of an existing solution cannot be made since no MIP model is available. No model is available because no problem has been attached to the MIP solution pool.

805 Unable to check if loaded sol is dupld: Memory allocation failure

  A check if the solution being loaded is a duplicate of an existing solution failed because of a memory allocation failure.

806 Unable to check if loaded sol is dupld: Incompat src prob

  A check if the solution being loaded is a duplicate of an existing solution cannot be made because the problem from which the solution originates does not match the MIP model used for duplicate checking.

807 Unable to check if loaded sol is dupld: MIP model unreliable

  A check if the solution being loaded is a duplicate of an existing solution cannot be made because a required update of the MIP model could not be made reliably.

808 Unable to check if loaded sol is dupld: MIP model reqd but inaccessible

  A check if the solution being loaded is a duplicate of an existing solution cannot be made because a required update of the MIP model could not be made.

809 Duplicate sol chck may not work: MIP model inaccessible in attaching prob

  A check if the solution being loaded is a duplicate of an existing solution cannot be made because a required capture of the MIP model could not be made from the problem being attached.

810 Destroying XPRSmipsolpool with problems still attached: Probs detached automatically

  The MIP solution pool is being destroyed and problems are still attached. This should be ok although the user should be aware. This message can be avoided by detaching the attached problems before destroying the MIP solution pool.

812 Compl duplicate sol chck: Failed

  A reset operation for the duplicate solution information failed. The duplicate solution checking may now not work reliably.

814 Failed to capture solution information

  Failure calculating the information for a solution with respect to a problem.

815 Failed to generate solution check sum

  A check of the problem state information failed when trying to calculate a check sum.

816 Failed to capture solution

  An unexpected failure when attempting to capture a solution.

817 Failure in internal event registration

  An object failed to register to receive system events.

818 Failure in internal event deregistration

  An object failed to deregister the receipt of system events.

821 Unrecoverable memory allocation failure

  A call made by the user failed because of a memory allocation failure.

822 Recoverable memory allocation failure: <operation_attempted>

  A memory allocation failed when attempting the operation < operation_attempted >. The system may still continue to function normally.

826 Soln col count does not match prob: <prob_id_string>: <solution_id>

  The numbers of columns of solution <solution_id> and of problem <prob_id_string> are required to be the equal (but they are not).

827 Soln is deleted and no longer available: <solution_id>

  The user has attempted to access information for the solution with id <solution_id> but the solution has been deleted.

829 Soln id does not exist: <solution_id>

  The user has attempted to access information for the solution with id <solution_id> but the id is for a solution that does not exist.

830 Unable to make a reliable list of sols for prob: <prob_id_string>: Unable to access prob state

  An attempt to make a list of solutions that relate to problem <prob_id_string> failed because state information of the problem could not be reliably accessed.

831 Unrecognized attribute id <attribute_id>: Solutions will not be sorted

  The user seems to want a list of solutions sorted by some attribute but the attribute id is not recognized.

835 Column count does not match prob: <num_solution_cols>: <num_prob_cols>

  The numbers of columns of a given solution vector and of a given problem are required to be the equal (but they are not).

836 Failure writing solution to file: <file_name>

  An unexpected failure was encountered writing solution(s) to file <file_name>.

837 Failure opening file for writing: <file_name>

  An unexpected failure was encountered opening file <file_name> for writing.

838 Failure opening file for reading: <file_name>

  An unexpected failure was encountered opening file <file_name> for reading.

839 Loading sol failed : <prob_id_string>: id=<solution_id> <message>

  A failure occurred when loading solution <solution_id> into problem <prob_id_string>. The failure is described in string <message>.

842 Loading sol interrupted: <prob_id_string>: id=<solution_id>

  Loading was interrupted of solution <solution_id> into problem <prob_id_string>.

851 Unrecognized duplicate solution policy id: <policy_id>

  The user has attempted to set an unrecognized value <policy_id> for the control MSP_DUPLICATESOLUTIONSPOLICY.

852 Reading solution skipped: `<solution_name>'

  The solution named <solution_name> was skipped while reading solutions from file. A previous message describes why the solution could not be read.

853 Error detected in debug duplicate solution check: <message>

  A rigorous duplicate solution checking routine found an anomaly described in <message>.

855 Changing <tolerance_name> for solution `<solution_name>' captured from problem: <system_tol_value> -> <user_tol_value>

  A warning that the user is changing the tolerance <tolerance_name> (MIPTOL or FEASTOL) for a solution from the value it was set to by the system <system_tol_value> to a different value <user_tol_value>.

859 No solutions written

  No solutions were written in a call to XPRS_msp_writeslxsol.

868 <operation_name> is only allowed for attached problems

  The operation <operation_name> is only allowed for problems attached to the MIP solution pool.

869 Soln is deleted and no longer available: <solution_id>

  The user has attempted to access information for the solution with id <solution_id> but the solution seems to have been deleted.

870 Soln id does not exist: <solution_id>

  The user has attempted to access information for the solution with id <solution_id> but the id is for a solution that has not yet been encountered.

871 Unrecoverable memory allocation failure

  A call made by the user failed because of a memory allocation failure.

874 Unrecognized solution metric id: <metric_id>

  The metric id <metric_id> passed by the user is unrecognized.

875 No solutions available

  The user is attempting to access information about the stored solutions but the solution storage is empty.

876 Enumerator is already running

  The user is attempting to run the enumeration while the enumeration is already running.

875 Failed to access XPRSmipsolpool state: <access_operation>

  The MIP solution enumerator failed accessing the MIP solution pool state with access operation <access_operation>.

878 Failed to access XPRSprob state: <access_operation>

  The MIP solution enumerator failed accessing the problem state with access operation <access_operation>.

879 Failed to allocate memory

  The MIP solution enumerator failed to allocate memory.

882 Missing required arguments for running enumerator

  Arguments passed to the enumeration-run routine (e.g., XPRS_mse_minim) were required to be non-NULL but were passed as NULL.

883 Problem no longer has the same number of columns

  The column dimension of the problem used by the MIP solution enumerator was changed by user.

885 Failure storing solution with memory allocation failure

  A memory allocation failure meant that a solution could not be captured.

886 Failure storing solution(s) with failed access to XPRSmipsolpool state: <access_operation>

  A solution could not be captured because of a failure accessing the state of the MIP solution pool with access operation <access_operation>.

887 Failure storing solution(s) with failed access to XPRSprob state: <access_operation>

  A solution could not be captured because of a failure accessing the state of the problem with access operation <access_operation>.

1000 Invalid parameter access : <error_message> (<routine_name>)

  Access to a parameter with a call to routine <routine_name> failed because of error described in <error_message>.

1006 Failed to capture solution information from problem

  Failure calculating the information for a solution with respect to a problem.

1012 Problem <prob_id_string> detached unexpectedly

  A problem <prob_id_string> attached to the MIP solution pool was unexpectedly detached by the user.

1013 Cannot attach thread problem to MIP solution pool

  The user has attempted to attach an internal problem being solved by the parallel MIP search to a MIP solution pool.

1014 Column count mismatch: <num_solution_cols> != <num_row_vector_cols>

  A row vector of length <num_row_vector_cols> passed to the MIP solution pool for evaluation against a solution does not contain the same number of columns as the solution <num_solution_cols>.

## MIP Solution Enumerator errors

869 Soln is deleted and no longer available: <solution_id>

  The user has attempted to access information for the solution with id <solution_id> but the solution seems to have been deleted.

870 Soln id does not exist: <solution_id>

  The user has attempted to access information for the solution with id <solution_id> but the id is for a solution that has not yet been encountered.

871 Unrecoverable memory allocation failure

  A call made by the user failed because of a memory allocation failure.

874 Unrecognized solution metric id: <metric_id>

  The metric id <metric_id> passed by the user is unrecognized.

875 No solutions available

  The user is attempting to access information about the stored solutions but the solution storage is empty.

876 Enumerator is already running

  The user is attempting to run the enumeration while the enumeration is already running.

877 Failed to access XPRSmipsolpool state: <access_operation>

  The MIP solution enumerator failed accessing the MIP solution pool state with access operation <access_operation>.

878 Failed to access XPRSprob state: <access_operation>

  The MIP solution enumerator failed accessing the problem state with access operation <access_operation>.

879 Failed to allocate memory

  The MIP solution enumerator failed to allocate memory.

882 Missing required arguments for running enumerator

  Arguments passed to the enumeration-run routine (e.g., XPRS_mse_minim) were required to be non-NULL but were passed as NULL.

883 Problem no longer has the same number of columns

  The column dimension of the problem used by the MIP solution enumerator was changed by user.

885 Failure storing solution with memory allocation failure

  A memory allocation failure meant that a solution could not be captured.

886 Failure storing solution(s) with failed access to XPRSmipsolpool state: <access_operation>

  A solution could not be captured because of a failure accessing the state of the MIP solution pool with access operation <access_operation>.

887 Failure storing solution(s) with failed access to XPRSprob state: <access_operation>

  A solution could not be captured because of a failure accessing the state of the problem with access operation <access_operation>.

1000 Invalid parameter access : <error_message> (<routine_name>)

  Access to a parameter with a call to routine <routine_name> failed because of error described in <error_message>.

1007 Unexpected failure evaluating solution difference metric

  An unexpected failure occurred while evaluating difference metrics for solutions.

1008 Solution difference metric value is reserved : -1.7976931348623158e+308

  The double value -1.7976931348623158e+308 to be assigned for a difference metric between two solutions is reserved by the system.

1009 Unexpected failure evaluating solution differences

  An unexpected error occurred while evaluating the diversity of the stored solutions.

1010 User signaled failure in solution difference metric callback

  The user signaled a failure in the callback defined by a call to XPRS_mse_setcbgetsolutiondiff.

1011 Cannot evaluate diversity of new solution: Column number mismatch: <num_solution_cols> != <num_prob_cols>

  The solution passed down to XPRS_mse_getcullchoice for the diversity metric does not have the same number of columns as the problem used in the enumeration run.

1015 Destroying while enumeration running

  The user is attempting to destroy the MIP solution enumerator while it is running.

1016 Failed to update MIPABSCUTOFF

  The MIP solution enumerator failed to update the MIPABSCUTOFF on the problem running the enumeration.

1017 Unable to check if loaded sol is dupld: Sol cols (num_solution_cols) does not match MIP model (num_global_model_cols)

  A check if the solution being loaded is a duplicate of an existing solution cannot be made because the solution array does not have the same number of columns as the MIP model used for duplicate checking.

1018 MIP model unavailable for diversity: <reason_string>

  The MIP solution enumerator is setup such that internal solution diversity calculations may be made although this will fail because it requires that an appropriate problem is attached to the MIP solution pool (see <reason_string> for details).

1019 Cannot handle diversity: <reason_string>

  The user has called a function that requires solution diversity calculations to be made internally by the MIP solution enumerator and this has failed because it requires that an appropriate problem is attached to the MIP solution pool (see <reason_string> for details).

Parent Topic Appendix

© 2001-2026 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.