How to enable remote erros for report server?

hi, all
When i tried to access a report via URL and I got an error page like:
Reporting Services Error
----
For more information about this error navigate to the report server on
the local server machine, or enable remote errors
----
SQL Server Reporting Services
So, How to enable the remote errors and then I was able to see what is
wrong.
Thanks.I'm getting the same error. We can get around the problem for now by logging
onto the server to see exactly what the error is, but I have yet to find out
how to turn on remote errors.
Any one have any ideas how to do this?
"Nick" wrote:
> hi, all
> When i tried to access a report via URL and I got an error page like:
> Reporting Services Error
> ----
> For more information about this error navigate to the report server on
> the local server machine, or enable remote errors
> ----
> SQL Server Reporting Services
> So, How to enable the remote errors and then I was able to see what is
> wrong.
> Thanks.
>|||I have done this with RS 2000.
It is in the machine.config file for .NET Framework v1.1 in the
<windows>\Microsoft.NET\Framework\<Version>\ folder.
There is a XML Tag <System.Web>/<customErrors>
I think you set the value to "RemoteOnly"
It looks like there is a similar tag for .NET 2.0 but the config file looks
a little different. Hopefully, this can can point you in the right direction
-Sean
"Nick" wrote:
> hi, all
> When i tried to access a report via URL and I got an error page like:
> Reporting Services Error
> ----
> For more information about this error navigate to the report server on
> the local server machine, or enable remote errors
> ----
> SQL Server Reporting Services
> So, How to enable the remote errors and then I was able to see what is
> wrong.
> Thanks.
>|||Sean, I found on another posting that this setting is within the
ConfigurationInfo table in the ReportServer database. Setting the value to
True makes it work.
Steve
"Sean P." wrote:
> I have done this with RS 2000.
> It is in the machine.config file for .NET Framework v1.1 in the
> <windows>\Microsoft.NET\Framework\<Version>\ folder.
> There is a XML Tag <System.Web>/<customErrors>
> I think you set the value to "RemoteOnly"
> It looks like there is a similar tag for .NET 2.0 but the config file looks
> a little different. Hopefully, this can can point you in the right direction
> -Sean
>
> "Nick" wrote:
> > hi, all
> >
> > When i tried to access a report via URL and I got an error page like:
> >
> > Reporting Services Error
> > ----
> >
> > For more information about this error navigate to the report server on
> > the local server machine, or enable remote errors
> > ----
> > SQL Server Reporting Services
> > So, How to enable the remote errors and then I was able to see what is
> > wrong.
> >
> > Thanks.
> >
> >|||setting *what* value exactly? my ConfigurationInfo table has 9 rows in
it and none of these contain anything that looks like it may be the right
setting to change.
heres the contents of my ConfigurationInfo table.
EnableExecutionLogging True
EnableMyReports False
ExecutionLogDaysKept 60
MyReportsRole My Reports
SessionTimeout 600
SiteName SQL Server Reporting Services
SystemReportTimeout 1800
SystemSnapshotLimit -1
UseSessionCookies true
"SteveIrwin" wrote:
> Sean, I found on another posting that this setting is within the
> ConfigurationInfo table in the ReportServer database. Setting the value to
> True makes it work.
> Steve
> "Sean P." wrote:
> > I have done this with RS 2000.
> > It is in the machine.config file for .NET Framework v1.1 in the
> > <windows>\Microsoft.NET\Framework\<Version>\ folder.
> >
> > There is a XML Tag <System.Web>/<customErrors>
> > I think you set the value to "RemoteOnly"
> >
> > It looks like there is a similar tag for .NET 2.0 but the config file looks
> > a little different. Hopefully, this can can point you in the right direction
> >
> > -Sean
> >
> >
> > "Nick" wrote:
> >
> > > hi, all
> > >
> > > When i tried to access a report via URL and I got an error page like:
> > >
> > > Reporting Services Error
> > > ----
> > >
> > > For more information about this error navigate to the report server on
> > > the local server machine, or enable remote errors
> > > ----
> > > SQL Server Reporting Services
> > > So, How to enable the remote errors and then I was able to see what is
> > > wrong.
> > >
> > > Thanks.
> > >
> > >|||My ConfigurationInfo table has the following info
EnableExecutionLogging True
EnableIntegratedSecurity true
EnableMyReports False
ExecutionLogDaysKept 60
ExternalImagesTimeout 600
MyReportsRole My Reports
SessionTimeout 600
SiteName SQL Server Reporting Services
SnapshotCompression SQL
SystemReportTimeout 1800
SystemSnapshotLimit -1
UseSessionCookies true
Do we need to add a record for customErrors?