It's a feature. Seriously. As far as I'm aware there is no way to
change it either.
On 12/4/06, Kim Aldis <XSI(at)kim-aldis.co.uk> wrote:
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
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
