Troubleshooting XFR Upload Failures Caused by File Locking or Read‑Only Requirements

📌 Problem

When running an Upload to Cloud or Upload to Support operation in LP360 or as a child job to another process, such as Post Process Trajectory Processing , the XFR job may fail during the archive‑creation phase. This failure occurs before any upload begins and is almost always caused by locked or read/write project files inside the LP360 project directory.

A typical log for this failure looks like:

[ ] Zip archive contains 1 entries of 8
[ ] Unable to include all files into the archive. Verify that your selected files are set to read only.
[ ] Cannot create archive.
[ ] Failure Uploading to Cloud – <archive>.7z

In this scenario, the XFR job cannot build the 7‑zip archive because some project files are being held open by LP360, Windows Explorer, antivirus, or another application.

Symptoms

You may observe one or more of the following:

• XFR job fails immediately after “Zipping up the folder…”
• Log reports a mismatch between the number of files expected vs. archived
  Example: “Contains 1 entries of 8”
• Error explicitly states:
  “Unable to include all files into the archive. Verify that your selected files are set to read only.”
• The upload fails without reaching the transfer phase
• Archive <name>.7z is never created

🔍 Root Cause

The failure is caused by file locking or read/write access on one or more files in the selected upload directory. Archiving requires all files to be readable and not held open for write.

Files may be locked because:

• LP360 has the LAS or project files open in Read/Write mode
• Another program has open files
• Windows Explorer preview panels are holding file handles
• Antivirus or backup software is scanning the folder
• Files reside on network storage (e.g., L:\) with restricted permissions or delayed file-handle release

Older versions of LP360 did not automatically reopen LAS files as read‑only, resulting in skipped entries and zip failures. Newer builds prompt users to switch files to read‑only, but manual correction may still be required.

✅ Probable Resolutions

Follow these steps in order—they address nearly all known causes.

1. Close All Applications That Could Lock Files

Before retrying:

• Close LP360
• Close POSPac
• Close any other software pointing to the project folder
• In Windows File Explorer:
  • Disable Preview Pane
  • Disable Details Pane
• Temporarily pause real‑time antivirus scanning for that folder if company policy allows (AV can hold handles).
  • Review antivirus and defender program settings and allow exceptions as necessary.

This eliminates common cases where applications continue holding write‑locks.

2. Set Project Files to Read‑Only

Make the files read‑only before uploading:

Option A – Inside LP360 (Recommended when LAS layers are part of a project)

1. Open LP360
2. In the LAS Files window, verify all LAS files are marked R/O
3. If any are R/W, change them to R/O
4. Retry the upload

Option B – In Windows Explorer

1. Right‑click the folder (e.g., POSPac_260114_140512)
2. Select Properties
3. Set files to Read‑only
4. Apply to Files only
5. Retry the upload

3. Move the Output to a Local Path (If Necessary)

If the data resides on a network drive (e.g., L:\LP360 Projects\…):

1. Copy the entire folder to a local path such as C:\Temp\POSPac_260114_140512
2. Retry the upload from the local location

This eliminates network share permission delays and path‑length issues.

4. Confirm Adequate Disk Space

The archiver needs space to create the .7z file.

Check:

• System temp drive (%TEMP%)
• The drive containing the source folder

Ensure several gigabytes of free space.

5. Update LP360 to the Latest Build

Recent releases have improvements that:

• Automatically reopen LAS files as read‑only
• Detect and warn when files are locked
• Improve Upload to Support user guidance
• Fix incomplete archive creation for edge cases

If you are running an older 2025.2 or earlier build, update before retrying.

6. Re‑run the Upload and Monitor via Job Manager

After submitting the upload, open Job Manager to confirm background progress.

Newer releases include an option to launch Job Manager directly after submission to reduce confusion.

📬 Need Help?

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

Collect the following information and provide it to LP360 Support:

• The full list of files in the folder
• The LP360 version
• Whether the project resides on a network drive
• Available free disk space on source and system drives
• The full XFR job log