I have a fresh install of SQL Server 2008 SP1 64bit and Reporting services on a Windows 2008 R2 machine with 6Gb ram and 2x Xeon 3.2Ghz CPUs. CPU usage is averaging around 3%, and there is around 4gb memory available. However, even with SQL and SSRS being freshly installed, and with no reports or data sources uploaded to the report server, and no databases created on the SQL server, already the Report Manager (http://localhost/reports) is very slow to use. Switching between the "Contents" and "Properties" pages takes around 10 seconds for each page to load. I have tried both with and without SSL and it doesn't seem to make any difference. I created a very basic report (just a textbox, no datasets) and the report also takes around 15 seconds to render. While I am waiting for these pages and report to load, the CPU and ram usage don't appear to change. I have another machine (Dual core 3.2Ghz, 2Gb ram) also with SQL 2008 64bit and SSRS installed, and Report Manager on that computer is almost instant when flicking between pages. I have tried uninstalling and reinstalling SQL and SSRS, but thus has not made any difference.

Hi, It sounds weird. Please refer to the part "Report Manager or the report server runs very slowly" of this aticle http://msdn.microsoft.com/en-us/library/ms345220.aspx to see if it is like your issue. If yes, you can request the asp.net fix to solve this issue from Microsoft Customer Support Services. thanks, Jerry

Unfortunately no those symptoms are not quite accurate: 1. Report Manager is able to start, it is just slow 2. All page loads are slow, not just the initial load. 3. All pages load eventually 4. I have un-installed Nod32 Antivirus which made no difference. Also, there is only one reportserver_<timestamp >.log file per day for Reporting Services.

Has there been a solution or any furth info on this? I am now experiencing this exact same behaviour with a fresh install of SQL 2008 R2. Craig Bryden - Please mark correct answers

I have exact same situation which I was unable to solve in 6 months. Just today I found something that I hope will help someone to resolve the issue: If I try using http://localhost/reportserver instead of http://localhost/reports then everything works very fast!!! What is happening? Tom.