Worksheet limit or size limit when exporting to Excel

Worksheet limit or size limit when exporting to Excel

Post by TWF0dE » Fri, 20 Jan 2006 08:46:02


I have a report with a chart that produces a corrupted Excel file when
exporting to that format only when the chart appears on more than 48 sheets.
I have tested this by toggling the visibility of the chart in various
scenarios, and it occurs regardless of which sheets are included or excluded.
It seems to be the number of chart-containing sheets that causes the error.
Has anyone seen this before? I suppose it could also be the file size,
because the Excel file that will successfully export is right under 1.5 MB. I
know that larger size files are possible, but maybe not with charts? I'm
running RS 2000 SP2.

Thanks!
Matt
 
 
 

Worksheet limit or size limit when exporting to Excel

Post by v-mingq » Fri, 20 Jan 2006 15:19:19

Hi Matt,

Thanks for your post.

I have never meet this scenario before, would you please let me knowif
there is any related error message in Event Logs or Reporting Services logs
when you render the Excel file? What's the behavior when you open the Excel
files?


Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 
 
 

Worksheet limit or size limit when exporting to Excel

Post by TWF0dE » Sat, 21 Jan 2006 00:08:56

Hi Michael - Thanks for your reply! When opening the spreadsheet, the message
says that errors were detected in the file and that Excel was able to opening
by making repairs, but then goes on to note that "damage to the file was so
extensive that repairs were not possible.

There's nothing of note in the event logs, and the only thing I can find in
the Report Server Web Service that looks odd is "INFO: ###
GetReportChunk('RenderingInfo_EXCEL', 2), chunk was not found!". But that may
be normal(?) since I noticed the same line was written when rendering another
report to Excel that has no problems.

Another interesting thing I've noticed: There's a sister report to the
problem report that has the same layout, just a different data source. This
happens to create 51 pages and renders to Excel fine. The file size of that
resulting spreadsheet is 1.3 MB. The file size of the spreadsheet that has
the errors is just over 1.5 MB. As I noted earlier, when I reduce the number
of pages for the report with the errors to 48 pages or less, the resulting
spreadsheet is fine and has a file size of 1.4 MB.

Thanks again,
Matt
 
 
 

Worksheet limit or size limit when exporting to Excel

Post by v-mingq » Sat, 21 Jan 2006 13:56:05

Hi Matt,

Thanks for the detailed information, it seems we will have to trace the
whole process of Excel rendering and debug internal to see what was wrong
with this. This job has to be done by opening a Support incident with
Microsoft Customer Service and Support so that a dedicated Support
Professional can assist with this case. If you need any help in this
regard, please let me know.

For a complete list of Microsoft Customer Service and Support phone
numbers, please go to the following address on the World Wide Web:
http://www.yqcomputer.com/

Thank you for your patience and cooperation.


Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
 
 

Worksheet limit or size limit when exporting to Excel

Post by UGF0b » Wed, 01 Mar 2006 09:44:26

I have the same problem with the same error in my logs, when I applied more
filters to my report, to reduce the number of rows it works... It works with
119 rows and 213 columns... I have 3 drill dows... but only not works with
some parameters (large number of rows), I also have tried the "No timeout"
option of the report.
Also have an ERROR: There is no data for the field at position 5.

Tnx