Bug 56240

Summary: Handle PP97_DUALSTORAGE streams
Product: POI Reporter: Christian Czech <c.czech>
Component: HSLFAssignee: POI Developers List <dev>
Severity: normal    
Priority: P2    
Version: 3.10-FINAL   
Target Milestone: ---   
Hardware: PC   
OS: All   
Attachments: the error file

Description Christian Czech 2014-03-10 13:09:18 UTC

1. I've got an error file (size 1,3 MB). I can't add this file to bug report.

2. My exception:
The CurrentUserAtom claims that the offset of last edit details are past the end of the file

Can you help me?

Comment 1 Nick Burch 2014-03-10 13:12:52 UTC
Does the Microsoft Binary File Format Validator say it's valid or broken?

Can Office open it? If so, and you save-as, does that fix it?

Can OpenOffice open it?
Comment 2 Christian Czech 2014-03-14 08:16:16 UTC
<BFFValidation result="PASSED" datetime="03/14/14 08:43:20" path="17f88.ppt"> </BFFValidation>

Office Professional Plus 2010 (Version 14.0.7116.5000)
Can open this file.
Save-as (to 17f88saveas.ppt) fixes the problem.

OpenOffice 4.0.1 can open it.
Comment 3 Nick Burch 2014-03-14 10:01:58 UTC
If you could post the whole file, that'd be a big help to fixing it

Otherwise, any chance you could post the dump of the Current User Atom stream from org.apache.poi.poifs.dev.POIFSViewer, along with the output of org.apache.poi.poifs.dev.POIFSLister and the POIFSViewer metadata + first few lines + last few lines for "PowerPoint Document"?
Comment 4 Christian Czech 2014-03-14 10:07:42 UTC
Where can I post the whole file?
Comment 5 Nick Burch 2014-03-14 10:11:51 UTC
Just add it as an attachment to the bug here in bugzilla. Zip it if you need to keep the size down
Comment 6 Christian Czech 2014-03-19 14:14:06 UTC
Created attachment 31405 [details]
the error file

Error file inside
Comment 7 Andreas Beeker 2014-12-30 02:25:20 UTC
Thank you for the test file, which contained a dual storage stream.
When googling for the stream name, the implementations used the inner stream entry instead of the top level document. Furthermore the current user record in the root node was anyway malformed.
Fix applied with r1648466