0

Tank mount point lookup errors in python.

Hello, I am trying to access a running tank instance (Maya) and am running into the following error:

# Error: TankError: file \\Software\shotgun\studio\install\core\python\tank\pipelineconfig.py line 904: You are trying to start using the configuration and tank command located in 'S:\Software\all\shotgun\dev'. The path '\\Projects\Dev' you are trying to load is not associated with that configuration. The path you are trying to load is associated with the following configurations: ['S:\\Software\\all\\shotgun\\dev']. Please use the tank command or Sgtk API in any of those locations in order to continue. This error can occur if you have moved a Configuration on disk without correctly updating it. It can also occur if you are trying to use a tank command associated with Project A to try to operate on a Shot or Asset that that belongs to a project B. #

It looks as if, internally, Tank is using a windows mount, despite having been configured to use the valid network url. There is a second problem, which appears to be caused by literal strings in python being inequal to regular ones.

I would like, as much as possible to strip any windows mounts out of our setups, and I have purged install files of them previously, but this looks like it is happening at the app level.

r

 

 

댓글 4개

  • 0
    Avatar
    Robert Durnin

    It looks as if SG has kept the install paths supplied to it at the time SGTK was installed for the project and cannot be updated (values are read-only).

    What can I do, besides reinstalling Tank for each project to update the mount path for Tank in SG?

    r

     

     

  • 0
    Avatar
    Alan Dann

    Hi Robert,

    Did you move the configuration on disk manually?

    Can you try using the tank move_configuration command from the command line instead?  This will also update the Pipeline Configuration entity in Shotgun to correctly point to the new location of the configuration.

    Thanks

    Alan

  • 0
    Avatar
    Robert Durnin

    Yes, I was trying to remove some of the superfluous apps/engines/etc out of the tk-default-config, and decided to revert files back manually (as it seemed I was creating more work than I was saving after ripping out the dependencies). The three files I changed were asset.yml, asset_step.yml, and project.yml, although none of them had any mount point information.

    I reinstalled a new configuration, although I'm not sure where it was getting it's default values from... There was a data path that I couldn't affect during the install (Core API path) which was pointing to a network mount, but I'm guessing that has to to with the path to the Tank.cmd.

    Regardless, it's working again, despite having to revert changes.

    r

     

     

  • 0
    Avatar
    Alan Dann

    Hi Robert,

    Glad you got it working.

    Just for reference, if you do need to move the studio installation (where the core API lives), there is a command for this as well:

    ./tank move_studio_install

    Hope that helps.

    Thanks

    Alan

댓글을 남기려면 로그인하세요.