External Class Exception

I am calling a custom assembly from within my RDL. If that class raises an
Exception I would like to catch the exception in my call to the RS Web
Service method RenderReport.
Is this possible. Or is it always caught by the report?Report server will always catch and wrap your exception.
In some cases report server will stop report processing (for example if
exception occured in grouping or filter expression); in other cases (text
box value) it will result in #Error and report execution will be continued.
If report processing was stopped Render will return error information.
If report was processed with #Errors then Render will return collection of
warnings
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dlloyd" <Dlloyd@.discussions.microsoft.com> wrote in message
news:8F3A380B-1E43-43D7-8C72-B0E68FCCFB78@.microsoft.com...
> I am calling a custom assembly from within my RDL. If that class raises an
> Exception I would like to catch the exception in my call to the RS Web
> Service method RenderReport.
> Is this possible. Or is it always caught by the report?|||Thank you for the response Alexandre...
The problem is I don't want the exception to end up in an #error in the
textbox. I want the exception rasied up to the software that made the call to
render that report.
With an exception that occurs in a textbox is there a way to throw the
exception back up again?
Dave
"Alexandre Mineev" wrote:
> Report server will always catch and wrap your exception.
> In some cases report server will stop report processing (for example if
> exception occured in grouping or filter expression); in other cases (text
> box value) it will result in #Error and report execution will be continued.
> If report processing was stopped Render will return error information.
> If report was processed with #Errors then Render will return collection of
> warnings
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Dlloyd" <Dlloyd@.discussions.microsoft.com> wrote in message
> news:8F3A380B-1E43-43D7-8C72-B0E68FCCFB78@.microsoft.com...
> > I am calling a custom assembly from within my RDL. If that class raises an
> > Exception I would like to catch the exception in my call to the RS Web
> > Service method RenderReport.
> >
> > Is this possible. Or is it always caught by the report?
>
>|||There is no clean way to prop exceptions, but you can analyze report
execution warnings and if you see traces of your exception then you can
re-throw it.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dlloyd" <Dlloyd@.discussions.microsoft.com> wrote in message
news:0CD7FA30-69AB-4CA1-A838-985DA6220EFE@.microsoft.com...
> Thank you for the response Alexandre...
> The problem is I don't want the exception to end up in an #error in the
> textbox. I want the exception rasied up to the software that made the call
to
> render that report.
> With an exception that occurs in a textbox is there a way to throw the
> exception back up again?
> Dave
> "Alexandre Mineev" wrote:
> > Report server will always catch and wrap your exception.
> > In some cases report server will stop report processing (for example if
> > exception occured in grouping or filter expression); in other cases
(text
> > box value) it will result in #Error and report execution will be
continued.
> >
> > If report processing was stopped Render will return error information.
> > If report was processed with #Errors then Render will return collection
of
> > warnings
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Dlloyd" <Dlloyd@.discussions.microsoft.com> wrote in message
> > news:8F3A380B-1E43-43D7-8C72-B0E68FCCFB78@.microsoft.com...
> > > I am calling a custom assembly from within my RDL. If that class
raises an
> > > Exception I would like to catch the exception in my call to the RS Web
> > > Service method RenderReport.
> > >
> > > Is this possible. Or is it always caught by the report?
> >
> >
> >sql