Export Report to File: default

Showing posts with label default. Show all posts

Thursday, March 29, 2012

Exporting Reports

I need some urgent advice. I used Crystal Reports 4.6 (distributed with Visual Studio 6) and designed a report containing saved data. By default the report prints to a window (Crystal Report Preview Window) from where the users can select to print the report to their printers. I need to remove the export and mail options from the Preview Window.
I understand that the later, more recent versions, of Crystal Reports allows for the export and mail buttons to be hidden, what about the version I have? Due to the fact that Crystal Reports 4.6 apparently does not facilitate for this function I considered moving the report to MS Data Report, but it contains export abilities as well. I am more than prepared to use either of the 2 as long as I know that the information contained within the report cannot be tampered with by way of file exports.
Can anybody please help me with this problem?I don't know anything about version 4.6, but maybe there's a way that you can trap the Export button being pushed and warn the user, then exit the function before the report is exported?|||I tried trapping it from within VB, but to no avail.

Wednesday, March 7, 2012

Export to Excel: How to rename Excel tabs from Reporting Services

Hello,
When I export a report of 1 page in Excel,
the default name of the tab is the name of my report.
BUT, when I export a report that has much of 1 page, I obtain
"sheet1, sheet2 and sheet3" for the Excel tabs.
It is possible to export my report with specific
names for my Excel tabs?
Did someone else also meet this problem before?
I found nothing about that.
I thought that maybe with subreport it could work, but it does not.
Thank you very muchProviding explicit names for the Excel tabs is not supported in RS 2000.
It is on the wishlist for inclusion in a future release, but we have seen
only limited demand for this feature compared to many other items on the
wishlist.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"So" <So@.discussions.microsoft.com> wrote in message
news:D2179240-6B4E-458C-9337-D0C47A31191B@.microsoft.com...
> Hello,
> When I export a report of 1 page in Excel,
> the default name of the tab is the name of my report.
> BUT, when I export a report that has much of 1 page, I obtain
> "sheet1, sheet2 and sheet3" for the Excel tabs.
>
> It is possible to export my report with specific
> names for my Excel tabs?
> Did someone else also meet this problem before?
> I found nothing about that.
> I thought that maybe with subreport it could work, but it does not.
> Thank you very much|||I have come across this issue as well. If its possible to get this in a
later release it would definitely be a feature that would interest us.
Thank you
"Robert Bruckner [MSFT]" wrote:
> Providing explicit names for the Excel tabs is not supported in RS 2000.
> It is on the wishlist for inclusion in a future release, but we have seen
> only limited demand for this feature compared to many other items on the
> wishlist.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "So" <So@.discussions.microsoft.com> wrote in message
> news:D2179240-6B4E-458C-9337-D0C47A31191B@.microsoft.com...
> > Hello,
> >
> > When I export a report of 1 page in Excel,
> > the default name of the tab is the name of my report.
> >
> > BUT, when I export a report that has much of 1 page, I obtain
> > "sheet1, sheet2 and sheet3" for the Excel tabs.
> >
> >
> > It is possible to export my report with specific
> > names for my Excel tabs?
> >
> > Did someone else also meet this problem before?
> >
> > I found nothing about that.
> > I thought that maybe with subreport it could work, but it does not.
> >
> > Thank you very much
>
>|||You can send your comments to:
mswish@.microsoft.com
http://www.microsoft.com/mswish
--
Adrian M.
MCP
"Tony Staley" <TonyStaley@.discussions.microsoft.com> wrote in message
news:00BC937F-5151-4FE2-AB09-27D4BD71C271@.microsoft.com...
>I have come across this issue as well. If its possible to get this in a
> later release it would definitely be a feature that would interest us.
> Thank you
> "Robert Bruckner [MSFT]" wrote:
>> Providing explicit names for the Excel tabs is not supported in RS 2000.
>> It is on the wishlist for inclusion in a future release, but we have seen
>> only limited demand for this feature compared to many other items on the
>> wishlist.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "So" <So@.discussions.microsoft.com> wrote in message
>> news:D2179240-6B4E-458C-9337-D0C47A31191B@.microsoft.com...
>> > Hello,
>> >
>> > When I export a report of 1 page in Excel,
>> > the default name of the tab is the name of my report.
>> >
>> > BUT, when I export a report that has much of 1 page, I obtain
>> > "sheet1, sheet2 and sheet3" for the Excel tabs.
>> >
>> >
>> > It is possible to export my report with specific
>> > names for my Excel tabs?
>> >
>> > Did someone else also meet this problem before?
>> >
>> > I found nothing about that.
>> > I thought that maybe with subreport it could work, but it does not.
>> >
>> > Thank you very much
>>|||Has this issue been resolved with 2005?
Thanks and have a nice weekend,
Ryan
"Adrian M." wrote:
> You can send your comments to:
> mswish@.microsoft.com
> http://www.microsoft.com/mswish
> --
> Adrian M.
> MCP
>
> "Tony Staley" <TonyStaley@.discussions.microsoft.com> wrote in message
> news:00BC937F-5151-4FE2-AB09-27D4BD71C271@.microsoft.com...
> >I have come across this issue as well. If its possible to get this in a
> > later release it would definitely be a feature that would interest us.
> >
> > Thank you
> >
> > "Robert Bruckner [MSFT]" wrote:
> >
> >> Providing explicit names for the Excel tabs is not supported in RS 2000.
> >> It is on the wishlist for inclusion in a future release, but we have seen
> >> only limited demand for this feature compared to many other items on the
> >> wishlist.
> >>
> >> --
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "So" <So@.discussions.microsoft.com> wrote in message
> >> news:D2179240-6B4E-458C-9337-D0C47A31191B@.microsoft.com...
> >> > Hello,
> >> >
> >> > When I export a report of 1 page in Excel,
> >> > the default name of the tab is the name of my report.
> >> >
> >> > BUT, when I export a report that has much of 1 page, I obtain
> >> > "sheet1, sheet2 and sheet3" for the Excel tabs.
> >> >
> >> >
> >> > It is possible to export my report with specific
> >> > names for my Excel tabs?
> >> >
> >> > Did someone else also meet this problem before?
> >> >
> >> > I found nothing about that.
> >> > I thought that maybe with subreport it could work, but it does not.
> >> >
> >> > Thank you very much
> >>
> >>
> >>
>
>|||I've been looking for some evidence that naming Excel tabs has been resolved
in SQL 2005, but haven't found it. In our company, wide use of reporting
services is dependent almost solely on the ability to replace creating Excel
reports manually or with our own proprietary tools (which are otherwise far
less flexible than SSRS). Having many tabs with meaningful names is central
to that question (arguably each tab today could be its own report, but that's
far less convenient for the user--I don't think our major customers would
accept it). I know it can seem like the way you do things is the way
everyone does it, but I'm honestly surprised this isn't a critical missing
feature for a lot of others like it is for us.
Regards,
Jason R
"Ryan" wrote:
> Has this issue been resolved with 2005?
> Thanks and have a nice weekend,
> Ryan
> "Adrian M." wrote:
> > You can send your comments to:
> > mswish@.microsoft.com
> > http://www.microsoft.com/mswish
> >
> > --
> > Adrian M.
> > MCP
> >
> >
> > "Tony Staley" <TonyStaley@.discussions.microsoft.com> wrote in message
> > news:00BC937F-5151-4FE2-AB09-27D4BD71C271@.microsoft.com...
> > >I have come across this issue as well. If its possible to get this in a
> > > later release it would definitely be a feature that would interest us.
> > >
> > > Thank you
> > >
> > > "Robert Bruckner [MSFT]" wrote:
> > >
> > >> Providing explicit names for the Excel tabs is not supported in RS 2000.
> > >> It is on the wishlist for inclusion in a future release, but we have seen
> > >> only limited demand for this feature compared to many other items on the
> > >> wishlist.
> > >>
> > >> --
> > >> This posting is provided "AS IS" with no warranties, and confers no
> > >> rights.
> > >>
> > >> "So" <So@.discussions.microsoft.com> wrote in message
> > >> news:D2179240-6B4E-458C-9337-D0C47A31191B@.microsoft.com...
> > >> > Hello,
> > >> >
> > >> > When I export a report of 1 page in Excel,
> > >> > the default name of the tab is the name of my report.
> > >> >
> > >> > BUT, when I export a report that has much of 1 page, I obtain
> > >> > "sheet1, sheet2 and sheet3" for the Excel tabs.
> > >> >
> > >> >
> > >> > It is possible to export my report with specific
> > >> > names for my Excel tabs?
> > >> >
> > >> > Did someone else also meet this problem before?
> > >> >
> > >> > I found nothing about that.
> > >> > I thought that maybe with subreport it could work, but it does not.
> > >> >
> > >> > Thank you very much
> > >>
> > >>
> > >>
> >
> >
> >|||I need a work around for this. I solved this by building a MACRO to solve the
problem back in 1996 but it required that EXCEL be installed on the server,
opening the file invoking the macro automatically and then saving the file.
There should be a way to call a method say "nameWksTab" and pass it into the
file, say a CSV.
This should do-able using some of XLS tools or VB to manipulate this.
Of course the SSRS should do this easily if it expects to stay competitive
in the ever expanding BI world.
"Jason R" wrote:
> I've been looking for some evidence that naming Excel tabs has been resolved
> in SQL 2005, but haven't found it. In our company, wide use of reporting
> services is dependent almost solely on the ability to replace creating Excel
> reports manually or with our own proprietary tools (which are otherwise far
> less flexible than SSRS). Having many tabs with meaningful names is central
> to that question (arguably each tab today could be its own report, but that's
> far less convenient for the user--I don't think our major customers would
> accept it). I know it can seem like the way you do things is the way
> everyone does it, but I'm honestly surprised this isn't a critical missing
> feature for a lot of others like it is for us.
> Regards,
> Jason R
> "Ryan" wrote:
> > Has this issue been resolved with 2005?
> >
> > Thanks and have a nice weekend,
> > Ryan
> >
> > "Adrian M." wrote:
> >
> > > You can send your comments to:
> > > mswish@.microsoft.com
> > > http://www.microsoft.com/mswish
> > >
> > > --
> > > Adrian M.
> > > MCP
> > >
> > >
> > > "Tony Staley" <TonyStaley@.discussions.microsoft.com> wrote in message
> > > news:00BC937F-5151-4FE2-AB09-27D4BD71C271@.microsoft.com...
> > > >I have come across this issue as well. If its possible to get this in a
> > > > later release it would definitely be a feature that would interest us.
> > > >
> > > > Thank you
> > > >
> > > > "Robert Bruckner [MSFT]" wrote:
> > > >
> > > >> Providing explicit names for the Excel tabs is not supported in RS 2000.
> > > >> It is on the wishlist for inclusion in a future release, but we have seen
> > > >> only limited demand for this feature compared to many other items on the
> > > >> wishlist.
> > > >>
> > > >> --
> > > >> This posting is provided "AS IS" with no warranties, and confers no
> > > >> rights.
> > > >>
> > > >> "So" <So@.discussions.microsoft.com> wrote in message
> > > >> news:D2179240-6B4E-458C-9337-D0C47A31191B@.microsoft.com...
> > > >> > Hello,
> > > >> >
> > > >> > When I export a report of 1 page in Excel,
> > > >> > the default name of the tab is the name of my report.
> > > >> >
> > > >> > BUT, when I export a report that has much of 1 page, I obtain
> > > >> > "sheet1, sheet2 and sheet3" for the Excel tabs.
> > > >> >
> > > >> >
> > > >> > It is possible to export my report with specific
> > > >> > names for my Excel tabs?
> > > >> >
> > > >> > Did someone else also meet this problem before?
> > > >> >
> > > >> > I found nothing about that.
> > > >> > I thought that maybe with subreport it could work, but it does not.
> > > >> >
> > > >> > Thank you very much
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >|||Hi,
can you help me how to write a marco in SSRS for the tabing names in excel?
so i can try on my report as i am having a similar issue.
Thanks in advance.
Regards
Vandana Mestri
vandana.mestri@.rave-tech.com
"Jim R" wrote:
> I need a work around for this. I solved this by building a MACRO to solve the
> problem back in 1996 but it required that EXCEL be installed on the server,
> opening the file invoking the macro automatically and then saving the file.
> There should be a way to call a method say "nameWksTab" and pass it into the
> file, say a CSV.
> This should do-able using some of XLS tools or VB to manipulate this.
> Of course the SSRS should do this easily if it expects to stay competitive
> in the ever expanding BI world.
>
> "Jason R" wrote:
> > I've been looking for some evidence that naming Excel tabs has been resolved
> > in SQL 2005, but haven't found it. In our company, wide use of reporting
> > services is dependent almost solely on the ability to replace creating Excel
> > reports manually or with our own proprietary tools (which are otherwise far
> > less flexible than SSRS). Having many tabs with meaningful names is central
> > to that question (arguably each tab today could be its own report, but that's
> > far less convenient for the user--I don't think our major customers would
> > accept it). I know it can seem like the way you do things is the way
> > everyone does it, but I'm honestly surprised this isn't a critical missing
> > feature for a lot of others like it is for us.
> >
> > Regards,
> > Jason R
> >
> > "Ryan" wrote:
> >
> > > Has this issue been resolved with 2005?
> > >
> > > Thanks and have a nice weekend,
> > > Ryan
> > >
> > > "Adrian M." wrote:
> > >
> > > > You can send your comments to:
> > > > mswish@.microsoft.com
> > > > http://www.microsoft.com/mswish
> > > >
> > > > --
> > > > Adrian M.
> > > > MCP
> > > >
> > > >
> > > > "Tony Staley" <TonyStaley@.discussions.microsoft.com> wrote in message
> > > > news:00BC937F-5151-4FE2-AB09-27D4BD71C271@.microsoft.com...
> > > > >I have come across this issue as well. If its possible to get this in a
> > > > > later release it would definitely be a feature that would interest us.
> > > > >
> > > > > Thank you
> > > > >
> > > > > "Robert Bruckner [MSFT]" wrote:
> > > > >
> > > > >> Providing explicit names for the Excel tabs is not supported in RS 2000.
> > > > >> It is on the wishlist for inclusion in a future release, but we have seen
> > > > >> only limited demand for this feature compared to many other items on the
> > > > >> wishlist.
> > > > >>
> > > > >> --
> > > > >> This posting is provided "AS IS" with no warranties, and confers no
> > > > >> rights.
> > > > >>
> > > > >> "So" <So@.discussions.microsoft.com> wrote in message
> > > > >> news:D2179240-6B4E-458C-9337-D0C47A31191B@.microsoft.com...
> > > > >> > Hello,
> > > > >> >
> > > > >> > When I export a report of 1 page in Excel,
> > > > >> > the default name of the tab is the name of my report.
> > > > >> >
> > > > >> > BUT, when I export a report that has much of 1 page, I obtain
> > > > >> > "sheet1, sheet2 and sheet3" for the Excel tabs.
> > > > >> >
> > > > >> >
> > > > >> > It is possible to export my report with specific
> > > > >> > names for my Excel tabs?
> > > > >> >
> > > > >> > Did someone else also meet this problem before?
> > > > >> >
> > > > >> > I found nothing about that.
> > > > >> > I thought that maybe with subreport it could work, but it does not.
> > > > >> >
> > > > >> > Thank you very much
> > > > >>
> > > > >>
> > > > >>
> > > >
> > > >
> > > >

Friday, February 24, 2012

Export to Excel - merge and centre issue

hi
I am exporting a report from SQL 2000 reporting services into excel and by
default all columns have merge and centre clicked. Can i change this so this
property is not checked which makes it easier for users to do things like
sorting etc.
Any help would be appreciated.
Thanks heaps
RidhimaIs this Excel export or CSV export? With CSV the default is Unicode which
Excel then merges (or doesn't split into different columns). In 2000 the
only thing you can do if this is the case is have a link the user clicks
that then uses jump to URL and you have it render in CSV ASCII. In RS 2005
you can configure it to export CSV in ASCII format as the default.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ridhima Sood" <RidhimaSood@.discussions.microsoft.com> wrote in message
news:511E9718-8B0F-4A84-AF8D-71DA3598E104@.microsoft.com...
> hi
> I am exporting a report from SQL 2000 reporting services into excel and by
> default all columns have merge and centre clicked. Can i change this so
> this
> property is not checked which makes it easier for users to do things like
> sorting etc.
> Any help would be appreciated.
> Thanks heaps
> Ridhima

Export to Excel

Hi, i am trying to export report data to excel but when i choose to print,
its default layout is set to LANDSCAPE and i want to set the layout to
PORTRAIT. HOw can i do. If anybody has done it pls share it with me.
Thanks
JAsvinderJasvinder,
we found the same problem with PDF files.
The way around it, for us, was to simply create the form wide so it
defaulted to lscape. This cannot be the correct way it was intended, but
after reading through the help files, it was the only solution we found, and
it worked.
Tony
"Jasvinder" wrote:
> Hi, i am trying to export report data to excel but when i choose to print,
> its default layout is set to LANDSCAPE and i want to set the layout to
> PORTRAIT. HOw can i do. If anybody has done it pls share it with me.
> Thanks
> JAsvinder|||This is by design. Setting the page wider than it is tall is equivalent to
landscape.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Logicalman" <tony9scott45us@.com7cast.net34> wrote in message
news:919C4AA9-9EA4-4159-81E2-12402D9C763D@.microsoft.com...
> Jasvinder,
> we found the same problem with PDF files.
> The way around it, for us, was to simply create the form wide so it
> defaulted to lscape. This cannot be the correct way it was intended, but
> after reading through the help files, it was the only solution we found,
> and
> it worked.
> Tony
> "Jasvinder" wrote:
>> Hi, i am trying to export report data to excel but when i choose to
>> print,
>> its default layout is set to LANDSCAPE and i want to set the layout to
>> PORTRAIT. HOw can i do. If anybody has done it pls share it with me.
>> Thanks
>> JAsvinder|||Open you RS project in the BI studio and click on the Report properties.
Towards the bottom of the properties dialog there is an Interactive Settings
and Page Settings for width/height. The Page width/height is probably set to
11 - 8.5, change this to 8.5 - 11. Build and deploy your project and see if
this corrects your problem.
"Jasvinder" wrote:
> Hi, i am trying to export report data to excel but when i choose to print,
> its default layout is set to LANDSCAPE and i want to set the layout to
> PORTRAIT. HOw can i do. If anybody has done it pls share it with me.
> Thanks
> JAsvinder

Sunday, February 19, 2012

Export to an ASCII CSV

I need to export my reports in CSV, however, the default Unicode encoding
does not work well with Excel. I am trying to change the encoding in the
RSReportServer.config and RSReportDesigner.config files by adding the
DeviceInfo structure described in the SQL 2005 online help. So far I have
not had success.
Below is the example from the online help.
<Render>
<Extension Name="IMAGE"
Type="Microsoft.ReportingServices.Rendering.ImageRenderer.ImageReport,Microsoft.ReportingServices.ImageRendering"/>
<OverrideNames>
<Name>Image (EMF)</Name>
</OverrideNames>
<Configuration>
<DeviceInfo>
<ColorDepth>32</ColorDepth>
<DpiX>300</DpiX>
<DpiY>300</DpiY>
<OutputFormat>EMF</OutputFormat>
</DeviceInfo>
</Configuration>
</Extension>
</Render>
Below is the modification I made to my configuration files.
<Extension Name="CSV"
Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering" >
<Configuration>
<DeviceInfo>
<Encoding>ASCII</Encoding>
</DeviceInfo>
</Configuration>
</Extension>what's the error you're getting? How are you not successful? Is it
still rendering the CSV as unicode? Or does it give you an exception?
Regards,
Thiago Silva|||Thanks for your interest. The CSV is correctly rendered in the default
Unicode which is not desired. I am not getting any errors just that the CSV
continues to be exported in Unicode. The DeviceInfo structure that the
online help provided did not have any affect. Am I doing something wrong or
is this structure not valid in the 2005 Reporting Services?
My goal is to modify the RSReportServer.config and RSReportDesigner.config
files to encode the exported CSV file in ASCII. This is where I have been
unsuccessful.
"tafs7" wrote:
> what's the error you're getting? How are you not successful? Is it
> still rendering the CSV as unicode? Or does it give you an exception?
> Regards,
> Thiago Silva
>|||You only need to change in one place, rsreportserver.config. Reboot after
the change. The below shows commenting out the existing entry and putting in
the needed change to have CSV export as ASCII
.

<Extension Name="CSV"
Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering">
<Configuration>
<DeviceInfo>
<Encoding>ASCII</Encoding>
</DeviceInfo>
</Configuration>
</Extension>
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Scott B." <mrScott@.community.nospam> wrote in message
news:6FF02F2C-8F3B-4520-865D-DE468D918317@.microsoft.com...
> Thanks for your interest. The CSV is correctly rendered in the default
> Unicode which is not desired. I am not getting any errors just that the
> CSV
> continues to be exported in Unicode. The DeviceInfo structure that the
> online help provided did not have any affect. Am I doing something wrong
> or
> is this structure not valid in the 2005 Reporting Services?
> My goal is to modify the RSReportServer.config and RSReportDesigner.config
> files to encode the exported CSV file in ASCII. This is where I have been
> unsuccessful.
>
> "tafs7" wrote:
>> what's the error you're getting? How are you not successful? Is it
>> still rendering the CSV as unicode? Or does it give you an exception?
>> Regards,
>> Thiago Silva
>>|||Thanks! I could not restart the box but restarting SQL Server Reporting
Services seemed to accomplish the same thing. The CSV is now encoded in
ASCII. Problem solved!
I made the same change in the RSReportDesigner.config file hoping for the
same result when I run the report in Visual Studio but the CSV is still
exported in Unicode. I do not need this functionality in Visual Studio but
it would be convenient. Do you have any thoughts on this?
"Bruce L-C [MVP]" wrote:
> You only need to change in one place, rsreportserver.config. Reboot after
> the change. The below shows commenting out the existing entry and putting in
> the needed change to have CSV export as ASCII
> ..
> 
> <Extension Name="CSV"
> Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering">
> <Configuration>
> <DeviceInfo>
> <Encoding>ASCII</Encoding>
> </DeviceInfo>
> </Configuration>
> </Extension>
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Scott B." <mrScott@.community.nospam> wrote in message
> news:6FF02F2C-8F3B-4520-865D-DE468D918317@.microsoft.com...
> > Thanks for your interest. The CSV is correctly rendered in the default
> > Unicode which is not desired. I am not getting any errors just that the
> > CSV
> > continues to be exported in Unicode. The DeviceInfo structure that the
> > online help provided did not have any affect. Am I doing something wrong
> > or
> > is this structure not valid in the 2005 Reporting Services?
> >
> > My goal is to modify the RSReportServer.config and RSReportDesigner.config
> > files to encode the exported CSV file in ASCII. This is where I have been
> > unsuccessful.
> >
> >
> > "tafs7" wrote:
> >
> >> what's the error you're getting? How are you not successful? Is it
> >> still rendering the CSV as unicode? Or does it give you an exception?
> >>
> >> Regards,
> >> Thiago Silva
> >>
> >>
>
>|||Sorry, I never cared about the development environment when exporting CSV. I
don't know if there is a way to do it there or not.
Bruce Loehle-Conger
"Scott B." <mrScott@.community.nospam> wrote in message
news:D597F83B-DC8E-403B-B081-EDEE475E48E0@.microsoft.com...
> Thanks! I could not restart the box but restarting SQL Server Reporting
> Services seemed to accomplish the same thing. The CSV is now encoded in
> ASCII. Problem solved!
> I made the same change in the RSReportDesigner.config file hoping for the
> same result when I run the report in Visual Studio but the CSV is still
> exported in Unicode. I do not need this functionality in Visual Studio
> but
> it would be convenient. Do you have any thoughts on this?
>
> "Bruce L-C [MVP]" wrote:
>> You only need to change in one place, rsreportserver.config. Reboot after
>> the change. The below shows commenting out the existing entry and putting
>> in
>> the needed change to have CSV export as ASCII
>> ..
>> 
>> <Extension Name="CSV"
>> Type="Microsoft.ReportingServices.Rendering.CsvRenderer.CsvReport,Microsoft.ReportingServices.CsvRendering">
>> <Configuration>
>> <DeviceInfo>
>> <Encoding>ASCII</Encoding>
>> </DeviceInfo>
>> </Configuration>
>> </Extension>
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Scott B." <mrScott@.community.nospam> wrote in message
>> news:6FF02F2C-8F3B-4520-865D-DE468D918317@.microsoft.com...
>> > Thanks for your interest. The CSV is correctly rendered in the default
>> > Unicode which is not desired. I am not getting any errors just that
>> > the
>> > CSV
>> > continues to be exported in Unicode. The DeviceInfo structure that the
>> > online help provided did not have any affect. Am I doing something
>> > wrong
>> > or
>> > is this structure not valid in the 2005 Reporting Services?
>> >
>> > My goal is to modify the RSReportServer.config and
>> > RSReportDesigner.config
>> > files to encode the exported CSV file in ASCII. This is where I have
>> > been
>> > unsuccessful.
>> >
>> >
>> > "tafs7" wrote:
>> >
>> >> what's the error you're getting? How are you not successful? Is it
>> >> still rendering the CSV as unicode? Or does it give you an exception?
>> >>
>> >> Regards,
>> >> Thiago Silva
>> >>
>> >>
>>|||Hi Scott,
I think after you change the RSReportDesigner.config, you need to restart
the box to take the effect on Visual Studio.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||I have also been trying to add deviceinfo settings to the config files,
but to set the Excel rendering SimplePageHeaders to true. I have had
no success with this (there are no errors, and export to Excel works as
previously) - is this something that is only available in RS2005? (I'm
using RS2000 SP2). I have also tried setting SimplePageHeaders via URL
but this generates an exception and I have found no resolution to this.
Config file update I am doing is:
<Extension Name="EXCEL"
Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering">
<Configuration>
<DeviceInfo>
<SimplePageHeaders>True</SimplePageHeaders>
</DeviceInfo>
</Configuration>
</Extension>
Wei Lu wrote:
> Hi Scott,
> I think after you change the RSReportDesigner.config, you need to restart
> the box to take the effect on Visual Studio.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.|||I know that the ASCII change only works for 2005. Don't know about what you
are trying to do but it wouldn't surprise me.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"AMasson" <ann.masson@.eds.com> wrote in message
news:1145433029.371431.162640@.v46g2000cwv.googlegroups.com...
>I have also been trying to add deviceinfo settings to the config files,
> but to set the Excel rendering SimplePageHeaders to true. I have had
> no success with this (there are no errors, and export to Excel works as
> previously) - is this something that is only available in RS2005? (I'm
> using RS2000 SP2). I have also tried setting SimplePageHeaders via URL
> but this generates an exception and I have found no resolution to this.
> Config file update I am doing is:
> <Extension Name="EXCEL"
> Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering">
> <Configuration>
> <DeviceInfo>
> <SimplePageHeaders>True</SimplePageHeaders>
> </DeviceInfo>
> </Configuration>
> </Extension>
>
> Wei Lu wrote:
>> Hi Scott,
>> I think after you change the RSReportDesigner.config, you need to restart
>> the box to take the effect on Visual Studio.
>> Sincerely,
>> Wei Lu
>> Microsoft Online Community Support
>> ==================================================>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> ==================================================>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>|||Is it just the setting of the deviceinfo in the config files that is
new for 2005 or the ability to pass it in via the URL as well?
I had been told previously (by a contact at Microsoft) that he had
tested out SimplePageHeaders=True via URL in RS2000 and it worked OK.
I have tried this without success.
I'm adding &rc:SimplePageHeaders=True to a valid URL. If I add
rc:RemoveSpace=0.5in, or rc:OmitFormulas=True, these work OK. If I use
SimplePageHeaders, the dialog to download the xls file displays no File
Name or File Type and if I select Open, I get an Internet Explorer
error "Internet Explorer cannot download from <servername>. Internet
Explorer was not able to open this Internet site. The requested site
is either unavailable or cannot be found. Please try again later". I
have tried running tcptrace on it - this shows the ExcelRendering
Exception thrown.
Is it possible to get a definite answer on whether SimplePageHeaders
should work via URL in RS2000 SP2, and if so, any idea what my problem
might be?
Bruce L-C [MVP] wrote:
> I know that the ASCII change only works for 2005. Don't know about what you
> are trying to do but it wouldn't surprise me.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "AMasson" <ann.masson@.eds.com> wrote in message
> news:1145433029.371431.162640@.v46g2000cwv.googlegroups.com...
> >I have also been trying to add deviceinfo settings to the config files,
> > but to set the Excel rendering SimplePageHeaders to true. I have had
> > no success with this (there are no errors, and export to Excel works as
> > previously) - is this something that is only available in RS2005? (I'm
> > using RS2000 SP2). I have also tried setting SimplePageHeaders via URL
> > but this generates an exception and I have found no resolution to this.
> >
> > Config file update I am doing is:
> >
> > <Extension Name="EXCEL"
> > Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering">
> > <Configuration>
> > <DeviceInfo>
> >
> > <SimplePageHeaders>True</SimplePageHeaders>
> > </DeviceInfo>
> > </Configuration>
> > </Extension>
> >
> >
> >
> > Wei Lu wrote:
> >> Hi Scott,
> >>
> >> I think after you change the RSReportDesigner.config, you need to restart
> >> the box to take the effect on Visual Studio.
> >>
> >> Sincerely,
> >>
> >> Wei Lu
> >> Microsoft Online Community Support
> >>
> >> ==================================================> >>
> >> When responding to posts, please "Reply to Group" via your newsreader so
> >> that others may learn and benefit from your issue.
> >>
> >> ==================================================> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >|||As far as CSV the URL worked in 2000. It was setting it in the config file
so the export renders as ASCII that was new for 2005.
To get around the CSV problem in 2000 I would have a link and use jump to
url to export CSV as ASCII.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"AMasson" <ann.masson@.eds.com> wrote in message
news:1145460618.827732.45560@.i39g2000cwa.googlegroups.com...
> Is it just the setting of the deviceinfo in the config files that is
> new for 2005 or the ability to pass it in via the URL as well?
> I had been told previously (by a contact at Microsoft) that he had
> tested out SimplePageHeaders=True via URL in RS2000 and it worked OK.
> I have tried this without success.
> I'm adding &rc:SimplePageHeaders=True to a valid URL. If I add
> rc:RemoveSpace=0.5in, or rc:OmitFormulas=True, these work OK. If I use
> SimplePageHeaders, the dialog to download the xls file displays no File
> Name or File Type and if I select Open, I get an Internet Explorer
> error "Internet Explorer cannot download from <servername>. Internet
> Explorer was not able to open this Internet site. The requested site
> is either unavailable or cannot be found. Please try again later". I
> have tried running tcptrace on it - this shows the ExcelRendering
> Exception thrown.
> Is it possible to get a definite answer on whether SimplePageHeaders
> should work via URL in RS2000 SP2, and if so, any idea what my problem
> might be?
>
> Bruce L-C [MVP] wrote:
>> I know that the ASCII change only works for 2005. Don't know about what
>> you
>> are trying to do but it wouldn't surprise me.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "AMasson" <ann.masson@.eds.com> wrote in message
>> news:1145433029.371431.162640@.v46g2000cwv.googlegroups.com...
>> >I have also been trying to add deviceinfo settings to the config files,
>> > but to set the Excel rendering SimplePageHeaders to true. I have had
>> > no success with this (there are no errors, and export to Excel works as
>> > previously) - is this something that is only available in RS2005? (I'm
>> > using RS2000 SP2). I have also tried setting SimplePageHeaders via URL
>> > but this generates an exception and I have found no resolution to this.
>> >
>> > Config file update I am doing is:
>> >
>> > <Extension Name="EXCEL"
>> > Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering">
>> > <Configuration>
>> > <DeviceInfo>
>> >
>> > <SimplePageHeaders>True</SimplePageHeaders>
>> > </DeviceInfo>
>> > </Configuration>
>> > </Extension>
>> >
>> >
>> >
>> > Wei Lu wrote:
>> >> Hi Scott,
>> >>
>> >> I think after you change the RSReportDesigner.config, you need to
>> >> restart
>> >> the box to take the effect on Visual Studio.
>> >>
>> >> Sincerely,
>> >>
>> >> Wei Lu
>> >> Microsoft Online Community Support
>> >>
>> >> ==================================================>> >>
>> >> When responding to posts, please "Reply to Group" via your newsreader
>> >> so
>> >> that others may learn and benefit from your issue.
>> >>
>> >> ==================================================>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >
>|||Thanks for the response. I've tested adding &rc:Encoding=ASCII to my
URL and this works as expected. Assuming that the SimplePageHeaders
deviceinfo should also work this way - any ideas as to what is causing
my problem? The exception from the RS log file is as follows:
aspnet_wp!webserver!fbc!04/20/2006-08:38:30:: e ERROR: Reporting
Services error
Microsoft.ReportingServices.Diagnostics.Utilities.RSException:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException
was thrown. -->
Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException
was thrown. -->
Microsoft.ReportingServices.ReportRendering.ReportRenderingException:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException
was thrown. --> System.NullReferenceException: Object reference not
set to an instance of an object.
followed by a large chunk of ExcelRenderer processing detail (I can
forward it if you think it may provide useful info - there may be some
clues if I could understand it!).
Am I correct in assuming there was some problem which prevented the xls
file from being generated? Any suggestions as to how I can track it
down ? I have to admit I'm getting very frustrated with this. It
would be the ideal resolution to a number of issues for our client who
is relying heavily on Excel format for reports, but there seems to be
little documentation on SimplePageHeaders, and not much mention of it
in various forums - I've had little feedback so far.
Bruce L-C [MVP] wrote:
> As far as CSV the URL worked in 2000. It was setting it in the config file
> so the export renders as ASCII that was new for 2005.
> To get around the CSV problem in 2000 I would have a link and use jump to
> url to export CSV as ASCII.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "AMasson" <ann.masson@.eds.com> wrote in message
> news:1145460618.827732.45560@.i39g2000cwa.googlegroups.com...
> > Is it just the setting of the deviceinfo in the config files that is
> > new for 2005 or the ability to pass it in via the URL as well?
> >
> > I had been told previously (by a contact at Microsoft) that he had
> > tested out SimplePageHeaders=True via URL in RS2000 and it worked OK.
> > I have tried this without success.
> >
> > I'm adding &rc:SimplePageHeaders=True to a valid URL. If I add
> > rc:RemoveSpace=0.5in, or rc:OmitFormulas=True, these work OK. If I use
> > SimplePageHeaders, the dialog to download the xls file displays no File
> > Name or File Type and if I select Open, I get an Internet Explorer
> > error "Internet Explorer cannot download from <servername>. Internet
> > Explorer was not able to open this Internet site. The requested site
> > is either unavailable or cannot be found. Please try again later". I
> > have tried running tcptrace on it - this shows the ExcelRendering
> > Exception thrown.
> >
> > Is it possible to get a definite answer on whether SimplePageHeaders
> > should work via URL in RS2000 SP2, and if so, any idea what my problem
> > might be?
> >
> >
> > Bruce L-C [MVP] wrote:
> >> I know that the ASCII change only works for 2005. Don't know about what
> >> you
> >> are trying to do but it wouldn't surprise me.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "AMasson" <ann.masson@.eds.com> wrote in message
> >> news:1145433029.371431.162640@.v46g2000cwv.googlegroups.com...
> >> >I have also been trying to add deviceinfo settings to the config files,
> >> > but to set the Excel rendering SimplePageHeaders to true. I have had
> >> > no success with this (there are no errors, and export to Excel works as
> >> > previously) - is this something that is only available in RS2005? (I'm
> >> > using RS2000 SP2). I have also tried setting SimplePageHeaders via URL
> >> > but this generates an exception and I have found no resolution to this.
> >> >
> >> > Config file update I am doing is:
> >> >
> >> > <Extension Name="EXCEL"
> >> > Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering">
> >> > <Configuration>
> >> > <DeviceInfo>
> >> >
> >> > <SimplePageHeaders>True</SimplePageHeaders>
> >> > </DeviceInfo>
> >> > </Configuration>
> >> > </Extension>
> >> >
> >> >
> >> >
> >> > Wei Lu wrote:
> >> >> Hi Scott,
> >> >>
> >> >> I think after you change the RSReportDesigner.config, you need to
> >> >> restart
> >> >> the box to take the effect on Visual Studio.
> >> >>
> >> >> Sincerely,
> >> >>
> >> >> Wei Lu
> >> >> Microsoft Online Community Support
> >> >>
> >> >> ==================================================> >> >>
> >> >> When responding to posts, please "Reply to Group" via your newsreader
> >> >> so
> >> >> that others may learn and benefit from your issue.
> >> >>
> >> >> ==================================================> >> >> This posting is provided "AS IS" with no warranties, and confers no
> >> >> rights.
> >> >
> >|||I suggest creating a new post with an appropriate subject. There might be
someone who knows but isn't following this thread. Also, there is more of a
Microsoft presense in the forums. You could try posting there as well.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"AMasson" <ann.masson@.eds.com> wrote in message
news:1145519676.955410.148880@.i40g2000cwc.googlegroups.com...
> Thanks for the response. I've tested adding &rc:Encoding=ASCII to my
> URL and this works as expected. Assuming that the SimplePageHeaders
> deviceinfo should also work this way - any ideas as to what is causing
> my problem? The exception from the RS log file is as follows:
> aspnet_wp!webserver!fbc!04/20/2006-08:38:30:: e ERROR: Reporting
> Services error
> Microsoft.ReportingServices.Diagnostics.Utilities.RSException:
> Exception of type
> Microsoft.ReportingServices.ReportRendering.ReportRenderingException
> was thrown. -->
> Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException:
> Exception of type
> Microsoft.ReportingServices.ReportRendering.ReportRenderingException
> was thrown. -->
> Microsoft.ReportingServices.ReportRendering.ReportRenderingException:
> Exception of type
> Microsoft.ReportingServices.ReportRendering.ReportRenderingException
> was thrown. --> System.NullReferenceException: Object reference not
> set to an instance of an object.
> followed by a large chunk of ExcelRenderer processing detail (I can
> forward it if you think it may provide useful info - there may be some
> clues if I could understand it!).
> Am I correct in assuming there was some problem which prevented the xls
> file from being generated? Any suggestions as to how I can track it
> down ? I have to admit I'm getting very frustrated with this. It
> would be the ideal resolution to a number of issues for our client who
> is relying heavily on Excel format for reports, but there seems to be
> little documentation on SimplePageHeaders, and not much mention of it
> in various forums - I've had little feedback so far.
>
> Bruce L-C [MVP] wrote:
>> As far as CSV the URL worked in 2000. It was setting it in the config
>> file
>> so the export renders as ASCII that was new for 2005.
>> To get around the CSV problem in 2000 I would have a link and use jump to
>> url to export CSV as ASCII.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "AMasson" <ann.masson@.eds.com> wrote in message
>> news:1145460618.827732.45560@.i39g2000cwa.googlegroups.com...
>> > Is it just the setting of the deviceinfo in the config files that is
>> > new for 2005 or the ability to pass it in via the URL as well?
>> >
>> > I had been told previously (by a contact at Microsoft) that he had
>> > tested out SimplePageHeaders=True via URL in RS2000 and it worked OK.
>> > I have tried this without success.
>> >
>> > I'm adding &rc:SimplePageHeaders=True to a valid URL. If I add
>> > rc:RemoveSpace=0.5in, or rc:OmitFormulas=True, these work OK. If I use
>> > SimplePageHeaders, the dialog to download the xls file displays no File
>> > Name or File Type and if I select Open, I get an Internet Explorer
>> > error "Internet Explorer cannot download from <servername>. Internet
>> > Explorer was not able to open this Internet site. The requested site
>> > is either unavailable or cannot be found. Please try again later". I
>> > have tried running tcptrace on it - this shows the ExcelRendering
>> > Exception thrown.
>> >
>> > Is it possible to get a definite answer on whether SimplePageHeaders
>> > should work via URL in RS2000 SP2, and if so, any idea what my problem
>> > might be?
>> >
>> >
>> > Bruce L-C [MVP] wrote:
>> >> I know that the ASCII change only works for 2005. Don't know about
>> >> what
>> >> you
>> >> are trying to do but it wouldn't surprise me.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "AMasson" <ann.masson@.eds.com> wrote in message
>> >> news:1145433029.371431.162640@.v46g2000cwv.googlegroups.com...
>> >> >I have also been trying to add deviceinfo settings to the config
>> >> >files,
>> >> > but to set the Excel rendering SimplePageHeaders to true. I have
>> >> > had
>> >> > no success with this (there are no errors, and export to Excel works
>> >> > as
>> >> > previously) - is this something that is only available in RS2005?
>> >> > (I'm
>> >> > using RS2000 SP2). I have also tried setting SimplePageHeaders via
>> >> > URL
>> >> > but this generates an exception and I have found no resolution to
>> >> > this.
>> >> >
>> >> > Config file update I am doing is:
>> >> >
>> >> > <Extension Name="EXCEL"
>> >> > Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering">
>> >> > <Configuration>
>> >> > <DeviceInfo>
>> >> >
>> >> > <SimplePageHeaders>True</SimplePageHeaders>
>> >> > </DeviceInfo>
>> >> > </Configuration>
>> >> > </Extension>
>> >> >
>> >> >
>> >> >
>> >> > Wei Lu wrote:
>> >> >> Hi Scott,
>> >> >>
>> >> >> I think after you change the RSReportDesigner.config, you need to
>> >> >> restart
>> >> >> the box to take the effect on Visual Studio.
>> >> >>
>> >> >> Sincerely,
>> >> >>
>> >> >> Wei Lu
>> >> >> Microsoft Online Community Support
>> >> >>
>> >> >> ==================================================>> >> >>
>> >> >> When responding to posts, please "Reply to Group" via your
>> >> >> newsreader
>> >> >> so
>> >> >> that others may learn and benefit from your issue.
>> >> >>
>> >> >> ==================================================>> >> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> >> rights.
>> >> >
>> >
>|||Thanks for your responses to this. I'll try posting again with a more
specific subject heading and in other forums - however I've already
done that more than once over the last few weeks with no response - I
jumped in on this thread because it seemed to be related and someone
was actually responding to the queries!
Bruce L-C [MVP] wrote:
> I suggest creating a new post with an appropriate subject. There might be
> someone who knows but isn't following this thread. Also, there is more of a
> Microsoft presense in the forums. You could try posting there as well.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "AMasson" <ann.masson@.eds.com> wrote in message
> news:1145519676.955410.148880@.i40g2000cwc.googlegroups.com...
> > Thanks for the response. I've tested adding &rc:Encoding=ASCII to my
> > URL and this works as expected. Assuming that the SimplePageHeaders
> > deviceinfo should also work this way - any ideas as to what is causing
> > my problem? The exception from the RS log file is as follows:
> >
> > aspnet_wp!webserver!fbc!04/20/2006-08:38:30:: e ERROR: Reporting
> > Services error
> > Microsoft.ReportingServices.Diagnostics.Utilities.RSException:
> > Exception of type
> > Microsoft.ReportingServices.ReportRendering.ReportRenderingException
> > was thrown. -->
> > Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException:
> > Exception of type
> > Microsoft.ReportingServices.ReportRendering.ReportRenderingException
> > was thrown. -->
> > Microsoft.ReportingServices.ReportRendering.ReportRenderingException:
> > Exception of type
> > Microsoft.ReportingServices.ReportRendering.ReportRenderingException
> > was thrown. --> System.NullReferenceException: Object reference not
> > set to an instance of an object.
> >
> > followed by a large chunk of ExcelRenderer processing detail (I can
> > forward it if you think it may provide useful info - there may be some
> > clues if I could understand it!).
> >
> > Am I correct in assuming there was some problem which prevented the xls
> > file from being generated? Any suggestions as to how I can track it
> > down ? I have to admit I'm getting very frustrated with this. It
> > would be the ideal resolution to a number of issues for our client who
> > is relying heavily on Excel format for reports, but there seems to be
> > little documentation on SimplePageHeaders, and not much mention of it
> > in various forums - I've had little feedback so far.
> >
> >
> > Bruce L-C [MVP] wrote:
> >> As far as CSV the URL worked in 2000. It was setting it in the config
> >> file
> >> so the export renders as ASCII that was new for 2005.
> >>
> >> To get around the CSV problem in 2000 I would have a link and use jump to
> >> url to export CSV as ASCII.
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "AMasson" <ann.masson@.eds.com> wrote in message
> >> news:1145460618.827732.45560@.i39g2000cwa.googlegroups.com...
> >> > Is it just the setting of the deviceinfo in the config files that is
> >> > new for 2005 or the ability to pass it in via the URL as well?
> >> >
> >> > I had been told previously (by a contact at Microsoft) that he had
> >> > tested out SimplePageHeaders=True via URL in RS2000 and it worked OK.
> >> > I have tried this without success.
> >> >
> >> > I'm adding &rc:SimplePageHeaders=True to a valid URL. If I add
> >> > rc:RemoveSpace=0.5in, or rc:OmitFormulas=True, these work OK. If I use
> >> > SimplePageHeaders, the dialog to download the xls file displays no File
> >> > Name or File Type and if I select Open, I get an Internet Explorer
> >> > error "Internet Explorer cannot download from <servername>. Internet
> >> > Explorer was not able to open this Internet site. The requested site
> >> > is either unavailable or cannot be found. Please try again later". I
> >> > have tried running tcptrace on it - this shows the ExcelRendering
> >> > Exception thrown.
> >> >
> >> > Is it possible to get a definite answer on whether SimplePageHeaders
> >> > should work via URL in RS2000 SP2, and if so, any idea what my problem
> >> > might be?
> >> >
> >> >
> >> > Bruce L-C [MVP] wrote:
> >> >> I know that the ASCII change only works for 2005. Don't know about
> >> >> what
> >> >> you
> >> >> are trying to do but it wouldn't surprise me.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "AMasson" <ann.masson@.eds.com> wrote in message
> >> >> news:1145433029.371431.162640@.v46g2000cwv.googlegroups.com...
> >> >> >I have also been trying to add deviceinfo settings to the config
> >> >> >files,
> >> >> > but to set the Excel rendering SimplePageHeaders to true. I have
> >> >> > had
> >> >> > no success with this (there are no errors, and export to Excel works
> >> >> > as
> >> >> > previously) - is this something that is only available in RS2005?
> >> >> > (I'm
> >> >> > using RS2000 SP2). I have also tried setting SimplePageHeaders via
> >> >> > URL
> >> >> > but this generates an exception and I have found no resolution to
> >> >> > this.
> >> >> >
> >> >> > Config file update I am doing is:
> >> >> >
> >> >> > <Extension Name="EXCEL"
> >> >> > Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering">
> >> >> > <Configuration>
> >> >> > <DeviceInfo>
> >> >> >
> >> >> > <SimplePageHeaders>True</SimplePageHeaders>
> >> >> > </DeviceInfo>
> >> >> > </Configuration>
> >> >> > </Extension>
> >> >> >
> >> >> >
> >> >> >
> >> >> > Wei Lu wrote:
> >> >> >> Hi Scott,
> >> >> >>
> >> >> >> I think after you change the RSReportDesigner.config, you need to
> >> >> >> restart
> >> >> >> the box to take the effect on Visual Studio.
> >> >> >>
> >> >> >> Sincerely,
> >> >> >>
> >> >> >> Wei Lu
> >> >> >> Microsoft Online Community Support
> >> >> >>
> >> >> >> ==================================================> >> >> >>
> >> >> >> When responding to posts, please "Reply to Group" via your
> >> >> >> newsreader
> >> >> >> so
> >> >> >> that others may learn and benefit from your issue.
> >> >> >>
> >> >> >> ==================================================> >> >> >> This posting is provided "AS IS" with no warranties, and confers no
> >> >> >> rights.
> >> >> >
> >> >
> >|||Hi Masson,
According to the Reporting Services 2000 Books Online, there is no
SimplePageHeaders settting.
The only available Excel Device Information Settings are :
OmitDocumentMap
Indicates whether to omit the document map for reports that support it. The
default value is false.
OmitFormulas
Indicates whether to omit formulas from the rendered report. The default
value is false.
RemoveSpace
Indicates whether to omit rows or columns that do not contain data and are
smaller than the given size. Use this setting to remove extra rows or
columns that do not contain report items. You must include an integer or
decimal value followed by "in" (for example, 0.5in). The default value is
0.125in.
You can use the SimplePageHeaders in Reporting Services 2005.
Hope this information is helpful.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||I realised that there was no mention in the Books Online. However,
since I had been told by someone at Microsoft "I just tested this on
2000 SP2 and it appears to work fine" I was assuming that it was an
option but that there was something I was doing wrong, or I had somehow
introduced a bug with the specific reports I was testing it on. Also,
when I first searched the forums for info on SimplePageHeaders, there
were several posts in July/Oct 2004 recommending using
SimplePageHeaders as a method of improving the layout in Excel and
responses indicating it had worked and was an ideal resolution (and a
comment that it wasn't in the online documentation at that time
either).
Does this mean that it worked previously, but now doesn't in RS2000 SP2
(or that there are enough inconsistencies in its behaviour that it's
not supported?)
Wei Lu wrote:
> Hi Masson,
> According to the Reporting Services 2000 Books Online, there is no
> SimplePageHeaders settting.
> The only available Excel Device Information Settings are :
> OmitDocumentMap
> Indicates whether to omit the document map for reports that support it. The
> default value is false.
> OmitFormulas
> Indicates whether to omit formulas from the rendered report. The default
> value is false.
> RemoveSpace
> Indicates whether to omit rows or columns that do not contain data and are
> smaller than the given size. Use this setting to remove extra rows or
> columns that do not contain report items. You must include an integer or
> decimal value followed by "in" (for example, 0.5in). The default value is
> 0.125in.
> You can use the SimplePageHeaders in Reporting Services 2005.
> Hope this information is helpful.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Masson,
I have checked in internal Knowledge Base, you can use the
SimplePageHeaders in URL for RS 2000.
So would you please provide the entire URL strings here, and please provide
the entire Error log information here.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||URL I am using is:
http://w2kzthfm02/ReportServer?/RptTestHeaders/rptTestHeaders&P_NOMTYPEID=5&P_PRODUCTIONAREA=Scott&P_FROMDATE=01+Jan+2007&P_VERSIONNO:isnull=True&P_USERNAME=Ann&P_VERSIONFLAG=N&rs:Command=Render&rs:Format=EXCEL&rc:SimplePageHeaders=True
(This works fine without the &rc:SimplePageHeaders=True added)
Error log info:
aspnet_wp!library!fc0!04/21/2006-12:19:06:: i INFO: Call to
RenderFirst( '/RptTestHeaders/rptTestHeaders' )
aspnet_wp!library!fc0!04/21/2006-12:19:06:: i INFO: Initializing
EnableIntegratedSecurity to 'True' as specified in Server system
properties.
aspnet_wp!library!fe0!4/21/2006-12:19:12:: i INFO: Initializing
SqlStreamingBufferSize to default value of '64640' Bytes because it was
not specified in Server system properties.
aspnet_wp!library!fe0!4/21/2006-12:19:12:: i INFO: Initializing
SnapshotCompression to 'SQL' as specified in Server system properties.
aspnet_wp!library!fc0!04/21/2006-12:19:13:: Using folder C:\Program
Files\Microsoft SQL Server\MSSQL\Reporting Services\RSTempFiles for
temporary files.
aspnet_wp!reportrendering!fc0!04/21/2006-12:19:14:: e ERROR: Throwing
Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException
was thrown., ;
Info:
Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException
was thrown. -->
Microsoft.ReportingServices.ReportRendering.ReportRenderingException:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException
was thrown. --> System.NullReferenceException: Object reference not
set to an instance of an object.
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.MarkHeaderFooterTextboxPosition(ReportItem
reportItem, IntList parentIndexPath, Int32 index, Double parentLeft,
Double parentTop, IPosArray& xArray, IPosArray& yArray)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.PreProcessHeaderFooterRectangle(ReportItemCollection
reportItemsCollection, IntList parentIndexPath, Double parentLeft,
Double parentTop, IPosArray& xArray, IPosArray& yArray)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.PreProcessHeaderFooterRectangle(ReportItemCollection
reportItemsCollection, IntList parentIndexPath, Double parentLeft,
Double parentTop, IPosArray& xArray, IPosArray& yArray)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.PreProcessHeaderFooter(PageSection
pageSection, Boolean isHeader)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.EvaluatePageHeaderFooterForLayout(Int32
currentPageNumber, Int32 pageCount, PageReportItems pageRIItems)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.CreatePages(ReportItemCollection
collection, MarkInformation parentMarkInfo, Boolean& isPBSPropagated,
Boolean hasLastPage, Boolean ignorePageBreaks, Boolean
isHeaderBeingProcessed, FormulaContext formulaContext, String language,
PageReportItems& firstPageReportItems, PageLayout& firstPageLayout,
PageCollection& pageCollection)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.PreProcessReport()
-- End of inner exception stack trace --
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.Render(Report
report, NameValueCollection reportServerParameters, NameValueCollection
deviceInfo, NameValueCollection clientCapabilities,
EvaluateHeaderFooterExpressions evaluateHeaderFooterExpressions,
CreateAndRegisterStream createAndRegisterStream)
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.a(DateTime
A_0, GetReportChunk A_1, ProcessingContext A_2, RenderingContext A_3,
CreateReportChunk A_4, Boolean& A_5)
-- End of inner exception stack trace --
aspnet_wp!library!fc0!04/21/2006-12:19:14:: i INFO: Initializing
EnableExecutionLogging to 'True' as specified in Server system
properties.
aspnet_wp!webserver!fc0!04/21/2006-12:19:16:: e ERROR: Reporting
Services error
Microsoft.ReportingServices.Diagnostics.Utilities.RSException:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException
was thrown. -->
Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException
was thrown. -->
Microsoft.ReportingServices.ReportRendering.ReportRenderingException:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException
was thrown. --> System.NullReferenceException: Object reference not
set to an instance of an object.
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.MarkHeaderFooterTextboxPosition(ReportItem
reportItem, IntList parentIndexPath, Int32 index, Double parentLeft,
Double parentTop, IPosArray& xArray, IPosArray& yArray)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.PreProcessHeaderFooterRectangle(ReportItemCollection
reportItemsCollection, IntList parentIndexPath, Double parentLeft,
Double parentTop, IPosArray& xArray, IPosArray& yArray)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.PreProcessHeaderFooterRectangle(ReportItemCollection
reportItemsCollection, IntList parentIndexPath, Double parentLeft,
Double parentTop, IPosArray& xArray, IPosArray& yArray)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.PreProcessHeaderFooter(PageSection
pageSection, Boolean isHeader)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.EvaluatePageHeaderFooterForLayout(Int32
currentPageNumber, Int32 pageCount, PageReportItems pageRIItems)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.CreatePages(ReportItemCollection
collection, MarkInformation parentMarkInfo, Boolean& isPBSPropagated,
Boolean hasLastPage, Boolean ignorePageBreaks, Boolean
isHeaderBeingProcessed, FormulaContext formulaContext, String language,
PageReportItems& firstPageReportItems, PageLayout& firstPageLayout,
PageCollection& pageCollection)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.PreProcessReport()
-- End of inner exception stack trace --
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.Render(Report
report, NameValueCollection reportServerParameters, NameValueCollection
deviceInfo, NameValueCollection clientCapabilities,
EvaluateHeaderFooterExpressions evaluateHeaderFooterExpressions,
CreateAndRegisterStream createAndRegisterStream)
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.a(DateTime
A_0, GetReportChunk A_1, ProcessingContext A_2, RenderingContext A_3,
CreateReportChunk A_4, Boolean& A_5)
-- End of inner exception stack trace --
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.a(DateTime
A_0, GetReportChunk A_1, ProcessingContext A_2, RenderingContext A_3,
CreateReportChunk A_4, Boolean& A_5)
at
Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(DateTime
executionTimeStamp, GetReportChunk getCompiledDefinitionCallback,
ProcessingContext pc, RenderingContext rc)
at
Microsoft.ReportingServices.Library.RSService.RenderAsLive(CatalogItemContext
reportContext, ItemProperties properties, ParameterInfoCollection
effectiveParameters, Guid reportId, ClientRequest session, String
description, ReportSnapshot intermediateSnapshot,
DataSourceInfoCollection thisReportDataSources, Boolean
cachingRequested, Warning[]& warnings, ReportSnapshot&
resultSnapshotData, DateTime& executionDateTime,
RuntimeDataSourceInfoCollection& alldataSources, UserProfileState&
usedUserProfile)
at
Microsoft.ReportingServices.Library.RSService.RenderAsLiveOrSnapshot(CatalogItemContext
reportContext, ClientRequest session, Warning[]& warnings,
ParameterInfoCollection& effectiveParameters)
at
Microsoft.ReportingServices.Library.RSService.RenderFirst(CatalogItemContext
reportContext, ClientRequest session, Warning[]& warnings,
ParameterInfoCollection& effectiveParameters, String[]&
secondaryStreamNames)
at
Microsoft.ReportingServices.Library.RenderFirstCancelableStep.Execute()
at
Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
-- End of inner exception stack trace --
at
Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
at
Microsoft.ReportingServices.Library.RenderFirstCancelableStep.RenderFirst(RSService
rs, CatalogItemContext reportContext, ClientRequest session,
JobTypeEnum type, Warning[]& warnings, ParameterInfoCollection&
effectiveParameters, String[]& secondaryStreamNames)
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderReport(HttpResponseStreamFactory
streamFactory)
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderReport()
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderItem(ItemType
itemType)
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPageContent()
at
Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage()
Wei Lu wrote:
> Hi Masson,
> I have checked in internal Knowledge Base, you can use the
> SimplePageHeaders in URL for RS 2000.
> So would you please provide the entire URL strings here, and please provide
> the entire Error log information here.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Masson,
Thanks for the update.
It did work on my side.
According to the error message, I think you need to check whether this
issue occur on all the report first.
Also, please check the report design that whether the report includes the
page header or not.
Please understand that we may need dump analysis or live debug to
troubleshoot the issue. We might take a long time to narrow down. During
the course of troubleshooting, we may redirect you to PSS if required.
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
I appreciate your understanding on this.
Please feel free to let us know if you have any update on this issue.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||The problem appears to be caused by setting the alignment property of
text boxes in the header using a value returned from a coded method. I
use a custom assembly to query a stylesheet file to apply configurable
formatting to report items. This works fine in all areas of the report
body/header/footer for font properties, background colour, border
colour etc, but if used for the Text alignment in the header or footer
it causes the above problem when exported to Excel (works fine in the
report body). It demonstrates the same problem if I reference a code
block in the report, but with the alignment hard-coded to a standard
value it's OK.
Wei Lu wrote:
> Hi Masson,
> Thanks for the update.
> It did work on my side.
> According to the error message, I think you need to check whether this
> issue occur on all the report first.
> Also, please check the report design that whether the report includes the
> page header or not.
> Please understand that we may need dump analysis or live debug to
> troubleshoot the issue. We might take a long time to narrow down. During
> the course of troubleshooting, we may redirect you to PSS if required.
> For a complete list of Microsoft Product Support Services phone numbers,
> please go to the following address on the World Wide Web:
> http://support.microsoft.com/directory/overview.asp
> I appreciate your understanding on this.
> Please feel free to let us know if you have any update on this issue.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.