Excel unreadable content error

[REI Software]

when I export a simple list of items to an excel worksheet (I bound to a collection of business objects, accepted basically the defaults). I get an error that excel recovered unreadable content and that it needs to repair.

The log shows the following:

<?xml version="1.0" encoding="UTF-8" standalone="true"?>

-<recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main">
<logFileName>error530880_01.xml</logFileName>
<summary>Errors were detected in file 'SignalListReport2.xlsx'</summary>
-<repairedRecords summary="Following is a list of repairs:">
<repairedRecord>Repaired Records: Cell information from /xl/worksheets/sheet.xml part</repairedRecord></repairedRecords>
</recoveryLog>

How do I fix this?

[Steve]

Hi Alan,

We have not been able to reproduce this behavior. Can you clarify what excel export are you using: Excel 97- 2003 which is binary format or the Excel 2007 (Open XML) format? Can you test exporting from our online demos and see if you have such problems? If the excel files from our demo open correctly, but the issue occurs with all reports from your server, then please check whether you're using any compression modules on your server and whether the issue can be still reproduced after disabling them.

On a side note, searching about this problem we found reports that it recently occurred after applying a Windows security patch. We found information that this update is causing problems with Excel files in general. Please, check the following thread: Excel Security Update Causing Issues with Excel (KB2597166).

Greetings,
Steve
the Telerik team

[Ave]

It was with the "Excel worksheet" export option, which I'm assuming is the Excel 2007. The Excel 97-2003 worked fine. I exported from the online demo, and it opened fine, so I assume it works on your server. Since I can open that file and other Excel files just fine, then it seems that Excel is working reasonably well.

However, I'm not using a server, I'm using the WPF report viewer and Open XML libraries etc, on my development machine in a WPF application. I have no idea what you mean by "compression modules" so I'm assuming that has to do with client/server communications which does not apply in this situation.

I recently upgraded to a retail version of reporting, so I will check if it still occurs. I'm running the latest internal build because the WPF reporting could not print on the release build due to a bug.

(Sorry wrong account, but this is Alan)

[Ave]

I just re-tested the export and it seems to be working alright in the retail version. I believe the only difference was the trial version versus the retail version.

I had initially downloaded the trial version official release, but after the printing bug I upgraded to the internal release. I do not remember if the excel worksheet issue existed in both versions or not, but i believe it was in the official release. I just tested the latest retail internal build and it works.

(Sorry wrong account, but this is Alan)

[Steve]

Hi Alan,

That explains a lot, as I assumed that you were using the latest version of the product. There was a small fix in Q2 2012, namely Fixed: Exported Excel files sometimes give error when opened. Should you use version after Q2 2012, you should not encounter such issues.

All the best,
Steve
the Telerik team

[REI Software]

Well, the first time I ever downloaded the reporting library was this December and it was Q3 (the latest official build). So I think I was using a later version than this bug report always. While that sounded convincing at first, I'm not sure it is related unless the bug fix you mentioned wasn't properly merged into the trial build?

I'm currently using:

6.2.12.1123

And I believe I was using something like... (it is the current official release unless you changed it since last week)

6.2.12.1017

I'm not sure that I would want to re-install the current trial build just to see if the error happens. Hmm..

[Steve]

Hi Alan,

The trial version is fully functional and does not have any difference other than a copyright message displayed on each report page. We appreciate your feedback, if somebody else reports similar issues, we would by all means ask for exact version.

Greetings,
Steve
the Telerik team

[Андрей]

[quote]Your quote goes here[/quote]

[Edward]

If you are searching excel file recovery tool in the online market and you are thinking that “How to Repair XLS and XLSX files? (<admin: please do not post ads>) Then you should give a try to Excel file recovery tool, that can repair corrupt excel files, open XLS files and restore in original file format. It supports all versions of MS Excel and MS Windows operating system.

 

[Stef]

Hi Edward,

If you have a corrupted Excel file produced by Telerik Reporting, please check the following:

1. If the report can gather in the number of rows and columns allowed by MS Excel - Excel Limitations;
2. If you use the Format text function or TextBox.Format property and if the set formatting string is correctly used with the type of data displayed by the reporting item;
3. If removing styles from the report in a Report Designer resolves the problem with the produced Excel files.

Greetings,
Stef
the Telerik team