Exeption on xlsx file

Hy we received a file that aspose.cells can’t convert (via stream) giving the exeption
System.NullReferenceException: Object reference not set to an instance of an object.
at ”..˜”(€ , )
at ”..™(€ , Int32 , Boolean )
at ”..Read()
at ”.‡.ƒ( , String )
at ”.‡.‰( , String )
at ”.‡.ƒ()
at ”.‡.Read()
at ”.†.(Workbook , LoadOptions )
at Aspose.Cells.Workbook.Ÿ(Stream , LoadOptions , Boolean )
at a2…ctor(a A_0, Stream A_1) — System.NullReferenceException: Object reference not set to an instance of an object.
at a2.b(MemoryStream A_0, String& A_1) Value cannot be null.

can you investigate? example file in attachment
thanks a lot

Hi,

Thanks for your posting and using Aspose.Cells.

We have looked into this issue and found your file is corrupt. Please see the error shown by MS-Excel 2010 while opening your excel file. If your file is corrupt then Aspose.Cells will throw exception automatically. So it is not a bug but normal and expected behavior of Aspose.Cells.

so the problem is the file probably created with numbers by apple: with this app there is no error.
it means all files created with numbers can’t have a good conversion with Aspose?

Hi,

Thanks for your posting and using Aspose.Cells.

By Apple, do you mean MAC operating system. Which software is able to open such files? Are all files created by your software system corrupt or only this file is corrupt? You can verify by creating such files and then loading it using Aspose.Cells. You can also provide us such files for our investigation.

yes we mean Mac OSX system. As said the name of Apple’s Software is Numbers. We cannot say if all of customer’s files or just one is applicable to this condition. We can open it with numbers without any problems.

Hi Valerio,


Thank you for sharing the details.

First of all, we have logged this incident in our bug tracking system as CELLSNET-44252 for tracking purposes. Moreover, we were able to find out the problem cause for the said exception which are as follow.

  1. Record about picture is not valid
  2. The font name in style.xml is too large therefore Excel cannot not open it correctly.
We have fixed the problem 1) however, you need to fix the problem 2) on your end. Here is the snippet from the style.xml.


Moreover, we have used the developer’s build to re-save your provided spreadsheet (attached). Could you please check it in MAC’s Number application to see if it is fine? Please note, Excel cannot open this spreadsheet in a similar fashion as of your original spreadsheet.

Thanks
your files is just fine in numbers, as the original one

How we (actually our customers that could have this problem) can fix the second problem? is there a “user friendly procedure”?

Hi again,

BooleServer:
T
your files is just fine in numbers, as the original one

Thank you for the confirmation. We have logged your feedback on aforementioned ticket for product team's review.

BooleServer:
T
How we (actually our customers that could have this problem) can fix the second problem? is there a "user friendly procedure"?

You do not need to make any changes if you do not wish to open the said sample in Excel application. Anyway, I will discuss this matter further with the concerned member of the product team to update you in this regard.
Hi Valerio,

I have discussed your recent concerns with the product team. I am afraid, there isn't a better way to shorten the font name(s) in XML but to manually update the file using any editor. Moreover, as discussed earlier, you do not need to change any thing if you have no intention to load such files in Excel. Please note, it is the limitation of Excel application that the font name should be between 0 and 31 characters.

Hi again,


This is to update you that the ticket logged earlier as CELLSNET-44252 has been marked resolved. We will shortly share the fix here after ensuring the quality and incorporating other enhancements.

Hi,

Thanks for using Aspose.Cells.

We have fixed the issue CELLSNET-44252.

Please download and try the latest fix:
Aspose.Cells for .NET v8.7.1.1 and let us know your feedback.


we tried on a test environment and it works!

Hi,

Thanks for your valuable feedback and using Aspose.Cells.

It is good to know that your issue is resolved now. Let us know if you encounter any other issue, we will be glad to look into it and help you further. Have a good day.

The issues you have found earlier (filed as CELLSNET-44252) have been fixed in this update.


This message was posted using Notification2Forum from Downloads module by Aspose Notifier.