Error: “3dsmax adapter error – The pipe has been ended – 109 3dsmax adapter error – 3dsmax.exe process no response.”

The "3dsmax adapter error: The pipe has been ended: 109" message appears in Backburner Server logs when 3ds Max fails to communicate with the Backburner rendering system. It means 3ds Max launched on the render node, attempted to open the scene, but the process died or became unresponsive before rendering could begin.

This error is generic — Backburner reports it whenever the 3dsmax.exe process stops responding to the adapter, regardless of the actual cause. Diagnosing it requires checking what went wrong inside 3ds Max itself.

What Causes the Error

The Backburner adapter launches 3dsmax.exe on each render node, sends it the scene file, and waits for a response. If 3ds Max crashes, hangs on a plugin dialog, or fails to load a required component, the communication pipe between the adapter and 3dsmax.exe breaks — resulting in the "pipe has been ended: 109" error.

Common triggers include:

• Plugin conflicts. A plugin installed on the render node crashes during scene loading. A frequently reported offender is the Autograss plugin for V-Ray (by Happy Digital, now discontinued but still installed in some studios), which can cause 3ds Max to hang on nodes where V-Ray is rendering without Autograss assets present.
• Mental Ray 2018 remnants. Older Mental Ray installations leave behind DLLs that conflict with current versions of 3ds Max. Even if Mental Ray is not the active renderer, its startup components can interfere with scene loading.
• Backburner version mismatch. Old Backburner user folder files from previous 3ds Max installations can confuse the current version. If the render node was upgraded from a previous 3ds Max version without cleaning Backburner data, the adapter may fail to initialize correctly.
• Missing plugins or licenses. If the scene requires a plugin that is not installed on the render node, 3ds Max may show a "Missing Plugin" dialog — which blocks the automated Backburner process because no user is present to click "OK."
• Corrupt scene file. In rare cases, the scene file itself causes 3ds Max to crash on load, which the adapter reports as a pipe error.

Solutions

Remove or Disable the Autograss Plugin

If you are rendering with V-Ray and have the Happy Digital Autograss plugin installed on render nodes, disable or remove it. Navigate to the 3ds Max plugins directory on the render node, find the Autograss DLL files, and move them to a backup folder. Restart the Backburner Server service and re-submit the job.

This is the single most common fix for this error in V-Ray production environments.

Uninstall Mental Ray 2018

If Mental Ray 2018 is installed alongside a newer version of 3ds Max, uninstall it through Windows Programs and Features. Mental Ray 2018 installs shader DLLs that load at 3ds Max startup and can conflict with V-Ray, Corona, or Arnold. If you need Mental Ray for legacy scenes, use a dedicated machine rather than sharing render nodes with modern renderers.

Clean Backburner User Data

Delete the Backburner user folder on the affected render node(s). The default location is C:\Users\[username]\AppData\Local\Autodesk\Backburner\. Removing this folder forces Backburner to regenerate fresh configuration files. Restart the Backburner Server service after deletion.

Reset Backburner

If cleaning user data does not help, perform a full Backburner reset:

1. Stop the Backburner Manager and Server services on all machines
2. Uninstall Backburner through Windows Programs and Features
3. Delete remaining Backburner folders in C:\Program Files\Autodesk\Backburner\ and AppData
4. Reinstall Backburner from your 3ds Max installation media
5. Restart services and re-submit the job

Check for Missing Plugins

Open the scene file on a workstation and check for "Missing Plugin" warnings. If you also see missing external file errors, resolve those first — missing textures can compound plugin failures on render nodes. Any plugin that triggers a dialog box will block Backburner's automated process. Either install the required plugin on render nodes, or remove the dependency from the scene before submitting.

Modern Alternatives to Backburner

Backburner is Autodesk's built-in network rendering tool. While it ships free with 3ds Max, it has received limited updates in recent years compared to third-party alternatives. Studios dealing with frequent adapter errors often evaluate modern render management systems such as Thinkbox Deadline, Royal Render, or cloud render farms — these tools typically handle plugin dependency resolution, version control, and automatic error retries at the job scheduler level, which reduces the manual debugging Backburner requires.

FAQ

Q: What does "The pipe has been ended: 109" actually mean? A: It means the communication channel between the Backburner adapter and the 3dsmax.exe process on a render node was terminated unexpectedly. This is a generic error — Backburner does not know why 3ds Max stopped responding. The actual cause is inside 3ds Max itself, typically a plugin crash, missing file dialog, or license issue.

Q: How do I identify which plugin is causing the crash? A: On the render node, open 3ds Max manually and load the same scene file. Watch for any dialog boxes, plugin errors, or crashes during loading. If 3ds Max hangs at a specific point, check which plugins are loaded using Customize > Configure System Paths > 3rd Party Plug-Ins. Disable plugins one at a time until the scene loads successfully.

Q: Can I still use Backburner with recent versions of 3ds Max? A: Yes. Backburner continues to ship with 3ds Max and functions for network rendering. However, Autodesk has not added significant new features to Backburner in recent years. If your studio is growing or encountering frequent errors, evaluating a dedicated render manager like Thinkbox Deadline or Royal Render — or a cloud render farm — may reduce the time spent on troubleshooting.

Q: Does this error affect cloud render farms? A: No. Cloud render farms do not use Backburner — they use dedicated render management software that handles plugin loading, error detection, and automatic retries without the adapter architecture that causes pipe errors. The "pipe ended" error is specific to Backburner's communication model between the adapter and 3dsmax.exe.

Q: How do I check Backburner logs for more details about the error? A: Backburner Server logs are stored in the Backburner installation directory, typically C:\Program Files\Autodesk\Backburner\. Open the server log file for the affected node and search for entries around the time of the failure. The log often reveals the specific DLL or plugin that caused 3ds Max to crash before the pipe ended. You can also check the Windows Event Viewer (Application log) for 3dsmax.exe crash records.

Last Updated: 2026-03-17