Cineversity

So is there some trick to getting R21 Team Render to run? I have tried a few times to run the EXE and the program never starts, or at least I never see the interface. Same with the client. I can run Team Render through the C4D interface, but not the standalone server. I’m thinking maybe this is something to do with the new licensing?

I imagine its user error on my part, so hopefully its a simple fix.

Thanks for your help!

Michael Stafford

Hi Michael,

Sorry to hear about your trouble. This is a problem for the Support team, I’m not supposed to handle those.
https://www.maxon.net/en/support-center

Fingers crossed you are up and running in no time.

Cheers

Thanks Sassi, I’ve created a support ticket. I’m sure its something simple, but I’ve never had this issue before, so its a little baffling. I’ll post back here once I find the fix in case anyone else has the issue.

Thanks!

Thanks for the offer, Michael, very kind of you.

Thanks as well as for your patience, it was a huge transition to get all of that to work. People like you, with a vast production-experience, know how this leads sometimes to leave even essential details behind.
There is always more than the surface might show (But I state the obvious, sorry about that). I’m grateful for your way of responding to it.

My best wishes.

OK, so we’ve got to the bottom of this and I can run TeamRender Standalone now.

Issue: The drive I’m running C4D on is a fairly small SSD, so I like to keep large amount of content files on a separate drive. The way I have been doing this is using a NTFS Junction to “point” the Maxon prefs folder to a different location. When C4D or Teamrender or The TR client or the commandline Renderer are run for the first time they setup a bunch of files in this directory. Apparently they are unable to do this when using a NTFS Junction. I was able to discover this was the issue when I ran the commandlind renderer and it spit out an error code to the console indicating it couldn’t create the files it need to and then promptly quit.

Solution: The solution was fairly simple. I deleted the NTFS Junction and ran all the standalone rendering applications. This allowed them to create the folder/files they needed to. I copied those files over to my Junction location, deleted the Maxon folder and then recreated the NTFS Junction. Voila! Everything runs fine.

It seems like this really shouldn’t have been an issue. Maxon is aware of the issue so maybe they can figure out why the EXE’s can’t create the folder structure needed when using a Junction to move the heavt content folders somewhere custom, or it would be nice if there was actually an option to select this location when you install the program, but either way I can make it work.

So anyway, if you have relocated the content folders somewhere else using an NTFS Junction and you are having issues running the apps, heres your solution.

Thank you very much, Michael, I hope that will help others to get quickly over this obstacle. I’m very glad you got it working!

It was clearly the right action to route this to the support. For many reasons.

My best wishes and hope the render farm is not running too hot this weekend.

Sorry to ask this, but how and where do I get an installer for Team render with this new subscription service. When I download the normal installer it doesn’t give me an option to install a client? Please help!

Found a more appropriate thread for this here…

https://www.cineversity.com/forums/viewthread/3575/

Hi steveb at sbdesigns dot ca,

The link that you posted in (post #6)  is the forum’s thread where I have answered your question.

I hope you have it running in no time.

Cheers