Click to Rate and Give Feedback
TechNet
TechNet Library
SQL Server
SQL Server 2008
Reporting Services
Deployment
New Installation
 How to: Enable Remote Errors

  Switch on low bandwidth view
Community Content
In this section
Statistics Annotations (0)
Other versions are also available for the following:
SQL Server 2008 Books Online (June 2009)
How to: Enable Remote Errors (Reporting Services Configuration)

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.

Aa337165.note(en-us,SQL.100).gifNote:
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.

  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.

  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 http://servername/ReportServer
Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Really?      philmee95 ... Thomas Lee   |   Edit   |   Show History

Does the top process work? I don't see it in my ssms. SQL 2005, 9.00.3073.00. Maybe becuase my report server is a named instance (something I will never do again as it causes many issues in SSIS too).

rs -i EnableRemoteErrors.rss -s http://servername/Reportserver$instance

[Tai Yee - MSFT] Hi, the best way to get questions answered is to post in the Microsoft Community Forum. The SQL Server Forums are located here: http://forums.microsoft.com/MSDN/default.aspx?ForumGroupID=19&SiteID=1. You may want to post this to the Reporting Services forum.

Echoing "Really?"      boyongoo ... Thomas Lee   |   Edit   |   Show History

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

To make changes active      Andreas_Apptus   |   Edit   |   Show History
What boyongoo says works fine, however to make the changes active immediately you should do an iisreset on the server running reporting services.
Tags What's this?: Add a tag
Flag as ContentBug
Management Studio did not have this feature in 2005.      Scott Munro   |   Edit   |   Show History

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.

Tags What's this?: Add a tag
Flag as ContentBug
Processing
© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Page view tracker