Error Code Reference
LiDAR360MLS user error codes contain four digits. The first digit identifies the problem domain and the remaining digits identify the problem type. The same code may appear as a warning or an error. Always retain both the four-digit code and the complete original message.
General Troubleshooting Order
- Record the code, complete original message, feature name, occurrence time, and full software version.
- Resolve the first, more specific error in the same time period. For example, resolve 2004 before the later summary code 4010.
- Correct input, data, or environment causes before retrying; finish or exit conflicting workflows; retry an internal error only once.
- Back up a complete project or legacy dataset before repair or upgrade. Do not bypass validation by editing extensions, version fields, or internal configuration.
Problem Domains
| Domain | Codes | Description |
|---|---|---|
| Input and Selection | 14 | Invalid parameters, required inputs, selections, or combinations. |
| Data and Files | 34 | Files, projects, databases, spatial data, point clouds, trajectories, or images. |
| Environment and Dependencies | 23 | Licensing, networks, services, hardware, runtimes, plug-ins, or configuration. |
| Algorithms and Results | 15 | Processing startup, execution, matching, convergence, or result generation. |
| Application State | 16 | Projects, tasks, resources, views, or conflicting tools in an unsuitable state. |
| Internal Errors | 14 | Internal conditions that normally require one safe retry and support escalation. |
| Compatibility and Migration | 7 | Version incompatibility between the software and projects, data, or legacy formats. |
If the issue cannot be resolved, see Contact Technical Support.