Forum Discussion
Paginated Report Error while loading dataset
Hi 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.
Hi Narasapuram-Swa,
Those first two errors seem to be the result of the last error.
Your XML data is being cut off as it times out, and therefore is no longer valid XML causing validation issues in the first two errors.
Microsoft’s guidance for paginated reports over semantic models is to reduce data volume as much as possible and push aggregations into the model, not the report. See Performance and scalability considerations for paginated reports.
One thing you can try:
Check and increase dataset timeout
- In Report Builder, go to Dataset Properties > Options and set an explicit timeout value (for example 600 seconds or higher) instead of leaving it at the default.
- For paginated reports, timeouts are controlled at the dataset level, and there are also environment-level limits. See Set time-out values for paginated report dataset processing.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
3 Replies
Hi Narasapuram-Swa,
Those first two errors seem to be the result of the last error.
Your XML data is being cut off as it times out, and therefore is no longer valid XML causing validation issues in the first two errors.
Microsoft’s guidance for paginated reports over semantic models is to reduce data volume as much as possible and push aggregations into the model, not the report. See Performance and scalability considerations for paginated reports.
One thing you can try:
Check and increase dataset timeout
- In Report Builder, go to Dataset Properties > Options and set an explicit timeout value (for example 600 seconds or higher) instead of leaving it at the default.
- For paginated reports, timeouts are controlled at the dataset level, and there are also environment-level limits. See Set time-out values for paginated report dataset processing.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Hi Narasapuram-Swa ,
I would also take a moment to thank tayloramy , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions
Hi Narasapuram-Swa ,
hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you
