 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Services / Reporting Services / August 2008Deep Integration Sharepoint (MOSS) SSRS - timeout issue
When I try running a specific report with a specific set of criteria, I get the [HttpException (0x80004005): Request timed out.] error and the report fails. Running the same report and same criteria even database connection in Native mode works albeit taking 3min 35 seconds to find 3 records I have tried increasing timeouts across MOSS in about 4 places, but still I get the timeout issue. Can someone tell me where else there is a stupid timeout limit that I can increase to allow this report (and others) to run just like Native Reporting Services does. HELP Please  SignatureSteve G Hi Steve, I understand that you encountered the query timeout when you ran your report. You had tried increasing timeout values in MOSS, however this issue persisted. If I have misunderstood, please let me know. Not sure if this issue was related to SQL Server Reporting Services or your MOSS. From the perspective of SSRS, There are some timeout settings in Report Server. You can find them in the report server configuration file (%SYSTEMDRIVE%\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer). You can refer to the following article: RSReportServer Configuration File http://technet.microsoft.com/en-us/library/ms157273.aspx Please try changing DatabaseQueryTimeout to 600 to see if it helps. By default the timeout value is 120 seconds. For MOSS, after my discussion with some Sharepoint professional, we recommend that you first check what the executionTimeout value is in your web.config file and change it to a large value, for example: <httpRuntime executionTimeout="900" maxRequestLength="512000" /> Hope this helps. If you have any other questions or concerns, please feel free to let me know. Best regards, Charles Wang Microsoft Online Community Support =========================================================== Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg@microsoft.com. =========================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ============================================================ SignatureThis posting is provided "AS IS" with no warranties, and confers no rights. ========================================================= Set the rsreportserver.config value as you said <Add Key="DatabaseQueryTimeout" Value="600"/> had already set the Sharepoint ones <httpRuntime maxRequestLength="10240" executionTimeout="36000" /> Still getting the timeout error within 2 minutes. What next please. As I said same report works fine in Native mode on a remote report server accessing my local sql database The timeout is when I access same database using local deep integrated sharepoint SignatureSteve G > Hi Steve, > I understand that you encountered the query timeout when you ran your [quoted text clipped - 52 lines] > This posting is provided "AS IS" with no warranties, and confers no rights. > ========================================================= Hi Steve, Thank you for your response. From your description, I think that we can exclude the SSRS factor. This issue should be caused by some configuration at Sharepoint side.From my research, I find that there is a setting "Report Processing Timeout" in Sharepoint Central Administration, you may change it to a larger value according to this article to see if it helps: How to: Configure the Report Server Integration Feature in SharePoint Central Administration http://msdn.microsoft.com/en-us/library/bb326213.aspx Hope this helps. Best regards, Charles Wang Microsoft Online Community Support ========================================================= Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg@microsoft.com. ========================================================= SignatureThis posting is provided "AS IS" with no warranties, and confers no rights. ========================================================= Hi Charles, thanks for your reply. Unfortunately this is another of the timeout settings things I had already tried along with about 4 others they are. 1) Configure Reporting Services Integration - report processing was 1800 seconds now set to do not timeout report processing 2) Central Admin operations - data retrieval service response was 3000 now 10000 3) Search Service Timeout was 60 now 600 4) Database Connection timeout set to 600 from 15 5) rsreportserver.config increased databasequerytimeout to 600 6) the reportserver web.config <httpRuntime executionTimeout = "9000" /> Now where else are there any more of these stupid timeout errors and how on earth can we track down which one is causing the actual error within SSRS Deep Integration?! Sorry for getting frustrated here, but as you may imagine this has now been going on for much too long already and we need a quick answer now to get rid of this and move onto something much more interesting! Regards SignatureSteve G > Hi Steve, > Thank you for your response. [quoted text clipped - 22 lines] > This posting is provided "AS IS" with no warranties, and confers no rights. > ========================================================= > When I try running a specific report with a specific set of criteria, I get the > > [HttpException (0x80004005): Request timed out.] > > > error and the report fails. Where did you get this error-message from? I also have a report which is not accessable via the web (MOSS), but can be viewed in the BI-studio. I tend to say it's due to some kind of timeout, since the reports takes a significantly amount of time in the BI-studio. But looking at the logs of MOSS and the reportsserver reveals nothing ... Did you solve your problem anyhow? Hi Henning, It has been such a long time since i did anything with this, but if I remember my issue seemed somehow related to my installing of Office Communicator, and as soon as I uninstalled this, my timeouts dissappeared completely. It may not have been purely related to Office Comunicator though, because I have reinstalled and uninstalled it and when I have had it installed subsequently I did not notice the timeouts. I may not have been testing the reports as vigorously though, and maybe the network was not as busy etc.... My first guess would be if you have installed something recently which seems to have any relationship to the timeouts happening, try uninstalling and see if that solves it. Also clearly if you have Office Communicator, that would be good to start with. Microsoft have been unable to deny or verify any relationship though between Office Communicator and timeouts. Hope that lot helps. Cheers SignatureSteve G > > When I try running a specific report with a specific set of criteria, I get the > > [quoted text clipped - 11 lines] > > Did you solve your problem anyhow? > It has been such a long time since i did anything with this, but if I > remember my issue seemed somehow related to my installing of Office [quoted text clipped - 4 lines] > testing the reports as vigorously though, and maybe the network was not as > busy etc.... Well, acutally this is not happening at my site, but at a customer site. And as far as I understand this is affecting not only one client, but a lot of clients. But I will check and make sure they're not using communicator or any other new software :) But how did you figure the exact error message? Did you find that in a logfile or did you disable custom errors within moss? I would not know how to disable custom errors, although I may have worked it out then I guess. AS far as I remember the error just showed up on the screen where I would expect the report to be seen. Let us know when you solve this as I am sure that it will be something of interest to everyone at this 'bleeding edge'! Steve G > > It has been such a long time since i did anything with this, but if I > > remember my issue seemed somehow related to my installing of Office [quoted text clipped - 12 lines] > But how did you figure the exact error message? Did you find that in a > logfile or did you disable custom errors within moss? > I would not know how to disable custom errors, although I may have worked it > out then I guess. AS far as I remember the error just showed up on the screen > where I would expect the report to be seen. But your accessing the reports from the MOSS integrated mode, right? I only get a standard moss error-message stating "an error occurred". Sorry I can't remember if I disabled custom errors etc..., but if you do not get timeout error message then how do you knowit is a timeout error? Sorry I cant be any more help, but suggest you do check log files and do the custom error thing etc. You may just need to raise a Support Incident for your customers to get working quickly. Good luck with that. SignatureSteve G > > I would not know how to disable custom errors, although I may have worked it > > out then I guess. AS far as I remember the error just showed up on the screen > > where I would expect the report to be seen. > > But your accessing the reports from the MOSS integrated mode, right? I only > get a standard moss error-message stating "an error occurred". |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.