Excluding Export Options on Report

In the rsreportserver.config there is a <ExcludedRenderFormats> element, which allows you to list the rendering formats that are excluded from the export option for all reports.

Is this the only way you can change this? i.e. can you change this through Management Studio or Report Manager, and also can you exclude the export options for a single report rather than having to do it for all reports?

Thank you

Hi,

no this is a serverwide property which can only be administered through the "XML-Interface" <:-)

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||To confirm the "XML-Interface" being the rsReportServer.config file|||Yes.sql

excel vs. pdf - is it possible to eliminate header?

I have a report that has images etc. (company logo) at the top which works
fine when rendering to pdf. However I'd like to elimiate this stuff when
rendering to xls. Is that possible?
Thanks.
--CoryTry CSV ASCII instead. Much faster and it will do what you want.
Here is an example of a Jump to URL link I use. This causes Excel to come up
with the data in a separate window:
="javascript:void(window.open('" & Globals!ReportServerUrl &
"?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
"&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Cory" <Cory@.discussions.microsoft.com> wrote in message
news:3CA7586B-D025-4561-9D32-6BD9A63303C3@.microsoft.com...
>I have a report that has images etc. (company logo) at the top which works
> fine when rendering to pdf. However I'd like to elimiate this stuff when
> rendering to xls. Is that possible?
> Thanks.
> --Cory

Excel versus PDF Rendering

We have a report that's rendered to a printable form over 1000 times
in a span of 2 hours. We're in the process of replacing the server
because this workload has been hammering the machine and running the
RS services out of memory. I've added a metering component (the page
that redirects users to the report checks to see how many reports are
running and holds them at that page if it's over a set number). My
question is... for a fairly plain report (about 8 pages, mostly just
gridlines and shaded areas, with column and row header text. No
embedded images), which rendering performs better - PDF or Excel?
I've done some un-scientific research, and found that the CPU and
clock-time for each is pretty consistent, but that PDF might require
less memory per rendering report? Any feedback on this would be very
helpful.With SP1 of Reporting, the Algoritm for PDF Render are improved.
Con el Service Pack 1, el algoritmo de renderizacion de PDF fue mejorado.
John Bocachica
Colombia
"TShay" wrote:
> We have a report that's rendered to a printable form over 1000 times
> in a span of 2 hours. We're in the process of replacing the server
> because this workload has been hammering the machine and running the
> RS services out of memory. I've added a metering component (the page
> that redirects users to the report checks to see how many reports are
> running and holds them at that page if it's over a set number). My
> question is... for a fairly plain report (about 8 pages, mostly just
> gridlines and shaded areas, with column and row header text. No
> embedded images), which rendering performs better - PDF or Excel?
> I've done some un-scientific research, and found that the CPU and
> clock-time for each is pretty consistent, but that PDF might require
> less memory per rendering report? Any feedback on this would be very
> helpful.
>

Excel Rendering updated?

I'm wondering whether Katmai Reporting Services will do a better job of "rendering" to Excel. Quite Frequently, I create nice looking reports for the PDF renderer, only to to make a separate copy of that same report and mangle it so that I can get half of what I wanted.

For example:

1. I am frequently lining up the left and right edges of text boxes everywhere, as to not generate way too many columns in excel. As a result, I'm often formatting for excel to look, often ignoring the formatting needs of my data. The worst case scenario of this is when I had two rows of textboxes (roughly seven textboxes each) , and the PDF renderer did a beautiful job. However the Excel renderer would randomly choose to push some of the textboxes down into another Excel row, giving a checker-board look to my report. Hours were wasted in attempts to reformat a separate copy of the report to eliminate the Checkerboard look, to no avail.

2. Formatting Data in any way (FormatCurrency(), FormatDate(), ect) converts the data type to string, and my excel reports are flooded with smart tags saying "Convert to Number". These reports do not gracefully import into my client's applications. In addition to this, there is no way to format the textboxes so that Excel's Cell formatting will be given to the cells (right click on a cell, "Format Cells" and choose a category and some options with different categories). I can leave the data unformatted, but it looks SO unprofessional. So I have been evaluating several other Excel reporting packages that will allow me to Format Cells without changing the data types of my data to a string.

3. Images. Yikes! The PDF renderer has had some occasional glitches with images that some vendors have given us. We have thousands of vendors that give us images created with a large spectrum of consumer digital cameras. Occasionally, the PDF renderer refuses to render (a large gamut of error messages have been seen), while the TIFF renderer will suceed. I have even had an image (still do if you would find them helpful) that will not even render through the TIFF renderer. I had to open the image and "Save As " to get the TIFF renderer to work, but the PDF renderer would still not work. So we had to create some backup tools to "Resave the images" and also "use the TIFF version instead", both of which cost us personnel time.

Please let me know if these will be fixed in the Katmai RS?!?

For #1, the Excel rendering has improved in Katmai, mainly around reducing the number of merged cells. However, it looks like you are looking for more of a data renderer, which is currently not planned.

For #2, why are you using the Format... functions instead of setting the format property? If you set the format property, you should get numbers with the appropriate formatting.

For #3, it sounds like you are running into a bug, either with our PDF renderer or the framework image libraries. Have you filed repro cases at http://connect.microsoft.com?

Brian|||

Alternatively, if you are having problem getting http://connect.microsoft.com to work, you can email me directly with a sample of the problem images. Clicking on my name to the left will show my email address. Just be sure to put a good subject line so my inbox doesn't delete your email as spam.

Thank you.

Excel Rendering updated?

I'm wondering whether Katmai Reporting Services will do a better job of "rendering" to Excel. Quite Frequently, I create nice looking reports for the PDF renderer, only to to make a separate copy of that same report and mangle it so that I can get half of what I wanted.

For example:

1. I am frequently lining up the left and right edges of text boxes everywhere, as to not generate way too many columns in excel. As a result, I'm often formatting for excel to look, often ignoring the formatting needs of my data. The worst case scenario of this is when I had two rows of textboxes (roughly seven textboxes each) , and the PDF renderer did a beautiful job. However the Excel renderer would randomly choose to push some of the textboxes down into another Excel row, giving a checker-board look to my report. Hours were wasted in attempts to reformat a separate copy of the report to eliminate the Checkerboard look, to no avail.

2. Formatting Data in any way (FormatCurrency(), FormatDate(), ect) converts the data type to string, and my excel reports are flooded with smart tags saying "Convert to Number". These reports do not gracefully import into my client's applications. In addition to this, there is no way to format the textboxes so that Excel's Cell formatting will be given to the cells (right click on a cell, "Format Cells" and choose a category and some options with different categories). I can leave the data unformatted, but it looks SO unprofessional. So I have been evaluating several other Excel reporting packages that will allow me to Format Cells without changing the data types of my data to a string.

3. Images. Yikes! The PDF renderer has had some occasional glitches with images that some vendors have given us. We have thousands of vendors that give us images created with a large spectrum of consumer digital cameras. Occasionally, the PDF renderer refuses to render (a large gamut of error messages have been seen), while the TIFF renderer will suceed. I have even had an image (still do if you would find them helpful) that will not even render through the TIFF renderer. I had to open the image and "Save As " to get the TIFF renderer to work, but the PDF renderer would still not work. So we had to create some backup tools to "Resave the images" and also "use the TIFF version instead", both of which cost us personnel time.

Please let me know if these will be fixed in the Katmai RS?!?

For #1, the Excel rendering has improved in Katmai, mainly around reducing the number of merged cells. However, it looks like you are looking for more of a data renderer, which is currently not planned.

For #2, why are you using the Format... functions instead of setting the format property? If you set the format property, you should get numbers with the appropriate formatting.

For #3, it sounds like you are running into a bug, either with our PDF renderer or the framework image libraries. Have you filed repro cases at http://connect.microsoft.com?

Brian|||

Alternatively, if you are having problem getting http://connect.microsoft.com to work, you can email me directly with a sample of the problem images. Clicking on my name to the left will show my email address. Just be sure to put a good subject line so my inbox doesn't delete your email as spam.

Thank you.

Excel Rendering Question

When a report is exported to Excel, each page in the report becomes a
worksheet. The worksheets are named as 'sheet 1', 'sheet 2' etc. Is there
any way to name the sheets as page headings?Hi Sanjay,
My grouping is exactly the same. However, I also have pagebreakatend set:
<Grouping Name="list1_Country_Name">
<GroupExpressions>
<GroupExpression>=Fields!CountryName.Value</GroupExpression>
</GroupExpressions>
<PageBreakAtEnd>true</PageBreakAtEnd>
</Grouping>
A.
"Sanjay" wrote:
> I have the following grouping element in my report:
> <Grouping Name="list2_Details_Group">
> <GroupExpressions>
> <GroupExpression>=Fields!customer_name.Value</GroupExpression>
> </GroupExpressions>
> </Grouping>
> Excel is rendered as each customer in a different sheet but I also need the
> sheet name to be =Fields!customer_name.Value.
> Andrew,
> Can you post the rdl extract where your groupings are named?
> Thanks
> Sanjay
> "Andrew Byrne" wrote:
> > I have seen this whenever I export to Excel and have my report grouped. For
> > example, if I group by country then excel will render with each sheet=a
> > country. In my case the country names were written to the Sheet Name, so
> > maybe you just need to name your groupings in the report?
> >
> > "Sanjay" wrote:
> >
> > > When a report is exported to Excel, each page in the report becomes a
> > > worksheet. The worksheets are named as 'sheet 1', 'sheet 2' etc. Is there
> > > any way to name the sheets as page headings?

Excel rendering problem(s)

I have a report containing a matrix.
The matrix cells contain a textbox with the data to display.
I need that textbox to appear only some times, so i wrote a function that
returns true or false depending on some field value that i pass as
parametter.
The report renders fine as PDF, but when i try to render it as XLS i get a
null refference error.
Does anyone know what the problem is ?
Also in another report i have 3 images in a cell (of a table or a matrix..
behave the same) and i set only one of them visible at a time based on other
fields values
in PDF also works fine, but when i try to render it in excel. Only one of
the images appear, and where the conditions call for one of the other two
images should
appear no image is visible.
The two problems might be related....
Thank you.
RazvanI had the same problem, it is a bug that Microsoft won't fix it.
Here's another one even worse, try exporting a report containing subreports
in Excel. None of the subreports will be rendered.
Needles to say all my clients want all their reports in Excel because it
allows them to easily do adhoc massages to their data.
Microsoft do you hear me, this is pretty basic stuff ! Fix it please!
Tzepesh
"Razvan Popov" wrote:
> I have a report containing a matrix.
> The matrix cells contain a textbox with the data to display.
> I need that textbox to appear only some times, so i wrote a function that
> returns true or false depending on some field value that i pass as
> parametter.
> The report renders fine as PDF, but when i try to render it as XLS i get a
> null refference error.
> Does anyone know what the problem is ?
> Also in another report i have 3 images in a cell (of a table or a matrix..
> behave the same) and i set only one of them visible at a time based on other
> fields values
> in PDF also works fine, but when i try to render it in excel. Only one of
> the images appear, and where the conditions call for one of the other two
> images should
> appear no image is visible.
> The two problems might be related....
> Thank you.
> Razvan
>
>

Excel Rendering Problem w/ SP1

Since installing SP1, RS does not render color information to Excel
correctly. The report in question renders to all other formats correctly. The
error occurs on a variance report where individual cells of a table have
color dynamically assigned based on the variance values (green = good, red = bad). Instead of formatting the individual cell based on the logic embedded
in the report, the entire column retains the color code of the first column.
Any help?Hi,
I had a problem while rendering to Excel before the SP1.
After SP1 is installed Excel rendering works fine.
Eralper
http://www.kodyaz.com
"SD Sills" wrote:
> Since installing SP1, RS does not render color information to Excel
> correctly. The report in question renders to all other formats correctly. The
> error occurs on a variance report where individual cells of a table have
> color dynamically assigned based on the variance values (green = good, red => bad). Instead of formatting the individual cell based on the logic embedded
> in the report, the entire column retains the color code of the first column.
> Any help?|||Same problem here .
Did you find a solution ?
"SD Sills" <SDSills@.discussions.microsoft.com> wrote in message
news:D74E38BA-08AC-4D7F-B54F-E4F5F9E7DE7B@.microsoft.com...
> Since installing SP1, RS does not render color information to Excel
> correctly. The report in question renders to all other formats correctly.
> The
> error occurs on a variance report where individual cells of a table have
> color dynamically assigned based on the variance values (green = good, red
> => bad). Instead of formatting the individual cell based on the logic
> embedded
> in the report, the entire column retains the color code of the first
> column.
> Any help?|||I'm using the below expression for background information of Active column
in my report. I want to see background green if the record is active, red
otherwise
so my expression for BackgroundColor is :
=iif(Fields!Active.Value="True","Green","Red")
Active field has a boolean type in SQl server.
I'm using MS Excel version 2003 SP1, 11.6355.6360 and colors of the exported
excel document is correct.
Excel version may cause rendering problems. I was having one with version 9.
Eralper
http://www.kodyaz.com
"Tudor VAsile" wrote:
> Same problem here .
> Did you find a solution ?
> "SD Sills" <SDSills@.discussions.microsoft.com> wrote in message
> news:D74E38BA-08AC-4D7F-B54F-E4F5F9E7DE7B@.microsoft.com...
> > Since installing SP1, RS does not render color information to Excel
> > correctly. The report in question renders to all other formats correctly.
> > The
> > error occurs on a variance report where individual cells of a table have
> > color dynamically assigned based on the variance values (green = good, red
> > => > bad). Instead of formatting the individual cell based on the logic
> > embedded
> > in the report, the entire column retains the color code of the first
> > column.
> >
> > Any help?
>
>

Excel Rendering Problem

When I render in Excel, the Excel cells do not grow to accomodate the cell
contents so data is hiding up, e.g. ABCD is not wrapping up as
AB
CD
but showing up as
AB
if the column width is small.
Anybody has seen this happen?
How to overcome this?
Thanks
SanjaySanjay,
I have experienced the same problem, but I cannot find any way for RS to
'instruct' excel to expand cells where required. Therefore this has to be
dealt with within the Excel app.
You will likely know the next part, but for those that do not: If you select
the whole worksheet, right click and turn on Word Wrapping, the rows will
expand virtically to display all the data. If you want the rows to remain the
same height, turn off WW and they will return to their original sizes. To
expand all columns, select whole worksheet, move the mousr along the top
column header bar until a double horizontal arrow appera, and double-click.
The columns will expand to their custom widths, dependant on what data is
contained in the column.
If you wish to automate this, and place in a macro, the following code will
assist you:
Cells.Select
Cells.EntireColumn.AutoFit
With Selection
.HorizontalAlignment = xlLeft
.VerticalAlignment = xlBottom
.WrapText = True 'False to turn off
.Orientation = 0
.AddIndent = False
.IndentLevel = 0
.ShrinkToFit = False
.ReadingOrder = xlContext
.MergeCells = False
End With
"Sanjay" wrote:
> When I render in Excel, the Excel cells do not grow to accomodate the cell
> contents so data is hiding up, e.g. ABCD is not wrapping up as
> AB
> CD
> but showing up as
> AB
> if the column width is small.
> Anybody has seen this happen?
> How to overcome this?
> Thanks
> Sanjay|||Thanks, Logicalman. Your post has been really useful. Can I cause a macro to
be included in a report server generated Excel spreadsheet?
I have several reports and this happens with only one of those reports. The
one report it happens with is modified from one of the reports with which
this doesn't happen. Something has changed in this rdl which is causing this
behavior. I was wondering if somebody knew what that change could be.
Thanks
Sanjay
"Logicalman" wrote:
> Sanjay,
> I have experienced the same problem, but I cannot find any way for RS to
> 'instruct' excel to expand cells where required. Therefore this has to be
> dealt with within the Excel app.
> You will likely know the next part, but for those that do not: If you select
> the whole worksheet, right click and turn on Word Wrapping, the rows will
> expand virtically to display all the data. If you want the rows to remain the
> same height, turn off WW and they will return to their original sizes. To
> expand all columns, select whole worksheet, move the mousr along the top
> column header bar until a double horizontal arrow appera, and double-click.
> The columns will expand to their custom widths, dependant on what data is
> contained in the column.
> If you wish to automate this, and place in a macro, the following code will
> assist you:
> Cells.Select
> Cells.EntireColumn.AutoFit
> With Selection
> .HorizontalAlignment = xlLeft
> .VerticalAlignment = xlBottom
> .WrapText = True 'False to turn off
> .Orientation = 0
> .AddIndent = False
> .IndentLevel = 0
> .ShrinkToFit = False
> .ReadingOrder = xlContext
> .MergeCells = False
> End With
>
> "Sanjay" wrote:
> > When I render in Excel, the Excel cells do not grow to accomodate the cell
> > contents so data is hiding up, e.g. ABCD is not wrapping up as
> > AB
> > CD
> >
> > but showing up as
> > AB
> >
> > if the column width is small.
> >
> > Anybody has seen this happen?
> > How to overcome this?
> >
> > Thanks
> > Sanjay|||Sanjay,
I apologise but that's the part I am still working on, the 'instruct' part.
I am certain it included in the URL used to create the Excel-formatted output.
One thing you say that may hold a key though is in the second para of your
reply '...one report it happens with is modified from one of the reports with
which this doesn't happen...', this leads me to belive that it is in the URL
of the export. I have taken the exporting to a level of simply placing a
button on a standard (or curently used) ASP page, and simply attaching the
URL to the Onclick event of the button.
You may take a look at the export part of the report you generate, this may
then hold the key to what is actually different between the two reports.
For myself, I would be more than interested in the results you get, as this
is just another step in my temas usage of RS to deliver ad-hoc reporting for
our current Intranet sites delivering mertics.
Please keep me informed of any progress there, and I will continue trying to
find the same answer also. I can be contacted via my email address, just
remove ALL the numbers from it first.
Thanks,
Tony
"Sanjay" wrote:
> Thanks, Logicalman. Your post has been really useful. Can I cause a macro to
> be included in a report server generated Excel spreadsheet?
> I have several reports and this happens with only one of those reports. The
> one report it happens with is modified from one of the reports with which
> this doesn't happen. Something has changed in this rdl which is causing this
> behavior. I was wondering if somebody knew what that change could be.
> Thanks
> Sanjay
> "Logicalman" wrote:
> > Sanjay,
> >
> > I have experienced the same problem, but I cannot find any way for RS to
> > 'instruct' excel to expand cells where required. Therefore this has to be
> > dealt with within the Excel app.
> > You will likely know the next part, but for those that do not: If you select
> > the whole worksheet, right click and turn on Word Wrapping, the rows will
> > expand virtically to display all the data. If you want the rows to remain the
> > same height, turn off WW and they will return to their original sizes. To
> > expand all columns, select whole worksheet, move the mousr along the top
> > column header bar until a double horizontal arrow appera, and double-click.
> > The columns will expand to their custom widths, dependant on what data is
> > contained in the column.
> >
> > If you wish to automate this, and place in a macro, the following code will
> > assist you:
> >
> > Cells.Select
> > Cells.EntireColumn.AutoFit
> > With Selection
> > .HorizontalAlignment = xlLeft
> > .VerticalAlignment = xlBottom
> > .WrapText = True 'False to turn off
> > .Orientation = 0
> > .AddIndent = False
> > .IndentLevel = 0
> > .ShrinkToFit = False
> > .ReadingOrder = xlContext
> > .MergeCells = False
> > End With
> >
> >
> >
> > "Sanjay" wrote:
> >
> > > When I render in Excel, the Excel cells do not grow to accomodate the cell
> > > contents so data is hiding up, e.g. ABCD is not wrapping up as
> > > AB
> > > CD
> > >
> > > but showing up as
> > > AB
> > >
> > > if the column width is small.
> > >
> > > Anybody has seen this happen?
> > > How to overcome this?
> > >
> > > Thanks
> > > Sanjay

Excel Rendering Failure

Hi,
Is there anyone out there that has had this problem.
All my renderings from the report server work except for
MS Excel for all of my reports.
The report contains the following about 5 times:
"This is a multi-part message in MIME format.
--=_NextPart_01C35DB7.4B204430
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: base64
Content-Location: file:///c:/Report.htm "
As I said, all other renders complete fine except for
excel - the very tool that my manager likes'?
Some one plese help - 1 week to deploy.
MichaelIs this on SP1? Does this happen only on the server or also from Preview tab
in report designer? Does this happen with all reports you have or just this
one? If so, could you please send me the rdl and the corresponding .rdata
file (found in the report project folder) - just remove "discussions" from
my email address when you send the files.
--
Ravi Mumulla (Microsoft)
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
<michael.mazzanti@.team.telstra.com> wrote in message
news:3d3401c4aaaa$7378df00$a401280a@.phx.gbl...
> Hi,
> Is there anyone out there that has had this problem.
> All my renderings from the report server work except for
> MS Excel for all of my reports.
> The report contains the following about 5 times:
> "This is a multi-part message in MIME format.
> --=_NextPart_01C35DB7.4B204430
> Content-Type: text/html;
> charset="utf-8"
> Content-Transfer-Encoding: base64
> Content-Location: file:///c:/Report.htm "
> As I said, all other renders complete fine except for
> excel - the very tool that my manager likes'?
> Some one plese help - 1 week to deploy.
> Michael
>|||I am having this same problem as well. The interesting
thing is that it does this on one computer and if I export
the same report from another computer it works fine. The
main difference in our computers is that I have Excel 2003
and he has Excel 2000. We created the reporting using the
Report Designer that is included with Reporting Services
Enterprise Ed.
Anyone have any thoughts'
>--Original Message--
>Is this on SP1? Does this happen only on the server or
also from Preview tab
>in report designer? Does this happen with all reports you
have or just this
>one? If so, could you please send me the rdl and the
corresponding .rdata
>file (found in the report project folder) - just remove
"discussions" from
>my email address when you send the files.
>--
>Ravi Mumulla (Microsoft)
>SQL Server Reporting Services
>This posting is provided "AS IS" with no warranties, and
confers no rights.
><michael.mazzanti@.team.telstra.com> wrote in message
>news:3d3401c4aaaa$7378df00$a401280a@.phx.gbl...
>> Hi,
>> Is there anyone out there that has had this problem.
>> All my renderings from the report server work except for
>> MS Excel for all of my reports.
>> The report contains the following about 5 times:
>> "This is a multi-part message in MIME format.
>> --=_NextPart_01C35DB7.4B204430
>> Content-Type: text/html;
>> charset="utf-8"
>> Content-Transfer-Encoding: base64
>> Content-Location: file:///c:/Report.htm "
>> As I said, all other renders complete fine except for
>> excel - the very tool that my manager likes'?
>> Some one plese help - 1 week to deploy.
>> Michael
>
>.
>

Excel rendering crash with parameters. Ok as HTML.

Hi,
I am trying to render report I have with a matrix on it using the web
service.
It works fine if I render to excel format with no parameters provided
to the report.
It also works fine if I use the exact same code and just change the
render format to "HTML4.0" instead of "EXCEL".
As the error only happens with Excel specified and parameters provided
could this be a bug?
I had a search in this group and didn't find anyone else reporting
this so I may well be doing something silly.
Any advice would be apreciated, code and the error message returned in
the SoapException.Detail.Text follow. Please let me know if you need
any more details about what I'm doing
Thanks
Code:
string strReportName = "/MyReport";
string Hist = null;
XL3Addin.ReportService.DataSourceCredentials[] Creds = new
XL3Addin.ReportService.DataSourceCredentials[0];
string ShowHide = "";
string Enc = "";
string Mime = "";
string[] Streams;
XL3Addin.ReportService.ParameterValue[] ParamsOut;
XL3Addin.ReportService.Warning[] Warns;
//get the parameters out of a datagrid I have
XL3Addin.ReportService.ParameterValue[] ParamsIn = new
XL3Addin.ReportService.ParameterValue[this.ParamterTable.Rows.Count];
for(int i=0; i<this.ParamterTable.Rows.Count; i++)
{
ParamsIn[i] = new XL3Addin.ReportService.ParameterValue();
ParamsIn[i].Name = this.ParamterTable.Rows[i].ItemArray[0].ToString();
ParamsIn[i].Value = this.ParamterTable.Rows[i].ItemArray[2].ToString();
ParamsIn[i].Label = this.ParamterTable.Rows[i].ItemArray[1].ToString();
}
byte[] rep = rs.Render(strReportName, RenderFormat, Hist, DeviceInfo,
ParamsIn, Creds, ShowHide, out Enc, out Mime, out ParamsOut, out
Warns, out Streams);
Works if:
string RenderFormat = "EXCEL";
string DeviceInfo = "<DeviceInfo><OmitDocumentMap>False</OmitDocumentMap><OmitFormulas>False</OmitFormulas><RemoveSpace>0.125in</RemoveSpace></DeviceInfo>";
Is changed to:
string RenderFormat = "HTML4.0";
string DeviceInfo = null;
Error Message :
rrRenderingError
400
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException
was thrown.
http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings.resources.Strings&EvtID=rrRenderingError&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=8.00
Microsoft SQL Server Reporting Services
8.00.878.00
127
OsIndependent
1033
Microsoft.ReportingServices.Processing
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException
was thrown.
Microsoft.ReportingServices.ExcelRendering
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException
was thrown.
Microsoft.ReportingServices.ExcelRendering
Object reference not set to an instance of an object.Hmm, no takers yet ;)
Will it help if i post my rdl definition?
It is an OLAP grid with drill down and filters.
Am an trying to render with parameters of "CA" and "Drink" for Param0
and Param1 respectively.
The HTML file is produced, but still .Render() with Excel as the type
crashes.
I hope posting this XML doesn't mess the board around too much.
Any help gratefully received
Thanks
Colin
<?xml version="1.0"?>
<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
xmlns:rd="<GridSpacing">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner"><GridSpacing
xmlns="0.25cm</GridSpacing><RightMargin>1in</RightMargin><Body><ReportItems><Matrix">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">0.25cm</GridSpacing><RightMargin>1in</RightMargin><Body><ReportItems><Matrix
Name="Martix0"><Corner><ReportItems><Textbox
Name="TextBox0"><Style><BorderStyle><Default>Solid</Default><Top>None</Top><Left>None</Left></BorderStyle><PaddingTop>2pt</PaddingTop><PaddingBottom>2pt</PaddingBottom><PaddingLeft>2pt</PaddingLeft><PaddingRight>2pt</PaddingRight><FontFamily>Tahoma</FontFamily><FontSize>26pt</FontSize><Color>DarkBlue</Color></Style><Value>Test
with filters</Value><CanGrow>true</CanGrow><ZIndex>0</ZIndex></Textbox></ReportItems></Corner><Style></Style><MatrixRows><MatrixRow><MatrixCells><MatrixCell><ReportItems><Textbox
Name="TextBox1"><Style><BorderStyle><Default>Solid</Default></BorderStyle><PaddingTop>2pt</PaddingTop><PaddingBottom>2pt</PaddingBottom><PaddingLeft>2pt</PaddingLeft><PaddingRight>2pt</PaddingRight><FontFamily>Tahoma</FontFamily><BackgroundColor>AliceBlue</BackgroundColor><TextAlign>Right</TextAlign><Format>C0</Format></Style><Value>=Sum(Fields!Measure0.Value)</Value><CanGrow>true</CanGrow><ZIndex
1</ZIndex></Textbox></ReportItems></MatrixCell></MatrixCells><Height>0.25in</Height></MatrixRow></MatrixRows><MatrixColumns><MatrixColumn><Width>0.875in</Width></MatrixColumn></MatrixColumns><DataSetName>DataQuery</DataSetName><ColumnGroupings><ColumnGrouping><DynamicColumns><Grouping
Name="ColGrp0"><GroupExpressions><GroupExpression>=Fields!ColLvl0.Value</GroupExpression></GroupExpressions></Grouping><ReportItems><Textbox
Name="ColTxtBox0"><Style><BorderStyle><Default>Solid</Default></BorderStyle><PaddingTop>2pt</PaddingTop><PaddingBottom>2pt</PaddingBottom><PaddingLeft>2pt</PaddingLeft><PaddingRight>2pt</PaddingRight><FontFamily>Tahoma</FontFamily><Color>White</Color><BackgroundColor>SteelBlue</BackgroundColor><TextAlign>Center</TextAlign></Style><Value>=Fields!ColLvl0.Value</Value><CanGrow>true</CanGrow><ZIndex>2
/ZIndex></Textbox></ReportItems></DynamicColumns><Height>0.25in</Height></ColumnGrouping><ColumnGrouping><DynamicColumns><Grouping
Name="ColGrp1"><GroupExpressions><GroupExpression>=Fields!ColLvl1.Value</GroupExpression></GroupExpressions></Grouping><Visibility><ToggleItem>ColTxtBox0</ToggleItem><Hidden>true</Hidden></Visibility><ReportItems><Textbox
Name="ColTxtBox1"><Style><BorderStyle><Default>Solid</Default></BorderStyle><PaddingTop>2pt</PaddingTop><PaddingBottom>2pt</PaddingBottom><PaddingLeft>2pt</PaddingLeft><PaddingRight>2pt</PaddingRight><FontFamily>Tahoma</FontFamily><Color>White</Color><BackgroundColor>SteelBlue</BackgroundColor><TextAlign>Center</TextAlign></Style><Value>=Fields!ColLvl1.Value</Value><CanGrow>true</CanGrow><ZIndex>3
/ZIndex></Textbox></ReportItems></DynamicColumns><Height>0.25in</Height></ColumnGrouping><ColumnGrouping><DynamicColumns><Grouping
Name="ColGrp2"><GroupExpressions><GroupExpression>=Fields!ColLvl2.Value</GroupExpression></GroupExpressions></Grouping><Visibility><ToggleItem>ColTxtBox1</ToggleItem><Hidden>true</Hidden></Visibility><ReportItems><Textbox
Name="ColTxtBox2"><Style><BorderStyle><Default>Solid</Default></BorderStyle><PaddingTop>2pt</PaddingTop><PaddingBottom>2pt</PaddingBottom><PaddingLeft>2pt</PaddingLeft><PaddingRight>2pt</PaddingRight><FontFamily>Tahoma</FontFamily><Color>White</Color><BackgroundColor>SteelBlue</BackgroundColor><TextAlign>Center</TextAlign></Style><Value>=Fields!ColLvl2.Value</Value><CanGrow>true</CanGrow><ZIndex>4
/ZIndex></Textbox></ReportItems></DynamicColumns><Height>0.25in</Height></ColumnGrouping><ColumnGrouping><DynamicColumns><Grouping
Name="ColGrp3"><GroupExpressions><GroupExpression>=Fields!ColLvl3.Value</GroupExpression></GroupExpressions></Grouping><Visibility><ToggleItem>ColTxtBox2</ToggleItem><Hidden>true</Hidden></Visibility><ReportItems><Textbox
Name="ColTxtBox3"><Style><BorderStyle><Default>Solid</Default></BorderStyle><PaddingTop>2pt</PaddingTop><PaddingBottom>2pt</PaddingBottom><PaddingLeft>2pt</PaddingLeft><PaddingRight>2pt</PaddingRight><FontFamily>Tahoma</FontFamily><Color>White</Color><BackgroundColor>SteelBlue</BackgroundColor><TextAlign>Center</TextAlign></Style><Value>=Fields!ColLvl3.Value</Value><CanGrow>true</CanGrow><ZIndex>5
/ZIndex></Textbox></ReportItems></DynamicColumns><Height>0.25in</Height></ColumnGrouping><ColumnGrouping><DynamicColumns><Grouping
Name="ColGrp4"><GroupExpressions><GroupExpression>=Fields!ColLvl4.Value</GroupExpression></GroupExpressions></Grouping><Visibility><ToggleItem>ColTxtBox3</ToggleItem><Hidden>true</Hidden></Visibility><ReportItems><Textbox
Name="ColTxtBox4"><Style><BorderStyle><Default>Solid</Default></BorderStyle><PaddingTop>2pt</PaddingTop><PaddingBottom>2pt</PaddingBottom><PaddingLeft>2pt</PaddingLeft><PaddingRight>2pt</PaddingRight><FontFamily>Tahoma</FontFamily><Color>White</Color><BackgroundColor>SteelBlue</BackgroundColor><TextAlign>Center</TextAlign></Style><Value>=Fields!ColLvl4.Value</Value><CanGrow>true</CanGrow><ZIndex>6
/ZIndex></Textbox></ReportItems></DynamicColumns><Height>0.25in</Height></ColumnGrouping><ColumnGrouping><Height>0.25in</Height><StaticColumns><StaticColumn><ReportItems><Textbox
Name="TextBox7"><Style><BorderStyle><Default>Solid</Default></BorderStyle><PaddingTop>2pt</PaddingTop><PaddingBottom>2pt</PaddingBottom><PaddingLeft>2pt</PaddingLeft><PaddingRight>2pt</PaddingRight><FontFamily>Tahoma</FontFamily><Color>White</Color><BackgroundColor>SteelBlue</BackgroundColor><TextAlign>Center</TextAlign></Style><Value>Unit
Sales</Value><CanGrow>true</CanGrow><ZIndex>7</ZIndex></Textbox></ReportItems></StaticColumn></StaticColumns></ColumnGrouping></ColumnGroupings><Filters><Filter><FilterExpression>=Fields!RowLvl1.Value</FilterExpression><Operator>Equal</Operator><FilterValues><FilterValue>=Parameters!Param0.Value</FilterValue></FilterValues></Filter><Filter><FilterExpression>=Fields!ColLvl0.Value</FilterExpression>
Operator>Equal</Operator><FilterValues><FilterValue>=Parameters!Param1.Value</FilterValue></FilterValues></Filter></Filters><RowGroupings><RowGrouping><DynamicRows><Grouping
Name="RowGrp0"><GroupExpressions><GroupExpression>=Fields!RowLvl0.Value</GroupExpression></GroupExpressions></Grouping><ReportItems><Textbox
Name="RowTxtBox0"><Style><BorderStyle><Default>Solid</Default></BorderStyle><PaddingTop>2pt</PaddingTop><PaddingBottom>2pt</PaddingBottom><PaddingLeft>2pt</PaddingLeft><PaddingRight>2pt</PaddingRight><FontFamily>Tahoma</FontFamily><Color>White</Color><BackgroundColor>SteelBlue</BackgroundColor><TextAlign>Left</TextAlign></Style><Value>=Fields!RowLvl0.Value</Value><CanGrow>true</CanGrow><ZIndex>8</
Index></Textbox></ReportItems><Subtotal><ReportItems><Textbox
Name="TextBox9"><Style><BorderStyle><Default>Solid</Default></BorderStyle><PaddingTop>2pt</PaddingTop><PaddingBottom>2pt</PaddingBottom><PaddingLeft>2pt</PaddingLeft><PaddingRight>2pt</PaddingRight><FontFamily>Tahoma</FontFamily><Color>SkyBlue</Color><BackgroundColor>SteelBlue</BackgroundColor><TextAlign>Left</TextAlign></Style><Value>Subtotal</Value><CanGrow>true</CanGrow><ZIndex>9</ZIndex></Text
ox></ReportItems></Subtotal></DynamicRows><Width>0.875in</Width></RowGrouping><RowGrouping><DynamicRows><Grouping
Name="RowGrp1"><GroupExpressions><GroupExpression>=Fields!RowLvl1.Value</GroupExpression></GroupExpressions></Grouping><Visibility><ToggleItem>RowTxtBox0</ToggleItem><Hidden>true</Hidden></Visibility><ReportItems><Textbox
Name="RowTxtBox1"><Style><BorderStyle><Default>Solid</Default></BorderStyle><PaddingTop>2pt</PaddingTop><PaddingBottom>2pt</PaddingBottom><PaddingLeft>2pt</PaddingLeft><PaddingRight>2pt</PaddingRight><FontFamily>Tahoma</FontFamily><Color>White</Color><BackgroundColor>SteelBlue</BackgroundColor><TextAlign>Left</TextAlign></Style><Value>=Fields!RowLvl1.Value</Value><CanGrow>true</CanGrow><ZIndex>10<
ZIndex></Textbox></ReportItems><Subtotal><ReportItems><Textbox
Name="TextBox11"><Style><BorderStyle><Default>Solid</Default></BorderStyle><PaddingTop>2pt</PaddingTop><PaddingBottom>2pt</PaddingBottom><PaddingLeft>2pt</PaddingLeft><PaddingRight>2pt</PaddingRight><FontFamily>Tahoma</FontFamily><Color>SkyBlue</Color><BackgroundColor>SteelBlue</BackgroundColor><TextAlign>Left</TextAlign></Style><Value>Subtotal</Value><CanGrow>true</CanGrow><ZIndex>11</ZIndex></Te
tbox></ReportItems></Subtotal></DynamicRows><Width>0.875in</Width></RowGrouping><RowGrouping><DynamicRows><Grouping
Name="RowGrp2"><GroupExpressions><GroupExpression>=Fields!RowLvl2.Value</GroupExpression></GroupExpressions></Grouping><Visibility><ToggleItem>RowTxtBox1</ToggleItem><Hidden>true</Hidden></Visibility><ReportItems><Textbox
Name="RowTxtBox2"><Style><BorderStyle><Default>Solid</Default></BorderStyle><PaddingTop>2pt</PaddingTop><PaddingBottom>2pt</PaddingBottom><PaddingLeft>2pt</PaddingLeft><PaddingRight>2pt</PaddingRight><FontFamily>Tahoma</FontFamily><Color>White</Color><BackgroundColor>SteelBlue</BackgroundColor><TextAlign>Left</TextAlign></Style><Value>=Fields!RowLvl2.Value</Value><CanGrow>true</CanGrow><ZIndex>12<
ZIndex></Textbox></ReportItems><Subtotal><ReportItems><Textbox
Name="TextBox13"><Style><BorderStyle><Default>Solid</Default></BorderStyle><PaddingTop>2pt</PaddingTop><PaddingBottom>2pt</PaddingBottom><PaddingLeft>2pt</PaddingLeft><PaddingRight>2pt</PaddingRight><FontFamily>Tahoma</FontFamily><Color>SkyBlue</Color><BackgroundColor>SteelBlue</BackgroundColor><TextAlign>Left</TextAlign></Style><Value>Subtotal</Value><CanGrow>true</CanGrow><ZIndex>13</ZIndex></Te
tbox></ReportItems></Subtotal></DynamicRows><Width>0.875in</Width></RowGrouping></RowGroupings></Matrix></ReportItems><Style></Style><Height>1.25in</Height><ColumnSpacing>1cm</ColumnSpacing></Body><TopMargin>1in</TopMargin><DataSources><DataSource
Name="DataSource1"><DataSourceID
xmlns="B7BD158F-94EE-41E4-BA21-CDC54DBA3983</DataSourceID><ConnectionProperties><DataProvider>OLEDB</DataProvider><ConnectString>Provider=MSOLAP.2;Client">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">B7BD158F-94EE-41E4-BA21-CDC54DBA3983</DataSourceID><ConnectionProperties><DataProvider>OLEDB</DataProvider><ConnectString>Provider=MSOLAP.2;Client
Cache Size=25;Data Source=iis-covertonxp;Initial Catalog=FoodMart
2000;Auto Synch Period=10000</ConnectString><IntegratedSecurity>true</IntegratedSecurity></ConnectionProperties></DataSource></DataSources><Width>7.125in</Width><DataSets><DataSet
Name="DataQuery"><Fields><Field
Name="ColLvl0"><DataField>[Product].[Product
Family].[MEMBER_CAPTION]</DataField><TypeName
xmlns="System.String</TypeName></Field><Field">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">System.String</TypeName></Field><Field
Name="ColLvl1"><DataField>[Product].[Product
Department].[MEMBER_CAPTION]</DataField><TypeName
xmlns="System.String</TypeName></Field><Field">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">System.String</TypeName></Field><Field
Name="ColLvl2"><DataField>[Product].[Product
Category].[MEMBER_CAPTION]</DataField><TypeName
xmlns="System.String</TypeName></Field><Field">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">System.String</TypeName></Field><Field
Name="ColLvl3"><DataField>[Product].[Product
Subcategory].[MEMBER_CAPTION]</DataField><TypeName
xmlns="System.String</TypeName></Field><Field">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">System.String</TypeName></Field><Field
Name="ColLvl4"><DataField>[Product].[Brand
Name].[MEMBER_CAPTION]</DataField><TypeName
xmlns="System.String</TypeName></Field><Field">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">System.String</TypeName></Field><Field
Name="RowLvl0"><DataField>[Customers].[Country].[MEMBER_CAPTION]</DataField><TypeName
xmlns="System.String</TypeName></Field><Field">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">System.String</TypeName></Field><Field
Name="RowLvl1"><DataField>[Customers].[State
Province].[MEMBER_CAPTION]</DataField><TypeName
xmlns="System.String</TypeName></Field><Field">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">System.String</TypeName></Field><Field
Name="RowLvl2"><DataField>[Customers].[City].[MEMBER_CAPTION]</DataField><TypeName
xmlns="System.String</TypeName></Field><Field">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">System.String</TypeName></Field><Field
Name="Measure0"><DataField>[Measures].[Unit
Sales]</DataField><TypeName
xmlns="System.Object</TypeName></Field></Fields><Query><DataSourceName>DataSource1</DataSourceName><CommandText>">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">System.Object</TypeName></Field></Fields><Query><DataSourceName>DataSource1</DataSourceName><CommandText>
SELECT
{[Measures].[Unit Sales]} on columns ,
{[Customers].[City].members} on rows ,
{[Product].[Brand Name].members} on pages
FROM
[Sales]
CELL PROPERTIES
VALUE, FORMATTED_VALUE, FORMAT_STRING, FORE_COLOR, BACK_COLOR,
FONT_FLAGS</CommandText></Query></DataSet><DataSet
Name="ParameterQuery0"><Fields><Field
Name="ParaLevelField0"><DataField>[Customers].[State
Province].[MEMBER_CAPTION]</DataField><TypeName
xmlns="System.String</TypeName></Field><Field">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">System.String</TypeName></Field><Field
Name="ParamNullField0"><DataField>[Measures].[NullColumn]</DataField><TypeName
xmlns="System.Object</TypeName></Field></Fields><Query><DataSourceName>DataSource1</DataSourceName><CommandText>WITH">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">System.Object</TypeName></Field></Fields><Query><DataSourceName>DataSource1</DataSourceName><CommandText>WITH
MEMBER Measures.NullColumn AS 'Null' SELECT {Measures.NullColumn} ON
COLUMNS, { [Customers].[State Province].Members } ON ROWS From
Sales</CommandText></Query></DataSet><DataSet
Name="ParameterQuery1"><Fields><Field
Name="ParaLevelField1"><DataField>[Product].[Product
Family].[MEMBER_CAPTION]</DataField><TypeName
xmlns="System.String</TypeName></Field><Field">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">System.String</TypeName></Field><Field
Name="ParamNullField1"><DataField>[Measures].[NullColumn]</DataField><TypeName
xmlns="System.Object</TypeName></Field></Fields><Query><DataSourceName>DataSource1</DataSourceName><CommandText>WITH">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">System.Object</TypeName></Field></Fields><Query><DataSourceName>DataSource1</DataSourceName><CommandText>WITH
MEMBER Measures.NullColumn AS 'Null' SELECT {Measures.NullColumn} ON
COLUMNS, { [Product].[Product Family].Members } ON ROWS From
Sales</CommandText></Query></DataSet></DataSets><LeftMargin>1in</LeftMargin><SnapToGrid
xmlns="true</SnapToGrid><PageHeight>12in</PageHeight><DrawGrid">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">true</SnapToGrid><PageHeight>12in</PageHeight><DrawGrid
xmlns="true</DrawGrid><PageWidth>8in</PageWidth><ReportID">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">true</DrawGrid><PageWidth>8in</PageWidth><ReportID
xmlns="7B383EFA-88B0-41CB-987B-3F766C0F4776</ReportID><BottomMargin>1in</BottomMargin><ReportParameters><ReportParameter">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">7B383EFA-88B0-41CB-987B-3F766C0F4776</ReportID><BottomMargin>1in</BottomMargin><ReportParameters><ReportParameter
Name="Param0"><DataType>String</DataType><DefaultValue><DataSetReference><DataSetName>ParameterQuery0</DataSetName><ValueField>ParaLevelField0</ValueField></DataSetReference></DefaultValue><Prompt>State
Province</Prompt><ValidValues><DataSetReference><DataSetName>ParameterQuery0</DataSetName><ValueField>ParaLevelField0</ValueField><LabelField>ParaLevelField0</LabelField></DataSetReference></ValidValues></ReportParameter><ReportParameter
Name="Param1"><DataType>String</DataType><DefaultValue><DataSetReference><DataSetName>ParameterQuery1</DataSetName><ValueField>ParaLevelField1</ValueField></DataSetReference></DefaultValue><Prompt>Product
Family</Prompt><ValidValues><DataSetReference><DataSetName>ParameterQuery1</DataSetName><ValueField>ParaLevelField1</ValueField><LabelField>ParaLevelField1</LabelField></DataSetReference></ValidValues></ReportParameter></ReportParameters></Report>

Excel rendering 65536 row limit?

I am experiencing a problem when we are rendering a large report in Excel
format, I get the following error thrown by the ExcelRenderer:
Number of rows in the excel sheet exceeded the limit of 65536 rows.
Has anyone seen this issue? I searched this forum and the SP2 docs.
Thanks,
MikeSilly question: does the report actually consist of more than 65536 rows?
Mike G.
"Mike Sandwick" <MikeSandwick@.discussions.microsoft.com> wrote in message
news:641C0BE6-689C-42E8-BF13-724232C11278@.microsoft.com...
>I am experiencing a problem when we are rendering a large report in Excel
> format, I get the following error thrown by the ExcelRenderer:
> Number of rows in the excel sheet exceeded the limit of 65536 rows.
> Has anyone seen this issue? I searched this forum and the SP2 docs.
> Thanks,
> Mike|||Thats an Excel limitation - it may have been increased with 2003
"Mike G." wrote:
> Silly question: does the report actually consist of more than 65536 rows?
> Mike G.
> "Mike Sandwick" <MikeSandwick@.discussions.microsoft.com> wrote in message
> news:641C0BE6-689C-42E8-BF13-724232C11278@.microsoft.com...
> >I am experiencing a problem when we are rendering a large report in Excel
> > format, I get the following error thrown by the ExcelRenderer:
> >
> > Number of rows in the excel sheet exceeded the limit of 65536 rows.
> >
> > Has anyone seen this issue? I searched this forum and the SP2 docs.
> >
> > Thanks,
> > Mike
>
>|||That is a limit in Excel, usually we have to have clients use a csv files
and load them into Access.
"Espo" <Espo@.discussions.microsoft.com> wrote in message
news:B29123AD-7272-41F9-8D21-5915F7AA57A0@.microsoft.com...
> Thats an Excel limitation - it may have been increased with 2003
> "Mike G." wrote:
> > Silly question: does the report actually consist of more than 65536
rows?
> >
> > Mike G.
> >
> > "Mike Sandwick" <MikeSandwick@.discussions.microsoft.com> wrote in
message
> > news:641C0BE6-689C-42E8-BF13-724232C11278@.microsoft.com...
> > >I am experiencing a problem when we are rendering a large report in
Excel
> > > format, I get the following error thrown by the ExcelRenderer:
> > >
> > > Number of rows in the excel sheet exceeded the limit of 65536 rows.
> > >
> > > Has anyone seen this issue? I searched this forum and the SP2 docs.
> > >
> > > Thanks,
> > > Mike
> >
> >
> >

Excel Rendering - Urgent

Hello,
I have a fairly simple report (with a lot of columns) that I'm trying to
export to Excel. Everytime I do this, I get the following error:
"Excel Rendering Extension: Width of excel cell in the excel sheet exceeded
the maximum limit of 1726.5 Points."
I know that 1726.5 equates to 255 characters in a column, but when I export
to CSV and check the lengths of every value, none of them reach 255.
Is there a workaround to this bug?
Any guidance on this matter would be much apprecited.
Best Regards,
Benjamin Pierce
Open Text CorporationThe experience I have is when the report is empty and you want to render it
to Excel, RS will combine all the columns into one single cell in Excel. One
way to solve this is to shrink the width of all the columns so that the total
length is less than 255 characters.
"Benjamin Pierce" wrote:
> Well, after much trial and error I found the problem.
> I had two tables. A summary table then a "data dump" below that. On the
> first table, I had the "PageBreakAtEnd" property set to true. When I
> changed it to False, the error went away.
> As a workaround, I attempted to set the "PageBreakAtStart" property of the
> second table to true, but this re-introduced the error.
> @. Microsoft: Is this a known bug? I'm attaching my RDL for further
> analysis. It seems like a fairly serious flaw in the Excel Renderer.
> Please let me know if you need more info.
>
> Regards,
> Benjamin Pierce
> Open Text Corporation
>
>
> "Benjamin Pierce" <bpierce@.opentext.com> wrote in message
> news:eRd9aCymEHA.3868@.TK2MSFTNGP11.phx.gbl...
> > Hello,
> >
> > I have a fairly simple report (with a lot of columns) that I'm trying to
> > export to Excel. Everytime I do this, I get the following error:
> >
> > "Excel Rendering Extension: Width of excel cell in the excel sheet
> exceeded
> > the maximum limit of 1726.5 Points."
> >
> > I know that 1726.5 equates to 255 characters in a column, but when I
> export
> > to CSV and check the lengths of every value, none of them reach 255.
> >
> > Is there a workaround to this bug?
> >
> > Any guidance on this matter would be much apprecited.
> >
> >
> >
> > Best Regards,
> >
> > Benjamin Pierce
> > Open Text Corporation
> >
> >
> >
>
>
>|||The fix will be available in the next service pack (SP2).
You may also contact Microsoft Product Support Services. See
http://support.microsoft.com/default.aspx?pr=cntactms&style=home. A hotfix
for the issue is available. The KB article (883501) should be available
soon.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Benjamin Pierce" <bpierce@.opentext.com> wrote in message
news:eRd9aCymEHA.3868@.TK2MSFTNGP11.phx.gbl...
> Hello,
> I have a fairly simple report (with a lot of columns) that I'm trying to
> export to Excel. Everytime I do this, I get the following error:
> "Excel Rendering Extension: Width of excel cell in the excel sheet
exceeded
> the maximum limit of 1726.5 Points."
> I know that 1726.5 equates to 255 characters in a column, but when I
export
> to CSV and check the lengths of every value, none of them reach 255.
> Is there a workaround to this bug?
> Any guidance on this matter would be much apprecited.
>
> Best Regards,
> Benjamin Pierce
> Open Text Corporation
>
>|||This patch appears to fix the stated problem, but creates another.
This is not a catastrophe; I will structure the report differently to work
around the problem, but I thought RS Engineering might want to hear about it.
The report contains a table followed by a textbox. One of the cells in the
table contains a formula like this:
=ReportItems!TextBoxInThisTable.Value *
ReportItems!TextBoxOnTheSecondPage.Value
This is rendered properly within the report designer and to excel. In
excel, the table data and the standalone textbox are rendered correctly and
the cell containing the formula is calculated correctly. The excel version
retains the formula which something like: _123 * _456.
So far so good.
The problem arises when I define a PageBreakAfter attribute on the table.
Before applying the hotfix, when I attempted to save as excel, report
designer generated the error as described in kb883501: "Excel Rendering
Extension : Width of excel cell in the excel sheet exceeded the maximum limit
of 1726.5 Points."
After the hotfix, the report designer saves the file, but the resulting file
contains a fatal flaw:
The cell containing the formula simply displays the value contained in
ReportItems!TextBoxInThisTable. When I click on the offending cell to view
the formula, Excel crashes with this signature:
AppName: excel.exe AppVer: 11.0.6355.0 AppStamp:40aa979f
ModName: excel.exe ModVer: 11.0.6355.0 ModStamp:40aa979f
fDebug: 0 Offset: 0010be7e
My guess is that this is related to the fact that Excel has always disliked
formulae that refer to cells in other sheets, though there are ways of
"tricking it" into working.
Cheers,
Jeff Gilbert|||I've created a simple rdl which reproduces the problem. It can be found
attached to SRX050121600563, or just let me know and I can provide it.
-Jeff|||Does this SP need to be applied to the Report Server as well or simply on
workstations developing?
"Robert Bruckner [MSFT]" wrote:
> The fix will be available in the next service pack (SP2).
> You may also contact Microsoft Product Support Services. See
> http://support.microsoft.com/default.aspx?pr=cntactms&style=home. A hotfix
> for the issue is available. The KB article (883501) should be available
> soon.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Benjamin Pierce" <bpierce@.opentext.com> wrote in message
> news:eRd9aCymEHA.3868@.TK2MSFTNGP11.phx.gbl...
> > Hello,
> >
> > I have a fairly simple report (with a lot of columns) that I'm trying to
> > export to Excel. Everytime I do this, I get the following error:
> >
> > "Excel Rendering Extension: Width of excel cell in the excel sheet
> exceeded
> > the maximum limit of 1726.5 Points."
> >
> > I know that 1726.5 equates to 255 characters in a column, but when I
> export
> > to CSV and check the lengths of every value, none of them reach 255.
> >
> > Is there a workaround to this bug?
> >
> > Any guidance on this matter would be much apprecited.
> >
> >
> >
> > Best Regards,
> >
> > Benjamin Pierce
> > Open Text Corporation
> >
> >
> >
>
>|||It needs to be applied on the report server also.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:1B570DFA-5592-4557-914A-740474FBBFDF@.microsoft.com...
> Does this SP need to be applied to the Report Server as well or simply on
> workstations developing?
> "Robert Bruckner [MSFT]" wrote:
>> The fix will be available in the next service pack (SP2).
>> You may also contact Microsoft Product Support Services. See
>> http://support.microsoft.com/default.aspx?pr=cntactms&style=home. A
>> hotfix
>> for the issue is available. The KB article (883501) should be available
>> soon.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Benjamin Pierce" <bpierce@.opentext.com> wrote in message
>> news:eRd9aCymEHA.3868@.TK2MSFTNGP11.phx.gbl...
>> > Hello,
>> >
>> > I have a fairly simple report (with a lot of columns) that I'm trying
>> > to
>> > export to Excel. Everytime I do this, I get the following error:
>> >
>> > "Excel Rendering Extension: Width of excel cell in the excel sheet
>> exceeded
>> > the maximum limit of 1726.5 Points."
>> >
>> > I know that 1726.5 equates to 255 characters in a column, but when I
>> export
>> > to CSV and check the lengths of every value, none of them reach 255.
>> >
>> > Is there a workaround to this bug?
>> >
>> > Any guidance on this matter would be much apprecited.
>> >
>> >
>> >
>> > Best Regards,
>> >
>> > Benjamin Pierce
>> > Open Text Corporation
>> >
>> >
>> >
>>

Excel rendering - MIME is'n suitable!

Hi,
I have problems openning rendered excel reports. I'm trying to view my
report in my machine (P4 2.4 mhz, 1 gb ddr) and it takes 15 minutes to open.
The report has 4000 rows.
I've been trying to find this problem's cause, and I finally concluded that
the issue is bothering me is the format in which the RS is rendering the
report. It renders like a MIME file.
After openning the excel file, and choose to "save as" an .xls file, the
saved report size is 1.4 mb (before doing this, was 19 mb). This file now
takes less than a minute to get openned in Excel, and is identical to the RS
rendered file.
So, the question is: how can I do in order to the RS render my report to a
"real" Excel file'
Thx,
Gastón.-Hi Gastón,
To the best of my knowledge, this issue has been addressed in RS SP1. Since
SP2 has been released, I suggest that you install it and then test to see
if the problem still exists. To download RS SP2, visit the following
Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyId=502C0D89-1308-4662-
8F58-CEC55EF1235B&displaylang=en
Feel free to let me know if you have any updates.
Sincerely,
William Wang
Microsoft Online Partner 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.|||It worked!!
Thanks a lot.
Gastón.-
"William Wang[MSFT]" <v-rxwang@.online.microsoft.com> wrote in message
news:SIe8PklkFHA.3672@.TK2MSFTNGXA01.phx.gbl...
> Hi Gastón,
> To the best of my knowledge, this issue has been addressed in RS SP1.
> Since
> SP2 has been released, I suggest that you install it and then test to see
> if the problem still exists. To download RS SP2, visit the following
> Microsoft Web site:
> http://www.microsoft.com/downloads/details.aspx?FamilyId=502C0D89-1308-4662-
> 8F58-CEC55EF1235B&displaylang=en
> Feel free to let me know if you have any updates.
> Sincerely,
> William Wang
> Microsoft Online Partner 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.
>

Excel rendering - merged columns etc.

Hi guys,

i have a client who is dissatisfied with the merged columns and rows produced when SSRS renders to Excel, it prevents them from easily copying and pasting data into another workbook.

Is there going to be any work done in this area of the product in the near future? My understanding is that this 'issue' has been around for quite some time, and shortly after the SSRS2005 RTM release the team were going to look at tidying up the Excel rendering. Can anyone from MS make an official comment on this?

Thanks,

sluggy

Hello,

This is a well known issue that people often encounter when rendering to Excel. First, I suggest reading this blog post which describes the problem and suggests several ways to reduce cell merging:

http://blogs.msdn.com/chrisbal/archive/2006/07/08/659545.aspx

There will be some improvement in this area in the next major release of Reporting Services. We have made some refinements to the renderer to prevent any adverse merging that is a result of internal rounding issues. This means that overall you should see a reduction in the number of merged cells, but you will still need to proactively make sure that your report items align properly as described in the referenced blog article.

Best regards,
Chris

|||

Chris Baldwin - MSFT wrote:

There will be some improvement in this area in the next major release of Reporting Services. We have made some refinements to the renderer to prevent any adverse merging that is a result of internal rounding issues.

Thanks Chris, that was the answer i was after, i can now tell the customer with some certainty that there will be an improvement in the future. In my particular case, i don't care about the header of the reports, i just care about the merged cells in the data area; i have seen cases where one table column spans three excel columns (merged into one), but when those excel columns are unmerged the data in the first few rows could be in colunmn 3 and for the rest of the rows it will be in column 2, with column 1 containing the column title - merged cells would be easier to live with if the data (and title) was in consistent columns once unmerged.

Thanks for you answer :)

sluggy

Excel rendering - Merged cells issue

Hi,
My rendered Excel reports have lot of merged cells (because of the layout I
made in the designer). Therefore when I open it, the excel takes lot of
minutes to open. So the question is: what can I do in order to avoid having
merged cells in the rendered excel file.
TIA,
Gastón.-
PS: I've opened the excel file, unmerged all cells, save, reopen it, and the
problem disapear.Are you using table or matrix?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Gastón Pírez" <gaspirez@.adinet.com.uy> wrote in message
news:O28R3kekFHA.1948@.TK2MSFTNGP12.phx.gbl...
> Hi,
> My rendered Excel reports have lot of merged cells (because of the layout
> I made in the designer). Therefore when I open it, the excel takes lot of
> minutes to open. So the question is: what can I do in order to avoid
> having merged cells in the rendered excel file.
> TIA,
> Gastón.-
> PS: I've opened the excel file, unmerged all cells, save, reopen it, and
> the problem disapear.
>
>|||I'm using table.
Thx,
Gastón.-
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%23DTU3CfkFHA.576@.TK2MSFTNGP15.phx.gbl...
> Are you using table or matrix?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Gastón Pírez" <gaspirez@.adinet.com.uy> wrote in message
> news:O28R3kekFHA.1948@.TK2MSFTNGP12.phx.gbl...
>> Hi,
>> My rendered Excel reports have lot of merged cells (because of the layout
>> I made in the designer). Therefore when I open it, the excel takes lot of
>> minutes to open. So the question is: what can I do in order to avoid
>> having merged cells in the rendered excel file.
>> TIA,
>> Gastón.-
>> PS: I've opened the excel file, unmerged all cells, save, reopen it, and
>> the problem disapear.
>>
>|||OK, here is what I did. Do not have any textboxes above your table. Instead,
add additional header rows. You can merge cells together, put in text and
center so usually I could still get it where it looked similar. For some
reason even though you are merging cells it does it differently when
exporting to Excel. After doing this you will be able to select the data
region and sort the data.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Gastón Pírez" <paytrue@.newsgroup.nospam> wrote in message
news:uyDMNJfkFHA.1464@.TK2MSFTNGP14.phx.gbl...
> I'm using table.
> Thx,
> Gastón.-
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:%23DTU3CfkFHA.576@.TK2MSFTNGP15.phx.gbl...
>> Are you using table or matrix?
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Gastón Pírez" <gaspirez@.adinet.com.uy> wrote in message
>> news:O28R3kekFHA.1948@.TK2MSFTNGP12.phx.gbl...
>> Hi,
>> My rendered Excel reports have lot of merged cells (because of the
>> layout I made in the designer). Therefore when I open it, the excel
>> takes lot of minutes to open. So the question is: what can I do in order
>> to avoid having merged cells in the rendered excel file.
>> TIA,
>> Gastón.-
>> PS: I've opened the excel file, unmerged all cells, save, reopen it, and
>> the problem disapear.
>>
>>
>

Excel rendering

Hi, does anyone know if it's possible to dynamically create excel tabs/worksheets possibly via RS web service library or some other method.
Thanks in advance,
JimNo.
--
Ravi Mumulla (Microsoft)
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jim" <Jim@.discussions.microsoft.com> wrote in message
news:B37D944C-B806-48EB-A991-905E9405A8D9@.microsoft.com...
> Hi, does anyone know if it's possible to dynamically create excel
tabs/worksheets possibly via RS web service library or some other method.
> Thanks in advance,
> Jim|||Hi,
when i export report in excel, sometimes document map color in excel comes
blue and sometimes it comes blue. Why is it so?. Is this a RDL issue or excel
issue? please help me out. My email id is kiran_nandedkar@.rediffmail.com
Thanks in advance

Excel Render - Damage to file was extensive and repairs not possible

I am posting this in hopes of saving others from my fate of searching hours...
days...months for a resolution to an error when rendering to excel. I have a
detailed report of tables and graphs that accepts multiple parameters. For
certain parameter values the report would not render to excel...saying that
damage to the files was too extensive. This would render in all other
formats with no problem.
I searched for a long time for resolution...maybe it was my mdx data... maybe
server install problem...and I wasted a lot of time.
Turns out that the objects on the report were too close to one another. I
stacked sections of the report on top of each other with very little or no
space between the sections (rectangles). This was not a problem for some
parameter values because the report sections did not require expansion.
However, certain parameter values forced an expansion of sections. I guess
that the excel render engine got confused when the sections expanded and
maybe? overlapped.
So I've learned my lesson on this one...make sure you provide some space
between your objects on your report. Even if you don't want the extra space
on your reports...avoid headaches...space your objects.
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200507/1Thank you for sharing this info.
"William Nichols via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:5143C47BD2275@.SQLMonster.com...
>I am posting this in hopes of saving others from my fate of searching
>hours...
> days...months for a resolution to an error when rendering to excel. I
> have a
> detailed report of tables and graphs that accepts multiple parameters.
> For
> certain parameter values the report would not render to excel...saying
> that
> damage to the files was too extensive. This would render in all other
> formats with no problem.
> I searched for a long time for resolution...maybe it was my mdx data...
> maybe
> server install problem...and I wasted a lot of time.
> Turns out that the objects on the report were too close to one another. I
> stacked sections of the report on top of each other with very little or no
> space between the sections (rectangles). This was not a problem for some
> parameter values because the report sections did not require expansion.
> However, certain parameter values forced an expansion of sections. I
> guess
> that the excel render engine got confused when the sections expanded and
> maybe? overlapped.
> So I've learned my lesson on this one...make sure you provide some space
> between your objects on your report. Even if you don't want the extra
> space
> on your reports...avoid headaches...space your objects.|||I had the same problem, some times even with objects spaced. In all cases it
was caused by the chart. I had to change at least one property of the chart
to solve the problem. In most cases changing Y-axis format from N0 to 0
(which produces the same result) fixed report.
Thanks,
ID
"William Nichols via SQLMonster.com" wrote:
> I am posting this in hopes of saving others from my fate of searching hours...
> days...months for a resolution to an error when rendering to excel. I have a
> detailed report of tables and graphs that accepts multiple parameters. For
> certain parameter values the report would not render to excel...saying that
> damage to the files was too extensive. This would render in all other
> formats with no problem.
> I searched for a long time for resolution...maybe it was my mdx data... maybe
> server install problem...and I wasted a lot of time.
> Turns out that the objects on the report were too close to one another. I
> stacked sections of the report on top of each other with very little or no
> space between the sections (rectangles). This was not a problem for some
> parameter values because the report sections did not require expansion.
> However, certain parameter values forced an expansion of sections. I guess
> that the excel render engine got confused when the sections expanded and
> maybe? overlapped.
> So I've learned my lesson on this one...make sure you provide some space
> between your objects on your report. Even if you don't want the extra space
> on your reports...avoid headaches...space your objects.
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200507/1
>|||Following that logic could you just set the properties of the object to not
expand to accomodate contents?
I have encountered this problem w/ no consistency. Typically to resolve the
issue all I do is deploy the report to the report server again w/o changing
anything and it works fine for the same parameters. A couple of the objects
on the report are right next to each other.
Thoughts?
"William Nichols via SQLMonster.com" wrote:
> I am posting this in hopes of saving others from my fate of searching hours...
> days...months for a resolution to an error when rendering to excel. I have a
> detailed report of tables and graphs that accepts multiple parameters. For
> certain parameter values the report would not render to excel...saying that
> damage to the files was too extensive. This would render in all other
> formats with no problem.
> I searched for a long time for resolution...maybe it was my mdx data... maybe
> server install problem...and I wasted a lot of time.
> Turns out that the objects on the report were too close to one another. I
> stacked sections of the report on top of each other with very little or no
> space between the sections (rectangles). This was not a problem for some
> parameter values because the report sections did not require expansion.
> However, certain parameter values forced an expansion of sections. I guess
> that the excel render engine got confused when the sections expanded and
> maybe? overlapped.
> So I've learned my lesson on this one...make sure you provide some space
> between your objects on your report. Even if you don't want the extra space
> on your reports...avoid headaches...space your objects.
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200507/1
>|||Yeah, I use the same technique or redeploying the same report on report
server. And this solves problem.. its strange.. i guess Reports on RS are
getting messed up so deplying the fresh copy brings it back to normal.
Thanks,
Mahesh
"Ben Sullins" wrote:
> Following that logic could you just set the properties of the object to not
> expand to accomodate contents?
> I have encountered this problem w/ no consistency. Typically to resolve the
> issue all I do is deploy the report to the report server again w/o changing
> anything and it works fine for the same parameters. A couple of the objects
> on the report are right next to each other.
> Thoughts?
> "William Nichols via SQLMonster.com" wrote:
> > I am posting this in hopes of saving others from my fate of searching hours...
> > days...months for a resolution to an error when rendering to excel. I have a
> > detailed report of tables and graphs that accepts multiple parameters. For
> > certain parameter values the report would not render to excel...saying that
> > damage to the files was too extensive. This would render in all other
> > formats with no problem.
> >
> > I searched for a long time for resolution...maybe it was my mdx data... maybe
> > server install problem...and I wasted a lot of time.
> >
> > Turns out that the objects on the report were too close to one another. I
> > stacked sections of the report on top of each other with very little or no
> > space between the sections (rectangles). This was not a problem for some
> > parameter values because the report sections did not require expansion.
> > However, certain parameter values forced an expansion of sections. I guess
> > that the excel render engine got confused when the sections expanded and
> > maybe? overlapped.
> >
> > So I've learned my lesson on this one...make sure you provide some space
> > between your objects on your report. Even if you don't want the extra space
> > on your reports...avoid headaches...space your objects.
> >
> >
> > --
> > Message posted via SQLMonster.com
> > http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200507/1
> >|||In my case redeploying the report didn's solve the problem
--
Thanks,
ID
"Mahesh Gaware" wrote:
> Yeah, I use the same technique or redeploying the same report on report
> server. And this solves problem.. its strange.. i guess Reports on RS are
> getting messed up so deplying the fresh copy brings it back to normal.
> Thanks,
> Mahesh
> "Ben Sullins" wrote:
> > Following that logic could you just set the properties of the object to not
> > expand to accomodate contents?
> >
> > I have encountered this problem w/ no consistency. Typically to resolve the
> > issue all I do is deploy the report to the report server again w/o changing
> > anything and it works fine for the same parameters. A couple of the objects
> > on the report are right next to each other.
> >
> > Thoughts?
> >
> > "William Nichols via SQLMonster.com" wrote:
> >
> > > I am posting this in hopes of saving others from my fate of searching hours...
> > > days...months for a resolution to an error when rendering to excel. I have a
> > > detailed report of tables and graphs that accepts multiple parameters. For
> > > certain parameter values the report would not render to excel...saying that
> > > damage to the files was too extensive. This would render in all other
> > > formats with no problem.
> > >
> > > I searched for a long time for resolution...maybe it was my mdx data... maybe
> > > server install problem...and I wasted a lot of time.
> > >
> > > Turns out that the objects on the report were too close to one another. I
> > > stacked sections of the report on top of each other with very little or no
> > > space between the sections (rectangles). This was not a problem for some
> > > parameter values because the report sections did not require expansion.
> > > However, certain parameter values forced an expansion of sections. I guess
> > > that the excel render engine got confused when the sections expanded and
> > > maybe? overlapped.
> > >
> > > So I've learned my lesson on this one...make sure you provide some space
> > > between your objects on your report. Even if you don't want the extra space
> > > on your reports...avoid headaches...space your objects.
> > >
> > >
> > > --
> > > Message posted via SQLMonster.com
> > > http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200507/1
> > >|||To add to my original post. I recieved the error again (but less frequently)
and I think it is related to my charts when certain parameter values are
specified.
Microsoft has a hotfix available ... but they are not distributing online...
http://support.microsoft.com/?kbid=905121
I don't have time to wait a few hours on the phone to get the patch. Anyone
know where we migh tbe able to get this?
exkievan wrote:
>In my case redeploying the report didn's solve the problem
>> Yeah, I use the same technique or redeploying the same report on report
>> server. And this solves problem.. its strange.. i guess Reports on RS are
>[quoted text clipped - 34 lines]
>> > > between your objects on your report. Even if you don't want the extra space
>> > > on your reports...avoid headaches...space your objects.
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200511/1|||I was getting the same error on a report and managed to fix it. One of the
charts had data on the y-axis that was formatted as currency "C" so I changed
it to "#,##0.00" and it fixed the problem. I hope this helps.
"William N via SQLMonster.com" wrote:
> To add to my original post. I recieved the error again (but less frequently)
> and I think it is related to my charts when certain parameter values are
> specified.
> Microsoft has a hotfix available ... but they are not distributing online...
> http://support.microsoft.com/?kbid=905121
> I don't have time to wait a few hours on the phone to get the patch. Anyone
> know where we migh tbe able to get this?
>
> exkievan wrote:
> >In my case redeploying the report didn's solve the problem
> >> Yeah, I use the same technique or redeploying the same report on report
> >> server. And this solves problem.. its strange.. i guess Reports on RS are
> >[quoted text clipped - 34 lines]
> >> > > between your objects on your report. Even if you don't want the extra space
> >> > > on your reports...avoid headaches...space your objects.
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server-reporting/200511/1
>

Excel Margins

Hello
Now with SP2 the page margins works fine. Exists a method to set the Footer
and Header margin in the Excel Rendering Extension?
Thanks...Hello Trace,
Can you pls share how the page margin works for excel. I want to define L/R
margin as 0.2 in but excel takes its default settings for .75 inche. What
setting do we need to make change for making it work on Excel with our page
margin.
Thanks in advance
Jasvinder
"Trace" wrote:
> Hello
> Now with SP2 the page margins works fine. Exists a method to set the Footer
> and Header margin in the Excel Rendering Extension?
> Thanks...|||Hello Jasvinder
I set the Margins with the Properties of the Report, but i set to 0.2cm. In
the Page preview of the Excel document the Margins are set to 0.2.
When i set the Margins to 0.2in then the Page preview display 0.5.
"Jasvinder" wrote:
> Hello Trace,
> Can you pls share how the page margin works for excel. I want to define L/R
> margin as 0.2 in but excel takes its default settings for .75 inche. What
> setting do we need to make change for making it work on Excel with our page
> margin.
> Thanks in advance
> Jasvinder
>
> "Trace" wrote:
> > Hello
> >
> > Now with SP2 the page margins works fine. Exists a method to set the Footer
> > and Header margin in the Excel Rendering Extension?
> >
> > Thanks...