Aximmetry Crashes in Multi-Mac | Forum

Aximmetry Crashes in Multi-Machine Environment Due to Unmapped Network Volume

Hello everyone,

I am currently working with Aximmetry in a multi-machine environment, where all the machines access project files and resources from a centralized Synology NAS RackStation RS2423RP+. We have a shared folder on the NAS, mapped as the Z: drive on each machine, called AXSHARE, which contains all the Aximmetry projects and resources.

The issue arises when I make changes to a completely separate volume called FOGREPO on the same NAS. This volume is not mapped on any of the Aximmetry machines and they do not have read or write permissions to it. However, whenever there is a modification on FOGREPO, Aximmetry crashes, even though the machines have no direct access to this folder.

It seems like Aximmetry is somehow detecting file changes on a volume it should not be monitoring, leading to instability. I’ve already verified that there are no explicit references to FOGREPO in my project files, and only AXSHARE is set as the project directory.

Has anyone encountered a similar issue? Any ideas on how to prevent Aximmetry from detecting or reacting to changes on unmapped volumes?

Thanks in advance for your help!

DTCTV

Eifert@Aximmetry

Hi,

If you receive a prompt window to generate a dump file when the crash happens, please share that file with us. You can do so by sending it to sales@aximmetry.com. It will greatly aid us in figuring out the issue. We've attempted to recreate the crash using some permission changes, but haven't had any success.

Note that it could be that you have a folder or file within the shared folder that is linked to the FOGREPO volume.
In Command Prompt, you can use the dir /S /A:L command to locate such files and folders.

Besides the project root folders, Aximmetry also monitors the Favorites, Recent folders, and any folder currently viewed by the File Browser. You can remove folders from Favorites and Recents by right-clicking on them.

Warmest regards,

DTCTV

Hi,

Thank you for your response and suggestions. I have gathered a bit more information regarding the issue.

To clarify, it's not exactly a crash as I previously described. What happens is that the Render engines lose connection with the main engine, displaying an error message stating that a modification has been detected on the shared folder containing Aximmetry resources on the NAS, even though no changes were made to that folder.

In parallel, some colleagues were working on a different NAS volume (FOGPROJECT). Their activity was minimal and only involved creating directories and writing small files in this separate volume to prepare for machine imaging using the FogProject service. There was very low bandwidth usage, so it shouldn't normally impact the shared AXSHARE volume.

I will try to replicate the issue by asking them to repeat the same actions and see if I can reproduce the disconnection. If it happens again, I will generate a dump file as you suggested and share it with you.

Thank you again for your help!

Aximmetry Crashes in Multi-Machine Environment Due to Unmapped Network Volume

Cookie consent