Deadline C4D R12 License Server Issues

Hey dear community,

recently I tried to render C4D jobs with version R12 and Deadline 4.1 SP1 and had problems with the C4D License Server. It includes 3 licenses, so rendering with 3 machines at a time is possible. Unfortunately, the render slave log says: 0: STDOUT: Invalid License from License Server 0: STDOUT: Fehlende Seriennummer für 'CINEMA 4D'! ---> (translation: missing serial number for "CINEMA 4D") 0: STDOUT: ---- 0: STDOUT: Invalid License from License Server 0: INFO: Process exit code: 0 0: INFO: Enforcing 64 bit build of Cinema 4D 0: INFO: Finished Cinema 4D Task
I already opened the C4D project on the slave manually and it rendered without issues. Going into “help/personalize/” I can see a valid serial number, only when the slave starts the executable, a license cannot be obtained. Is there any known issue like that? I really can’t help myself :frowning:
Any help is much appreciated.

Further information:
Deadline Repository & C4D License Server running on Windows Server 2003 x64
Deadline Slaves running on Windows 7 Prof. x64
Missing serial number is not reported as an error! So the tasks are instantly marked as completed. Can this be fixed maybe?

Thank you & best regards
dziga

Hi there,

That’s strange that you can start up C4D manually just fine, but it fails to find a license in command line mode. Can you send us a full log from a job that is producing this error? You can the log by right-clicking on the job in the Monitor and selecting Job Reports -> View Log Reports. I just want to see the full log to get a better idea of what’s going on. We can also use the log to set up a proper handler to report an error when C4D complains about a missing license.

Thanks!

  • Ryan

Hi Ryan,

here’s the full slave log:

[code]=======================================================
Log Message

0: Task timeout is disabled.
0: Loaded job: title (000_050_00d_238dcbad)
0: INFO: StartJob: initializing script plugin Cinema4D
0: INFO: Any stdout that matches the regular expression “Error:." will be handled as appropriate
0: INFO: Any stdout that matches the regular expression “.Document not found.” will be handled as appropriate
0: INFO: Any stdout that matches the regular expression “.Error rendering document.” will be handled as appropriate
0: INFO: About: Cinema 4D Plugin for Deadline
0: Plugin rendering frame(s): 0-9
0: INFO: Starting Cinema 4D Task
0: INFO: Enforcing 64 bit build of Cinema 4D
0: INFO: Stdout Handling Enabled: True
0: INFO: Popup Handling Enabled: True
0: INFO: Using Process Tree: True
0: INFO: Hiding DOS Window: True
0: INFO: Creating New Console: False
0: INFO: Enforcing 64 bit build of Cinema 4D
0: INFO: Render Executable: “C:\Program Files\MAXON\CINEMA 4D R12\CINEMA 4D 64 Bit.exe”
0: INFO: Render Argument: -nogui -render "path/file/
.c4d” -frame 0 9
0: INFO: Startup Directory: “C:\Program Files\MAXON\CINEMA 4D R12”
0: INFO: Process Priority: BelowNormal
0: INFO: Process is now running
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Agent does not respond
0: STDOUT: Startup Directory: C:\Program Files\MAXON\CINEMA 4D R12
0: STDOUT: Write Directory: C:\Users#\AppData\Roaming\MAXON\CINEMA 4D R12_1CC4E3E1
0: STDOUT: Preferences Directory: C:\Users#\AppData\Roaming\MAXON\CINEMA 4D R12_1CC4E3E1\prefs
0: STDOUT: Missing serial number for ‘CINEMA 4D’!
0: STDOUT: ----
0: STDOUT: Invalid License from License Server
0: STDOUT: Missing serial number for ‘CINEMA 4D’!
0: STDOUT: ----
0: STDOUT: Invalid License from License Server
0: STDOUT: Missing serial number for ‘CINEMA 4D’!
0: STDOUT: ----
0: STDOUT: Invalid License from License Server
0: STDOUT: Missing serial number for ‘CINEMA 4D’!
0: STDOUT: ----
0: STDOUT: Invalid License from License Server
0: STDOUT: Missing serial number for ‘CINEMA 4D’!
0: STDOUT: ----
0: STDOUT: Invalid License from License Server
0: STDOUT: Missing serial number for ‘CINEMA 4D’!
0: STDOUT: ----
0: STDOUT: Invalid License from License Server
0: STDOUT: Missing serial number for ‘CINEMA 4D’!
0: STDOUT: ----
0: STDOUT: Invalid License from License Server
0: STDOUT: Missing serial number for ‘CINEMA 4D’!
0: STDOUT: ----
0: STDOUT: Invalid License from License Server
0: STDOUT: Missing serial number for ‘CINEMA 4D’!
0: STDOUT: ----
0: STDOUT: Invalid License from License Server
0: STDOUT: Missing serial number for ‘CINEMA 4D’!
0: STDOUT: ----
0: STDOUT: Invalid License from License Server
0: INFO: Process exit code: 0
0: INFO: Enforcing 64 bit build of Cinema 4D
0: INFO: Finished Cinema 4D Task

=======================================================
Log Details

Log Date/Time = Jan 12/11 14:36:08
Frames = 0-9

Slave Machine = Rk09
Slave Version = v4.1.0.43205 R

Plugin Name = Cinema4D

[/code]

Additionally, I attached a screenshot of the Monitor. As you can see, there’s no error listed and the task is marked as complete almost instantly. Thank you for your effort!

Best regars,
dziga

Thanks for the log. We’ll use that to add a handler to catch the “Invalid License from License Server” error in the next Deadline release. To add the handler yourself, go to \your\repository\plugins\Cinema4D and open Cinema4D in a text editor. Look for this line:

		self.AddStdoutHandler(".*Error loading document.*",self.HandleStdoutError)

Insert a new line after this line, and add a new handler for the license error, like this:

		self.AddStdoutHandler(".*Error loading document.*",self.HandleStdoutError)
		self.AddStdoutHandler(".*Invalid License from License Server.*",self.HandleStdoutError)

Save the file, and Deadline should catch this error in the future. Now we just need to figure out why you’re getting this error. Note that all Deadline is doing is performing a command line render, so for testing purposes, we’ll get you to do the same without Deadline. Go to a slave that is reporting this error, open a command prompt, and run this command:

"C:\Program Files\MAXON\CINEMA 4D R12\CINEMA 4D 64 Bit.exe" -nogui -render "path/file/*.c4d" -frame 0 9

I’m assuming you changed the path to the c4d file in the log for privacy reasons, so just make sure to point to a valid c4d file for this test. If you get the same licensing error, then at least we know it’s a C4D problem, and not a Deadline problem. Let us know how the test goes.

Cheers,

  • Ryan

Hey,

ok, it isn’t a Deadline issue as I get the same message when rendering via command prompt. That’s good to know :slight_smile: I’ll do some research on rendering C4D files with r12 & Licenseserver, maybe someone else has experienced this issue before.
Thanks for helping me and for the C4D script line.

Best regards,
dziga

I found an interesting quote

. So, possibly we didn’t get the command line license with the server and need to request it first.

Thanks for the information! We weren’t aware of this, so we’ll update our FAQs appropriately!

I contacted Maxon and will report the facts here.

p.s.: Did someone tackle the integrated drive mounting issues already? We had a discussion about that a few months ago :slight_smile:

Thanks for your effort again!

dziga

My memory of our previous discussion is a bit fuzzy, but there was a problem with the Drive Mounting feature in 4.1 where the password was getting garbled. That will be fixed in Deadline 5.0, which went into beta today: viewtopic.php?f=10&t=4497

Cheers,

  • Ryan

Applied for beta testing :wink: