topic Re: Items stuck in Unidentified folder in Lakehouse and fail to register as tables in Data Engineering

Items stuck in Unidentified folder in Lakehouse and fail to register as tables

jimmy101 — Wed, 29 Nov 2023 06:51:56 GMT

A Gen2 Dataflow with write as Replace to Lakehouse suddenly started failing to register the table and placing it in Unidentified. I am observing the same behavior for multiple dataflows. No edits were completed on the dataflow from when it was working properly to now. In the SQL endpoint the table does showup as a table. On the notebook I get the same behavior as the Lakehouse explorer with the item showing under the Unidentified folder.

I even created a new workspace, new lakehouse, and new dataflow and get the same behavior. The dataflow completes successfully writes the data but the table is just stuck in the Unidentified folder. Any ideas on how to troubleshoot the issue?

[Edit]

I have attempted creating the table with a pipeline copy activity and also creating a shortcut to the Lakehouse and I get the same behavior where the item is added to the Unidentified folder but does not get registered as a Table.

Here is how the files look when clicking on DIM_SALES_CHANNEL

Re: Items stuck in Unidentified folder in Lakehouse and fail to register as tables

Anonymous — Wed, 29 Nov 2023 07:12:29 GMT

Hi @jimmy101
Thanks for using Fabric Community and reporting this.
At this time, we are reaching out to the internal team to get some help on this.
We will update you once we hear back from them.
Thanks

Re: Items stuck in Unidentified folder in Lakehouse and fail to register as tables

Anonymous — Mon, 04 Dec 2023 19:17:02 GMT

Hi @jimmy101
Thanks for using the Fabrics community.
I will request you to please go ahead with Microsoft support on this. 
https://support.fabric.microsoft.com/en-US/support/

Thanks

Re: Items stuck in Unidentified folder in Lakehouse and fail to register as tables

Anonymous — Tue, 12 Dec 2023 21:27:37 GMT

Is there a solution for this? I am seeing the exact same issue.

Re: Items stuck in Unidentified folder in Lakehouse and fail to register as tables

adrianat — Tue, 12 Dec 2023 23:49:21 GMT

I'm having the same issue. Any solution?

Re: Items stuck in Unidentified folder in Lakehouse and fail to register as tables

Anonymous — Wed, 13 Dec 2023 09:47:52 GMT

Hi @adrianat @Anonymous
Thanks for using the Fabrics community.
I will request you to please go ahead with Microsoft support on this. 
https://support.fabric.microsoft.com/en-US/support/

Re: Items stuck in Unidentified folder in Lakehouse and fail to register as tables

RobSBD — Fri, 12 Jan 2024 08:02:55 GMT

I'm also seeing this. Have you received any update from Microsoft?

Re: Items stuck in Unidentified folder in Lakehouse and fail to register as tables

jimmy101 — Tue, 23 Jan 2024 15:30:23 GMT

For me the issue seemed to go away on its own. Wondering if there was some task that cleaned some hung up files or processes behind the scenes. I did not change any settings but within a few days issue went away.

Re: Items stuck in Unidentified folder in Lakehouse and fail to register as tables

JE_test — Thu, 08 Feb 2024 07:28:48 GMT

I also have the same issue, but in the DataflowsStagingLakehouse. It seems to go away by simply refreshing the page when in the Lakehouse. But that is not good enough if you want to make an automatic solution for loading data... pls fix.

Currently my notebook can't find the files since they are not in the expected folder.

Maybe a bit late, but

EthernetIP — Fri, 10 Jan 2025 21:49:28 GMT

I got the same issue when schema was defined on lakehouse:
Solution turned out to be in case sensitivity.

I had a schema "prd" in lower case , my SQL on prem had PRD.blatable .
And after copy I had the Unidentified folder with files in it (by the way to get rid of it , you need to move it to files first, then you can delete).
So I thought about the case and tried to rename "prd" to "PRD" but was told already exists. So I deleted "prd" and let copy run "PRD" was created and worked fine.
PS in a query it will not like prd.bla either it needs the correct case , in my case PRD.bla