Unable to connect to remote server - SSRS 2008 - webservice
I have an asp.net page that is trying to access the SSRS 2008 Report Server through the ReportViewer control. The reports are accessed using a proxy server account that is configured with the Browser role on the server. With a normal report access script, this setting works fine. but whenever we try to load a test page using 100 virtual users, we start seeing "unable to connect to remote server" errors. Load test is set to start with 10 users and deploy 10 users every 30 seconds. the test is configurable for 30 minutes.
The stack trace looks like this:
System.Net.WebResponse GetWebResponse (System.Net.WebRequest) System.Web.Services.Protocols.WebClientProtocol.GetWebResponse (WebRequest request) at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse request .Execution.RSExecutionConnection.GetWebResponse (WebRequest request) at Microsoft.Reporting.WebForms.ServerReportSoapProxy.GetWebResponse (WebRequest request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke.Protocols (String) .Execution.ReportExecutionService.LoadReport (String Report, String HistoryID) at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.LoadReport (String Report, String HistoryID) at Microsoft.Reporting.WebForms.ServerReport.GetExecution.Report () ...ServerReport.SetParameters (IEnumerable`1 parameters)
Is there anything in the report server configuration that needs to be changed to support one such load profile?
I guess 100 users are not that much fit for the box considering the box has a QuadCore Xeon 3.Ghz and 10GB of RAM.
a source to share
Some questions;
What is the observed load on the report server; depending on the report, you can overload it with low user counts by returning thousands upon thousands of rows of data and manipulating them. Depending on how you load your VU, you may be pumping too much data / requests too quickly.
Is there an adaptive Windows firewall / firewall on one of the computers? Some firewalls would treat this load test as hostile behavior and block it partially in the test.
Have you ruled out the AD problem? If the sqlserver configuration in AD is not configured correctly (trusted for delegation and has a registered SPN) and is / is the executor of the AD server (s) during the test execution; I was involved in a load test on one site that used regular domain servers; During the test, we kicked users out of non-testing applications and servers across the network as we were overloading domain controllers with millions of requests through poorly configured servers.
a source to share
I strongly believe your SSRS server is overloaded. Are you hosting your SSRS on a shared or dedicated server? If you are hosting it on a shared server, you should talk to your host about this issue. I host my SSRS 2008 at asphostdirectory.com and so far the service is really excellent! I can remotely connect to my ReportManager and I can manage my reports online. So far, I pay about $ 6.99 a month to host my site with them, and of course this is the best I can get at the moment.
If you are hosting your SSRS on a dedicated server, you should consider updating the server resources. If you do have 10GB with a Quad Core server, you shouldn't have any problems at all! I'm not sure how much traffic your SSRS can generate, but I do believe that a DEDICATED server with 4GB of RAM is much more than enough to handle only 100 concurrent users.
Hope it helps
You might want to check the application pool settings for the website that hosts the SSRS service. Make sure none of the query limits are set to anything low. You can change some parameters and rerun your tests to see if it has any effect anyway.
Also, if you are starting with 10 users, add 10 more users every 30 seconds and run the test for 30 minutes, wouldn't that be more than 600 users? Or do you stop adding users after five minutes?
a source to share