Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
2 years ago
Solved

Cannot Delete Lakehouse Issue

Yesterday I tried to delete some old test Lakehouses and was met with the error "This item couldn't be deleted. Please try again later." I'm able to delete other objects as normal. As a test I create...
admin
data warehouse
  • Anonymous's avatar
    Anonymous
    2 years ago

    Update: If I first delete the one-time pipeline used to populate the Lakehouse, I'm able to delete the Lakehouse. It's like Fabric sees that something is connected to the Lakehouse and won't let me delete it. Is this expected behavior?

     

    I tested again by creating a Lakehouse with a copy data pipeline, and a completely blank Lakehouse. The blank Lakehouse deleted with no problem. The other lakehouse would not delete until I deleted the associated pipeline first.

jesvytcan's avatar
jesvytcan
New Member
2 years ago
Update: I was finally able to delete the DataflowStagingLakehouse and it's related SQL Endpoint & Semantic model from my workspace (I do not see any other dependent objects). Looks like something finally synced-up on Microsoft's end. HOWEVER, I am still not able to move the workspace back to PRO licensing, with this error: "workspace cannot be reassigned because it includes Fabric items or you're attempting to move them across regions. This is not supported currently. Remove the Fabric items, or move the workspace within the same region, and then try again.". If anybody has a fix please let us know, I'll post here if I'm able to work around this later on. Thanks
Anonymous's avatar
Anonymous
Not applicable
2 years ago
jesvytcan wrote:
with this error: "workspace cannot be reassigned because it includes Fabric items or you're attempting to move them across regions. This is not supported currently. Remove the Fabric items, or move the workspace within the same region, and then try again."

This is pure speculation on my part, but it is possible that the Fabric items you deleted are only soft-deleted as part of disaster recovery. If this is true, then the items still exist from Fabric's point of view. For reference:

Reliability in Microsoft Fabric | Microsoft Learn

 

It could also be a delay in Fabric updating its own tables (or whatever Fabric uses behind the scenes to track all the objects). It is possible that after a little while you will be able to reassign the workspace.