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.