Deadline Monitor Support for Apple M1

Hi there,

I’d like to use Deadline Monitor on mc MacBook Pro (13-inch, M1, 2020) running Monterey.
However it seems that the current Build of Deadline Monitor for Mac is not compatible with M1 as I get a bunch of python errors when trying to launch the Monitor.
On my PC I dont get any error message connecting to the same Repo.

Here is the error message that I get on my M1 Mac:

Time to initialize: 659.000 ms
Auto Configuration: No auto configuration for Repository Path could be detected, using local configuration
ERROR: DataController threw a configuration exception during initialization: The specified repository path (/Users/goetzmoritz/deadline) does not contain the necessary database connection settings file.

There may be a network issue, or a valid repository has not been installed at this location. If one has not yet setup a repository, it is possible to do so using the repository installer included in the installation files. (Deadline.Configuration.DeadlineConfigException)
Traceback (most recent call last):
  File "UI/Forms/", line 147, in Startup
  File "C:\thinkbox-conda\conda-bld\deadline_1634169462354\work\DeadlineProject\DeadlineUI\Forms\", line 68, in __init__
ApplicationException: Error encountered when trying to open or create config file '/Users/Shared/Thinkbox/Deadline10/dconf.bin':
Access to the path '/Users/Shared/Thinkbox/Deadline10/dconf.bin' is denied.
   at FranticX.Security.ProtectedConfig.RefreshConfig(Nullable`1 timeout)
   at FranticX.Security.ProtectedConfig..ctor(String configFilePath, Boolean isUserScope)
   at Deadline.Configuration.DeadlineConfig.b(Boolean dec)
   at Deadline.Configuration.DeadlineConfig.RefreshProtectedSettings(ConfigLevel level)
   at Deadline.Configuration.DeadlineConfig.RefreshProtectedSettings()

Listener Thread - OnConnect: Listener Socket has been closed.

Thanks for checking out!


Seems to me that the cause is not having permissions to write to /Users/Shared/Thinkbox/Deadline10/dconf.bin and/or the repo is not configured to connect to the database. So not sure it’s caused by the particular platform.

Your observation is correct, actually it is due to the weird way my Mac is setup (company restrictions). This topic is closed, thank you @mois.moshev

Privacy | Site terms | Cookie preferences