October 9, 2017 at 4:10 am
Hi guys,
I am currently facing an issue with SSRS 2008 and I will like to get your support regarding this.
I have a report which can run without any problem, from report builder (prod).
However, when I run it directly from report server with IE11, It will show the following message after 2 minutes:"server is not responding due to a long-running script"
This only happen when my table have many records,in this case more than 5000 records should be displayed on the report.Once I removed this table from my report, It will run smoothly.
I have also tried to add the Page break option to "Keep together on one page if possible" but without any success.
Can you please give me any suggestions?
Thank you for your support.
Cheers,
October 9, 2017 at 4:28 am
The problem isn't IE11, it's that your SSRS instance is set to time out the query after 2 minutes. As your report is taking more than 2 minute to run and render, the error is presented.
You can change a report's time out settings in the processing options, when managing your report in the Web Portal. Alternatively, you can change the global default, which is would in the configuration file for Reporting Services. If I recall correctly, the node is called QueryTimeout, or DatabaseQueryTimeout. Most likely it will have a value of 120 (seconds), which is 2 minutes.
To amend the global setting you'll need to restart the SSRS service after saving the new copy of the configuration file. Personally, however, I prefer to stop it, save, and the start; just in case SSRS decides to save off the current settings when it stops (like some applications do).
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
October 9, 2017 at 6:11 am
Hi Thom,
Thank you for your prompt reply.
Regarding the Report timeout it's already set to 3600 seconds.(Site Setting->General->Report Timeout) but it does not solve the problem.
I have other report which run more than 2 min but provides results.
So I don't think it's related to that or maybe I am not looking in the right timeout configuration .
October 9, 2017 at 6:18 am
zouhair.ouichdani - Monday, October 9, 2017 6:11 AMHi Thom,
Thank you for your prompt reply.
Regarding the Report timeout it's already set to 3600 seconds.(Site Setting->General->Report Timeout) but it does not solve the problem.
I have other report which run more than 2 min but provides results.
So I don't think it's related to that or maybe I am not looking in the right timeout configuration .
What is the setting on the report itself?
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
October 9, 2017 at 6:33 am
From report server when I launch report builder to open the report and execute it,it works without any issue and I get results in about 2minutes.
What do you mean by report setting?
October 9, 2017 at 6:42 am
zouhair.ouichdani - Monday, October 9, 2017 6:33 AMFrom report server when I launch report builder to open the report and execute it,it works without any issue and I get results in about 2minutes.
What do you mean by report setting?
On the report itself you can also set time out settings. What does the report's own setting state?
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
October 9, 2017 at 7:02 am
From the report itself I set Report timeout on the processing option to 'Do not timeout report',I restarted Report server afterwards,but still the same issue.
October 9, 2017 at 7:26 am
Hi Tom,
I checked the logs and it seems that it initilaize the DatabaseQueryTimeout to 120 seconds.
So I run this script to put the time out unlimilited
EXEC sp_configure 'remote query timeout', 0 ;
GO
RECONFIGURE ;
GO
But I still have the same problem and the DatabaseQueryTimeout is still set to 120 seconds.
October 9, 2017 at 7:33 am
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
October 9, 2017 at 7:47 am
I changed the DatabaseQueryTimeout to 1200 seconds but still the same issue.
From Execution log in reporting database it shows that the report run successfuly after 2min,but still the error is there.
October 9, 2017 at 8:04 am
Here is the logs from report server
rshost!rshost!1b4c!10/09/2017-15:40:26:: i INFO: CLR runtime is initialized.
rshost!rshost!1b4c!10/09/2017-15:40:26:: i INFO: Derived memory configuration based on physical memory as 33553976 KB
appdomainmanager!DefaultDomain!16c4!10/09/2017-15:40:26:: i INFO: Entered managed ServiceMain in DefaultDomain.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing ConnectionType to '0' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing DatabaseQueryTimeout to '1200' second(s) as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException,Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Threading.ThreadAbortException,System.Web.UI.ViewStateException,System.OutOfMemoryException,System.Web.HttpException,System.IO.IOException,System.IO.FileLoadException,Microsoft.SharePoint.SPException' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing AuthenticationTypes to '5' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing RSWindowsExtendedProtectionLevel to 'Off' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing RSWindowsExtendedProtectionScenario to 'Proxy' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing EnableAuthPersistence to 'True' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing MemorySafetyMargin to '80' percent as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing MemoryThreshold to '90' percent as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: w WARN: Initializing UrlRoot to default value of '' because it was incorrectly specified in Configuration file as ''.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing IsReportManagerEnabled to 'True' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing MaxConnections to '2' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing Timeout to '10' second(s) as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing AppID to '(Default)' as specified in Configuration file.
library!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Initializing CacheLevel to 'Default' as specified in Configuration file.
resourceutilities!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Reporting Services starting SKU: Enterprise
configmanager!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Using report server internal url http://localhost:80/ReportServer_RSNATIVE.
configmanager!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Using report server external url http://SMUC3647:80/ReportServer_RSNATIVE.
configmanager!DefaultDomain!de0!10/09/2017-15:40:26:: i INFO: Using url root http://SMUC3647:80/ReportServer_RSNATIVE.
rshost!rshost!de0!10/09/2017-15:40:26:: i INFO: Configuring maxPhysicalCpu=8, minLogicalCpu=0
rshost!rshost!de0!10/09/2017-15:40:26:: i INFO: Logical processor per physical processor 1
rshost!rshost!de0!10/09/2017-15:40:26:: i INFO: Maximum logical CPU is 4
configmanager!DefaultDomain!de0!10/09/2017-15:40:27:: i INFO: Using report server internal url http://localhost:80/ReportServer_RSNATIVE.
configmanager!DefaultDomain!de0!10/09/2017-15:40:27:: i INFO: Using report server external url http://SMUC3647:80/ReportServer_RSNATIVE.
configmanager!DefaultDomain!de0!10/09/2017-15:40:27:: i INFO: Using url root http://SMUC3647:80/ReportServer_RSNATIVE.
appdomainmanager!DefaultDomain!de0!10/09/2017-15:40:27:: i INFO: Appdomain:2 WindowsService_0 started.
resourceutilities!WindowsService_0!de0!10/09/2017-15:40:27:: i INFO: Reporting Services starting SKU: Enterprise
library!WindowsService_0!8a4!10/09/2017-15:40:27:: i INFO: Catalog SQL Server Edition = Enterprise
October 9, 2017 at 12:00 pm
Thom A - Monday, October 9, 2017 7:33 AMDatabaseQueryTimeout is a setting in your SSRS config file, as I stated in my 1st reply. Sounds like that is still set to 120. Like I said before, check it and up the value if needed.
Hi Tom,
Unfortunately It still didn't solve the issue.
October 9, 2017 at 12:57 pm
Do you get the error with any other websites and IE 11? Have you tried another browser to see if you get the same error?
Also, Thom asked about the Reporting Services log and if there are any related errors in there. The log you posted above is just from Reporting Services starting up so it isn't going to provide any information. If you go to Report Manager, to the Report and run the report, that would log any potential errors for the report.
Sue
October 9, 2017 at 2:15 pm
zouhair.ouichdani - Monday, October 9, 2017 12:00 PMThom A - Monday, October 9, 2017 7:33 AMDatabaseQueryTimeout is a setting in your SSRS config file, as I stated in my 1st reply. Sounds like that is still set to 120. Like I said before, check it and up the value if needed.Hi Tom,
Unfortunately It still didn't solve the issue.
Did you stop SSRS before making the change and start it back up after doing so?
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply