I have SSRS 2005 on a Win2k3 SP2 box in a domain with Active Directory on Win2k8 machine. The RS and SQL Db are on the same box. Hello, I am having a problem that just started in the last 6 weeks. When a user accesses RS from inside the domain everything is fine, but when someone tries to access the report outside of the domain, even with a domain account, the reports that take more than 5 min to run never return. If the report is less than 5 min, they return fine. The ExecutionLog shows the report completes, but the browser is just sitting there spinning. There are no errors in the Event Log or the IIS Log. Please Help!

Hi, Based on your issue description, does it also take more than 5 minutes from inside the domain to execute the report which fail to be returned ? Please check it. If no, please set bigger time-out value for the report while running from outside of the domain. How to set report time-out value, please access http://msdn.microsoft.com/en-us/library/ms155782.aspx . If yes, I think you need to troubleshoot the network load issue. Thanks, Jerry

Hello, Yes, it does take more than 5 minutes to run inside of the domain too. When I check the IIS logs, it appears that the out of domain request returns with a 200 code, but the report never displays on the browser outside of the domain, It just continues to spin the "Generating Report" icon. Thanks

Hi, In your 2nd POST, you said it just continues to spin the Generating Report icon. But how many minutes it will take to the end, and whats the end result? This issue is caused by either SQL server & report manager or Networkperformance issue, you can identify which one by my suggestions. If its on SQL server & report manager, please post the exception information you see. If its a network load issue, you can split the large report into multiple small reports. Please followthe suggestions for further troubleshooting and work around: In order tovalidate anything to do with report manager & sql server, we use report exectution timeout featurefor test. 1. I assume the report takes 7 minutes to run inside of domain, and is never returned from outside of domain as it just continues to spin the Generating Report icon, please follow the steps below: 1) Set this report execution timeout value for 5400 seconds(>7minutes), you can do it in this report property page->Execution option->Report Execution Timeout->Limit report execution to the following number of seconds 2) Please make sure this report still works properly inside of the domain after set its timeout setting, then run this report from outside of the domain. 3) After 7 minutes, please use sp_lock command in SQL server management studio to check any locked resources and any error messages in the report execution. 4) After 9 minutes, does it continue to spin the Generating Report icon? Please use step 3 to check error message. 5) If no any exception error occurred in SQL server and report manager, we can be sure that this report has been produced, and is now being loaded in your network. If an exception error occurred, please post it to us. 2. If you did not find any exceptions after 9 minutes in step 1-5, then the root cause is a network performance issue, I advise you to split this large report into multiple small reports to avoid the network bottleneck. For example, split the year report into 4 quarter reports. Please try these and let me know the result. Regards, Jerry

Thanks for the quick response. I have narrowed it down to when the report is greater than 2 minutes, this occurs, otherwise it will return fine. I was seeing a lot of NetBIOS traffic going on, so I disabled that. The problem is that all of these reports were working just fine before around 4/25/2009, I rolled back all of the Windows updates to see if that helped and it didn't. I tried your suggestions and still nothing, I have the default execution time in the web.config set at<httpRuntime executionTimeout="9000" /> Here is the IIS log from a request that just sit there. #Software: Microsoft Internet Information Services 6.0 #Version: 1.0 #Date: 2009-06-19 04:21:58 #Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs-version cs(User-Agent) cs(Cookie) cs(Referer) cs-host sc-status sc-substatus sc-win32-status sc-bytes cs-bytes time-taken 2009-06-19 17:05:17 W3SVC1 10.1.1.107 GET /EncompassReportServer /CSTS/Incident_Report_byQuarter_for4&rs:Command=Render&rc:Toolbar=false&county=Monroe&FiscalYear=2009&teamType=%&sentinel=%&critical=%&rs:Format=HTML4.0 80 - 12.159.32.66 HTTP/1.1 Mozilla/5.0 - - 10.1.1.107 401 2 2148074254 1872 364 0 2009-06-19 17:05:17 W3SVC1 10.1.1.107 GET /EncompassReportServer /CSTS/Incident_Report_byQuarter_for4&rs:Command=Render&rc:Toolbar=false&county=Monroe&FiscalYear=2009&teamType=%&sentinel=%&critical=%&rs:Format=HTML4.0 80 - 12.159.32.66 HTTP/1.1 Mozilla/5.0 - - 10.1.1.107 401 1 0 1803 454 0 2009-06-19 17:10:12 W3SVC1 10.1.1.107 GET /EncompassReportServer /CSTS/Incident_Report_byQuarter_for4&rs:Command=Render&rc:Toolbar=false&county=Monroe&FiscalYear=2009&teamType=%&sentinel=%&critical=%&rs:Format=HTML4.0 80 WCHOATPCE\encompass 12.159.32.66 HTTP/1.1 Mozilla/5.0 - - 10.1.1.107 200 0 121 0 610 294861 I see this sc-win32-status code of 121 a lot. Here is the report server log: w3wp!runningjobs!5!6/19/2009-13:06:16:: i INFO: Adding: 1 running jobs to the database w3wp!session!7!06/19/2009-13:07:57:: e ERROR: Client does not support cookies, session will be disabled w3wp!webserver!7!06/19/2009-13:07:57:: i INFO: Processed report. Report='/CSTS/Incident_Report_byQuarter_for4', Stream='' Here is the Report Execution Log: Instance Name, ReportID, Username, RequestType, Format, Parameters, TimeStart, TimeEnd, TimeDataRetrieval, TimeProcessing, TimeRendering, Source, Status, ByteCount, RowCount, ItemID, Path, Name WSHSQLRPT E0805C49-735B-4A7A-949D-375EE69B2ECD WCHOATPCE\encompass 0 HTML4.0 county=Monroe&FiscalYear=2009&teamType=%&sentinel=%&critical=% 2009-06-19 13:05:17.427 2009-06-19 13:07:57.350 159826 16 6 1 rsSuccess 34201 41 E0805C49-735B-4A7A-949D-375EE69B2ECD /CSTS/Incident_Report_byQuarter_for4 Incident_Report_byQuarter_for4 thanks

Hi, I am researching the logs you post. In report server and Report Execution logs: Everything is ok. This says that this report runs successfully in the report server side. Based on the third part of IIS logs, the IIS has sent out the data so that the HTTP status is 200(success). But the client or intermediate router maybe reset the session, which makes the IIS log the win-32-status as 121(The semaphore timeout period has expired). Can you capture a trace on the client and server simultaneously when requesting the report from outside of domain? By the way, is the client Microsoft IE? Regards, Jerry

Hi Jerry, Thanks for looking into this. So I did a Network Monitor trace on the server and nothing looks out of the ordinary between a successful report and a failing report. Has there been anything in any recent Windows updates that may have caused this problem? I can't seem to export the Network Monitor capture file, can I upload that file to you? Thanks

Hi Jerry, Now we are getting an IIS error of 200 0 64 and no 121 Semaphore errors Thanks

Hi Jernel Did you manage to solve the problem described in this thread. We seem to encounter the same issue in our reporting services. Thanks

No answer, so this issue might be still open... I had the same problem and after searching all configurable parameters in SSRS, there's nothing that defaults to 5 minutes (or 300 seconds). so I looked a bit deeper and found the cause: in almost any firewall, the HTTP-session timeout defaults to 5 minutes (or 300 seconds). changing the default value (at both sides if you're working in an LAN-to-LAN vpn environment or whatever) to at least the time the report needs to run sovles the problem. regards, Tom