Hello Guys, I stack here. I made a custom AMI and loaded the exact Cinema 4D version and Redshift. When I try to load a spot fleet the AWS workers appear but they don’t render. The logs write this message: Scheduler Thread - Could not initialize usage-based licensing for cinema4d. The UBL credentials are not set for the repository. (System.Exception). I have attached all the logs and my UBL settings. I have put my URL and my Activation code into the Configure repository options. I also have a limit for UBL.
Could you check out the steps mentioned in this thread - Render nodes can't get UBL license | AWS Portal | Arnold? This sounds really similar to that thread’s trouble.
Thanks for the reply. I try to run these commands in Powershell but I get this error. Also, I looked for an article on how to run these commands but couldn’t find anything.
I also believe that the error is about the Identities and roles. I read from an article that the gateway instance must have a server role. Is this correct? Also, I see that I don’t have an administrator OS user in the manage identities window like tutorials from Thinkbox. I only have one OS user. Is this important?
Update: I run the commands but nothing happened. I get the same error.
After running the command you need to put in your password, I wonder if powershell is eating the prompt?
For example in command prompt I get:
Anyways - what do you see in the Monitor logs after trying to set the URL and access code?
Yes, I put in the admin password and I got a successful message. I all run it Comand Prompt. I have attached the monitor logs. Thanks,
Also to summarize: I want to run AWS Workers and my PC as a worker with Cinema 4D and Redshift. I create a custom AMI with my exact version of C4D and Redshift and run this Custom AMI. I didn’t install License Forwarder because I run the gateway instance from AWS which will act as License Forwarder. Is this Right? I also assign the gateway instance and my PC a server role only and for all other workers a client role. Also, I didn’t install any RLM (Floating) License server because I only have my Standard Subscription with Maxon. Is it something that I missed or something that I didn’t understand?
UPDATE: I also noticed that I try to deactivate Dynamic Licensing in configure repository options and when I restart monitor, launcher and worker the setting don’t change. I try it many times but I cannot deactivate it.
Finally Solved.
This is the solution:
After I have done all commands in command prompt I re-enter the URL and Activation Code in Repository Options-UBL and Finnaly it worked.
Thanks Justin
1 Like