| Summary: | protected worksheet | ||
|---|---|---|---|
| Product: | POI | Reporter: | Robert Nice <rnice> |
| Component: | HSSF | Assignee: | POI Developers List <dev> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | syyid |
| Priority: | P2 | ||
| Version: | 3.0-dev | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | other | ||
| Attachments: | Workbook that won't open | ||
Created attachment 18021 [details]
Workbook that won't open
Thanks for your efforts.
Can you confirm that this file was written by excel in the first instance. Debugging it is Wierd, seems like the Font records are all screwed up. Jason (In reply to comment #2) > Can you confirm that this file was written by excel in the first instance. > Debugging it is Wierd, seems like the Font records are all screwed up. No I can't. But it does open fine in Excel and OpenOffice. Agreed. And if i save in excel, the problem still exists. Wierd. Ill keep looking into it but may be headed to the too hard basket. Jason *** Bug 34727 has been marked as a duplicate of this bug. *** What seems to be happening is there there are some illegal font records, these have whacked out values for all of the fields including the length of the font name, so when we attempt to read the font name it barfs because it expects more characters than what are remaining in the FontRecord. As indicated above this does open in excel, so there much be some trickery going on here that we are not aware of, or excel simply ignores these whacked out records. Dont know what to do yet. Jason Refer to Bug 27548, the reason for this is that the workbook is encrypted. At this point in time HSSF does not support handling of encrypted workbooks see FAQ. To prevent this confusion (in regards to this exception stacktrace) i will throw a RecordFormatException when we hit a FILEPASS record. Jason *** This bug has been marked as a duplicate of 27548 *** I don't understand. Are you saying that the workbook, or portions of it are encrypted? I don't need a password to open it, so is it that just parts of it are locked or something? Is there a suggested workaround to get it to skip any parts it can't read? Help! |
See attached xls sheet, won't open. Stack trace below. Checked 2.5.1-final and 3.0-alpha1-20050704 java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.apache.poi.hssf.record.RecordFactory.createRecord(RecordFactory.java:237) at org.apache.poi.hssf.record.RecordFactory.createRecords(RecordFactory.java:160) at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:183) at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:152) at test.main(test.java:10) Caused by: java.lang.IllegalArgumentException: Illegal length at org.apache.poi.util.StringUtil.getFromUnicodeLE(StringUtil.java:70) at org.apache.poi.hssf.record.FontRecord.fillFields(FontRecord.java:135) at org.apache.poi.hssf.record.Record.fillFields(Record.java:90) at org.apache.poi.hssf.record.Record.<init>(Record.java:55) at org.apache.poi.hssf.record.FontRecord.<init>(FontRecord.java:88) ... 9 more Exception in thread "main" org.apache.poi.hssf.record.RecordFormatException: Unable to construct record instance, the following exception occured: null at org.apache.poi.hssf.record.RecordFactory.createRecord(RecordFactory.java:250) at org.apache.poi.hssf.record.RecordFactory.createRecords(RecordFactory.java:160) at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:183) at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:152) at test.main(test.java:10)