Return to Question

We have a simple SSRS report that acts as a landing page. It has hyperlinks to subsequent report.

It seems the problem is that SSRS somehow treats these connections differently than if a real user hits the report. Even though the report is run it doesn't appear to be handled in the same way as if a user is hitting it via the portal. And so.. the first user get hit with a big delay.

Using the F12 debugging features in internet explorer, I managed to reproduce and capture what the browser is seeing. SSRS only took 4 seconds to produce and return the report, however in the browser it took 122 seconds from click "go" to the screen being rendered. 2 minutes!!! No wonder users are complaining.

We have a simple SSRS report that acts as a landing page. It has hyperlinks to subsequent reports.

It seems the problem is that SSRS somehow treats these connections differently than if a real user opens the report through a web browser. Even though the report is run it doesn't appear to be handled in the same way as if a user is hitting it via the portal. And so.. the first user experiences a big delay.

Using the F12 debugging features in internet explorer, I managed to reproduce and capture what the browser is seeing. SSRS only took 4 seconds to produce and return the report, however in the browser it took 122 seconds from trying to open the URL to the screen being rendered. 2 minutes!!! No wonder users are complaining.

Looking at my SSRS log files in: C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\LogFiles

It appears that the SSRS appdomain is restarting or reloading.

Looking at my SSRS log files ( Located in: C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\LogFiles) it appears that the SSRS appdomain is restarting or reloading.