Showing posts with label groups. Show all posts
Showing posts with label groups. Show all posts

Tuesday, March 27, 2012

excel export /collapsed fails to render excel file

Trying to render a report that has three groups two expand and collapse and
have charts. The first attempts to render were successful but all later ones
fail. And excel produces the following message:
Microsoft Office Excel File Repair Log
Errors were detected in file 'C:\Documents and Settings\johnsond\Local
Settings\Temporary Internet
Files\Content.IE5\UT38LWFQ\CustomerSalesByPartType[2].xls'
The following is a list of repairs:
Damage to the file was so extensive that repairs were not possible. Excel
attempted to recover your formulas and values, but some data may have been
lost or corrupted.
Can anyone help with this?DJJIII,
I wish I were writing with a solution (as I also am getting the annonying
"damage too extensive" message in excel.) I have an MSDN subscription, so we
should get a MS reply. I will repost under the subject: "Damage to file
message when exporting to excel" for good measure.
The interesting thing in my case is that I have a fairly complex report with
many charts and tables. My "top level" report throws this excel error.
However, if I add parameters ("drill down report") the structure of the
report is exactly the same with charts and tables, just less (or different)
data and then it renders fine. I am not using groups at all, so I don't
think the issue is directly related to your use of groups.
My guess is there is some data-related issue as our same report (both
top-level and drilldown) with different data works fine.
Our report actually is a collection of 10 or so subreports, so I will be
doing a little debugging by removing subreports to see if I can identify the
subreport or data that is causing the issue.
-David
"DJJIII" wrote:
> Trying to render a report that has three groups two expand and collapse and
> have charts. The first attempts to render were successful but all later ones
> fail. And excel produces the following message:
> Microsoft Office Excel File Repair Log
> Errors were detected in file 'C:\Documents and Settings\johnsond\Local
> Settings\Temporary Internet
> Files\Content.IE5\UT38LWFQ\CustomerSalesByPartType[2].xls'
> The following is a list of repairs:
> Damage to the file was so extensive that repairs were not possible. Excel
> attempted to recover your formulas and values, but some data may have been
> lost or corrupted.
> Can anyone help with this?
>

Friday, March 23, 2012

Excel consuming 100% CPU

Hi,
We are using RS Sp2 andExcel XP on the clients.
One report outputs 5000+ rows and are grouped like this:
account group (25 groups)
account (250 groups)
values (4725 rows)
When exported to Excel the XL-file is 11Mb+ !
All groups are collapsed in XL by default, and when trying to work in the
sheet XL consumes all CPU! If all groups are expanded it is possible to work
with the data and there is no unusual CPU consuming.
If collapsing a group again then the CPU consumtion becomes heavy again.
My question, is this a limitation in XL? If it is, does this work better in
XL 2003?
Is there anything we can do to boost performance, as it is now we cant work
in XL...
Any ideas?
/FredrikAt this point this is just an Excel file. It looks like Excel is not
handling that amount of data and that amount of groups very well. You could
ask in Excel newsgroup if XL 2003 might work better for you.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
news:64659432-7804-4443-83D6-454F665C650A@.microsoft.com...
> Hi,
> We are using RS Sp2 andExcel XP on the clients.
> One report outputs 5000+ rows and are grouped like this:
> account group (25 groups)
> account (250 groups)
> values (4725 rows)
> When exported to Excel the XL-file is 11Mb+ !
> All groups are collapsed in XL by default, and when trying to work in the
> sheet XL consumes all CPU! If all groups are expanded it is possible to
> work
> with the data and there is no unusual CPU consuming.
> If collapsing a group again then the CPU consumtion becomes heavy again.
> My question, is this a limitation in XL? If it is, does this work better
> in
> XL 2003?
> Is there anything we can do to boost performance, as it is now we cant
> work
> in XL...
> Any ideas?
> /Fredrik
>|||Tested 2003 but the same problem occured. I would be very happy to now what
the heck is going on in Excel here...
"Bruce L-C [MVP]" wrote:
> At this point this is just an Excel file. It looks like Excel is not
> handling that amount of data and that amount of groups very well. You could
> ask in Excel newsgroup if XL 2003 might work better for you.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
> news:64659432-7804-4443-83D6-454F665C650A@.microsoft.com...
> > Hi,
> > We are using RS Sp2 andExcel XP on the clients.
> > One report outputs 5000+ rows and are grouped like this:
> >
> > account group (25 groups)
> > account (250 groups)
> > values (4725 rows)
> >
> > When exported to Excel the XL-file is 11Mb+ !
> > All groups are collapsed in XL by default, and when trying to work in the
> > sheet XL consumes all CPU! If all groups are expanded it is possible to
> > work
> > with the data and there is no unusual CPU consuming.
> > If collapsing a group again then the CPU consumtion becomes heavy again.
> >
> > My question, is this a limitation in XL? If it is, does this work better
> > in
> > XL 2003?
> > Is there anything we can do to boost performance, as it is now we cant
> > work
> > in XL...
> >
> > Any ideas?
> >
> > /Fredrik
> >
>
>|||The problem may be merged cells or show/hide regions. Excel reports with
thousands of these elements are slow to load because for each new cell they
need to check to see if it intersects with all of the other merged cells.
If you can, removing some of the show/hide elements or other obvious merged
cells and you should see a speed increase in Excel.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
news:3F5CB660-BFB5-4712-A30C-A0081A888A29@.microsoft.com...
> Tested 2003 but the same problem occured. I would be very happy to now
> what
> the heck is going on in Excel here...
> "Bruce L-C [MVP]" wrote:
>> At this point this is just an Excel file. It looks like Excel is not
>> handling that amount of data and that amount of groups very well. You
>> could
>> ask in Excel newsgroup if XL 2003 might work better for you.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
>> news:64659432-7804-4443-83D6-454F665C650A@.microsoft.com...
>> > Hi,
>> > We are using RS Sp2 andExcel XP on the clients.
>> > One report outputs 5000+ rows and are grouped like this:
>> >
>> > account group (25 groups)
>> > account (250 groups)
>> > values (4725 rows)
>> >
>> > When exported to Excel the XL-file is 11Mb+ !
>> > All groups are collapsed in XL by default, and when trying to work in
>> > the
>> > sheet XL consumes all CPU! If all groups are expanded it is possible to
>> > work
>> > with the data and there is no unusual CPU consuming.
>> > If collapsing a group again then the CPU consumtion becomes heavy
>> > again.
>> >
>> > My question, is this a limitation in XL? If it is, does this work
>> > better
>> > in
>> > XL 2003?
>> > Is there anything we can do to boost performance, as it is now we cant
>> > work
>> > in XL...
>> >
>> > Any ideas?
>> >
>> > /Fredrik
>> >
>>