Enable Remote Errors (Reporting Services)

You can set server properties on a Reporting Services report server to return additional information about error conditions that occur on remote servers. If an error message contains the text:

• "For more information about this error, navigate to the report server on the local server machine, or enable remote errors",

You can set the EnableRemoteErrors property to access additional information that can help you troubleshoot the problem. For more information, see Report Server System Properties in SQL Server Books Online.

In this topic:

• Enable Remote errors for SharePoint Mode

• Enable remote errors through SQL Server Management Studio (Native Mode)

• Enable remote errors through script (Native Mode)

• Modifying the ConfigurationInfo table (Native Mode)

Enable Remote Errors for SharePoint Mode

There are two different procedures for enabling remote errors for Reporting Services SharePoint mode. The procedure is different for the two different report server architectures. The newer SharePoint service based architecture that was introduced in the SQL Server 2012 release, utilizes a setting that can be configured for each Reporting Services service application. The older architecture utilizes a single site level setting.

Enable Remote errors for a Reporting Services Service Application

1. For a SharePoint mode report server installed with SQL Server 2012 or a newer version of Reporting Services, enable the service application setting Enable remote errors. The setting can be configured for each Reporting Services service application.

2. In SharePoint Central Administration, click Manage service applications in the Application Management group.

3. Find your service application and click the name of your service application.

4. Click System Settings.

5. Click Enable Remote Errors in the Security section.

6. Click OK.

   Top

Enable Remote Errors for a SharePoint Site

1. For a SharePoint mode report server installed with a version of Reporting Services prior to SQL Server 2012, enable the site setting Enable remote errors in local mode.

2. In Site Actions click Site Settings for the site you want to modify.

3. Click Reporting Services Site Settings in the Reporting Services group.

4. Click Enable remote errors in local mode.

5. Click OK

   Top

Enable remote errors through SQL Server Management Studio

1. Start Management Studio and connect to a report server instance. For more information, see Connect to a Report Server in Management Studio in SQL Server Books Online.

2. Right-click the report server node, and select Properties.

3. Click Advanced to open the properties page. For more information, see Server Properties (Advanced Page) - Reporting Services in SQL Server Books Online.

4. In EnableRemoteErrors, select True.

5. Click OK.

   Top

Enable remote errors through script

1. Create a text file and copy the following script into the file.

   Public Sub Main()
     Dim P As New [Property]()
     P.Name = "EnableRemoteErrors"
     P.Value = True
     Dim Properties(0) As [Property]
     Properties(0) = P
     Try
       rs.SetSystemProperties(Properties)
       Console.WriteLine("Remote errors enabled.")
     Catch SE As SoapException
       Console.WriteLine(SE.Detail.OuterXml)
     End Try
   End Sub
   

2. Save the file as EnableRemoteErrors.rss.

3. Click Start, point to Run, type cmd, and click OK to open a command prompt window.

4. Navigate to the directory that contains the .rss file you just created.

5. Type the following command line, replacing servername with the actual name of your server:

   rs -i EnableRemoteErrors.rss -s https://servername/ReportServer
   

6. For more information, see rs Utility (rs.exe) (SSRS)

   Top

Modifying the ConfigurationInfo table

• Note

  You can edit the ConfigurationInfo table in the report server database to set EnableRemoteErrors to True, but if the report server is actively used, you should use SQL Server Management Studio or script to modify the settings. If you modify the setting in the database, you need to restart the service before the changes take effect.

  Top