DR Spawner bug

[renderfarmer]

Hi,

I think I might have found a new bug.

I installed Vray on two servers (Win2003 Server x64) as Slaves. For whatever reason, I used the "registered DR spawner service" on one, but simply dragged the "launch DR Spawner shortcut" to the Startup folder on the other. Then when I did a DR render the one with the registered service wouldn't render any textures, while the other server did.

Both had equal access to my mapped textures folder. I could read the textures from both machines manually and using Backburner.

So it occurred to me that the only difference between the two was that one had the spawner registered and the other didn't so i unregistered the spawner and launched it manually and that fixed the problem.

Is this a known issue?

[RErender]

More likely the service could not see the drives. The drives need to be mounted specifically for the account that the service is running in though I'm not sure exactly what that means but our old IT guy did...

[renderfarmer]

That makes sense. All this server admin BS really gets in my craw. Only reason I put up with Win2K3 Server is because it's the only Windows OS I could install on these Dell Poweredge servers...

Thanks for the reply.

[DAVIS_CARTER_SCOTT]

Run the service as an account on the domain that can see your network shares. I use RUSER with a password as the user account to launch the spawner on all my slaves. I don't have to log in on the machines, just boot them up.