Aspose.Note.FileCorruptedException

Aspose.Note Product Family
1

We have a problem with processing large OneNote file (1.8 Gb).
But it can be opened with OneNote app.

Code example:

var fileStream = File.OpenRead("D:\\Downloads\\Bob Work.one");
return new Document(fileStream);

Exception:

Aspose.Note.FileCorruptedException: ‘File container wasn’t found!’

image.png (121.6 KB)

This is a customer’s file so we can attach it as an example right now.
Aspose.Note v.22.9.0

Could you help?

2

@Andrei86,

Thanks for the screenshot.

How much time it takes to open such a large document into OneNote application? I guess it might take long time to open into it. But surely to open such a file (1.8 Gb) into Aspose.Note document object, the process will surely demand more and more resources (memory, cpu, etc.). Anyways, could you please upload the large file to some file sharing service (Google drive, dropbox, etc.) and provide us Download link here to download the file seamlessly. We will check it.

3

Broken file: OnlyBadFile.zip (3.9 KB)

4

@Andrei86,

Thanks for the sample document.

We reproduced the issue after an initial test as you mentioned by loading your OneNote document into object model of Aspose.Note for .NET. We found an exception “Aspose.Note.FileCorruptedException: ‘File container wasn’t found!’”.

We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes accordingly:
Issue ID(s): NOTENET-5756

Once we have an update on it, we will let you now here.

5

Perhaps you can provide a workaround to be able to process such files?

6

@Andrei86,

I am afraid, your issue is pending for analysis, so we might not share any workaround for it. Once we evaluate your issue in details then, we might share more details or possible workaround (to cope with it) if it will take more time to fix it.

We are sorry for any inconvenience caused!

7

Hello.

Maybe there is news on this case.
This issue really affects our customers and makes them frustrated because such documents can be opened using the standard OneNote tool.
It would be nice to get some sort of solution soon.

Thank you!

8

@Andrei86,

We will try to evaluate your issue soon. Please note, we work on issues in first come, first served format. We feel this is the fairest and appropriate way to deal with the clients.

Maybe, you can avail paid support service where we try to give user issue(s) higher priority.

9

Hello,

Maybe you have an update for this case?

10

@Andrei86,

We are sorry but still there is no update on it. Once we have some progress on it, we will update you.

11

Hello,

About paid support.
We have a developer subscription to Aspose.Total.
Does it include paid support?

This issue is really affecting us a lot.
What can we do to speed up the processing of this case?
Can it be solved in the nearest future?

12

@Andrei86,

Please contact Sales team in the relevant section to check your subscription if it includes paid support.

13

We have found one more file that cannot be opened by Aspose.Note but can be opened by OneNote native application.

image.png (7.8 KB)

file: broken.zip (12.2 KB)

14

@Andrei86,

We reproduced the issue after an initial test as you mentioned by loading your OneNote document into object model of Aspose.Note for .NET. We found an exception “System.Collections.Generic.KeyNotFoundException: ‘The given key was not present in the dictionary.’”

We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): NOTENET-5762

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

15

Hello,

Do you have any updates for reported issues?

16

@Andrei86,

We are sorry but your issues are not resolved yet. Maybe, you could avail paid support to give your issue(s) highest (possible) priority.

17

@Andrei86,

We are pleased to inform you that your issue (logged earlier as “/NOTENET-5756”) has been resolved. We will include the fix in our upcoming releases. Once we publish the supported version, we will notify you in the thread.

18

Good news.

What about the case NOTENET-5762?
Will it be fixed as well?

19

@Andrei86,

No, it has not been addressed yet. Once we figure it out or we have some other updates on it, we will let you know here.

20

The issues you have found earlier (filed as NOTENET-5756) have been fixed in this update. This message was posted using Bugs notification tool by senua.remizova