AWS Thinkbox Discussion Forums

Houdini deadline command trying to create invalid deadline.ini

We recently migrated to a new deadline repository and since then have been seeing some odd/inconsistence errors in our houdini jobs. It’s specifically occurring in the Houdini plugin’s file. When it tries to execute a CallDeadlineCommand for -CheckPathMapping in the files it creates “path_pathmap.txt” for example, it throws an error on most of our render nodes.

2022-06-15 15:10:24:  0: STDOUT: System.UnauthorizedAccessException: Access to the path 'C:\Program Files\Side Effects Software\Houdini 18.5.596\bin\Thinkbox\Deadline10' is denied.
2022-06-15 15:10:24:  0: STDOUT:    at System.IO.FileSystem.CreateDirectory(String fullPath, Byte[] securityDescriptor)
2022-06-15 15:10:24:  0: STDOUT:    at System.IO.Directory.CreateDirectory(String path)
2022-06-15 15:10:24:  0: STDOUT:    at Deadline.Configuration.DeadlineConfig.h(String dey)
2022-06-15 15:10:24:  0: STDOUT:    at Deadline.Configuration.DeadlineConfig.CheckConfigFile(Boolean allUsers)
2022-06-15 15:10:24:  0: STDOUT:    at Deadline.Configuration.DeadlineConfig.GetIniFileSetting(String key, String defaultValue, Boolean errorOnNoConfig)
2022-06-15 15:10:24:  0: STDOUT:    at Deadline.DeadlinePythonRuntime.ResolvePythonVersion(DeadlineApplication application, String commandLineArgument)
2022-06-15 15:10:24:  0: STDOUT:    at DeadlineCommand.DeadlineCommandAppStartup.Main(String[] args)

Out of curiosity I created that folder at that location just to see why it would be trying to access this directory that does not exist, and the error changed slightly:

Creating default config file:Thinkbox\Deadline10\deadline.ini
2022-06-16 11:15:26:  0: STDOUT: Error writing ini file: Access to the path 'C:\Program Files\Side Effects Software\Houdini 18.5.596\bin\Thinkbox\Deadline10\deadline.ini' is denied.

Which makes me think that these machines are maybe not discovering the existing deadline.ini files in their usual locations. I verified that the deadline.ini files do in fact exist where they normally would- programdata and localappdata.

I’m a bit stumped now as to why this plugin is attempting to access/create files at that location, other than it being the startup directory for the plugin and the relative path it’s using in that output ^. Does this mean the deadline command is not finding the usual deadline.ini files it would check so it’s making a new one? Is this a bug?

1 Like

Huh, that’s weird, looks like a bug. This should be ProgramData, not Program Files.

Privacy | Site terms | Cookie preferences