Troubleshooting KeyShot Network Rendering Archive Creation Errors
Issue
When attempting to send a render to the Network Rendering queue in KeyShot, the following error message appears:
"Could not create archive for name.nrext! Make sure you have enough disk space."
Despite having sufficient disk space (e.g., 60GB or more), the issue persists, and the job does not reach the render queue.
Environment
-
KeyShot Studio (Any Version)
-
KeyShot Network Rendering (Manager, Worker, and Client)
-
Windows operating system (paths referenced are for Windows, but troubleshooting steps may apply to macOS/Linux)
Cause
The error message may not refer to total disk space but instead to a specific folder where the archive file (.nrext) is being stored. Possible causes include:
-
Insufficient permissions – The user may not have the necessary write permissions to the "Scenes" folder.
-
File name or character issues – Special characters or excessively long file names in the project files may cause archiving failures.
-
Antivirus interference – Some antivirus software may block or delete the .nrext file type, preventing the rendering process from completing.
-
Corrupt resource files – A problematic file in the scene could be preventing the archive from being created.
Resolution
Step 1: Verify Rendering via Background/Queue
-
Try rendering with Background Rendering or Add to Queue instead of Network Rendering.
-
Check if the same error occurs.
-
If successful, navigate to the Scenes folder (default location:
C:\Users\Public\Documents\KeyShot Studio\Scenes
) and check if aq.xml
and a*.ext
file appear.
Step 2: Test Saving as a KSP File
-
Attempt to save the project as a KeyShot Package (.ksp) file.
-
If saving fails, check for special characters or long file names in the project files and rename them as necessary.
Step 3: Check Folder Permissions
-
Verify that the user has full write permissions to the Scenes folder.
-
Adjust permissions if necessary.
Step 4: Disable Antivirus Temporarily
-
Disable the antivirus software and try sending the render to the queue again.
-
If this resolves the issue, add an exception in the antivirus settings for
.nrext
files or the KeyShot directory. -
Re-enable the antivirus and check if the issue remains resolved.
Step 5: Review Network Rendering Logs (If Issue Persists)
If the issue is unresolved, gather Network Rendering logs from both the Manager and Worker machines and review for additional errors. Logs can be found in:
-
Windows:
C:\Users\Public\Public Documents\KeyShot Network Resources\Logs
-
macOS:
/Library/Application Support/KeyShot Network Resources/Logs
-
Linux:
/var/local/share/KeyShot11NetworkResources