AWS Thinkbox Discussion Forums

Deadline Repository Sudden Connection Issues

So I recently got Deadline working on my local network about a month ago and it has been working great. But last weekend suddenly a bunch of connection errors started to occur. Earlier in the day all of the nodes were connected and visible on the Deadline Monitor but then all of my render nodes could no longer connect to the repository, and I hadn’t changed anything about the repository or the computer that hosts the repository. I tried uninstalling and reinstalling both the clients and the repository, but the exact same issue persists. I continue to get this error when I try to run Monitor or Worker

The Monitor was unable to connect to the specified Repository (\FHS-W001\deadlinerepository).

Failed to register the client with the selected repository. Consult log files for further information.
at Deadline.Applications.DeadlineApplicationManager.RegisterIdentity()
at Deadline.Applications.DeadlineApplicationManager.CreateDataController(RepositoryConnectionSettings connSettings)
at Deadline.Applications.DeadlineApplicationManager.Connect(RepositoryConnectionSettings connSettings, Boolean updateScriptManager)
at Deadline.Monitor.MonitorManager.Connect(RepositoryConnectionSettings connectionSettings, Boolean updateScriptManager)

And when I go to check the Logs I see this

2022-05-09 09:28:51: BEGIN - FHS-003\FHS_Render
2022-05-09 09:28:51: Operating System: Windows 10 Pro
2022-05-09 09:28:51: CPU Architecture: x64
2022-05-09 09:28:51: CPUs: 20
2022-05-09 09:28:51: Video Card: NVIDIA GeForce RTX 3090
2022-05-09 09:28:51: Deadline Monitor 10.1 [v10.1.21.4 Release (690edd3fe)]
2022-05-09 09:28:51: Time to initialize: 94.000 ms
2022-05-09 09:28:55: Auto Configuration: No auto configuration for Repository Path could be detected, using local configuration
2022-05-09 09:28:55: Error: Failed to register the client with the selected repository: Key not valid for use in specified state.
2022-05-09 09:28:55: at Deadline.Applications.Identity.IdentityContext.e()
2022-05-09 09:28:55: at Deadline.Applications.Identity.IdentityContext.d()
2022-05-09 09:28:55: at Deadline.Applications.Identity.IdentityContext…ctor()
2022-05-09 09:28:55: at Deadline.Applications.Identity.IdentityContext.<>c.a()
2022-05-09 09:28:55: at System.Lazy1.ViaFactory(LazyThreadSafetyMode mode) 2022-05-09 09:28:55: at System.Lazy1.ExecutionAndPublication(LazyHelper executionAndPublication, Boolean useDefaultConstructor)
2022-05-09 09:28:55: at System.Lazy1.CreateValue() 2022-05-09 09:28:55: at System.Lazy1.get_Value()
2022-05-09 09:28:55: at Deadline.Applications.Identity.IdentityContext.GetInstance()
2022-05-09 09:28:55: at Deadline.Applications.DeadlineApplicationManager.RegisterIdentity()

I have several nodes that are all displaying this same thing.

I then decided to install a client onto the computer that is acting as the repository to see if it has the same issue. But no, when I install the Client onto the Repository computer it connects to the repository just fine and shows up in the Deadline Monitor as a worker.

What can I do to fix this issue?

EDIT- After messing around a bit more it seems that when I’m logged onto the main/admin account for the nodes that the client connects to the repository without any issues. But if I’m logged into a different account on the computer that the client will not connect to the repository and throw this error. I’m not sure why this would be the case, especially since earlier I was able to connect to the repository using either account on the nodes, and the only thing that I recently changed was stripping admin privileges on the secondary accounts. But even then for a time I was still able to connect to the repository with no issues on the secondary accounts, and re-adding admin privileges to these accounts does not in fact fix the issue.
And even worse it seems that SOME of the render nodes can be logged into this secondary account and connect to the repository, while others can not.

Privacy | Site terms | Cookie preferences