High severityconfiguration
Power BI Refresh Error:
VOLUME_NOT_FOUND
What does this error mean?
A SQL statement or job task referenced a Unity Catalog volume using a three-part name that does not exist, has been dropped, or is in a different catalog or schema than expected.
Common causes
- 1The volume was dropped and the pipeline was not updated to reference the replacement
- 2The three-part name (catalog.schema.volume) has a typo or uses the wrong catalog for the environment
- 3The job is running in a workspace attached to a different metastore that does not contain the volume
- 4The volume was created in a personal or dev schema that does not exist in production
How to fix it
- 1Step 1: Run SHOW VOLUMES IN catalog.schema to list existing volumes and verify the name.
- 2Step 2: If the volume was recently dropped, determine whether it needs to be recreated or if the pipeline reference needs to be updated.
- 3Step 3: Check that the job is running in the correct workspace and against the correct catalog (dev vs. prod catalog).
- 4Step 4: Update the pipeline code or job configuration to use the correct three-part volume name.
- 5Step 5: Test by running a SELECT or LIST DIRECTORY on the volume path before re-enabling the scheduled job.