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

Extending RDL & rendering

How can I add new elements to an RDL report definition and then render those
elements? For example, I'd like to add a new type of report (i.e. not a
table, matrix, list, or chart), and write the code to generate the rendering
of that particular type of element.
A further complication: the implementation of this new element would also
need to do the database queries, since it does not fit into the Reporting
Services model (i.e. getting a flattened dataset back)
Is this possible within Reporting Services?You can extend with a new renderer but you have to render the whole thing
yourself, which is not what you want. There is no way that I know of to
extend by adding new elements. You can definitely create a data processing
extension, that is not a problem.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Andrew" <Andrew@.discussions.microsoft.com> wrote in message
news:AB288ABC-0055-47FC-A9C8-5AA151DC1791@.microsoft.com...
> How can I add new elements to an RDL report definition and then render
> those
> elements? For example, I'd like to add a new type of report (i.e. not a
> table, matrix, list, or chart), and write the code to generate the
> rendering
> of that particular type of element.
> A further complication: the implementation of this new element would also
> need to do the database queries, since it does not fit into the Reporting
> Services model (i.e. getting a flattened dataset back)
> Is this possible within Reporting Services?

Exporting/downloading a .RDL

I had a close call when my local PC's drive crashed and I was afraid I'd
lost the latest copies of the reports I'd created. Turns out not to be the
case (whew!) but it left me with a question.
I'd looked around the SQL server for the .rdl files and didn't find them.
Does deploying a report to the report server mean that the .rdl is copied to
the server and then configured in the SQL database appropriately? Is so,
where is the .rdl file copied since, in the case I'd lost my local copy, I
would want to copy it from the server back onto my local machine for further
development.
If not, is there some recovery tool somewhere by some nifty programmer that
would reconstruct the report based on what SQL Server has in it's
ReportServer database?
Thanks.
JonOpen Report Manager (http://localhost/reports), select your report and
click the 'Properties' tab. You'll see a section on the page called
"Report Definition". Click the Edit link and you'll have the RDL.
Andy Potter|||That's really easy and exactly what I was looking for.
Thanks, Andy.
Jon|||In addition to the previous reply, you can use Reporting Services Scripter
to dump out all your reports
http://www.sqldbatips.com/showarticle.asp?ID=62
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Jon Limmer" <jonlimmer@.hotmail.com> wrote in message
news:eFtdTEGHGHA.3100@.tk2msftngp13.phx.gbl...
>I had a close call when my local PC's drive crashed and I was afraid I'd
>lost the latest copies of the reports I'd created. Turns out not to be the
>case (whew!) but it left me with a question.
> I'd looked around the SQL server for the .rdl files and didn't find them.
> Does deploying a report to the report server mean that the .rdl is copied
> to the server and then configured in the SQL database appropriately? Is
> so, where is the .rdl file copied since, in the case I'd lost my local
> copy, I would want to copy it from the server back onto my local machine
> for further development.
> If not, is there some recovery tool somewhere by some nifty programmer
> that would reconstruct the report based on what SQL Server has in it's
> ReportServer database?
> Thanks.
> Jon
>
>