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
>