Getting Error While Pulling Data from EventHub Via Eventstream into Lakehouse

[Anonymous]

We are attempting to pull data from Event Hub to Lakehouse using Eventstream. The Eventstream is running fine, and data is coming from the source, but it is not ingesting into the Lakehouse. When we used the "Create new Table" option while configuring the destination, it threw an error stating "Destination Table Not Found." We then created the destination table and tried to ingest the data again, but encountered the following error in the data preview tab:

"No data to preview. Possible reason: 1. Node is not configured. 2. No events fetched in source or upstream nodes, or result is empty."

While receiving error this we were able to see data coming from source in Data preview of source.

Later on, we started receiving a different error.

Please help us resolve this issue.

[Wenyang · Accepted solution]

Hi @Anonymous ,

The initial error occurred because the new table in the Lakehouse was still in the process of being created. The subsequent error was likely due to refreshing too frequently. Please wait until the table creation is complete and then refresh again. You should be able to preview the data at that point.

Thanks,

Wenyang

[Anonymous]

Thanks @Wenyang Will try this once.

[Anonymous]

i Have waited nearly one to two hrs but did not work out , i chose to create new table options in Lakehouse(Destination) getting below error 

[Anonymous]

Hi @Anonymous ,

Please check that you have met the following prerequisites:

Please refer to the documentations to check that your procedure is not incorrect.

Add Azure Event Hubs source to an eventstream - Microsoft Fabric | Microsoft Learn

Add a lakehouse destination to an eventstream - Microsoft Fabric | Microsoft Learn

If the data preview displays “No data available for preview”, this may be due to data not flowing correctly to the target node.

Check the output of the upstream node to make sure that the data is flowing properly to the target node. Ensure that the target node is configured correctly and that there are no issues with data mapping.

If the target table already exists and the problem persists, try deleting and recreating the target table to ensure that the table structure and configuration are correct.
When recreating the table, ensure that the table name, schema, and fields match the source data exactly.

Best Regards,

Neeko Tang

If this post  helps, then please consider Accept it as the solution  to help the other members find it more quickly.