Paginated Report error while loading dataset

[Narasapuram-Swa]

Hi Power BI Community,

I have loaded data from a Semantic model to my paginated report. During loading the data, I am able to see it as a successful step.

However when I try to create a report in the report server, the report runs for a lot of time and finally fails to render the data. 

Below are the issues observed. Anyone having any idea on these issues ? 

Issue1:

Unexpected end of file while parsing Name has occurred. Line 1, position XXXX. The server sent an unrecognizable response. Cannot read the next data row for the dataset 'DataSet1'. An error has occurred during report processing. An error occurred during local report processing.

Issue2:

Unexpected end of file has occurred. The following elements are not closed: Projects_x005B_Project_x0020_Name_x005D_, row, root, return, ExecuteResponse, soap:Body, soap:Envelope. Line 1, position XXXXX. The server sent an unrecognizable response. Cannot read the next data row for the dataset 'DataSet1'. An error has occurred during report processing. An error occurred during local report processing.

Issue3:

The operation has timed out. The read operation failed, see inner exception. The connection either timed out or was lost. Cannot read the next data row for the dataset 'DataSet1'. An error has occurred during report processing. An error occurred during local report processing.

[V-yubandi-msft]

Hi @Narasapuram-Swa ,
If you need any additional information or further discussion, please stay connected with the community as we move forward.

Thanks.

[V-yubandi-msft]

Hi @Narasapuram-Swa ,
May I know if your issue has been resolved, or if you need any further assistance? Please feel free to let us know.
Thank you.

[V-yubandi-msft · Accepted solution]

Hi @Narasapuram-Swa ,

Thank you for engaging with the Microsoft Fabric Community. This issue occurs because the paginated report cannot fully retrieve data from the Semantic Model. Typically, this is due to very large or slow queries, which can result in incomplete or timed out responses. If the data stream is interrupted, the XML response may break, causing unexpected end of file or timeout errors.

To fix this, you can.

1. Reduce the amount of data returned by applying filters or limiting columns and rows.
2. Optimize the query or use aggregated data instead of detailed rows.
3. Increase timeout settings for the report and dataset.
4. Check for any network, gateway, or proxy issues that could affect the connection.

Regards,
Yugandhar.

[vivien57]

hello @Narasapuram-Swa 

This is not the right group on the forum. Please move your post here for a better chance of getting a response.

https://community.fabric.microsoft.com/t5/Service/bd-p/power-bi-web-app