Paginated Report Builder error while loading the dataset

Question

Issue1:

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.

Issue2:

Unexpected end of file while parsing Name has occurred. Line 1, position 1073663436.

---

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:

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 1745613140.

---

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.

---

Moved from: Community Center | Discuss the Q&A site | Get started on Q&A

Answer 1

Hi Swathi,

Thank you for sharing your concerns.

Unfortunately, Microsoft Q&A does not support Fabric-related.

Please ask questions in the dedicated official community below.

Fabric Community

Best regards.

Answer 2

The errors you are encountering while loading the dataset in the Paginated Report Builder can be attributed to a few common issues:

1. Timeout Errors: The first issue indicates that the operation has timed out. This often occurs during query processing, especially if the dataset query takes too long to execute. You may want to increase the dataset query timeout value. By default, this value is set to 0 seconds (infinite timeout), but if you are using a Power BI on-premises data gateway, it has a maximum timeout of 600 seconds. Ensure that your dataset query timeout is set to a value greater than this if needed.
2. Parsing Errors: The second and third issues indicate unexpected end-of-file errors while parsing XML responses. This can occur if the server response is incomplete or malformed. It may be beneficial to check the data source and ensure that it is returning valid and complete data. Additionally, ensure that the data source type is correctly configured in your report.
3. Connection Issues: The repeated message about the server sending an unrecognizable response suggests there may be connectivity issues between the report server and the data source. Check the network connection and ensure that the data source is accessible and properly configured.

To troubleshoot these issues, consider the following steps:

• Increase the dataset query timeout value in your report properties.
• Verify the data source configuration and ensure it is returning valid data.
• Check for network connectivity issues that may affect the connection to the data source.
• Review any logs or error messages for additional details that may help identify the root cause of the errors.

If problems persist, you may need to consult documentation or support resources specific to your reporting environment for further assistance.