|
|
You're in the
sql server reporting services
group:Excel Render - Damage to file was extensive and repairs not possible
sql server reporting services:
[quoted text, click to view] "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 [quoted text, click to view] "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
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
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? [quoted text, click to view] "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 [quoted text, click to view] "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 [quoted text, click to view] "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? [quoted text, click to view] 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
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. [quoted text, click to view] "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
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |