Drive mapping conflict

Viewing 2 posts - 1 through 2 (of 2 total)
  • Back to forum
    Posted in: Muster usage
  • chris_422
    1st February 2007 at 10:43 am #14156

    Hi all,

    We are currently evaluating muster at our studio.

    We have a problem here with drive mapping errors and different render engines.

    The output error message is ‘Chunk 1 belonging to job maya_test(44) processed by host DUALCORE-4[1] reported the following error: Drive mapping conflict. Drive S: is mapped to \sledgevol1 instead of \192.168.1.239vol1 (Service) Goliath3(127.0.0.1)’

    However, this error only occurs when trying to render a maya sw scene.
    Mental ray and Renderman for maya engines render fine, although for RFM we have to use the -rd flag to specify the output directory, otherwise it’s not found.

    We do have all machines set up in a specific workgroup and have tried changing the drive mapping properties between unc paths and ip paths.
    This can solve the maya sw renders but then stops the mental ray and RFM from creating output.

    We’re running an XP based network.

    Hope I’ve provided enough info on this.

    Any help would be greatly appreciated as it’s the only thing thats now stopping us to moving over to muster for our studio.

    Thanks

    Chris

    Leonardo Bernardini
    22nd May 2007 at 12:22 am #14666

    Disable automatic drive mapping and set the Renderclient to statically map a drive on startup.

    Muster uses a string-based comparation. If you map a drive using the IP address (in your example \192.168.1.239) and then submission a job from an host that has the drive mapped using a UNC name, they will raise an exception.

    Off course, you can get an headache normalizing your mappings on your network…

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.