Upload or Download XFR job fails because qpTransfer terminated

📌 Problem

When attempting to upload or download data to/from LP360 Cloud, the XFR job fails with the message, "qpTransfer terminated", followed by a number.

🔍 What Is “qpTransfer terminated”?

This error refers to a failure in the qpTransfer.exe process, which is part of the LP360 software suite used for geospatial data processing. The termination typically occurs during data transfer jobs, especially when handling large datasets or encountering system-level issues. The number describes the process ID so will change.

🛠️ Troubleshooting Guidance

• Check for Windows fail events related to qpTransfer.exe.
• Look for .dmp crash files in %LocalAppData%\CrashDumps.
• Update the x64 Microsoft VS C++ Redistributable.
• Review the _log.txt file from the XFR job in the Job Manager for diagnostics.

✅ Probable Resolutions

1. Update the x64 Microsoft VS C++ Redistributable:

Outdated Microsoft VS Redistributable on a machine may cause components of LP360 to crash. Update your x64 Microsoft VS C++ Redistributable, then attempt the process again.

2. Ensure the AWS Settings are valid:

If the XFR log entries showing "upload chunk size: 0MB" and "request timeout: 0s" as invalid. These values indicate a misconfiguration that can prevent successful uploads. Although the correct values may appear in the dialog, they are not saved into the underlying settings file used by the job. This is a known issue in LP360 v2025.1. Apply the settings, toggle them back to valid values (e.g., 5MB for chunk size and 15s for timeout), and apply again to force the update.

Here’s a step-by-step fix based on your guidance and support documentation:

1. Open LP360 Project Settings .
2. Navigate to TrueView → AWS Settings.
3. Set:
   • Upload Chunk Size to a valid value (e.g., 5MB or 10MB).
   • Request Timeout to a reasonable value (e.g., 15s).
4. Press Apply.
5. Retry the upload.
6. If it doesn't work, then toggle the values again and re-apply to ensure they persist.

📬 Need Help?

If you're still stuck, please Contact Support for assistance and provide the latest dmp file found in your in %LocalAppData%\CrashDumps folder which has qpTransfer in the name.