Flame 2026.2 – Project Creation Fails on AutoFS Mount (/ProjectServer/projects) Despite Matching Permissions

Sysadmins General
1

Hi all,

I’m running into an issue with Flame 2026.2 and Project Sharing that doesn’t seem to line up with the current documentation, and I’m hoping someone else has seen this behaviour.

Setup Overview

We’re using a central Project Server to host all Flame project metadata.
The configuration looks like this:

Project Server

  • Local storage at:
    /<storage>/flame/projects

  • This path is exported over NFS to all workstations.

Workstations

  • AutoFS mounts the Project Server export to:
    /ProjectServer/projects

  • GPFS is mounted locally on each workstation for media and cache paths (matching the same location on the Project Server but exported via NFS).

  • Permissions on both locations are identical:

    • /hosts/<ip>/flame/projects

    • /ProjectServer/projects

Documentation vs. Actual Behaviour

According to the Flame 2026 documentation:
https://help.autodesk.com/view/FLAME/2026/ENU/?guid=project-sharing

Recommended mount paths for shared project metadata and media are:

/mnt/<hostname>/projects
/mnt/<hostname>/media

And the documentation clearly states that /hosts/<host>/… should not be used.

However, Flame only allows project creation using the /hosts/<host>/... path.
When I try to create a project using the correct AutoFS mount at /ProjectServer/projects, Flame fails with this error:

image
image486×320 13.8 KB

Failed to clone /opt/Autodesk/presets/2026.2/expressions ->
/ProjectServer/projects/Test1/setups/expressions

Everything about the mount is working normally (read/write confirmed, ownership and permissions identical on both paths). The failure seems specific to Flame’s ability to clone the setups directory during project creation.

Questions

Before I file a ticket, I’d like to know:

  1. Has anyone else successfully created projects on a non-/hosts/... AutoFS mount in 2026.x?

  2. Is the 2026 documentation still accurate regarding recommended mount paths?

  3. Is Flame now expecting /hosts/<host>/... even though /ProjectServer/projects is fully writable and mounted correctly?

  4. Is this a known limitation or a regression?

Any insight or examples of working configs would be greatly appreciated.

Thanks!

2

if you’re copying from a local workstation from /opt/Autodesk/presets/2026.2/expressions
i think this directory is owned by root
and may interfere with your other permissions

what happens if you use wiretap to create projects on ProjectServer?

project creation via command line

it could also be the users in the postgresdb

3

Thanks for the suggestion, but Wiretap/IFFFS isn’t available on this Project Server setup. The INSTALL_PROJECTSERVER script installs only the minimal services needed for NFS-based project sharing, not the full Flame installation with Wiretap support. So correct me if I’m wrong but I don’t think command-line project creation via Wiretap isn’t an option here.

Regarding the /opt/Autodesk/presets/2026.2/expressions ownership: you’re right, having it owned by root is expected and consistent with our other 2025.X Flame installations. That alone wouldn’t explain the clone failure or why it works fine with the /hosts/ path.

4

We spent some over zoom with Laurence and he is now up and running using /hosts//

We are investigating why the original mount for the Project server is not behaving the same way as /hosts.

1 Like