Overview
BlackBox may encounter various issues that prevent it from generating results from its input. This guide presents common errors in a table format for easier troubleshooting by highlighting symptoms, possible causes, and corresponding solutions.
Symptoms
There are various symptoms that may occur within the software. (see list below)
Possible Causes
For each symptom there are various root causes that can affect the software's functionality. (see list below)
Troubleshooting Steps
Common Errors & Troubleshooting
| Symptom | Possible Cause | Troubleshooting Steps |
|---|---|---|
|
“Unknown Container: <id>” “Unknown container settings: <id>” “Unknown Product: <id>” |
Input data is missing or incorrectly referenced. | Verify that the input file includes the correct item, ensuring proper spelling, capitalization, and spaces. |
|
“Bad / missing data in load” “Corrupted or missing <containerstoload> record” “Corrupted or missing <productstoload> record” |
XML tags are missing or improperly formatted. | Ensure the input file contains all required XML tags and is properly structured. |
| “This load contains <producttoload quantity=’0’…/> only” | Product quantity not specified. | Assign a valid quantity for each product in the input file. |
| “Check product weights and dimensions” | Zero values in the product’s length, width, height, or weight fields. | Ensure all dimensions and weight fields have valid non-zero values. |
| “Error creating graphics engine” | Manual relocation of the BlackBox folder. | Contact MagicLogic for proper instructions on moving the BlackBox installation. |
| “Static data file: not found” | Static data file missing or misconfigured. | Verify the file location and update the BlackBox ini file to reflect the correct path. |
| “Cannot bind to the address specified” | TCP port conflict or insufficient privileges. | Check the port settings in the ini file, ensure no other application uses the port, and try running BlackBox with Administrator rights. |
|
“Exception caught from CLE preparation” “Exception caught from optimizer” “Serious error occurred during Optimization results processing” |
Internal exception triggered by optimization processes. | Contact MagicLogic support with the relevant log files for further assistance. |
Assistance
If any further assistance is needed, please contact our Support team.
Related Articles