New config won't launch Maya

Flow Production Tracking
1

Myself:
I’ve inherited a shotgun setup from someone who isn’t around for me to ask questions of. I’m pretty familiar with dealing with the SG database from a python perspective but I’m not really familiar with toolkit or desktop and I have some questions.

My Setup:
This project was originally set up with a config that is uploaded and referenced as a Git Repo URI. Now I’m trying to change some things in the project config that’s displayed in ShotGrid Desktop. I’ve forked off the config repo, added myself as a local config option in the Pipeline Configuration Entity that looks to a Windows Path, made some changes in the config yamls (getting rid of un-needed apps in tk-desktop.yml). I can switch to my named local config, the yaml changes I made appear to have taken effect (I’ve only got icons for the apps I want).

My Issue:
Now, when I try and launch Maya I get an SG dialog saying: “Hang on, Toolkit is preparing folders… Toolkit is retrieving folder listings from SG and ensuring that your setup is up to date. Hang tight while data is being downloaded…”

This goes away real quick and so I check the console log and see an error:
2023-07-12 17:15:14,901 [ ERROR] [PROXY] Error calling __commands::tk-multi-launchapp:Maya:maya_2022((), {}):
Traceback (most recent call last):
File “C:\Users<user name>\scripts\Shotgrid\toolkit\configs<project name>-config\install\app_store\tk-desktop\v2.6.0\python\tk_desktop\desktop_engine_project_implementation.py”, line 210, in _trigger_callback
callback(*args, **kwargs)
File “C:\Users<user name>\scripts\Shotgrid\toolkit\configs<project name>-config\install\core\python\tank\platform\engine.py”, line 1083, in callback_wrapper
return callback(*args, **kwargs)
File “C:\Users<user name>\scripts\Shotgrid\toolkit\configs<project name>-config\install\app_store\tk-multi-launchapp\v0.12.0\python\tk_multi_launchapp\base_launcher.py”, line 138, in launch_version
**kwargs
File “C:\Users<user name>\scripts\Shotgrid\toolkit\configs<project name>-config\install\app_store\tk-multi-launchapp\v0.12.0\python\tk_multi_launchapp\base_launcher.py”, line 393, in _launch_callback
“Could not create folders on disk. Error reported: %s” % err
TankError: Could not create folders on disk. Error reported: The path ‘C:\Users<user name>\Perforce<computer name>\Projects<project name>’ could not be split up into a project centric path for any of the storages C:\Users<user name>\Perforce<computer name>\Projects\Pipeline, T:\Projects\Pipeline, T:\p4<project name>\dev-main\Projects\Pipeline, F:\p4<company name>\Projects\Pipeline that are associated with this project.

I went ahead an created those folders by hand but it didn’t change anything.

My Questions:
Is it safe to assume that these paths are stored in the SG database and not in the config?
Either way, where might I find them?
Perhaps I need specific permissions in order to create these folders properly?
Is there a way I can tell this config to not to try and look for those local folder paths?
Am I missing some obvious step in setting up a new local config that I can then upload?

Thanks for any help?

2

This sounds a bit complicated…
First, were you able to launch Maya using the previous config ok?
If so, then that should have created the folders that SG is expecting to find. If they don’t exist, then something in the config has changed what folders SG is expecting for your maya project context.
Can you confirm exactly what files changed between the previous working config and this new one?

This sounds like either you’ve removed some logic from the app_launch hook that provided the necessary context to create the folders, or templates.yml has been changed.

Making folders by hand to resolve these problems is never a good idea as SG won’t be aware of any changes made; you’re right to say they are stored in the SG database. I would remove the folders you created to avoid confusion as you continue to debug this issue.

I might also investigate the path it’s trying to get a project-centric path for. What does C:\Users<user name>\Perforce<computer name>\Projects<project name> resolve to exactly? Does this match the path that was working with the previous pipeline config?

Perhaps I need specific permissions in order to create these folders properly? - No, if this was working with the previous pipeline config, then there’s no reason why it shouldn’t work with your new one.

Is there a way I can tell this config to not to try and look for those local folder paths? - No, SG needs to resolve the project path to launch Maya in to a context. It’s not going to serve you any benefit to skip fixing this problem before you do any more work/changes.

Am I missing some obvious step in setting up a new local config that I can then upload? - If it’s loading your custom config, then it seems to be working on that level. It may be that there are assumptions in the config based on uploaded configs that you’ve not picked up on. I would investigate the core/hooks to see if there’s anything obvious related to setting up prior to engine_init, although from your error message, theres no reference to any custom hooks, so that might not be the issue.