Bug 62144 - RuntimeException: Shared formula record should follow a FormulaRecord
Summary: RuntimeException: Shared formula record should follow a FormulaRecord
Status: RESOLVED LATER
Alias: None
Product: POI
Classification: Unclassified
Component: HSSF (show other bugs)
Version: 3.16-FINAL
Hardware: Other Linux
: P2 major (vote)
Target Milestone: ---
Assignee: POI Developers List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-01 00:51 UTC by ccentofonti
Modified: 2018-04-02 21:02 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ccentofonti 2018-03-01 00:51:56 UTC 
Receiving the following stack trace when calling WorkbookFactory.create on a .xls file

java.lang.RuntimeException: Shared formula record should follow a FormulaRecord
at org.apache.poi.hssf.model.RowBlocksReader.<init>(RowBlocksReader.java:73) ~[poi-3.16.jar:3.16]
at org.apache.poi.hssf.model.InternalSheet.<init>(InternalSheet.java:216) ~[poi-3.16.jar:3.16]
at org.apache.poi.hssf.model.InternalSheet.createSheet(InternalSheet.java:157) ~[poi-3.16.jar:3.16]
at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:359) ~[poi-3.16.jar:3.16]
at org.apache.poi.ss.usermodel.WorkbookFactory.create(WorkbookFactory.java:99) ~[poi-ooxml-3.16.jar:3.16]
at org.apache.poi.ss.usermodel.WorkbookFactory.create(WorkbookFactory.java:256) ~[poi-ooxml-3.16.jar:3.16]
at org.apache.poi.ss.usermodel.WorkbookFactory.create(WorkbookFactory.java:226) ~[poi-ooxml-3.16.jar:3.16]
at org.apache.poi.ss.usermodel.WorkbookFactory.create(WorkbookFactory.java:205) ~[poi-ooxml-3.16.jar:3.16]

Running a java web application through tomcat 8.5.15, Java 8
Comment 1 PJ Fanning 2018-03-01 19:44:50 UTC 
Would it be possible to provide a sample file that demonstrates the issue?
Comment 2 ccentofonti 2018-03-01 19:52:12 UTC 
(In reply to PJ Fanning from comment #1)
> Would it be possible to provide a sample file that demonstrates the issue?

Some of our files have sensitive information in them. I will see if I can provide one that produces the issue.
Comment 3 Dominik Stadler 2018-04-02 21:02:34 UTC 
We cannot do much without a file that reproduces the problem, thus closing as LATER for now, please reopen with a sample file that we can use to reproduce the problem.