I have a report that is stuck on loading in the reporting server portal (it's been over a day). However when i check the ExecutionLog...

select * from ExecutionLog3 
AND ExecutionID = 'cbk0hdnpzrspg5qpkvqxubyn'
order by TimeStart desc

...it says that the status is 'rsSuccess'. Results

Here is the AdditionalInfo XML which might help... The query took about 1 minute to run which is how long it took to run in SSMS. Rendering seems pretty fair with the amount of data returned so I am not sure what's going on.

I made sure that Interactive Sizing is standard 8.5 x 11 so that it can show at least some data while processing the other pages but that did not help.


Edit: SSRS - 14.0.807.134 / SSMS - 14.0.17177.0 / Browser - Chrome Edit: Trying IE - 11.309.16299.0 - I don't have the access to update report viewer settings.

  • Do you see any errors in the logs? technet.microsoft.com/en-us/library/cc512029.aspx Commented Mar 22, 2018 at 13:58
  • No errors for that specific report, only ProcessAborted ones that i stopped myself. Commented Mar 22, 2018 at 14:07
  • 2
    You should post the version of SQL Server / SSRS. Does this same behavior exist with multiple web browsers? Chrome gives me similar behavior and other weirdness, I usually have to use IE to get best behavior results with SSRS. Commented Mar 22, 2018 at 14:11
  • I have edited my post. Commented Mar 22, 2018 at 14:29
  • 1
    Any joy with IE? SSRS is so flaky in other browsers I tend to stick with IE for SSRS (and nothing else!). Commented Mar 22, 2018 at 14:53

2 Answers 2


Sometimes the browser will time out or otherwise not return a rendered report even though the process is still running in the background and ultimately succeeds. The browser will likely not even tell you it failed, it will just keep spinning or return a blank page. The logs are indicating "success" meaning the process itself did indeed run correctly, but the logs won't tell you if browser successfully returned a rendered report. I've usually seen this happen around the 10 minute mark, regardless of the configuration of server or report level timeout settings. Your Execution Log shows it as over 10 minutes, so this is the possible reason. Also, the Execution Log returned a massive Byte Count (~353 MB), and this may also be a culprit.

There are a few possible solutions to this problem:

  1. Limit the amount of data that will be rendered in browser using pagination. The Data Retrieval & Processing time should stay the same, but the Rendering time will be reduced as it is only returning the first page, and will only render other pages when you navigate to those using the arrows. Reflecting back on the aforementioned massive Byte Count, so somewhere along the way it may have broke the camel's back. Once the data is processed, exporting to a static format, such as Excel or PDF, will also likely be successful & should throw an error if it failed, rather than it attempting to render the entire report in browser as HTML.
  2. Deploy the report in the export format to a File Share using a Subscription. This will allow the process to run in the background on the server and render it to a file directly. If you are unable to schedule this on a regular interval, this may be a bit inconvenient for the user to request it from an admin and require that admin to manually deploy it. However, I believe this is better than the report user rerunning the same report multiple times, resulting in concurrent executions, further compounding processing issues, affecting all users.

I had the exact same issue. My SSRS report is bound to a SQL stored proc. After many attempts to run, i logged into SQL server, open the "Activity Monitor" and found several SUSPENDED threats. I killed all threads and my report worked

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.