finalrender doesn't want to render?

Deadline
1

I’m getting the code below when I try to render something with finalrender.
It renders without a problem locally, but doesn’t seem to want to work via deadline.

what am I missing?

2

Hi,

3dsMax needs to be started with Administrative rights the first time it runs. Please try either running 3ds Max as administrator (right-click on 3dsmax.exe → “Run as administrator”) or disable User Access Control (UAC) (requires reboot).

Also a couple of other things I noticed:

  1. Your running the base version of 3dsMax 2014, which is 5 x service packs behind. I’d recommend updating to get all those Autodesk fixes…
  2. Your running Deadline v6.2.0.18, which is quite a few versions (9 x versions to be precise) behind the now public release of v6.2.0.32.

Hope this helps!
Mike

3

yeah i know, need to keep track of all new versions :slight_smile:
but that proves challenging when busy with deadlines…

the funny thing is that i can render vray and sim fumefx with the current setup…

4

ok, everything is up to date. but on my workstation/win8 machine it still gives the elevated error.

The windows 7 machines do run the job properly.

5

Hi,

Did you try this on the machine? If it’s still not working, then I think it’s down to the non-standard software install location: “C:\Software\Autodesk” and a lack of security permissions and/or ownership in the directory structure. Probably wise to make a backup before attempting a change here. I would look at flushing the permissions and ‘ownership’ of this entire directory structure to ensure all the files (including 3dsmax.exe) have the correct permissions and can elevate themselves during start-up.

Mike

6

Mmmh, the odd thing only is that it does work with the Vray and any other max job.
I’ve had some fights with the win8 UAC, but besides this all works ‘normal’ now.

I think i’ll just leave it then and only render on the other machines… no wish to break stuff that is working in all other situations.

7

Yep, understood. My thought was not so much that 3dsmax.exe is complaining about needing elevated permission as it’s already working for Max/VRay, but rather that the FinalRender components are demanding this elevated level when the plugin is instantiated within the 3dsMax environment, but as it’s effectively running within 3dsMax, then it’s this executable which complains about access. I was hoping that running 3dsMax on your machine once “as Administrator, via the right-click menu” would sort it out for you. With regard, UAC in Win8. I understand that you can’t really turn it off completely in Win8 and lowering it’s interaction, just ends up potentially causing more problems further down the road.

I would get in touch with the Cebas guys and perhaps clarify that your version of Final Render is compatible with Win8 or is this a known issue with Final Render in Win 8?

Let us know if you find anything out!

Hope this helps!
Mike

8

mmh… funny thing… just now put a vray in the queue… doesn’t work either anymore.
2 days ago was the last time I used my machine in a render with deadline and then it all worked properly.

I do recall that at some point that 3dsMax was complaining about the admin rights so I enabled start as admin again on the .exe file.
This just happened at random after a reboot. I haven’t installed anything. I might have run an anti-virus check (trendmicro - housecall) but not sure if that was before or after.
After this (yesterday) I installed the SP5 and the new deadline.

Just now after the error message I checked if 3dsmaxcmd.exe has admin rights re-enabled it and restarted the slave.
so now both 3dsmax & 3dsmaxcmd have admin rights by default (see attached), but yet it still renders with errors.

Is there another .exe that deadline uses?

----------------edit-------

problem solved… manually enabled ‘run with admin rights’ for the deadline slave/launcher solved it…

like i said before… had allot of crap with win8 UAC settings.
I really find them annoying… wish it could just be turned of as with win 7

max.PNG
max.PNG704×52 3.75 KB

9

Glad to hear it’s all sorted now.