Troubleshooting Report Manager Problems
Use this topic to troubleshoot problems that you encounter when using Report Manager.
A network error occurs when launching Report Manager as https://localhost/reports
If you get a network error when starting Report Manager, you might need to adjust the LAN settings for your browser. In Internet Explorer, open the Internet Options dialog box, click Connections, click LAN Settings, and select Bypass proxy server for local addresses.
Note
You can also specify Web.config settings to configure proxy server settings. For more information, see Planning for Extranet or Internet Deployment.
Report Manager cannot be started
If you can access the report server at http://<webservername>/reportserver but you cannot start Report Manager, check the report server virtual directory setting in the RSReportServer.config file and verify that it is referencing a valid report server instance. For more information, see RSReportServer Configuration File.
Report Manager starts slowly
Report Manager requires extra time to load the initial page. Additional wait time is required to start ASP.NET. After the initial page opens in the Web browser, subsequent application pages open much faster.
Selected Pages in Report Manager do not open
If you are using Internet Information Services (IIS) 6.0 configured with default settings on your report server, you must add the Web server name as a Trusted Site (for example, http://mywebservername). Otherwise, you cannot open the New Folder page, New Data Source page, and Upload File page from the Contents tab. Also, the frameset used in Report Manager Help does not open correctly.
Report Manager or the report server runs very slowly
In some circumstances, ASP.NET applications run very slowly on computers that are running anti-virus software. If the Report Server Web service is restarting frequently, and you are running anti-virus software, you can obtain an ASP.NET fix from Microsoft Customer Support Services.
Symptoms include Web applications or Application Domains restarting for no apparent reason, slow performance, session restarts, and more. For more information about the symptoms, cause, and resolution, see Microsoft Knowledge Base article 821438.
You can find out whether there are excessive server restarts by viewing the number of reportserver_<timestamp>.log files. A new log is created each time the server starts. A large collection of logs created at very short intervals is an indication that the conditions described in article 821438 exist on your server.