Received : 2007/07/31 04:31:00
Message : Hi,
I’ve evaluating the Reporting services word renderer, and in the most part it appears to work well. The problem that I have is that when we set it up with query driven subscriptions the word document appears to be encoded (word can’t understand it) and viewing the binary data of the word file it is very different to that of the file rendered from the reporting services portal using the same renderer. Is this a bug?, a limitation placed on the evaluation version?
Regards,
Chris Howle
This message was posted using Aspose.Live 2 Forum
Hi Chris,
Thank you for posting this request. No, this does not seem to be a limitation and I have never faced such behaviour. Could you please attach a sample RDL report that ends up with a problematic document as well as describe how I can reproduce the issue? I will try to help you promptly then.
RDL below: It renders correctly throught the reporting services portal, and when subscribing via email, but when exporting to the file system (through query based subscriptions) it appears corrupt. I don’t appear to be able to include the produced document here.
Regards, Chirs
<?xml version="1.0" encoding="utf-8"?>
<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<BottomMargin>2.5cm</BottomMargin>
<RightMargin>2.5cm</RightMargin>
<PageWidth>21cm</PageWidth>
<rd:DrawGrid>true</rd:DrawGrid>
<InteractiveWidth>8.5in</InteractiveWidth>
<rd:GridSpacing>0.25cm</rd:GridSpacing>
<rd:SnapToGrid>true</rd:SnapToGrid>
<Body>
<ColumnSpacing>1cm</ColumnSpacing>
<ReportItems>
<Textbox Name="textbox5">
<Top>4.5cm</Top>
<ZIndex>4</ZIndex>
<Width>12.69841cm</Width>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<FontWeight>700</FontWeight>
<FontSize>20pt</FontSize>
<Color>SteelBlue</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Height>0.91429cm</Height>
<Value>Test Report</Value>
</Textbox>
<Textbox Name="textbox4">
<Top>1.5cm</Top>
<ZIndex>3</ZIndex>
<Width>12.69841cm</Width>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<FontWeight>700</FontWeight>
<FontSize>20pt</FontSize>
<Color>SteelBlue</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Height>0.91429cm</Height>
<Value>Test Report</Value>
</Textbox>
<Textbox Name="textbox3">
<Top>5.75cm</Top>
<ZIndex>2</ZIndex>
<Width>12.69841cm</Width>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<FontWeight>700</FontWeight>
<FontSize>20pt</FontSize>
<Color>SteelBlue</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Height>0.91429cm</Height>
<Value>Test Report</Value>
</Textbox>
<Textbox Name="textbox2">
<Top>2.91785cm</Top>
<ZIndex>1</ZIndex>
<Width>12.69841cm</Width>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<FontWeight>700</FontWeight>
<FontSize>20pt</FontSize>
<Color>SteelBlue</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Height>0.91429cm</Height>
<Value>Test Report</Value>
</Textbox>
<Textbox Name="textbox1">
<rd:DefaultName>textbox1</rd:DefaultName>
<Width>12.69841cm</Width>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<FontWeight>700</FontWeight>
<FontSize>20pt</FontSize>
<Color>SteelBlue</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Height>0.91429cm</Height>
<Value>Test Report</Value>
</Textbox>
</ReportItems>
<Height>6.75cm</Height>
</Body>
<rd:ReportID>254f6bd7-35b0-4080-b4b1-328579c14fe8</rd:ReportID>
<LeftMargin>2.5cm</LeftMargin>
<Width>12.94841cm</Width>
<InteractiveHeight>11in</InteractiveHeight>
<Language>en-US</Language>
<TopMargin>2.5cm</TopMargin>
<PageHeight>29.7cm</PageHeight>
</Report>
Thank you Chris. I will try to reproduce it given this information and get back to you shortly.
I have been looking at this a little more and have found that using query driven subscriptions to a file share works for RTF and WordprocessingML formats, but not the .DOC format, so I think it is just a problem with that.
Chris,
I’ve succeeded to reproduce the issue with an arbitrary report and now am trying to determine the cause of this strange problem.
Thanks.
Chris,
I have spotted the cause (had to do with encoding) and fixed the issue. I’m planning to release a hotfix very soon, the likeliest date is Monday. Does this timeframe suit you?
Thanks.
Excellent news. Monday will be fine. Thanks for the quick response.
Hi Chris,
We have released Aspose.Words for Reporting Services 1.3.2 that addresses your issue. Please download it here:
https://downloads.aspose.com/words/reportingservices
Thanks.
Thanks Dmitry,
I have just installed it and a few quick tests look good.
Chris
Dmitry, Just one more question:
The rendering to DOC looks good, but now that is working we are seeing a limitation of ‘only 10 pages’ in the evaluation version. is this a limitation placed on the evaluation version?
Chris.
Yes, it is. You can request a free 30-days testing license to avoid this limitation if you need. Please contact our sales managers in the Aspose.Purchase forum then:
https://docs.aspose.com/words/reportingservices/evaluation-version-limitations/