# Interpret InductEx® process status and printed diagnostic codes

Record the process outcome and the printed controlled diagnostic separately. Use the current log and complete documented reference to choose the correction.

## Compatibility

8.0.2 isolated Windows CLI review candidate; final package applicability pending

Published guidance with release-applicability limits. Confirm package applicability before following this guide.

**KB-DOC-006 · supported path**: Check the shell process outcome and printed numbered diagnostics separately. A retained solution file or Job finished message alone does not prove successful extraction.

[Download Complete Windows teaching extraction and receipt checker (ZIP)](/_functions/kbExample?name=inductex-scripted-run.zip)

Includes: strip.ixi, process.ldf, strip.cir, run_extraction.py, README.txt.

## Separate process status from the printed number

Record the operating-system process result, the supervisor state and any printed diagnostic number separately. The manual’s numbered list describes messages printed in the log; it is not a universal table of shell exit values.

On the checked Windows 8.0.2 CLI, a missing main IXI and an unknown option each return process status 2 before extraction. That does not mean controlled diagnostic (2), which the manual associates with a port-label file. Engine failures tested here return process status 1, with further detail in their current logs.

Status 0 means the process ended through its normal path; it does not establish that the requested calculation, study or numerical acceptance succeeded. The legacy SWEEP example returns 0 with a warning and no extracted elements. An external watchdog also records its own timeout state independently of a numeric process exit.

## Use the exercised failures as bounded examples

These are exercised outcomes for exact teaching inputs, not a promise that every related failure reaches the same code path. The missing process/netlist wording can say Cannot create file while describing a read attempt; check the stage and actual path before changing permissions.

| Actual case | OS process status | Printed diagnostic / next check |
| --- | --- | --- |
| Missing main IXI or unknown option | 2 | CLI rejection; no controlled number. Check the invocation and intended main file. |
| Missing process reference | 1 | No controlled (4) was emitted in this path. The current log reports a process-file read failure; inspect the exact missing path. |
| Missing extraction netlist | 1 | (5); restore the intended circuit file or correct its reference. |
| Duplicate L1 name | 1 | (40); resolve the duplicate component declaration. |
| P2 terminal replaced by P9 | 1 | (48); inspect the actual missing-terminal condition. Do not infer (49) solely from the fact that port names differ. |
| Owned output path occupied by a file | 1 | (10); inspect the destination obstruction before assuming an access-control problem. |
| Valid legacy SWEEP | 0 | Migration warning; no extracted elements. Use the complete external study workflow rather than accept process zero. |

## Find the first failure and verify recovery

The complete downloadable teaching runner is shared with the scripting guide. Its missing-netlist case leaves a partial sol.txt and a failed receipt; the corrected fresh generation reproduces the original detailed result. It rejects warnings, unsupported SWEEP, failed processes and timeout states.

1. Keep the exact executable/version, process/supervisor outcome, printed diagnostic text, complete saved inputs and current run log.
2. Read the earliest current error. A missing solver result may follow an earlier failure to load a dependency, launch the solver, construct the model or create its output.
3. Use a printed controlled number with the documented reference below. Follow the actual file paths named by the selected runtime: older engine-specific filenames in the reference may differ from current artifacts.
4. Correct the cause in a separate working copy and use a new result directory. Require a fresh successful receipt and the intended current numerical data, not merely disappearance of the previous error or existence of sol.txt.

## Look up every active documented diagnostic

The following 68 entries cover the active numbered descriptions in the maintained Exit Codes source. Treat unexercised rows as source-qualified reference information; their current emission path and release applicability still need verification. Do not use this list to reinterpret a shell result such as 2.

Legacy format/feature descriptions are retained within their reference scope. The virtual-cut row is deliberately phrased as a span/intersection check because the legacy wording needs clarification. No product/source manual was edited and no broad numerical or release acceptance is inferred.

Use the lookup to narrow the table, then select the number to open its stable row link. Show all diagnostics restores the complete reference. Every entry remains readable when JavaScript is unavailable; the linked number is also included in the Markdown answer and numbered-reference JSON index.

| Printed reference number | Documented meaning / check | Evidence scope |
| --- | --- | --- |
| 0 | Clean exit. | Documented reference; emission/current-path applicability not exercised here |
| 1 | Error while trying to open layout input file (GDS or IXI). The file does not exist, or cannot be read. | Documented reference; emission/current-path applicability not exercised here |
| 2 | Error while trying to open port label text file. The file does not exist, or cannot be read. | Documented reference; emission/current-path applicability not exercised here |
| 4 | Error while trying to open process (layer definition, LDF) file, or process file not defined. | Documented reference; emission/current-path applicability not exercised here |
| 5 | Error while trying to open netlist file. | Printed diagnostic exercised; OS process status 1 |
| 6 | Error while trying to open FFH/TTH port current or capacitance result file. Engine did not execute correctly (examine ffh.log or tth.log) or directory has write restrictions. | Documented reference; emission/current-path applicability not exercised here |
| 7 | Error while trying to open mesh file. | Documented reference; emission/current-path applicability not exercised here |
| 8 | Error reading solver output file solver_out.txt. Check if solver is in the path. | Documented reference; emission/current-path applicability not exercised here |
| 9 | The input file format is not supported anymore (CIF or DXF). | Documented reference; emission/current-path applicability not exercised here |
| 10 | InductEx® cannot create an output file. Check the destination and whether the working directory is writable. | Printed diagnostic exercised; OS process status 1 |
| 20 | Cannot resolve all inductor (branch) currents when solving inductance; no solution possible. | Documented reference; emission/current-path applicability not exercised here |
| 30 | No parameter block defined in LDF file, leaving modelling parameters undefined. Check if parameter block starts with $Parameters. | Documented reference; emission/current-path applicability not exercised here |
| 31 | Invalid input format or syntax in LDF file. $End statement found without an appropriate opening statement. | Documented reference; emission/current-path applicability not exercised here |
| 32 | Duplicate layer number in LDF file, or no layer number defined in layer block. Layer number ambiguity could cause modelling errors and must be corrected. | Documented reference; emission/current-path applicability not exercised here |
| 33 | Process uses a ground plane, but ground plane layer not identified. Add the parameter gplayer=n to the LDF file, where n is the ground plane layer’s GDS number. | Documented reference; emission/current-path applicability not exercised here |
| 34 | Capacitance conductor layer definition invalid, or does not support conductors (should be FilmType S or R). | Documented reference; emission/current-path applicability not exercised here |
| 35 | Duplicate layer name in LDF file, or no layer name defined in layer block. Layer name ambiguity could cause modelling errors and must be corrected. | Documented reference; emission/current-path applicability not exercised here |
| 36 | Superconductor layer has zero or negative lambda. | Documented reference; emission/current-path applicability not exercised here |
| 37 | Duplicate layer order in LDF file, or no layer order defined in layer block. Layer order ambiguity makes it impossible to construct a layer stack. | Documented reference; emission/current-path applicability not exercised here |
| 38 | Missing Text or Term layer, or layer number non-fabrication layer number collision. | Documented reference; emission/current-path applicability not exercised here |
| 39 | Range check error -- length of sorted and unsorted layer arrays mismatch. | Documented reference; emission/current-path applicability not exercised here |
| 40 | Component (such as inductor or port) name duplicated in circuit netlist file. Remove ambiguity by renaming one of the components (case-insensitive). | Printed diagnostic exercised; OS process status 1 |
| 41 | Error in port definition in netlist, such as a missing negative terminal. | Documented reference; emission/current-path applicability not exercised here |
| 42 | Cannot link positive or negative terminal of a port to a layout figure. Check layer names in port labels or in LDF file. | Documented reference; emission/current-path applicability not exercised here |
| 43 | Port positive or negative terminal layer definition invalid, or does not support terminals (should be FilmType S or R). | Documented reference; emission/current-path applicability not exercised here |
| 44 | Cannot identify port surface while building Gmsh geometry file. | Documented reference; emission/current-path applicability not exercised here |
| 45 | Component in parallel with another of its kind (inductor-inductor or port-port). This cannot be resolved for extraction. | Documented reference; emission/current-path applicability not exercised here |
| 46 | No cycles in netlist, or bad cycle found. Check for floating inductors or resistors, where one or more nodes are not connected to the circuit. | Documented reference; emission/current-path applicability not exercised here |
| 47 | There is a mismatch between the number of ports (including magnetic field sources) in the netlist, layout and current output file (ix.cur or ixth.cur) when inductance is solved. | Documented reference; emission/current-path applicability not exercised here |
| 48 | A port misses a terminal in layout. | Printed diagnostic exercised; OS process status 1 |
| 49 | Port defined in netlist not found in layout. | Documented reference; emission/current-path applicability not exercised here |
| 50 | Layout object (e.g. path, poly, sref) outside of Struct record in IXI file. Structure cannot be resolved. | Documented reference; emission/current-path applicability not exercised here |
| 51 | Coordinates not specified for a layout object in IXI file. | Documented reference; emission/current-path applicability not exercised here |
| 52 | Non-unity SREF magnification in layout input file not supported by InductEx®. Model geometry will not match layout. | Documented reference; emission/current-path applicability not exercised here |
| 53 | Collapsed polygon in layout. | Documented reference; emission/current-path applicability not exercised here |
| 54 | No objects in layout, either because layout file is empty or objects are all deleted by cut layers or operators, or were declared on layers not defined in the LDF file. A 3D extraction model cannot be built. | Documented reference; emission/current-path applicability not exercised here |
| 55 | Duplicate terminal labels in layout at different locations - ambiguity cannot be resolved. | Documented reference; emission/current-path applicability not exercised here |
| 56 | Invalid record length in GDS file - read-in aborted. | Documented reference; emission/current-path applicability not exercised here |
| 57 | Structure name in GDS file exceeds 127 characters. | Documented reference; emission/current-path applicability not exercised here |
| 58 | Port terminal defined on layer with no objects. | Documented reference; emission/current-path applicability not exercised here |
| 59 | Record or command not recognised in IXI file. | Documented reference; emission/current-path applicability not exercised here |
| 60 | No structures were read from the IXI layout. Check for STRUCT records, particularly in pre-v6 input. | Documented reference; emission/current-path applicability not exercised here |
| 61 | A virtual-cut terminal cannot divide a conductor into two polygons. Review its span and intersections; the legacy reference wording needs clarification. | Documented reference; emission/current-path applicability not exercised here |
| 62 | Layout cannot be identified in multiple-layout IXI input or for linking bonds. | Documented reference; emission/current-path applicability not exercised here |
| 63 | IXI record not supported when cuboid meshing is used. | Documented reference; emission/current-path applicability not exercised here |
| 64 | Port terminal defined as oblique line (not in x or y direction) with a cuboid mesh, which is not allowed. | Documented reference; emission/current-path applicability not exercised here |
| 70 | Abnormal termination or failed execution of external module (such as TTH or Gmsh). | Documented reference; emission/current-path applicability not exercised here |
| 82 | Incompatible format in Solver output file solver_out.txt. Use the solver version packaged with this version of InductEx®. | Documented reference; emission/current-path applicability not exercised here |
| 90 | Different capacitance conductors linked to the same conductive structure. | Documented reference; emission/current-path applicability not exercised here |
| 91 | No capacitance conductors identified. | Documented reference; emission/current-path applicability not exercised here |
| 110 | Licence key tier does not support requested functionality (as listed in the exit message). | Documented reference; emission/current-path applicability not exercised here |
| 111 | Licence key error. | Documented reference; emission/current-path applicability not exercised here |
| 112 | Licence key is for older version of InductEx®, and is not supported anymore. | Documented reference; emission/current-path applicability not exercised here |
| 113 | Invalid licence. | Documented reference; emission/current-path applicability not exercised here |
| 114 | Cannot decrypt protected process file. | Documented reference; emission/current-path applicability not exercised here |
| 120 | Mesh file not found. Gmsh did not complete mesh. Cannot execute TTH without a mesh. | Documented reference; emission/current-path applicability not exercised here |
| 190 | No valid edge found in fundamental circuit construction. Check netlist. | Documented reference; emission/current-path applicability not exercised here |
| 191 | Positive and negative node the same for an edge (component) in fundamental circuit construction. Check netlist. | Documented reference; emission/current-path applicability not exercised here |
| 192 | Missing node declaration for an edge (component) in fundamental circuit construction. Check netlist. | Documented reference; emission/current-path applicability not exercised here |
| 200 | Component lookup returned invalid dynamic array index - will result in memory error. | Documented reference; emission/current-path applicability not exercised here |
| 210 | Syntax error in expression string (such as missing parenthesis). | Documented reference; emission/current-path applicability not exercised here |
| 211 | Cannot parse variable in expression string. Variable identification symbol might be absent, or variable not defined. | Documented reference; emission/current-path applicability not exercised here |
| 212 | Syntax error boolean expression string. | Documented reference; emission/current-path applicability not exercised here |
| 220 | No IC read for Josephson junction in JoSIM netlist. | Documented reference; emission/current-path applicability not exercised here |
| 230 | No filament info found in FFH mesh file - check ffh.log. | Documented reference; emission/current-path applicability not exercised here |
| 231 | Exception – positive or negative terminal of a port has no nodes. This is an InductEx® node-building error for cuboid meshes and should be reported if encountered. | Documented reference; emission/current-path applicability not exercised here |
| 240 | Construct construct type not defined in LDF file. | Documented reference; emission/current-path applicability not exercised here |
| 255 | Catch-all code for entry into prohibited code (typically during range check error debugging). | Documented reference; emission/current-path applicability not exercised here |

## Check the result

The original failure is resolved in a fresh run, with correct input/output identity, requested quantities/units and independent numerical acceptance. Process status, controlled message number, solver verdict, artifact publication and physical accuracy remain distinct.

## If the problem remains

Prepare a minimal complete reproducer and relevant first-error context for private support. Review logs and process files before sharing; omit licence contents, holder information and private fabrication data. Do not manufacture licence denials or change system permissions to guess at a diagnostic.

## Sources and verification details

Recorded inputs/builds only. Complete walkthrough and final-package acceptance remain separate.

- VAL-067: Fresh isolated Windows current-source InductEx 8.0.2 CLI and installed licensed TTH. Frozen Windows InductEx 8.0.2 CLI and real installed licensed TTH, complete teaching runner, actual process/controlled-diagnostic distinctions, partial/stale artifact rejection and real owned-process timeout/recovery. No GUI, general arbitrary-model/convergence, final package or other platform acceptance. No GUI, arbitrary-model validator, general convergence/accuracy, every documented code, other platform or final-package qualification. A printed diagnostic code and process result are distinct.


- inductex:docs/manual/ix_exitcodes.tex: Exit Codes
- inductex:docs/manual/ix_parameters.tex: Current CLI identity/invocation and legacy-interface scope
- validation:cli-workflow-20261104: VAL-067 actual OS/printed-code distinctions; source-qualified 68-entry catalog

- Actual fresh-source Windows CLI and real licensed TTH; installed products, issued licence/configuration and source version metadata are preserved. No final package/platform qualification.
- 30 bounded checks retain CLI rejection, engine failure, printed diagnostics, partial sol.txt, actual timeout and correction. The complete reference preserves 68 active manual entries with explicit unexercised/legacy scope.
- KB-DOC-006 tracks the process-status/printed-number distinction and the still-open legacy/code61 reference clarification. No source manual or product fix is claimed.

## Related guides

- [An IXI project cannot find an input file](/knowledge-base/inductex-missing-input)
- [A port produces a mesh error or appears shorted](/knowledge-base/inductex-terminal-geometry)
- [Prepare a useful support report without exposing a licence or private design](/knowledge-base/support-effective-report)
- [Run an IXI extraction from a script or agent](/knowledge-base/inductex-cli-batch)
- [Run an InductEx® parameter study with separate checked cases](/knowledge-base/inductex-sweeps)
- [Create an IXI file or move a project in Studio](/knowledge-base/inductex-create-project)