RE: service-based render can't see mapped drives.

["Felici Andrea" <a.felici(at)rai.it>]

Try loading scenes directly from UNC path, on both A & B machine.

 

Andrea Felici

RAI Radiotelevisione Italiana

 

 

---

From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On Behalf Of Kim Aldis
Sent: Monday, December 04, 2006 12:21 PM
To: XSI(at)Softimage.COM
Subject: OT: service-based render can't see mapped drives.

I’ve an interesting situation here. My renderfarm uses a service to run jobs submitted remotely.  I have machine ‘A’ with a drive attached to it, mounted as Q: and shared with share name Q. The rendering service runs on both A and B and logs in as user ‘Adminstrator’. Permissions on A’s Q: give everbody full control. Adminstrator on B has Q: mapped to \\A\Q. Logged in to B, Adminstrator can start XSI, load scenes from Q: and render quite happily. However, the service log output is telling me that the scene on Q: can’t be read and that drive Q: will be marked unreadable for 300 seconds. If I add a line in my rendering script that makes a system call to ‘net use’ that tries to map the share to Q:, I get a warning that : is already mapped. No other errors or warnings are logged and the event viewer shows no entries that could be relevant. I’ve checked the number of sessions on machine A and it’s well within limits.

 

This is undoubtedly a windows problem but it’s not one I’ve encountered before. As far as I can see this should be working. Does anyone have any thoughts as to why the service can’t see this drive?

 

Thanks.

 

www.kim-aldis.co.uk   |   kim(at)kim-aldis.co.uk

 

*****************************************************************
Questa e-mail, ed i suoi eventuali allegati, contengono informazioni confidenziali
e riservate. Se avete ricevuto questa comunicazione per errore non utilizzatene
il contenuto e non portatelo a conoscenza di alcuno. Siete inoltre pregati di elimi-
narla dalla vostra casella e avvisare il mittente. E' da rilevare inoltre che l'attuale
infrastruttura tecnologica non puo' garantire l'autenticita' del mittente, ne' tanto-
meno l'integrita' dei contenuti.Opinioni, conclusioni ed altre informazioni contenu-
te nel messaggio possono rappresentare punti di vista personali a meno di diversa
esplicita indicazione autorizzata.
*****************************************************************