 | | | 'fatal errors ' accessing image files on network renders | 'fatal errors ' accessing image files on network renders 2004-05-03 - By Ben Kilgore
Back
Kim,
Forgot to mention--the farm completed other scenes without a hitch. It just
seems to be this texture and/or scene that's having this effect.
Ben
-- -- Original Message -- --
From: "kim aldis" <kim@(protected)>
To: <XSI@(protected)>
Sent: Monday, May 03, 2004 3:49 AM
Subject: RE: 'fatal errors' accessing image files on network renders
> Sounds like that could your problem. Localhost connected to the same
machine
> will lift a client licence, so you've effectively taken 6 licences. Go to
> control panel->administrative tools->Computer Management and look under
> shared folders->sessions, see how many sessions are active. You can close
> sessions from there.
>
> This is one of the many reasons to consider Linux, at least as a file
> server. The only other way is to buy more MS client license. The fact that
> Windows does this is bad enough. That it does it so badly and consts som
> much is outrageous.
>
> > -- --Original Message-- --
> > From: owner-xsi@(protected)
> > [mailto:owner-xsi@(protected)] On Behalf Of Ben Kilgore
> > Sent: 02 May 2004 19:44
> > To: XSI@(protected)
> > Subject: Re: 'fatal errors' accessing image files on network renders
> >
> > It's 2000 Professional.
> >
> > 5 machines (10 CPUs), plus the render control (localhost?) is
> > rendering, as well.
> >
> >
> >
> >
> > -- -- Original Message -- --
> > From: "kim aldis" <kim@(protected)>
> > To: <XSI@(protected)>
> > Sent: Sunday, May 02, 2004 2:09 PM
> > Subject: RE: 'fatal errors' accessing image files on network renders
> >
> >
> > > How many machines do you have trying to access the files on
> > the remote
> > > machine? Remember, if you're serving files from NT
> > Workstation or XP,
> > > Microsoft limits you to 10 connections only. In practice
> > this usually
> > works
> > > out to be around 6 after you take into consdiration browsr
> > connections and
> > > the fact that a connection usually won't be dropped for
> > quite a while
> > after
> > > it's no longer needed. Take a look in computer management,
> > under sharing.
> > >
> > > > -- --Original Message-- --
> > > > From: owner-xsi@(protected)
> > > > [mailto:owner-xsi@(protected)] On Behalf Of Ben Kilgore
> > > > Sent: 02 May 2004 02:21
> > > > To: XSI@(protected)
> > > > Subject: Re: 'fatal errors' accessing image files on
> > network renders
> > > >
> > > > Amazing...no one has seen this before?
> > > >
> > > > -- -- Original Message -- --
> > > > From: "Ben Kilgore" <ben@(protected)>
> > > > To: <XSI@(protected)>
> > > > Sent: Thursday, April 29, 2004 2:06 PM
> > > > Subject: 'fatal errors' accessing image files on network renders
> > > >
> > > >
> > > > > List,
> > > > >
> > > > > I know in advance I am probably not supplying enough
> > > > information but I
> > > > have
> > > > > the problem of not being able to access my list account
> > > > from where the
> > > > > render farm is:
> > > > >
> > > > > I have a scene that's consistently crashing xsi (or
> > > > xsibatch) on a render.
> > > > > It'll actually get partway through some frame, actually
> > > > displaying tiles
> > > > if
> > > > > I try and render from the UI, but every time, it'll give me
> > > > a file error
> > > > > message about net being able to find a texture (and of
> > > > course the texture
> > > > is
> > > > > right where it is looking and was accessed earlier in the
> > > > render) and
> > > > it'll
> > > > > stop. The textures are not on the local blades (couldn't
> > > > set that up last
> > > > > night), are all .map, and none of them are over
> > 2048x2048. The .map
> > > > > versions of these textures will actually cause the same
> > > > crash if projected
> > > > > all alone in a bare scene onto a sphere, but the targas did
> > > > not--although
> > > > > the targas do crash the complex scene. We are not
> > using batchserve.
> > > > Scene
> > > > > renders fine on a completely local render--obviously it's a
> > > > network-related
> > > > > problem. I know diddly about network rendering, but this
> > > > had even someone
> > > > > quite experienced with network rendering scratching his
> > > > head well into the
> > > > > wee hours.
> > > > >
> > > > > Poked around the archives a bit--found nothing related to
> > > > this issue.
> > > > >
> > > > > As I left the farm at 5:30 in the morning, I forgot to
> > bring more
> > > > > information with me, but would greatly appreciate any
> > of your input.
> > > > >
> > > > > Ben Kilgore
> > > > > FIT
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ---
> > > > > Outgoing mail is certified Virus Free.
> > > > > Checked by AVG anti-virus system (http://www.grisoft.com).
> > > > > Version: 6.0.667 / Virus Database: 429 - Release Date: 4/23/2004
> > > > >
> > > > > ---
> > > > > Unsubscribe? Mail Majordomo@(protected) with the
> > > > following text in body:
> > > > > unsubscribe xsi
> > > >
> > > >
> > > > ---
> > > > Outgoing mail is certified Virus Free.
> > > > Checked by AVG anti-virus system (http://www.grisoft.com).
> > > > Version: 6.0.667 / Virus Database: 429 - Release Date: 4/23/2004
> > > >
> > > > ---
> > > > Unsubscribe? Mail Majordomo@(protected) with the following
> > > > text in body:
> > > > unsubscribe xsi
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > ---
> > > Unsubscribe? Mail Majordomo@(protected) with the
> > following text in body:
> > > unsubscribe xsi
> >
> >
> > ---
> > Outgoing mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.667 / Virus Database: 429 - Release Date: 4/23/2004
> >
> > ---
> > Unsubscribe? Mail Majordomo@(protected) with the following
> > text in body:
> > unsubscribe xsi
> >
> >
> >
>
>
>
> ---
> Unsubscribe? Mail Majordomo@(protected) with the following text in body:
> unsubscribe xsi
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.667 / Virus Database: 429 - Release Date: 4/23/2004
---
Unsubscribe? Mail Majordomo@(protected) with the following text in body:
unsubscribe xsi
|
|
|