Error saving out frames only on some servers...

Hello --

We recently installed an office server, running Win2003 server.  When I 
attempt to net render, I get file save error messages, but only on a couple of 
my machines.  All machines can see the server folders.  The error messages 
are two and begin with either the expression "Task Error: Tif Error: 
Tiffopen (UNC FILE LOCATION)" or just "Tif Error:TIFFOpen (UNC FILE
LOCATION)"

I'm guessing this has something to do with access privileges or something.  
I'm a novice with WIN2003 Server and using it, so I'm really hoping someone 
out there can clue me in as to what might be going on on these two 
machines...

Thanks!

dave

"David Hitt"  wrote in message 
news:275878.69895@82-36-17-46.cable.ubr01.smal.blueyonder.co.uk...
> Hello --
>
> We recently installed an office server, running Win2003 server. 
> When I
> attempt to net render, I get file save error messages, but only on a 
> couple of
> my machines.  All machines can see the server folders.  The error 
> messages
> are two and begin with either the expression "Task Error: Tif Error:
> Tiffopen (UNC FILE LOCATION)" or just "Tif Error:TIFFOpen (UNC
FILE 
> LOCATION)"
>
> I'm guessing this has something to do with access privileges or 
> something.
> I'm a novice with WIN2003 Server and using it, so I'm really hoping 
> someone
> out there can clue me in as to what might be going on on these two
> machines...


How many client licenses do you have (for the server)? Enough for all 
the render machines /plus/ any other office computers that may be 
attaching to it?

Is it a problem with those two machines specifically? If you have 
access to restart the server, try restarting it with a couple of the 
known-working render machines switched off, then run a quick job and 
see whether the troublesome machines can now access the shares 
properly. If so, it's a licensing thing.

You could try sharing a drive on another computer (not the server, 
just one of the render stations, say) and use that for outputting 
frames to.

h

Hi there --

Thanks for looking at my issues and I apologize for not getting back to this 
thread sooner.  The server is a new install and we were having these issues 
prior to installing it, when we were just set up peer to peer.  
Ironically, this was one of the issues that precipitated our decision to go to a
true 
server setup.  So, then, we'd likely have the same issues if we mounted 
the textures to a different drive.  Also, the server has ten licenses; we 
have five machines and three nodes. So, it shouldn't be a licensing issue with 
win 2003 server.  Interestingly, three of our machines (the new rendering 
nodes) NEVER have this problem, regardless of how many machines are 
running.

It really seems to be a file type issue.  I've noticed that we only get these 
messages for .tga or .jpeg texture files.  Tiffs don't seem to throw this 
error message.

It's very bizzare...

thanks

dave