Troubleshooting LP360 Export (LDE) Jobs

Use this article to troubleshoot an LP360 Export (LDE/LDExport) job that will not start, fails during processing, or cannot be completed. Depending on the workflow, LDE jobs may export point clouds, surfaces, intensity or hillshade images, or a point-cloud index shapefile. Delete Classes workflows may also use an LDE job.

First, select the affected job in Job Manager and open its log. Look for the ACTIONABLE FAILURE SUMMARY, including Detail, Environment checks, Hints, and any Input check. Also find the first relevant error before the final failure message. Message wording and available diagnostics vary with the LP360 version and language. Text following a colon, such as a filename or Windows error detail, is specific to your job.

Before retrying: Preserve the job log and any existing output. For an overwrite workflow, back up the source data and project before attempting completion again. Do not delete job files or temporary export settings while diagnosing the problem.

Find your error message

Match the message or hint in the job log. Use Problem to see what it means, or jump directly to Probable resolution.

• Out of memory, bad_alloc, cell count, or an unexpected TIN raster error: Problem | Increase cell size | Reduce/split extent
• no populated pixels, cell size too small, or too few points per pixel: Problem | Increase pixel size | Check coverage and filters
• The cell size is greater than the tile height or width or tile overlap warning: Problem | Adjust cell/tile sizes | Align tile dimensions
• BIGTIFF, classic TIFF, 4 GB, or AppendToStrip: Problem | Reduce raster size | Check large-file support
• no valid raster pixels or raster coverage reports zero valid pixels: Problem | Check product data/filters | Check extent/clip/CRS
• Export extent invalid, no overlap, outside extent, or projection/CRS hint: Problem | Correct export extent | Verify CRS and overlap
• No polygons to export, Input Layer is not a polygon layer, invalid geometry, or TIN/triangulation error: Problem | Repair polygon input | Check surface points
• Write access was denied, Drive is full, Path is too long, or locked/network/corrupt-file hint: Problem | I/O resolution table | Check source files
• GDAL Driver, RasterIO, CreateCopy, or unsupported format/compression: Problem | Use supported format/options | Check storage/size
• RGB export was requested or Maximum file size limit reached: Problem | Check RGB data | Split vector output
• 10599 or WriteToXMLStream: Problem | Check LP360 build | Provide reproducible example
• License not available to run LDExport or Failed to obtain the license: Problem | Verify license access | Check connectivity
• Failed to create LasExportSettings, Initialize failed, or COM/HRESULT component error: Problem | Repair LP360 | Check runtime dependency
• Failed to load/read/write job or Failed to set job ...: Problem | Check folder access | Check locks/security cleanup
• Error in ExecCmd with Cmd Line or LDExport fails before progress: Problem | Check Windows detail | Repair executable
• Failed to read Export Settings xml file or Failed to set input location: Problem | Check settings/input access | Recreate job
• Output location is not a folder, Output location is not a file, or Failed to set output location: Problem | Match destination to export | Check write access
• Failed to set Export Format, Failed to set surface params, or intensity-modulation error: Problem | Create supported settings | Isolate the option
• Job FAILED, Failed to Export Surface files, or Job Canceled: Problem | Find first specific error | Validate data/filters/extent
• Failed add files to map in Export Job or a completion/post-processing error: Problem | Check project and outputs | Retry completion
• No exported LAS files were found for Delete Classes overwrite Complete or source-layer error: Problem | Restore project context | Check exported files

📌 Problem

The job ends with a generic failure such as Job FAILED: or HRESULT 0x80004005.

Job Manager reports an export failure, but the final message, such as ERROR: Failed to Export Surface files or Job FAILED:, does not explain what to change.

🔍 Root Cause

The final status summarizes the failure. More specific exporter, Windows, and environmental diagnostics may appear earlier in the log. A generic HRESULT, such as 0x80004005 (E_FAIL), does not identify a unique cause.

🧠 What is the actionable failure summary?

Builds with the enhanced export diagnostics group the operation, HRESULT, underlying error detail, input/output/temp paths, disk-space readings, memory readings, and probable resolutions into an ACTIONABLE FAILURE SUMMARY. The Temp path is the Windows temporary directory used for this diagnostic check; it is not necessarily the configured LP360 Working Directory.

A hint beginning The error details suggest... is an interpretation, not proof. A failed access probe describes the path at failure time. A successful folder probe does not establish that every source file can be read or that an existing output file is unlocked. The summary may provide one classified hint even when other problems are also present.

✅ Probable Resolutions

1. Read the specific detail and environmental checks together

Open the full job log and search for ACTIONABLE FAILURE SUMMARY. Note the failing operation and Detail:, then review hints beside Output and Temp, the Environment checks, and the Hints section. If an Input check: is present, follow its path-specific guidance. Use the sections below to make the corresponding correction.

2. Keep the full log when the hint is inconclusive

If the summary says No specific cause could be identified from the error details., review earlier warnings and preserve the full log for Support. Do not infer a memory, permission, or licensing diagnosis from a generic failure code alone.

📌 Problem

ERROR: Out of memory in LDExport command, bad_alloc, or raster size/cell count too large.

The log reports a memory or raster-size problem. Examples include:

• ERROR: Out of memory in LDExport command
• LASExporterV2::ExportTINRaster() ran out of memory (cell size ...). The raster is too large for the available memory at this cell size.
• Allocating row buffer failed or Unable to allocate row buffer
• bad_alloc, bad allocation, or 0x8007000E (E_OUTOFMEMORY)
• Hint: Export failed due to insufficient memory.
• Hint: Memory pressure was detected at failure time (low available physical or commit).
• A hint that the output is infeasibly large for the selected resolution and extent, or detail mentioning grid size, too many cells, raster size, or cell count.
• Unexpected error in LASExporterV2::ExportTINRaster() with a hint to retry using a larger cell size or smaller export area.

🔍 Root Cause

A fine cell size combined with a large export extent can require an excessive number of raster cells and processing buffers. Multiple output attributes and concurrent work can add memory demand. Low available physical memory or commit headroom can also contribute. A memory-pressure hint is a probable cause; an explicit out-of-memory error is stronger evidence.

🧠 What is the relationship between cell size and memory?

A larger cell size is a coarser resolution and creates fewer cells over the same area. For example, changing from 0.10 to 0.20 in the same horizontal units produces approximately one-quarter as many cells for the same extent. Decreasing cell size does the opposite and can worsen a memory failure. Grid alignment, output bands, interpolation, and processing buffers affect actual resource use.

The summary reports physical memory, available commit and its limit, and the process WorkingSet/private commit at failure time. These are diagnostic snapshots, not minimum hardware requirements. A log entry saying processing block reduced ... to fit memory is an automatic protective adjustment, not itself a failure, and does not mean the requested output resolution was changed.

✅ Probable Resolutions

1. Increase the export cell size

In the surface/raster export settings, choose a larger cell-size value that still meets the product requirements. If automatic cell-size computation is enabled, explicitly choose a manual value for this diagnostic test. Compare the estimated Rows, Columns, and Cells on the export extent page before submitting a new job. Do not deliver a coarser product without confirming that it meets the required resolution.

2. Reduce the export extent or split the output

Select a smaller area that overlaps the intended source data, use smaller export tiles, or cookie-cut with smaller polygons. If the required resolution must remain unchanged, dividing the area is preferable to silently changing the resolution. Preserve the requested coverage, alignment, and any required overlap when assembling the final products.

3. Reduce competing memory use

Save work and close unnecessary applications or wait for other memory-intensive processing to finish. Review available memory and commit in the summary. If memory remains insufficient at the required resolution and extent, ask IT to review RAM capacity and Windows virtual-memory configuration. Retry a small representative area before another full export.

📌 Problem

No populated pixels/cells, too few points per pixel, or cell size too small.

The detail mentions no populated pixels, no populated cells, too few points per pixel, not enough points per pixel, pixel size too small, or cell size too small. The summary may say:

The error details suggest the selected raster pixel size may be too small for the available point density, so no pixels could be populated.

🔍 Root Cause

The selected resolution and the population/interpolation requirements may be unsuitable for the eligible point density. Class, return, and attribute filters can reduce that density substantially. An empty raster can also result from non-overlapping extents or clipping, so confirm those before deciding that cell size is the cause.

🧠 What is eligible point density?

The relevant density is that of the points available to the selected output after filtering and clipping, not necessarily the density of the complete source cloud. A finer pixel size does not create additional source information. Different surface methods have different point requirements.

✅ Probable Resolutions

1. Increase pixel size to suit the qualifying points

Test a larger cell size on a small area with known qualifying coverage. Use automatic cell-size estimation, if available for the selected workflow, as a starting point rather than assuming an arbitrarily fine resolution is appropriate. Verify the resulting coverage and product quality before exporting the whole area.

2. Review filters and choose an area with usable coverage

Check classes, returns, and attribute constraints against the points that actually exist. Correct an unintended filter, or choose a denser overlapping test area. For a ground-only DEM, do not include non-ground classes merely to eliminate NoData; retain the intended surface definition and address inadequate ground coverage appropriately.

📌 Problem

The cell size is greater than the tile height or width, or the cell size does not divide evenly into tile dimensions.

The export setup reports:

• The cell size is greater than the tile height or width.
• The cell size and tile height and/or width do not divide evenly. Overlap will occur between tiles.

🔍 Root Cause

The pixel size is larger than a tile dimension, or the chosen tile dimensions are not whole multiples of the pixel size. This is a tile/grid compatibility problem, not the same as a too-fine-resolution memory problem.

🧠 When should cell size be decreased?

Decrease cell size when it is too large for the intended tile dimensions or when a finer resolution is required and supported by the data and resources. Increase it for excessive grid size or sparse-point population problems. The correct direction depends on the actual message; neither change is a universal fix.

✅ Probable Resolutions

1. Make the cell size and tile dimensions compatible

Choose a positive cell size no greater than either tile dimension. Decrease the cell size, or increase the tile width/height if larger tiles are appropriate. Check estimated row/column counts and resource demand after the change.

2. Use tile dimensions that divide evenly by the cell size

Set width and height to whole multiples of the cell size in the same horizontal units. For example, a 100-unit tile width divides evenly by a 0.5-unit cell size. If exact tiling is a deliverable requirement, correct the mismatch rather than accepting the overlap warning.

📌 Problem

BIGTIFF, classic TIFF, 4 GB, or AppendToStrip appears in raster output detail.

Raster export detail mentions BIGTIFF, classic TIFF, 4 GB, Maximum TIFF file size exceeded, file too large, or AppendToStrip. The summary may suggest that the raster exceeded the 4 GB GeoTIFF limit.

🔍 Root Cause

A classic TIFF cannot store an arbitrarily large raster. Fine resolution, large extent, multiple bands, and output encoding can push the file beyond its approximately 4 GB addressing limit. A generic file too large message is not proof of this cause; confirm that the detail identifies TIFF or its writer.

🧠 What is BigTIFF?

BigTIFF is a TIFF variant that supports larger files. Availability depends on the selected LP360 workflow and writer, and compatibility depends on the software consuming the result. Freeing disk space alone does not remove a classic TIFF format limit.

✅ Probable Resolutions

1. Reduce the size of each output raster

Increase pixel size if the required resolution permits, reduce the export extent, or cookie-cut the area into smaller polygons/tiles. If resolution must be preserved, split the coverage into smaller output files.

2. Verify large-file format support

If one large file is required, confirm with Support whether your LP360 version and export workflow support BigTIFF or another suitable output format, and verify that downstream software accepts it. Do not assume that changing the file extension enables BigTIFF.

📌 Problem

Raster export failed: no valid raster pixels were written for one or more products.

The log reports:

Raster export failed: no valid raster pixels were written for these products across all output tiles: ... . Their outputs contain only NoData.

It may also report Raster export coverage: followed by a product name, valid-pixel count, and output-tile count. Some products can contain valid data while another requested product is entirely NoData.

🔍 Root Cause

At least one tracked raster product has no valid pixels across all its output tiles. Possible causes include filters excluding suitable points, lack of the requested attributes, insufficient qualifying coverage, clipping outside the point cloud, projection mismatch, or inability to build the requested surface.

🧠 What is NoData coverage?

NoData represents a pixel without a usable value; it is not a valid elevation or other measurement. In builds with coverage validation, each raster product is evaluated across its output tiles using its NoData definition. An empty tile alone does not fail a product if that product has valid pixels elsewhere. Conversely, a valid elevation product does not make an entirely empty requested intensity or other product acceptable.

✅ Probable Resolutions

1. Identify the empty products and verify their input requirements

Read the product names listed in the failure and their coverage counts. Confirm that qualifying points contain the attributes needed for those products. Check class, return, and attribute filters. Remove an unintended product from the export, or provide the required data; do not change NoData values just to make an empty raster appear populated.

2. Correct extent, clipping, and projection

Display the source point cloud and clip polygons together. Confirm actual overlap and compatible coordinate systems. Test a small extent inside known qualifying coverage without the clip polygon, then reintroduce the intended clipping. Review the extent and polygon sections below if this isolates the failure.

3. Evaluate resolution only after confirming coverage

If points overlap but are too sparse for the chosen method or per-cell requirements, test a coarser cell size and review the filters. A larger cell size will not repair non-overlap, missing attributes, or a filter that excludes all points.

📌 Problem

Export extent invalid, no overlap, outside extent, or a projection/CRS hint.

Possible messages and diagnostic detail include:

• Export extent invalid
• Tile width and/or height is invalid
• Failed to get extents of the data
• no overlap, does not intersect, outside extent, outside bounds, or an empty extent.
• A hint that the AOI/export extent may not overlap the input LAS data.
• A hint that the detail suggests a coordinate reference system (CRS/projection) issue.

🔍 Root Cause

The requested bounds may have zero/negative width or height, lie outside the source data, or be expressed in incompatible coordinates or units. For tiled exports, non-positive tile dimensions are invalid. An apparently valid polygon can still be located far from the point cloud if its CRS is wrong.

🧠 What is the export extent?

The extent describes the output area. It must have XMax greater than XMin and YMax greater than YMin, and contain the intended qualifying coverage. Reducing the area is useful for resource problems; expanding or relocating it may be appropriate when the current area misses the source points. Changing a CRS label is not the same as reprojecting data.

✅ Probable Resolutions

1. Reset the extent to known source coverage

Confirm the intended LAS layer is active and has accessible files. Use its full data extent as a reference, or choose a small area visibly inside the qualifying cloud. Correct reversed or equal bounds and verify horizontal units. Avoid using the entire cloud as the first retry if its size was already causing resource problems.

2. Verify input, polygon, and output coordinate systems

Check CRS definitions, units, and datum in the source LAS data, AOI layer, and export configuration. Resolve undefined or incorrect definitions using the known source CRS. Reproject with the appropriate transformation when needed; do not relabel coordinates to force visual agreement. Test the overlap again before submitting a new job.

3. Correct tile dimensions and naming setup

Set tile width and height to positive values and check their relationship to the cell size. If the log reports File start number is invalid, use a non-negative start number. Review estimated tile and cell counts so that the corrected setup is still practical.

📌 Problem

No polygons to export, invalid polygon geometry, or a TIN/triangulation failure.

Possible messages or underlying detail include:

• No polygons to export. If using the selected option make sure at least one polygon is selected then continue.
• Cookie cut by polygons requires a polygon object or Cookie cut by polygons requires a valid field index
• Input Layer is not a polygon layer
• invalid polygon, self-intersect, ring not closed, empty geometry, empty shapefile, or topology errors.
• Failed to build TIN for thin surface, triangulation/Delaunay errors, collinear points, insufficient unique points, or degenerate triangles.

🔍 Root Cause

Cookie-cut input may be missing, have no selected polygons, have invalid geometry, or reference an invalid naming field. A surface/TIN can fail when too few suitable unique points remain or the points do not form usable two-dimensional coverage.

🧠 What are polygon and TIN requirements?

Cookie cutting requires usable polygon features, not merely a shapefile name. A TIN connects source points into triangles; points lying on one straight line or an excessively restrictive filter cannot supply a meaningful two-dimensional surface. A coarser grid alone cannot create missing point geometry.

✅ Probable Resolutions

1. Correct polygon selection, geometry, and naming fields

Confirm the correct polygon layer is selected. If using selected features only, select at least one intended polygon or deliberately switch to all intended features. Remove empty features and repair invalid/self-intersecting geometry with an appropriate geometry-validation tool, preserving the intended boundary. Recheck the naming field and submit a fresh export.

2. Provide enough suitable points for surface construction

Check the eligible points inside the AOI. Correct unintended filtering or thinning, or enlarge/relocate a very narrow test area to include valid non-collinear coverage. Test a coarser cell size when the point coverage supports a surface but the requested raster is impractical. Do not loosen ground filters in a way that changes the intended DEM.

📌 Problem

An I/O hint reports denied access, a lock, low disk space, an invalid/missing path, network failure, or corrupt data.

The log contains Hint:, Input check:, a Windows I/O error, a file-copy/move failure, or a raster seek/read/write error. Possible messages include Write access was denied, Drive is full, Path is too long, Path contains invalid characters, or a locked/inaccessible file or network path.

Coverage-check errors such as Cannot seek raster output while checking NoData coverage, Cannot read raster output while checking NoData coverage, or Cannot restore raster output position after checking NoData coverage are I/O failures. They are not evidence that the raster actually contains only NoData.

🔍 Root Cause

LP360 could not perform a required operation on a source, destination, temporary, settings, or job file. Use the actual operation and named path to distinguish read access from write access. Potential causes and the corresponding user actions are listed below.

🧠 What do the I/O checks establish?

A write probe tests creating a temporary file in the affected folder. An existing output can still be locked even when that succeeds. An input-file or folder check tests current access to the configured path, not the integrity or availability of every LAS file referenced by an input list. A file that was readable at failure time may have failed earlier because of a transient connection or because a different file was affected.

Access denied alone cannot distinguish NTFS permissions from antivirus/EDR blocking. The Explorer read-only checkbox for a folder is not proof that writes are denied. A read-only attribute on an existing file can block an update, but does not by itself explain a read failure.

✅ Probable Resolutions

1. Match the error or hint to the correct action

2. Validate the complete source set, not just the configured path

If the input check says the folder/file is readable but export still cannot open input, inspect the individual LAS/LAZ files referenced by the layer or file list. Verify they exist, open in LP360, and remain accessible during processing. A readable list file does not prove that its referenced point clouds exist or are valid.

3. Run a controlled local-storage test

When permitted, test a known-good subset on reliable local storage using a new short, writable output path. If this succeeds while the network/removable-media run fails, investigate that storage path with IT before repeating the full export. Keep original and test results separate.

📌 Problem

GDAL Driver, CreateCopy, RasterIO, unsupported format, compression, or dataset-creation error.

The detail mentions a GDAL driver, unsupported format, CreateCopy, RasterIO, compression, creation options, or failure to create an output dataset. Examples include Failed to get Tiff driver from GDAL, Failed to get GDAL Driver for COG, Failed to create GDAL image file, and Creating raster file '...' failed.

🔍 Root Cause

The writer could not create or use the requested raster dataset. Possible causes include unsupported options or format combinations, an unavailable driver, a destination problem, insufficient resources, or a lower-level raster I/O error. A GDAL-related hint is not necessarily an installation diagnosis.

🧠 What is a raster driver?

A raster driver encodes the output in its selected format. The filename extension, export format, output attributes, and compression/creation options must be compatible. RasterIO describes raster reading/writing, so the underlying detail may point to storage rather than format configuration.

✅ Probable Resolutions

1. Use a supported format and matching extension

Recreate the export with a format offered by the LP360 interface and its matching filename extension. If the workflow exposes compression or creation options, return to supported/default options for a small diagnostic test, then add required options individually.

2. Resolve the underlying storage or size error first

Look for disk-full, access, lock, memory, or TIFF-limit text in the same detail and follow that section. Test a short local output path and small extent. If the driver is explicitly unavailable, or a supported format fails repeatedly on good storage, repair/update through the supported LP360 installer and contact Support.

📌 Problem

An RGB export lacks source color bands, or a vector/shapefile reaches its size limit.

Examples of product-specific failures include:

• RGB export was requested, but the selected LAS layer does not contain RGB color bands.
• You must select a LAS Layer that has been 'Colorized' (RGB values other than zero).
• Maximum file size limit reached, Reached Shapefile limit, or Unable to close shapefile. Overflow
• Failed to write Shapefile. One possible reason is, the output shape file might have reached it's limit

🔍 Root Cause

An RGB product needs usable RGB source attributes. Separately, a vector export may exceed the selected writer's file-size or format limits. Neither problem is resolved simply by retrying unchanged settings.

🧠 What are product prerequisites and format limits?

Selecting RGB output cannot create colors that are absent from the source. Vector limits are distinct from the classic TIFF raster limit. Cell-size adjustments apply to raster products and should not be treated as a general fix for point/vector exports.

✅ Probable Resolutions

1. Use an appropriately colorized layer or omit RGB output

Select a source layer with valid RGB bands and usable color values. If color is required but missing, perform the applicable colorization workflow before exporting. Otherwise, remove the RGB product and choose an available attribute that meets the intended deliverable.

2. Split an oversized vector output

Export smaller extents or separate tiles/polygons so individual files remain within the selected format's limits. If necessary, use another supported format compatible with the deliverable. Preserve required point/feature content; do not introduce arbitrary filtering merely to make the file smaller.

📌 Problem

10599 / WriteToXMLStream, or a repeatable internal raster error persists.

A repeatable internal raster error remains after coverage, settings, resources, and storage have been checked, or the log shows 10599 / WriteToXMLStream associated with saving export/SDASN settings.

🔍 Root Cause

Some failures can be version-specific software defects rather than incorrect user settings. Code changes have addressed irregular-polygon processing coverage, excessive TIN raster buffer allocation at fine cell sizes, all-NoData product detection, and SDASN cell-filter serialization. Availability of these changes depends on the installed build.

🧠 What is the difference between a workaround and a software correction?

A smaller extent or coarser cell size can be a useful diagnostic or resource workaround, but it is not proof that the original requested product was invalid. Likewise, an XML serialization error after processing does not by itself establish that the raster contains valid data. Check both the export result and the settings/completion stage.

✅ Probable Resolutions

1. Confirm the installed build and applicable correction

Record the LP360 version/build and ask Support whether a supported update includes the relevant correction. Use How to Update LP360 for the update process. Do not assume every published version contains recently added diagnostics or fixes.

2. Provide a reproducible example without changing the required product

Preserve the failing configuration and full log. Test a small representative extent or a coarser resolution in a separate destination and report exactly which change affects the result. For a serialization error, retain the settings if available and do not manually remove XML fields to suppress it. Send Support the version, error, settings, and an approved sample if requested.

📌 Problem

License not available to run LDExport, Failed to obtain the license, or a license check failed.

The LDE job does not become ready to run, or it fails with one of these messages:

• License not available to run LDExport.
• Failed to open License file.
• Failed to check if license is available to run LDExport.
• ERROR: Failed to obtain the license
• ERROR: Failed to get license to execute this tool

🔍 Root Cause

LP360 could not confirm or obtain the license access needed at that stage of the workflow. Possible causes include unavailable license access, an unreadable license configuration, or a licensing service or connectivity problem. A message that a license is unavailable does not, by itself, establish that the installation is damaged.

🧠 What is an LDE license check?

The queue processor checks whether an export job can run before starting LDExport. License availability can change between that check and execution. Some export utilities use runtime licensing internally, so the message and the workflow determine which licensing check needs attention.

✅ Probable Resolutions

1. Verify license access in LP360

Open LP360 under the same Windows account used to submit the job and check its license status. Resolve any activation, sign-in, or license-manager error first. If your organization uses a shared license, ask the license administrator to confirm that an appropriate license is available.

2. Check connectivity required by your licensing method

If your licensing method requires access to a license server or an online service, verify that connection. Have IT review firewall, proxy, or security-software blocks rather than disabling protection. After restoring access, retry the job.

3. Distinguish a licensing error from a component-loading error

If the log also reports Failed to create LPLicense COM instance, follow the component troubleshooting section below. If license access works in LP360 but the LDE job still fails, provide Support with the full log and your licensing method.

If the actionable summary identifies licensing or entitlement during export, confirm that the Export feature is included in the applicable license tier as well as checking general license availability.

📌 Problem

Initialize failed or an LP360 component/COM object could not be created.

The job fails while initializing LP360 components. Possible messages include:

• Initialize failed
• Failed to create LPLicense COM instance (hr=...)
• ERROR: Failed to create LasExportSettings object
• ERROR: Failed to create Map Environment object.
• ERROR: Failed to create LasExporter object
• ERROR: Failed to create LasExporter object.

🔍 Root Cause

A required LP360 component could not be initialized, loaded, or connected to the export environment. Possible causes include an incomplete installation, missing runtime dependencies, component-registration problems, or blocked access. The HRESULT and surrounding log messages help identify which cause applies.

🧠 What is a COM component error?

LDExport uses shared LP360 components installed on the computer. Windows COM errors indicate that an application could not create or use one of those components. For example, 0x80040154 means the class is not registered, 0x800401F8 indicates a component DLL could not be found, 0x800401F9 indicates a DLL could not load or initialize, and 0x80070005 means access was denied.

✅ Probable Resolutions

1. Repair the LP360 installation

Save your project and allow other processing to finish before closing LP360. Use the LP360 installer or the repair option available in Windows Installed apps/Programs and Features. Have an authorized administrator perform the repair if required. Restart Windows if prompted, then reopen LP360 and retry.

2. Check the required Visual C++ runtime

If the message says a component was found but could not load, follow Troubleshooting LP360 Installation Error: Visual C++ Redistributable Need to be Updated. Use the runtime packages recommended for your LP360 version.

3. Investigate access-denied or security-software blocks

Ask IT to review quarantine records, application-control events, and Windows Application events at the time of failure. Review Antivirus Exceptions for LP360 for approved configuration guidance. Do not download replacement DLLs from third-party sites or make registry changes without Support or IT guidance.

📌 Problem

Failed to load/read/write job or Failed to set job ....

The job cannot read or update its processing information. Possible messages include:

• Failed to load job:
• Failed to read job file:
• Failed to write job file:
• Failed to save job file when setting RunReady flag
• Failed to set job in progress:
• Failed to set job to post processing ready:
• Failed to set job to complete:
• Failed to set job to failed:

🔍 Root Cause

LP360 could not read, save, or move the job file. Possible causes include a missing or damaged file, insufficient folder permissions, a file lock, unavailable storage, insufficient free space, or security software removing or blocking the file. Read the error detail after the message for the affected path and Windows error.

🧠 What is an LDE job file?

The job file stores processing instructions and job status. LP360 updates or moves it as the job progresses. Failure to change the job state is different from failure to export the data: output files may already exist even when a status update fails.

✅ Probable Resolutions

1. Verify the affected folder and account permissions

Identify the path in the job log or error detail. Confirm that the storage is available and that the processing account can read, create, modify, and move files in the relevant job and working folders. Ask IT to correct access problems. Check free disk space on those drives.

2. Check for file locks, cleanup, or quarantine

Have IT review security and cleanup activity at the failure time. Ensure that temporary-file cleanup tools are not removing active job files. Do not manually move a job between state folders or edit its contents to force a successful status.

3. Preserve output before retrying or resubmitting

Inspect the output folder before rerunning an export. If the job file is missing or unreadable, preserve the remaining log and settings, then submit a new job from LP360 after correcting the underlying problem. Use a separate output location to avoid mixing old and new results.

📌 Problem

Error in ExecCmd with Cmd Line : or LDExport fails before showing export progress.

The log reports Error in ExecCmd with Cmd Line :, followed by the LDExport command and a Detail: message. The job may end with Job FAILED: without showing export progress.

🔍 Root Cause

The queue processor could not set up communication with, or start, the LDExport process. Possible causes include a missing executable, an installation problem, blocked process execution, or a Windows resource or access error. The accompanying Windows detail is more diagnostic than the final job status.

🧠 What is LDExport?

The LDE queue processor starts LDExport.exe to perform the export and captures its output in the job log. A launch failure occurs before normal export processing; changing surface or point-filter settings will not resolve a missing or blocked executable.

✅ Probable Resolutions

1. Use the Windows error detail to identify the problem

For a file-not-found error, check whether the executable at the logged path exists. For access denied, ask IT to review execution permissions and security events. If Windows reports a resource problem, save your work, finish other processing, and restart Windows before trying again.

2. Restore the installed executable through LP360 repair

If LDExport is missing or damaged, repair LP360 using the supported installer. Do not copy executables from a different LP360 version. If security software blocked the executable, have IT resolve the block using the LP360 antivirus guidance linked above.

📌 Problem

Failed to read Export Settings xml file, Failed to set input location, or Failed to set Export input type.

The export cannot use its saved settings or input. Possible messages include:

• ERROR: Failed to read Export Settings xml file
• ERROR: Failed to set input location
• ERROR: Failed to set Export input type

🔍 Root Cause

The saved export settings cannot be loaded, or the input location/type cannot be applied. Possible causes include missing or unreadable settings, unavailable input paths, or an invalid configuration. A job's input-file list can still exist even when the LAS files referenced by that list have been moved or are inaccessible.

🧠 What are saved export settings?

An LDE job uses an export-settings XML file and an input-file list created for the submitted export. Retrying a job normally reuses its saved instructions. Changing the current project or export dialog does not necessarily update an already-submitted job.

✅ Probable Resolutions

1. Confirm the settings and source files are accessible

Check the settings and input paths shown in the job information or log. Restore any disconnected network share or external drive. Confirm that the processing account can read the files and that the source point clouds can be opened in LP360.

2. Recreate the job from the export interface

If the saved settings are missing, damaged, or no longer describe the intended input, preserve the original log and submit a new export from LP360 with the corrected source layer and options. Do not manually alter XML or job-file fields as a troubleshooting shortcut.

📌 Problem

Output location is not a folder, Output location is not a file, or Failed to set output location.

The export rejects its destination. Possible messages include:

• ERROR: Output location is not a folder. Please set folder -o option and rerun it
• ERROR: Output location is not a file. Please set folder -o option and rerun it
• ERROR: Failed to set output location
• ERROR: Failed to set Output filename

🔍 Root Cause

The destination does not match the selected export mode, or LP360 cannot apply the destination path. File-by-file, polygon cookie-cut, and certain tiled exports require an output folder. A single-output export requires a filename instead of a folder. An unavailable or invalid path may also prevent the destination from being set.

🧠 What is a file destination versus a folder destination?

A folder destination identifies where multiple output files will be created, for example C:\LP360_Output\Export. A file destination includes the output filename and extension, for example C:\LP360_Output\Export\surface.flt, when that format is selected. The wording of the second error above is misleading: when it says not a file, supply a filename, despite its instruction to set a folder.

✅ Probable Resolutions

1. Match the destination to the export mode

Reopen the export setup in LP360. For a multi-file export, select an existing output folder. For a single-output export, specify the complete output filename with the extension appropriate to the selected format. Submit a new job if the saved destination is incorrect. The -o text refers to LDExport's internal command-line argument; you can correct the destination through the LP360 export interface.

2. Verify write access, free space, and file availability

Confirm that the destination or its parent folder exists, is writable by the processing account, and has sufficient free space. Close applications using the intended output files. If a network destination is unreliable, test with a new writable local output folder. Preserve existing results before choosing an overwrite option.

📌 Problem

Failed to set Export Format, Failed to set surface params, or intensity-modulation error.

The export cannot apply its type, format, or surface options. Possible messages include:

• ERROR: Failed to set export type
• ERROR: Failed to set Export Type
• ERROR: Failed to set Export Format option
• ERROR: Failed to get surface params
• ERROR: Failed to set surface params
• ERROR: Failed to set Intensity Modulate flag
• ERROR: Failed to set Intensity Modulate percent
• ERROR: Failed to get Nyquist Method supports flag.

🔍 Root Cause

LP360 could not read or apply an export option. Possible causes include an invalid or incompatible settings combination, damaged saved settings, or an internal component problem. These messages alone do not establish which setting is invalid or whether the problem is data-specific.

🧠 What are surface and intensity-modulation options?

Surface settings define how point-cloud data becomes a raster or other surface product. Intensity modulation combines intensity information with hillshade presentation. The Nyquist message concerns a capability check for the selected export settings; it does not, by itself, mean that the point cloud has insufficient density.

✅ Probable Resolutions

1. Create fresh settings with a supported combination

Create a new export using the LP360 interface rather than reusing the affected job. Select the intended export type and a format offered for that type. For surfaces, review the interpolation, resolution, and attribute settings. Enter intensity-modulation values within the range accepted by the dialog.

2. Isolate the option that triggers the failure

Test a small representative area using a basic export configuration and a separate output folder. If that succeeds, add the required optional settings one at a time. Disabling intensity modulation for a diagnostic test changes the appearance of hillshade output; do not treat that test output as equivalent to the intended product.

3. Escalate repeatable capability or parameter errors

If fresh settings still produce the same error, provide Support with your LP360 version, the selected export options, and the log. If component-creation errors also appear, follow the component troubleshooting section.

📌 Problem

Job FAILED:, Failed to Export Surface files, or Job Canceled.

The export starts but does not produce the expected result. Possible messages include:

• ERROR: Failed to Export Shape Index file
• ERROR: Failed to Export Surface files
• Input Layer is not a polygon layer
• ERROR: An error occurred in LDExport command
• Exception occurred processing LDExport Job:
• Job FAILED:
• Job Canceled

🔍 Root Cause

These messages may summarize an earlier export error, an exception, or a cancellation. Possible underlying causes include unreadable source data, output access problems, invalid polygon input, unsuitable settings, or insufficient resources. For a cookie-cut export, a non-polygon layer directly explains the polygon-layer message.

🧠 What does a generic export failure tell me?

Job FAILED: is a final status, not a diagnosis. Likewise, ERROR: An error occurred in LDExport command may follow a more specific error. The message ERROR: Failed to Export Surface files can also appear during a point export, so use the selected export type and earlier log entries rather than that wording alone. Filters and extents can leave no eligible points, and some workflows skip files with no remaining points.

✅ Probable Resolutions

1. Resolve the first specific error in the log

Read backward from the final failure message to locate the first relevant error and its detail. Apply the matching licensing, settings, component, input, or output resolution above. Do not assume that repeatedly pressing Retry will correct the underlying cause.

2. Validate the source data, filters, and export extent

Confirm that the source point clouds open in LP360 and contain points eligible for the chosen class/return filters and export extent. For an index shapefile, verify the source files and output-folder access. For a surface, test a small representative area and verify that the selected points are suitable for the requested product.

3. Validate polygon cookie-cut inputs

Use a polygon layer, not a point or line layer. Confirm that the polygon dataset opens, includes its required companion files, and overlaps the point cloud in the intended coordinate system. Verify that the selected output-naming field exists and contains values suitable for filenames. Submit a fresh job after correcting the polygon layer or naming field.

4. Check resources or an intentional cancellation

Check free space on both the working and output drives. If a small test succeeds but the full export fails, review memory use, output size, and storage availability during processing. If the job was canceled, preserve or separate any partial output before submitting another run. Cancellation does not guarantee that partially created files have been removed.

📌 Problem

Failed add files to map in Export Job or another completion/post-processing error.

Processing has finished, but completing the job or adding its output to the map fails. Possible messages include:

• Failed to create LASExportSettings object in running Export Job
• Failed to get Map Environment object in running Export Job
• Failed to get cpp interface object in running Export Job
• Failed to cast to cpp object in running Export Job
• Failed add files to map in Export Job
• An unexpected error occurred running Export Job :

🔍 Root Cause

The completion step could not use the export settings, obtain the project environment, or add a generated file to the map. The exported data may already exist. Possible causes include a component problem, unavailable output, damaged settings, or a project/layer access problem.

🧠 What is completion or post-processing?

Some LDE workflows separate background export from completion in LP360. Completion uses the recorded output-file information to add results to the map or, for an overwrite workflow, replace files on the source layer. An error at this stage does not necessarily mean the export itself must be rerun.

✅ Probable Resolutions

1. Verify the original project and exported files

Open the project associated with the job and verify that the output files still exist at their recorded locations. Restore disconnected storage and check read access. Preserve the job's settings and file list until completion is resolved.

2. Retry completion without immediately rerunning the export

After correcting the project or file-access problem, use the job's Complete action if available. Inspect the map first because an earlier completion attempt may have added some output before failing. If a component or interface error persists, save the project, restart LP360 after other processing has finished, and follow the component troubleshooting section.

3. Use manual loading only for a verified, non-overwrite export

If ordinary export files are valid, they may be loaded into the project manually while Support investigates the completion problem. Manual loading does not complete or repair the job record. Do not use it as a substitute for Delete Classes overwrite completion, which has separate source-file replacement behavior.

📌 Problem

No exported LAS files were found for Delete Classes overwrite Complete, or the source layer cannot be found.

A Delete Classes overwrite job cannot be completed. Possible messages include:

• Delete Classes overwrite Complete is missing the source LAS layer name.
• Failed to find LAS layer for overwrite Complete:
• No exported LAS files were found for Delete Classes overwrite Complete.
• Delete Classes overwrite Complete found no surviving LAS files after class filtering.
• Every exported file had 0 points remaining for this layer, so the source layer was not modified.
• Error getting LAS Files interface.

🔍 Root Cause

Completion could not identify or access the source layer, find usable exported LAS files, or match surviving exports to the source files. A missing source-layer name indicates incomplete job information. A layer that was renamed, removed, or is in a different project may not be found. No surviving output can also occur when the class filter leaves no points.

🧠 What is Delete Classes overwrite completion?

Unlike an ordinary export that adds a result layer, overwrite completion replaces files on the existing source layer. Files with no points remaining after filtering may be dropped from that layer. If no usable surviving files are found, the reported completion path stops rather than replacing the source layer with an empty result.

✅ Probable Resolutions

1. Back up the source and restore the expected project context

Before another completion attempt, back up the source LAS files and project. Open the original project and verify that the original source layer exists under the name used when the job was submitted. If it was renamed, restore the expected name only when you can positively identify the correct layer. Do not create a dummy layer just to satisfy the name check.

2. Check the exported LAS files and remaining points

Verify that the job's output folder still contains its exported LAS files and that their names have not been changed. Review the selected classes to confirm that the intended points should remain. If the selection would remove all points, revise it and submit a new job. Preserve existing output while comparing it with the source.

3. Resubmit incomplete jobs rather than editing their metadata

If the job is missing its source-layer name or its recorded inputs no longer match the project, submit a new Delete Classes job after verifying the layer and filters. If a LAS interface or replacement error persists, contact Support before further overwrite attempts. Do not manually delete or replace source files to force completion.

📚 Additional Notes

• Enhanced summaries and all-NoData coverage checks are build-dependent. Older logs may contain only the underlying error and final job status; the same user actions can still apply when supported by that detail.
• For memory/grid-size failures, increase cell size or reduce/split the extent. For a cell larger than a tile, decrease cell size or enlarge the tile. For no overlap, correct the bounds/CRS rather than changing resolution blindly.
• The messages License is available to run LDExport., Starting LDExport Job..., Job Run Post Process:, and Job SUCCEEDED: are informational; they are not error messages.
• A queued job is not necessarily failed. It may be waiting for prerequisites or scheduling. Check its processing message before diagnosing a failure.
• A status-update or completion error can occur after output has been created. Inspect and preserve that output before rerunning.
• Changes to the export configuration generally require a newly submitted job; retrying an existing job can reuse the original saved settings.
• The message Delete Classes overwrite removed ... LAS file(s) that had no remaining points after class filtering. is informational. Verify that this matches the intended class-removal result.
• Possible causes in this article are troubleshooting guidance, not a diagnosis of every instance. Use the specific log detail and a reproducible test to determine the cause.

Related resources: Visual C++ Redistributable troubleshooting and Antivirus Exceptions for LP360.

📬 Need Help?

If you're still stuck, please Contact Support for assistance.

Include the following so Support can identify the failing stage:

• Your LP360 version/build and Windows version.
• The job name, status, failure time, complete log, and a screenshot of the exact error.
• The workflow: ordinary Export, index shapefile, intensity/hillshade, surface export, or Delete Classes overwrite.
• The export type, format, extent, filters, and whether polygon cookie-cut or overwrite was enabled.
• The cell size and its units, interpolation method, requested raster products, tile width/height, and whether cell size was automatic or manual.
• The complete ACTIONABLE FAILURE SUMMARY, including Detail, Input check, paths, Environment checks, Hints, and raster coverage counts if present.
• Whether input, working, and output locations are local, network, or external-drive paths.
• Whether a small test reproduces the problem and whether any output files were created.

Share project data, settings files, or sample point clouds only through the transfer method requested by Support. Do not include passwords, license keys, or other credentials.