Forum Discussion

dineshuthayakum's avatar
dineshuthayakum
Frequent Visitor
4 months ago
Solved

DataSource.Error: Downstream service call to url failed.

The following error doesnt occur in company tenant but occurs in client's tenant.

 

I am developing items in a Fabric Workspace using our Company's account as External/Guest account in the Client's Fabric Tenant.

I switch the tenant after navigating to app.fabric.microsoft.com 

A Lakehouse was created in the Fabric Workspace.

I then created a DataFlow Gen2. Selected the source as Lakehouse, using a valid connection.

I am unable to see the Lakehouse instances in the Current Workspace.

The following error message appears

 

 

DataSource.Error: Downstream service call to url 'https://api.powerbi.com/v1/workspaces/{workspaceid}/lakehouses ' failed with status code 404.

Details
Reason = DataSource.Error
ErrorCode = Lakehouse034
Error = [requestId=5ef0a576-f099-4f12-8fb6-486dc28e4c2c,errorCode=EntityNotFound,message=The entity could not be found,isRetriable=false]
ErrorCode = EntityNotFound
RequestId = 5ef0a576-f099-4f12-8fb6-486dc28e4c2c
HttpStatusCode = 404

 

---------- Message ----------
DataSource.Error: Downstream service call to url 'https://api.powerbi.com/v1/workspaces/{workspaceid}/lakehouses ' failed with status code 404.

---------- Session ID ----------
e996215f-b0f6-4259-9a89-e7ec7bd20edc

---------- Request ID ----------
04c1debb-b859-4dcc-b3a1-a9f230f9e0b3

---------- Mashup script ----------
[StagingDefinition = [Kind = "FastCopy"]]
section Section1;
shared Query = let
Source = Lakehouse.Contents([HierarchicalNavigation = null, EnableVorder = true, OutputMetadataRefresh = true])
in
Source;

one lake
workspaces

4 Replies

  • dineshuthayakum's avatar
    dineshuthayakum
    Frequent Visitor
    4 months ago

    Is the Guest/External account the root cause of the error?

     

    https://learn.microsoft.com/en-us/fabric/data-factory/data-factory-limitations

    In the above article on Data Factory in Fabric, I see the below.

    Dataflow Gen2 doesn't support for guest users in the tenant to connect to the data sources and destinations in the tenant the user is guest. Use a native user in the tenant to connect to the data sources and destinations.

    • v-menakakota's avatar
      v-menakakota
      Icon for Community Support rankCommunity Support
      4 months ago

      Hi dineshuthayakum  ,

      Thank you for reaching out to the Microsoft Community Forum.

       

      Yes, this is very likely related to the account being a Guest/B2B user in the client tenant rather than an issue with the Lakehouse itself. As the Microsoft document you shared shows, Dataflow Gen2 does not support guest users connecting to sources or destinations within the tenant where they are guests and your scenario matches that limitation closely.

      Although the Lakehouse and Dataflow Gen2 are in the same workspace and the connection itself appears valid, the backend API call used to enumerate Lakehouses is failing with Lakehouse034 / EntityNotFound / 404, which is consistent with this limitation. Test with a native member account created directly in the client tenant instead of the external guest account.

       

      If I’ve misunderstood your needs or if you still encounter issues, please let us know.

      Best regards,
      Community Support Team