We have a problem with the Reporting Services 2008 R2 (Developer Edition) 64bit version. A colleague of mine is experiencing problems when connecting to the ReportServer address. The first time is really slow (as usual, this is by design we know). But after that it should work great. Instead after 20-30 seconds on incativity with the ReportServer it stops. So the next time he access the ReportServer it needs to reaload (agian!). In the log we can read: "Reporting Web Server stopped". The configuration is standard, we didn't changed any particular parameter. On my PC (I have same edition but 32bit version), I'm not experiencing this problem and I didn't even found the message in the log. Someone is experiencing this problem of have any idea of what is causing it?

Hi Wang, first of all thanks for reply. Actually the problem is slightly different. The fact is that the reporting services are unloaded (not stopped) after an incativity of about 30 seconds. You know that the first time you access the reporting services they need to load all the web stuff. They keep on unloading/loading. A system reboot solved the problem. Anyway it seems that when they are running low of resources they auto unload. Like sql server does for the databases, to try to free some resources. This is not such a great beaviour, at least not with such a short timeout.

Hi Luigi, Thanks for your question here. According to your description, my understanding is that: when user opened the reportserver in browser, after 20-30 seconds without any operations, when you click any links in reportserver webpage, it will display an error about the reportserver is stops, however, if didn’t keep inactivity or on inactivity in a short time, the error doesn’t appear, right? If I misunderstand your question, please let me know. In this case, please check the default value of Report Execution Timeout by detail steps: 1. Open the ReportManager. 2. Click on the Site Setting link button on the top right corner. 3. By default, check the check box of Limit report execution to the following number of seconds: 1800. Hope it helps you. If the issue still exists, please feel free to let me know. Thanks, Sharp Wang Please remember to mark the replies as answers if they help you and unmark them if they provide no help.