Problem Note 33347: A com.sas.solutions.finance.models.FinanceServerException occurs when compiling drivers
When using the SAS® Financial Management Add-in for Excel with Microsoft Office 2007, the following exception is generated when you compile driver formulas:
com.sas.solutions.finance.models.FinanceClientException:
com.sas.solutions.finance.models.FinanceServerException: java.io.IOException:
Invalid header signature; read 1688935826934608, expected -2226271756974174256
at
com.sas.solutions.finance.models.data.client.JMSDelegate.sendToServer(JMSDelegate.java:134)
at
com.sas.solutions.finance.models.data.client.JMSDelegate.generateFormulaFacts(JMSDelegate.java:248)
at
com.sas.solutions.finance.models.planning.client.FormSetManagerDelegate.generate
FormulaFacts(FormSetManagerDelegate.java:869)
at
com.sas.solutions.finance.app.dataentry.commands.CalculateFormulaFactsCommand.on
Construct(CalculateFormulaFactsCommand.java:161)
at
com.sas.solutions.finance.app.commands.FinanceCommand.construct(FinanceCommand.j
ava:296)
at com.sas.solutions.app.util.SwingWorker.construct(SwingWorker.java:50)
at com.sas.solutions.app.util.AbstractSwingWorker$2.run(AbstractSwingWorker.java:113)
at java.lang.Thread.run(Unknown Source) Caused by:
com.sas.solutions.finance.models.FinanceServerException: java.io.IOException:
Invalid header signature; read 1688935826934608, expected -2226271756974174256
at
com.sas.solutions.finance.models.planning.util.ExcelTemplateUtilities.getExcelSpreadsheet(ExcelTemplateUtilities.java:231) at
com.sas.solutions.finance.models.planning.util.ExcelTemplateUtilities.getFormSet
TemplateHierarchies(ExcelTemplateUtilities.java:91) at
com.sas.solutions.finance.models.planning.ejb.FormSetManagerBean.generateFormula
Facts(FormSetManagerBean.java:2973) at
com.sas.solutions.finance.models.planning.ejb.FormSetManager_yuvbte_ELOImpl.gene
rateFormulaFacts(FormSetManager_yuvbte_ELOImpl.java:1699) at
com.sas.solutions.finance.models.data.ejb.ExecuteMessageDrivenBean.onMessage(ExecuteMessageDrivenBean.java:261) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:400) at
weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2698)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2610)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: java.io.IOException: Invalid header signature; read 1688935826934608,
expected -2226271756974174256 at
org.apache.poi.poifs.storage.HeaderBlockReader.(HeaderBlockReader.java:124) at
org.apache.poi.poifs.filesystem.POIFSFileSystem.(POIFSFileSystem.java:120) at
com.sas.solutions.finance.models.planning.util.ExcelTemplateUtilities.getExcelSpreadsheet(ExcelTemplateUtilities.java:117)
...
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Financial Management | Microsoft® Windows® for x64 | 4.4 | 4.4.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Advanced Server | 4.4 | 4.4.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Datacenter Server | 4.4 | 4.4.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Server | 4.4 | 4.4.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows 2000 Professional | 4.4 | 4.4.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows NT Workstation | 4.4 | 4.4.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows Server 2003 Datacenter Edition | 4.4 | 4.4.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows Server 2003 Enterprise Edition | 4.4 | 4.4.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows Server 2003 Standard Edition | 4.4 | 4.4.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Microsoft Windows XP Professional | 4.4 | 4.4.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
Windows Vista | 4.4 | 4.4.1 | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2008-10-14 13:41:33 |
Date Created: | 2008-09-18 13:04:57 |