This topic describes the error codes that the solver may return during runtime.
Solver runtime error codes
Error code | Description | Solution |
-1 | Unspecified internal error. | Check whether this is a secondary error code. See the License error codes section below. If you confirm it is a primary error, contact us. |
-2 | Out of memory. | Increase the memory or reduce the scale of the optimization problem. |
-3 | Invalid parameter. | Check the input parameters. |
-10 | Invalid license. |
|
-11 | The environment variable | Set the environment variable as instructed in 3. Check environment variables and perform a test run. |
-12 | Failed to load the MindOpt dynamic library. | Check the dynamic library. If necessary, reinstall the software package. |
-1000 | I/O communication error. | Check the file input and output. |
-1001 | Failed to read data from the file. | Check whether the file to be read is correct. |
-1002 | Failed to write data to the file. | Check whether the data to be written is correct and whether you have write permissions. |
-1003 | Path error. | Check whether the path exists and whether you have write permissions. |
-1100 | File parsing error. | Check whether the file to be parsed is correct. |
-1200 | The token ID entered for the remote computing service is invalid. | Check whether the token ID is valid and entered correctly. |
-1201 | Failed to connect to the remote computing server. | Check whether the remote computing server address is correct and the network connection is stable. |
-2000 | Error inputting or reading the optimization model. | Check whether the optimization model is correct. |
-2001 | The optimization model is empty. | Check whether the optimization model was entered correctly. |
-2002 | Invalid row index for the model. | Check whether the referenced row index is within the valid range. |
-2003 | Invalid column index for the model. | Check whether the referenced column index is within the valid range. |
-2004 | Invalid row name for the model. | Check whether the referenced row name is correct. |
-2005 | Invalid column name for the model. | Check whether the referenced column name is correct. |
-2006 | Invalid index for the symmetric matrix. | Check the input data. |
-2007 | Invalid row index for the symmetric matrix. | Check the input data. |
-2008 | Invalid column index for the symmetric matrix. | Check the input data. |
-2010 | Unrecognized string attribute. | Check whether the model's string attribute API is used correctly. |
-2011 | Unrecognized integer attribute. | Check whether the model's integer attribute API is used correctly. |
-2012 | Unrecognized real number attribute. | Check whether the model's real number attribute API is used correctly. |
-2013 | Unrecognized real number attribute for the symmetric matrix. | Check the input data. |
-3000 | The solution to the problem is unavailable. | Check whether the solution to the optimization problem was generated correctly. |
-3001 | The primal ray is unavailable. | Check whether the primal ray was generated correctly. |
-3002 | The solver statistics are unavailable. | |
-3003 | Unrecognized basis status value. | Check whether the basis status value is set correctly. |
-3004 | The Irreducible Inconsistent Subsystem (IIS) is unavailable for the current model. | You cannot call IIS. Check whether the problem type is supported. |
-3005 | The IIS is inactive for the solvable model. | The problem is feasible. No IIS exists. |
-4000 | Error setting a parameter. | Check whether the parameter setting API is used correctly. |
-4001 | Error getting a parameter. | Check whether the parameter retrieval API is used correctly. |
-9000 | The maximum number of iterations was reached. | Check whether the maximum number of iterations is set correctly. |
-9001 | The maximum solving time was reached. | Check whether the maximum solving time is set correctly. |
-9002 | The solving process was interrupted by a Ctrl+C command. | Check whether the process was interrupted by a Ctrl+C command. |
-9003 | The node limit was reached. | Check the node limit setting. |
-9004 | The limit for consecutive nodes without finding a better solution was exceeded. | The solving process failed. Check the problem model, or contact us. |
-9011 | The selected optimization algorithm is not supported. | Check the solving method settings and the license scope. Check for new versions, or contact us. |
-9012 | The solver does not support the input problem. | Check the file. Check for new version releases, or contact us. |
-10000 ~ -19999 | Numerical error in the simplex method. | |
-20000 ~ -29999 | Numerical error in the interior-point method. | |
-30000 | A numerical error occurred while computing the IIS. |
Authentication license error codes (secondary error codes for solver error code -10)
These errors are mainly related to the configuration of the fl_client.ini authentication file and network connectivity. For information about how to configure the fl_client.ini file, see 3. Use an Alibaba Cloud license key for authentication.
Error code | Problem description | Solution |
-1 | Request timed out. | Check whether you are connected to the internet and whether the network is stable. You can also increase the timeout period in the configuration file (default: 2 seconds). For more information, see 3. Use an Alibaba Cloud license key for authentication. |
-2 | Failed to create a socket. | Check the network connection. |
-3 | Failed to set the socket to non-blocking mode. | Check the network connection. |
-4 | Failed to parse the host. | Check the network connection. Then, check whether `server.name` is correctly configured in the configuration file. For more information, see 3. Use an Alibaba Cloud license key for authentication. |
-5 | Connection failed. | Check the network connection. |
-6 | Write request failed. | Check the network connection. |
-7 | Read request failed. | Check the network connection. |
-200 | Configuration file error. | Check the configuration file. For more information, see 3. Use an Alibaba Cloud license key for authentication. |
-201 | URL error. | Check whether `server.name` is correctly configured in the configuration file. For more information, see 3. Use an Alibaba Cloud license key for authentication. |
500 | Internal server-side exception. |
If the issue persists, contact us. |
400 | Invalid request format. |
If the issue persists, contact us. |
401 | Unauthorized. The LicenseKey failed verification. | Check whether the LicenseKey belongs to the Alibaba Cloud account that corresponds to the AccessKey. You can view the LicenseKey in the console > Purchased Services. |
410 | The resource has expired. | The configured LicenseKey has expired. Go to the console > Overview page to renew it. |
409 | Insufficient concurrency. | The number of concurrent tasks has reached the maximum limit allowed by the purchased LicenseKey. If the concurrency is insufficient, go to the console > Overview page to change the configuration. Note that completed tasks must be released promptly. For long-running tasks, you can set `MaxTime` to limit the total time consumed and release the concurrent resources right away. Normally, concurrency is automatically released after the solver program exits. However, if the program terminates abnormally, such as a crash, the concurrency is not automatically released. You can manually release it from the console or wait for the connection to time out for automatic release. |
403 | No permission. | Check whether the Alibaba Cloud account has granted permissions to the RAM user. In the Alibaba Cloud account's authorization settings, search for "opt" to query the relevant permissions. |
Console SDK runtime error codes
For more Alibaba Cloud authentication error codes, see the Alibaba Cloud Error Center.
In addition to the link above, there is also:
"404": Check whether the AccessKey ID and AccessKey secret are correct. Use a matching AccessKey pair.