Home Library Learn Downloads Support Community
Sign in | United States - English | |
1 out of 9 rated this helpful - Rate this topic

How to: Enable Remote Errors (Reporting Services Configuration)

SQL Server 2008

You can set server properties on a 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.

NoteNote

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.

Enable remote errors through SQL Server Management Studio

  1. Start Management Studio and connect to a report server instance.

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

  3. Click Advanced to open the properties page.

  4. In EnableRemoteErrors, select True.

  5. Click OK.

Enable remote errors through script

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

    Copy 
    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:

    Copy 
    rs -i EnableRemoteErrors.rss -s http://servername/ReportServer

Tasks

How to: Connect to a Report Server in Management Studio

Reference

Report Server System Properties
Server Properties (Advanced Page) - Reporting Services
Did you find this helpful?
(1500 characters remaining)
Community Content Add
Annotations FAQ
Script method - don't forget authentication!
If you receive the following message: 
Could not connect to server: http://servername/ReportServer/ReportService2005.asmx
it could be attributed to a lack of authentication. In this case, add the -u and -p options to your command line:
rs -i EnableRemoteErrors.rss -s http://servername/ReportServer -u SERVERNAME\admin_account -p my_password

History
Properties is disabled

If SSRS is installed on Windows 2008, you need to right click on "SQL Server Management Studio"'s icon and select "Run as Administrator" to ensure you have the correct permissions; otherwise you will be unable to access properties.

History
Management Studio did not have this feature in 2005.

Hi All,

This is the page for Sql Server 2008. There is a link for the 2005 documentation at the top of this page under the following lable.

Other versions are also available for the following:

Or you can just use this link.

http://technet.microsoft.com/en-us/library/aa337165(SQL.90).aspx

There is no mention of the Management Studio feature there so I take it that the feature was introduced with 2008.

I used the following solution to solve the problem on my 2005 server...

1. Execute the following T-SQL statements on the Sql Server that is hosting your ReportServer database.

Use ReportServer;
update ConfigurationInfo set Value = 'True' where Name = 'EnableRemoteErrors';

2. Restart IIS

Note that this solution simply consolidates the information provided by boyongoo and Andreas_Apptus. I did however leave out the redundant transation.

History
To make changes active
What boyongoo says works fine, however to make the changes active immediately you should do an iisreset on the server running reporting services.
History
Echoing "Really?"

Phil is right, this doc seems to be wrong. There is no EnableRemoteErrors option in SQL Server Management Studio, either on the server level or the database level.

Here is the proper way to do it in sql:

use reportserver
go

begin tran

update dbo.ConfigurationInfo
set Value = 'True'
where Name = 'EnableRemoteErrors'

commit tran

History