Hi,I have reporting service running off IIS 7.0 (Windows Server 2008/SQL Server 2005).Any report which takes more than 2 minutes to return data times out. I have increased the timeouts on dataset, IISconnection timeout, setping enabled= false in application ppol settings, set report execution time out to never time out. The report runs finewhen run through visual studio 2005 on my local machine & also runs fine in scheduled mode.Its only when I change my selection on the go try to bring back a report does it time out. What am I missing?Pankaj Mhatre

Which layer is showing you the Timeout message?Regards.Mike

I am not sure if I understood your question correctly but hope this helps. I am pasting the screen error, log file(reportserverwebapp.log) entry and the executionlog table entry below:The screen error is as below: The requested URL could not be retrieved While trying to retrieve the URL: <Link to report >The following error was encountered: We can not connect to the server you have requested. This means that: The server might be busy at this time. The server is not reachable. Please try later to see if you can go through. -----------------------------------------------------------This is what shows in the log file(reportserverwebapp.log)<Header> <Product>Microsoft SQL Server Reporting Services Version 9.00.3282.00</Product> <Locale>en-US</Locale> <TimeZone>Eastern Daylight Time</TimeZone> <Path>c:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\LogFiles\ReportServerWebApp__04_16_2009_12_35_05.log</Path> <SystemName>USTRYSVTRPTSVC1</SystemName> <OSName>Microsoft Windows NT 6.0.6001 Service Pack 1</OSName> <OSVersion>6.0.6001.65536</OSVersion></Header>w3wp!library!4!4/16/2009-12:35:05:: i INFO: Initializing ReportBuilderTrustLevel to '0' as specified in Configuration file.w3wp!library!4!4/16/2009-12:35:05:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.w3wp!library!4!4/16/2009-12:35:05:: i INFO: Initializing MaxScheduleWait to default value of '1' second(s) because it was not specified in Configuration file.w3wp!library!4!4/16/2009-12:35:05:: i INFO: Initializing DatabaseQueryTimeout to default value of '30' second(s) because it was not specified in Configuration file.w3wp!library!4!4/16/2009-12:35:05:: i INFO: Initializing ProcessRecycleOptions to default value of '0' because it was not specified in Configuration file.w3wp!library!4!4/16/2009-12:35:05:: i INFO: Initializing RunningRequestsScavengerCycle to default value of '30' second(s) because it was not specified in Configuration file.w3wp!library!4!4/16/2009-12:35:05:: i INFO: Initializing RunningRequestsDbCycle to default value of '30' second(s) because it was not specified in Configuration file.w3wp!library!4!4/16/2009-12:35:05:: i INFO: Initializing RunningRequestsAge to default value of '30' second(s) because it was not specified in Configuration file.w3wp!library!4!4/16/2009-12:35:05:: i INFO: Initializing CleanupCycleMinutes to default value of '10' minute(s) because it was not specified in Configuration file.w3wp!library!4!4/16/2009-12:35:05:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.w3wp!library!4!4/16/2009-12:35:05:: i INFO: Initializing WatsonFlags to default value of '1064' because it was not specified in Configuration file.w3wp!library!4!4/16/2009-12:35:05:: i INFO: Initializing WatsonDumpOnExceptions to default value of 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' because it was not specified in Configuration file.w3wp!library!4!4/16/2009-12:35:05:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to default value of 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' because it was not specified in Configuration file.w3wp!library!4!4/16/2009-12:35:05:: i INFO: Initializing SecureConnectionLevel to default value of '1' because it was not specified in Configuration file.w3wp!library!4!4/16/2009-12:35:05:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.w3wp!library!4!4/16/2009-12:35:05:: i INFO: Initializing WebServiceUseFileShareStorage to default value of 'False' because it was not specified in Configuration file.w3wp!ui!4!4/16/2009-12:35:05:: v VERBOSE: User map'<Users><User><Name /><Paths><Path>/Reports/Pages/Folder.aspx</Path><NrReq>2</NrReq></Paths></User></Users>'w3wp!ui!5!4/16/2009-12:35:05:: v VERBOSE: User map'<Users><User><Name /><Paths><Path>/Reports/Pages/Folder.aspx</Path><NrReq>2</NrReq></Paths></User></Users>'w3wp!ui!8!4/16/2009-12:35:16:: v VERBOSE: User map'<Users><User><Name /><Paths><Path>/Reports/Pages/Folder.aspx</Path><NrReq>3</NrReq></Paths></User></Users>'w3wp!ui!8!4/16/2009-12:35:52:: e ERROR: The report server is not responding. Verify that the report server is running and can be accessed from this computer.w3wp!ui!8!4/16/2009-12:35:52:: e ERROR: HTTP status code --> 500---------------------------------------------------------The table entry is as below: InstanceName ReportID UserName RequestType Format Parameters TimeStart TimeEnd TimeDataRetrieval TimeProcessing TimeRendering Source Status ByteCount RowCount SERVERNAME ID sysadmin 0 HTML4.0 param1=0&param2=2 4/15/09 5:17 PM 4/15/09 5:20 PM 0 158732 0 1/1/1900 0:00 rsProcessingAborted 0 88 ----------------------------------------------------------What seems to be the issue here?Pankaj Mhatre

pankaj, I am having almost the same error on a sharepoint server. did you ever discover a solution to this problem?my blog - Tea Time with Meowkins

Looks like most of the time is being spent on the Report Processing. But I would suggest you to check if there is any Report timeout option being set in the Report manager. On the Report manager page, go to site settings, and you will find an option to never timeout report execution. Check the default value, and set to never timeout option, and then check the behavior. You might be hitting the ASP.NET timeout values. Check the web.config file of Report Server and Report Manager, and verify executionTimeOut values For SharePoint integrated mode check: http://portal.sqltrainer.com/2008/05/sharepoint-sql-server-reporting.html Check for the values TimeOut settings mentioned on this blog for SSRS: http://blogs.msdn.com/b/emilianb/archive/2009/05/28/timeouts-and-microsoft-sql-server-2005-reporting-services.aspx Hope this helps!! Chaitanya