Troubleshooting Report Manager Problems
Use this topic to troubleshoot problems that you encounter when using Report Manager.
If you enable Anonymous access for the report server virtual directory, you will effectively disable role-based security. All user connections to the report server are made with minimum permissions that do not provide access to server management features. Even members of the local administrator group will not have permission to access the Site Settings menu or set role-based security for items stored on the report server. To enable role-based security, disable Anonymous access for the report server virtual directory. For more information about authentication settings, see Configuring Authentication for Reporting Services.
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.
|You can also specify Web.config settings to configure proxy server settings. For more information, see Configuring a Report Server for Internet Access.|
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.
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.
By default, the Web.config file in SQL Server 2005 SP2 had the customErrors mode property set to off. As a best practice, you should configure the Web.config file for Report Manager so that the customErrors mode property is set to RemoteOnly. To configure this property, update the property to be <customErrors mode="RemoteOnly"> in the <system.Web> section of the Web.config file for Report Manager.
When this property is set to RemoteOnly and a request results in an error for which a custom error page is not defined, clients will receive a generic ASP.NET error page instead of a detailed error page. By configuring Report Manager in this way, you can reduce the possibility of disclosing sensitive information to client computers. The local computer will continue to receive detailed ASP.NET errors so that you can debug problems that occur.