Use this section to help you troubleshoot SQL Server Reporting Services. For additional troubleshooting information related to SQL Server Reporting Services, go to http://msdn.microsoft.com/en-us/library/ms159135.aspx.
|
Problem |
Solution |
|---|---|
|
One of the following messages appears when you are browsing to http://localhost/reportserver OR http://localhost/reports:
|
Note:
Start the Reporting Services Configuration Manager. This tool is located under the program group for your edition of SQL Server software (for example, Microsoft SQL Server 2014 > Configuration Tools > SQL Server Reporting Services Configuration Manager). Verify that each component is configured properly. For details, see Verifying SQL Server Report Server configuration. |
|
When you attempt to verify that SQL Server Reporting Services is running, the following message appears (where 20xx is 2016, 2014, or 2012):
|
To resolve this error, follow these steps:
|
|
When you attempt to verify that SQL Server Reporting Services is running, you are presented with a Windows Security login prompt. |
Enhanced security in the browser is preventing you from loading the page. Run the Internet Explorer web browser as an administrator (right-click the Internet Explorer icon, select Run or Run as Administrator). Then, try to load the Reporting Services page. If the Reporting Services page still does not appear, log in to the operating system with the Administrator account and run the Internet Explorer web browser as an administrator. When the Windows Security login prompt appears, enter Administrator as the user name and the Administrator's password. Wait for the Reporting Services page to appear. If the Reporting Services page still does not appear, turn off IE Enhanced Security for the server operating system by following these steps:
|
|
When you attempt to verify that SQL Server Reporting Services is running, you see this message:
|
The Reporting Services log file contains the error No DSN present in configuration file. A database connection to Reporting Services has not been created. Start the Reporting Services Configuration Manager. This tool is located under the program group for your edition of SQL Server software (for example, ). Perform the steps in Specific system requirements for the Metasys Advanced Reporting System. |
|
When you attempt to verify that SQL Server Reporting Services is running, a scripting error occurs. |
Enhanced security in the browser is preventing you from loading the page. Add the computer as a trusted site. For example, if the computer is called ADX-01, add http://ADX-01 to the list of trusted sites under security options for the browser. Alternatively, turn off IE Enhanced Security for the server operating system by following these steps:
|
|
You configured SQL Server Reporting Services, but you cannot connect to http://localhost/reportserver or http://localhost/reports. |
Make sure you are verifying SQL Server Reporting Services on the correct computer. In a split ADX, this computer is the web/application server. Also, if you are using a SQL Server named instance other than MSSQLSERVER, use a web address that includes the suffix _instancename, where instancename is the SQL Server instance name. For example: http://localhost/ReportServer?ThisInstance http://localhost/ReportServer_ThisInstance. Lastly, on a split ADX, the Reporting Services Database Setup/Database Connection might not be configured properly. See Verifying SQL Server Report Server configuration. |
|
When you have the Reporting Configuration Manager open for SQL Server software, and make a change under Service Manager, the following Backup Encryption Key dialog box appears: |
The backup encryption key is not used by Metasys software. However, to satisfy Reporting Services configuration, click the browse button (...), specify a file name for the encryption key, and click OK. Specify a password for the file and click OK. |
|
You are installing SQL Server software with Reporting Services, but the Install the native mode default configuration option is unavailable. |
This problem may occur when SQL Server software is already installed on the ADX and you install the software again to add Reporting Services. To resolve this problem, follow these steps:
|