external image not rendering when generated from aspx page

I'm having problems displaying images generated by aspx pages from a report. It works fine if I point the external value to a static image on the web. I can paste the url to the page into IE and it generates the image with no issues. What am I doing wrong? I used a textbox to verify that the correct url is being generated (= Parameters!MYPROJECT_URL.Value & Parameters!MYPROJECT_NO.Value).

Are there any issues with generating external images with reporting services?

I have installed SP1 for MS 2005...shouldn't I see some sort of visual confirmation in Management studio when I click the Help Menu->about? saying the version is MS SQL Server 2005? how do I verify that the upgrade was successful?

You can check if the upgrade is successful from the error logs, they contain the build number on the top.

|||Check if ASPX pase generate the image have anonymouse accesssql

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?

Extend CSV Rendering

Is there anyway to extend the existing CSV rending to change deviceinfo
settings that would be used when export is selected from the standard
ReportServer interface.
Example would be to have TXT rendering capability that used the CSV
rendering components, but changed the deviceinfo settings so that
Extension=txt, FieldDelimiter=|. I want to use the parameter selection
capability, and then allow the user to export to this TXT format instead of
CSV.
Logically I would think that you could added some DeviceInfo settings to the
config file in the Report Service directory where Render is defined. But I
am unable to find any sort of documentation.
Also the BOL talks about extending existing rendering formats, as opposed to
create custom rendering extensions. I have yet to find out how it is
possible to extend the CSV rendering extension to accomplish this. I really
want to be able to leverage the existing CSV rendering extension, to modify
a couple of settings.
I know that this can be done via URL and Hidden values in the calling web
page that shells the Report Services window. But when you click the Export
functionality and pick CSV none of the CSV deviceinfo settings are carried
forward to the Export window that is opened before prompting to Save or Open
the file.
Thanks,
MikeUnfortunately, we do not support setting the device info through report
manager.
Regarding the BOL reference to extending rather than writing your own: I
think this might just be a case of terminology confusion. You cannot extend
a particular format. You can extend the report server by adding your own
formats. I'll see about getting the wording changed.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael McCallum" <mmccallum@.honovi.net> wrote in message
news:%23D35dY2FFHA.3648@.TK2MSFTNGP09.phx.gbl...
> Is there anyway to extend the existing CSV rending to change deviceinfo
> settings that would be used when export is selected from the standard
> ReportServer interface.
> Example would be to have TXT rendering capability that used the CSV
> rendering components, but changed the deviceinfo settings so that
> Extension=txt, FieldDelimiter=|. I want to use the parameter selection
> capability, and then allow the user to export to this TXT format instead
> of CSV.
> Logically I would think that you could added some DeviceInfo settings to
> the config file in the Report Service directory where Render is defined.
> But I am unable to find any sort of documentation.
> Also the BOL talks about extending existing rendering formats, as opposed
> to create custom rendering extensions. I have yet to find out how it is
> possible to extend the CSV rendering extension to accomplish this. I
> really want to be able to leverage the existing CSV rendering extension,
> to modify a couple of settings.
> I know that this can be done via URL and Hidden values in the calling web
> page that shells the Report Services window. But when you click the
> Export functionality and pick CSV none of the CSV deviceinfo settings are
> carried forward to the Export window that is opened before prompting to
> Save or Open the file.
> Thanks,
> Mike
>|||Thanks for the information. Maybe this could be a wishlist type item?
Mike
"Lukasz Pawlowski [MSFT]" <lukaszp@.online.microsoft.com> wrote in message
news:eg8QrjHGFHA.2156@.TK2MSFTNGP09.phx.gbl...
> Unfortunately, we do not support setting the device info through report
> manager.
> Regarding the BOL reference to extending rather than writing your own: I
> think this might just be a case of terminology confusion. You cannot
> extend a particular format. You can extend the report server by adding
> your own formats. I'll see about getting the wording changed.
> -Lukasz
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Michael McCallum" <mmccallum@.honovi.net> wrote in message
> news:%23D35dY2FFHA.3648@.TK2MSFTNGP09.phx.gbl...
>> Is there anyway to extend the existing CSV rending to change deviceinfo
>> settings that would be used when export is selected from the standard
>> ReportServer interface.
>> Example would be to have TXT rendering capability that used the CSV
>> rendering components, but changed the deviceinfo settings so that
>> Extension=txt, FieldDelimiter=|. I want to use the parameter selection
>> capability, and then allow the user to export to this TXT format instead
>> of CSV.
>> Logically I would think that you could added some DeviceInfo settings to
>> the config file in the Report Service directory where Render is defined.
>> But I am unable to find any sort of documentation.
>> Also the BOL talks about extending existing rendering formats, as opposed
>> to create custom rendering extensions. I have yet to find out how it is
>> possible to extend the CSV rendering extension to accomplish this. I
>> really want to be able to leverage the existing CSV rendering extension,
>> to modify a couple of settings.
>> I know that this can be done via URL and Hidden values in the calling web
>> page that shells the Report Services window. But when you click the
>> Export functionality and pick CSV none of the CSV deviceinfo settings are
>> carried forward to the Export window that is opened before prompting to
>> Save or Open the file.
>> Thanks,
>> Mike
>|||Yes, we plan (at some point :-)) to expose UI around device info settings.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael McCallum" <mmccallum@.honovi.com> wrote in message
news:%23oBG%234OGFHA.1836@.tk2msftngp13.phx.gbl...
> Thanks for the information. Maybe this could be a wishlist type item?
> Mike
> "Lukasz Pawlowski [MSFT]" <lukaszp@.online.microsoft.com> wrote in message
> news:eg8QrjHGFHA.2156@.TK2MSFTNGP09.phx.gbl...
>> Unfortunately, we do not support setting the device info through report
>> manager.
>> Regarding the BOL reference to extending rather than writing your own: I
>> think this might just be a case of terminology confusion. You cannot
>> extend a particular format. You can extend the report server by adding
>> your own formats. I'll see about getting the wording changed.
>> -Lukasz
>>
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Michael McCallum" <mmccallum@.honovi.net> wrote in message
>> news:%23D35dY2FFHA.3648@.TK2MSFTNGP09.phx.gbl...
>> Is there anyway to extend the existing CSV rending to change deviceinfo
>> settings that would be used when export is selected from the standard
>> ReportServer interface.
>> Example would be to have TXT rendering capability that used the CSV
>> rendering components, but changed the deviceinfo settings so that
>> Extension=txt, FieldDelimiter=|. I want to use the parameter selection
>> capability, and then allow the user to export to this TXT format instead
>> of CSV.
>> Logically I would think that you could added some DeviceInfo settings to
>> the config file in the Report Service directory where Render is defined.
>> But I am unable to find any sort of documentation.
>> Also the BOL talks about extending existing rendering formats, as
>> opposed to create custom rendering extensions. I have yet to find out
>> how it is possible to extend the CSV rendering extension to accomplish
>> this. I really want to be able to leverage the existing CSV rendering
>> extension, to modify a couple of settings.
>> I know that this can be done via URL and Hidden values in the calling
>> web page that shells the Report Services window. But when you click the
>> Export functionality and pick CSV none of the CSV deviceinfo settings
>> are carried forward to the Export window that is opened before prompting
>> to Save or Open the file.
>> Thanks,
>> Mike
>>
>|||Lukasz, Is there any complexity in rendering dynamically generated matrix
total columns in CSV format? I have been having this problem that when I
export my reports to CSV, if a matrix in the report has column groupings as
well as dynamic total columns, these total columns don't generate in CSV
version. I was thinking of writing my own CSV renderer but then I thought
there's probably a complexity into that, otherwise the Microsoft CSV renderer
would do it. Is that right? Or do you think CSV rendere just wasn't intended
to render dynamic columns in a matrix?
"Lukasz Pawlowski [MSFT]" wrote:
> Yes, we plan (at some point :-)) to expose UI around device info settings.
> -Lukasz
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Michael McCallum" <mmccallum@.honovi.com> wrote in message
> news:%23oBG%234OGFHA.1836@.tk2msftngp13.phx.gbl...
> > Thanks for the information. Maybe this could be a wishlist type item?
> > Mike
> >
> > "Lukasz Pawlowski [MSFT]" <lukaszp@.online.microsoft.com> wrote in message
> > news:eg8QrjHGFHA.2156@.TK2MSFTNGP09.phx.gbl...
> >> Unfortunately, we do not support setting the device info through report
> >> manager.
> >>
> >> Regarding the BOL reference to extending rather than writing your own: I
> >> think this might just be a case of terminology confusion. You cannot
> >> extend a particular format. You can extend the report server by adding
> >> your own formats. I'll see about getting the wording changed.
> >>
> >> -Lukasz
> >>
> >>
> >> --
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >>
> >> "Michael McCallum" <mmccallum@.honovi.net> wrote in message
> >> news:%23D35dY2FFHA.3648@.TK2MSFTNGP09.phx.gbl...
> >> Is there anyway to extend the existing CSV rending to change deviceinfo
> >> settings that would be used when export is selected from the standard
> >> ReportServer interface.
> >>
> >> Example would be to have TXT rendering capability that used the CSV
> >> rendering components, but changed the deviceinfo settings so that
> >> Extension=txt, FieldDelimiter=|. I want to use the parameter selection
> >> capability, and then allow the user to export to this TXT format instead
> >> of CSV.
> >>
> >> Logically I would think that you could added some DeviceInfo settings to
> >> the config file in the Report Service directory where Render is defined.
> >> But I am unable to find any sort of documentation.
> >>
> >> Also the BOL talks about extending existing rendering formats, as
> >> opposed to create custom rendering extensions. I have yet to find out
> >> how it is possible to extend the CSV rendering extension to accomplish
> >> this. I really want to be able to leverage the existing CSV rendering
> >> extension, to modify a couple of settings.
> >>
> >> I know that this can be done via URL and Hidden values in the calling
> >> web page that shells the Report Services window. But when you click the
> >> Export functionality and pick CSV none of the CSV deviceinfo settings
> >> are carried forward to the Export window that is opened before prompting
> >> to Save or Open the file.
> >>
> >> Thanks,
> >> Mike
> >>
> >>
> >>
> >
> >
>
>

Exporting to Excel - OmitFormulas

Hi,
I want to prevent formulas to be exported to Excel. I know it can be done by
Implementing a Rendering Extension for EXCEL but don't know how.
How can it be done for the all reports in the solution?
Thanks.Are you sure that you are exporting the formulas? Because I though I was not
possible to export the formulas. I am typing =sum(Fields!Value.Value) how do
I have to introduce the formula in order to export it?
"dpbobrock" wrote:
> Hi,
> I want to prevent formulas to be exported to Excel. I know it can be done by
> Implementing a Rendering Extension for EXCEL but don't know how.
> How can it be done for the all reports in the solution?
> Thanks.
>