Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Cdm failed to generate manifest

I am getting the above error message when connecting via Azure Datalake Gen2 connector against a storage account that is connected to a Power BI workspace.
The table I want to retrieve is generated by a dataflow that uses linked entities. This seems to be the cause for the error, as when I retrieve the data via ADLS Gen2 connector instead of dataflow/linked entity, everything works fine.
Upon further investigation, I recognized that when using linked entities, every dataflow refresh generates 2 model jsons instead of one. Could that be the cause?

 

Status: Investigating

Hi @ImkeF 

I found a similar error reported, see if that helps you.

DataSource.Error: Cdm failed to generate manifest - Microsoft Fabric Community

 

Best Regards,
Community Support Team _ Ailsa Tao

Comments
ImkeF
Super User

Adding further information:
This is happening in dataflows gen1.

v-yetao1-msft
Community Support
Status changed to: Investigating

Hi @ImkeF 

I found a similar error reported, see if that helps you.

DataSource.Error: Cdm failed to generate manifest - Microsoft Fabric Community

 

Best Regards,
Community Support Team _ Ailsa Tao

ImkeF
Super User

Hi @v-yetao1-msft ,
thanks, but that is not the issue here.
Maybe I was unclear in my description:
I can connect via ADLS Gen2 to my blob storage, but only if I don't use any linked entities in the dataflow that is creating those files (Workspace connected to an Azure Blob).
So instead of using the fast linked entities, I have to swap them for ADLS Gen2 connections instead. 
I think this is a bug and should be corrected.