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?
>
>
Showing posts with label render. Show all posts
Showing posts with label render. Show all posts
Friday, February 17, 2012
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
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 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>
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 Render - Print Header on Each Page
Hello Microsoft or Forum Members:
This seems like a simple Microsoft Based Reporting System 101 feature...But I can not find out how to do it (among other things that seem like it should work with Microsoft rendering to Microsoft).
How do I make the SSRS 2005 Header for the Report print on each of the pages in excel once it is rendered from SSRS?
All I want is an answer by MSFT that says "YES" it can be done and how or "No" it is not currently available.
I noticed I am not the only one with this type of simple question:
(see this unanswered post)
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1281464&SiteID=1
Thank You guys!
goodguy1974 wrote:
"No" it is not currently available.
I believe that would be the answer. It seems to me that the Excel export renders only the content of the report, not so much the layout of the page. A page rendered in an internet browser is not quite the same as a page rendered in excel.
|||Thank you...
I wish you had a MSFT after your name so I could tell my boss that Microsoft says it can't be done with this version....
Still hoping...
Thanks Again!
|||How many pages are your reports?
|||
The reports range from 14-200 pages...
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
>
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
>
Subscribe to:
Posts (Atom)