How to troubleshoot folder creation errors

[I’m gonna talk to myself here, as this issue comes up every once in a while, and I want to make sure it’s documented here :slight_smile: ]

This post addresses a couple errors that occur at folder creation time.

  • Could not resolve row id for path!
  • Database concurrency problems: The path <PATH> is already associated with Shotgun entity <ENTITY>.

Error 1: Could not resolve row id for path!

A Toolkit user is getting the error “Could not resolve row id for path!” when they create folders.

Oddly, this is creating FileSystemLocation entities, but sometimes resulting in duplicates, which can cause a whole host of problems.

The full error looks something like:

Creating folders, stand by...

ERROR: Could not resolve row id for path! Please contact support! trying to 
resolve path '\\server\nas_production\CLICK\00_CG\scenes\Animation\01\001'. 
Source data set: [{'path_cache_row_id': 8711, 'path': 
'metadata': {'type': 'shotgun_entity', 'name': 'sg_scenenum', 'filters': 
[{'path': 'sg_sequence', 'values': ['$sequence'], 'relation': 'is'}], 
'entity_type': 'Shot'}, 'primary': True, 'entity': {'type': 'Shot', 'id': 
1571, 'name': '001_01_001'}}, {'path_cache_row_id': 8712, 'path': 
'metadata': {'type': 'shotgun_step', 'name': 'short_name'}, 'primary': True, 
'entity': {'type': 'Step', 'id': 6, 'name': 'FX'}}, {'path_cache_row_id': 
8713, 'path': 

(actually it can go on much longer than that…)

Error 2: Database concurrency problems

Similarly, this error can also occur when a Toolkit user tries to create folders. Here’s the full error:

ERROR: Database concurrency problems: The path
'Z:\projects\SpaceRocks\shots\ABC_0059' is already associated with
Shotgun entity {'type': 'Shot', 'id': 1809, 'name': 'ABC_0059'}. Please re-run
folder creation to try again.

What do these errors mean and how do I fix them?


What’s causing the errors?

Error 1 points to a mismatch between the storage roots as specified in Shotgun (Site Prefs -> File Management) and config/core/roots.yml in the Pipeline Configuration.

It often comes up because of a case mismatch in studios running Windows. Their paths are case-insensitive, but our configs are case-sensitive. A difference as simple as E:\Projects vs E:\projects can cause this error.

Error 2 seems related, though I’m not exactly sure why it happens. It happens when you’re in a state where you’re trying to create a FilesystemLocation entity for a folder that already has one.

What’s happening behind the scenes?

In the case of Error 1, I believe what’s happening is this: The code creates the FilesystemLocation entity in Shotgun for the path it just created, using Shotgun’s storage roots to determine the root for the path. Then, it goes to create the same entry in the local cache, and has to determine where to put it in the database. For the local cache, it uses roots.yml to determine the root for the path, and because of the case mismatch, the path it generates doesn’t match what was just entered in Shotgun. At this point, it throws the error.

It’s especially bad because it doesn’t error cleanly: the folders are created, the FilesystemLocation entries are created, they are not synced in the local path cache, nor will they ever be able to be synced because of the storage root mismatch.

How to fix

  • For Error 1 only, First, make sure the storage root paths in the Site Prefs match the paths in config/core/roots.yml . Fixing the mismatch should make the error go away in subsequent folder creation calls.
  • [The rest of the steps apply to both Error 1 and Error 2.] Clear the bad FilesystemLocation entities. If you can narrow down to a set of errant FilesystemLocation entities, just remove those. In a lot of cases though, all of the paths for a project are compromised, so they all need to go.
    • How to clear the FilesystemLocation entities: ideally you can run tank unregister_folders . To clear all of them, run tank unregister_folders --all . (For all the options for tank unregister_folders , just run it with no arguments and it will output usage notes.)
    • However, because the db is already in a wonky state, this may not work, or may only partially work. Once you’ve run the command, go back to FilesystemLocations in Shotgun, and confirm that what you expected to be deleted is actually gone. If not, select the bad entities, and move them to trash manually.
  • At this point, the FilesystemLocations in Shotgun are clean, but artists’ local caches may not reflect your changes. The last step is to actually sync the local cache on each user’s machine. To do this, they should run tank synchronize_folders --full .

Once all those steps are taken, the path cache should be in a good state, and that errors shouldn’t appear anymore.

Related Links


Edit: I’ve modified the original post to include the below error.

I’ll note that the following error can also be a symptom of the same issue:

ERROR: Database concurrency problems: The path
'Z:\projects\SpaceRocks\shots\ABC_0059' is already associated with
Shotgun entity {'type': 'Shot', 'id': 1809, 'name': 'ABC_0059'}. Please re-run
folder creation to try again.

I’m not sure how the db ends up in this state, but above “How To Fix” steps, save for the first one about roots.yml, should also apply to this error.


So I have a similar error. Creating a folder with an asset of the same first letter as an existing one seems to think its already registered.
For the schema in question we are placing assets in a letter subdirectory so that it looks like:
But then the registered file for this ends up being assets/Prop/C
So creating another C asset causes this error.

Does something have to be registered with the schema so that it recognizes the proper Asset root and not the parent directory?

This is the yaml for the initial directory

type: "shotgun_entity"

name: "{code:^([A-Z])[a-z]}"

entity_type: "Asset"

    - { "path": "project", "relation": "is", "values": [ "$primary" ] }
    - { "path": "sg_asset_type", "relation": "is", "values": [ "$asset_type"] }

And this is the yaml for the asset directory

type: "shotgun_entity"

name: "code"

entity_type: "Asset"

    - { "path": "project", "relation": "is", "values": [ "$primary" ] }
    - { "path": "sg_asset_type", "relation": "is", "values": [ "$asset_type"] }

Anything here I might be missing or configuring incorrectly?


Scratch that! I fixed it.

I consolidated the schema into just the asset directory’s yaml file and it works now.

type: "shotgun_entity"

name: "{code:^([A-Z])[a-z]}/{code}"

entity_type: "Asset"

    - { "path": "project", "relation": "is", "values": [ "$primary" ] }
    - { "path": "sg_asset_type", "relation": "is", "values": [ "$asset_type"] }

Sorry to re-open this topic!