on 11-07-2014 1:15 PM
Hi,
When I start AO 1.4 SP09 PL1, I get the error: "Object reference not set to an instance of an object". The log file contains the detail below. This is on a fresh install of Windows 8.1 and .Net, with Office 2013.
Would anyone have an idea why this happens or how to fix it?
Thank you!
John
- Critical: | 102001 #msl.genexcept | | 2014-11-07T07:40:22 | | com.sap.ip.bi.pioneer.common.messagehandling.CoMessenger.WriteToLog() () |
- Information: | @@@@@ Application Start. (SharedAddIn 2007 Build 1.4.9.3241 loaded/OnConnection method) @@@@@ | | 2014-11-07T07:54:46 | | com.sap.ip.bi.pioneer.shared.addin2007.Connect.OnConnection() () |
- Critical: | General .NET Exception: |
Object reference not set to an instance of an object.
at com.sap.ip.bi.pioneer.addins.xl.EaTaskpaneControl.UpdateTabVisibility(List`1 iHideList)
at com.sap.ip.bi.pioneer.addins.xl.EaTaskpane.UpdateTabVisibility(List`1 iHideList)
at com.sap.ip.bi.pioneer.excel.main.EaSession.ActivateWorkbook(IWorkbook iWb)
at com.sap.ip.bi.pioneer.excel.main.xlcallback.EaExcelCallBackHandler.XlApplication_NewWorkbookEvent(IWorkbook Wb)
at com.sap.ip.bi.pioneer.addins.xlwrap.XlAppWrapBase.<>c__DisplayClass1.<mXlApplication_NewWorkbook>b__0()
at com.sap.ip.bi.pioneer.controls.main.CnSession.CallbackWrapForOfficeEvents(CallbackWrapDelegate iDelegate, CnCallbackErrorSeverity iSeverity, CoUseWaitCursorEnum iWaitCursor)
| 2014-11-07T07:57:42 | | com.sap.ip.bi.pioneer.common.messagehandling.CoMessenger.WriteToLog() () | ||
- Critical: | 102001 #msl.genexcept | | 2014-11-07T07:57:42 | | com.sap.ip.bi.pioneer.common.messagehandling.CoMessenger.WriteToLog() () |
If I read the PAM correctly it doesn't appear that Analysis Office supports Windows 8.1 yet - see https://websmp110.sap-ag.de/~sapidb/011000358700000429322013E - so that could be a reason why it is not working.
Another idea is that you have to install the same version of Office - for example I have a 32 bit version of Excel on Windows 7 so I have to install a 32 bit version of Analysis Office and not the 64 bit version of Analysis Office
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks as always for the reply Tammy! Looks like PAM is out of date - chek SAP Note 1466118 - Hardware & Software requirements for Analysis, edition for MS Office
In this it says that Windows 8.1 and MS Office 2013 are supported.
I am using 32-bit Office and 32-Bit Analysis - been bitten by that before!
Looks like maybe a .Net problem but not sure where to go.
When I came to install Analysis for Office, it complained that I didn't have .Net installed, and provided a link to download .Net 3.5 SP1
Download Microsoft .NET Framework 3.5 Service Pack 1 from Official Microsoft Download Center
That's what I installed. I did try to install .Net 4.5 and get the following message:
Microsoft .NET Framework 4.5 is already a part of this operating system. You do not need to install the .NET Framework 4.5 redistributable. Same or higher version of .NET Framework 4.5 has already been installed on this computer.
Hi John,
The .Net installer has been moved to "Control Panel -> Programs and Features -> Turn Windows Features on or off".
There is an entry for both 4.5 and 3.5 (which contains 3.0 and 2.0). Probably worth taking both..
The error helpfully doesn't say what the object was meant to be, anything in event viewer? Although it does talk about attempting to write a log file, wonder if it is some strange authorisations/UAC issue? Try running as admin?
Oli
I have the same environment and the version 1.4.9 is working as expected but I need to know the steps that you are executing to check deeper. By the description you are opening a created (in an old version) workbook. Is that the correct information?
On our database we have a error message as:"- Critical: 102001 #msl.genexcept | 2014-11-07T07:40:22 |com.sap.ip.bi.pioneer.common.messagehandling.CoMessenger.WriteToLog()()" by the version 1.4.8 but was for a specific situation.
John, could you please describe the steps that I can check internally if this is on the environment or if this is on the version?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the response Diego! All I did was to install Analysis for Office, and then open it. I wasn't using an existing workbook, it happened when I clicked the new Blank Worksheet button.
Now, I get a new error message once I open a HANA View. I'm able to login to HANA (Rev.84 client) and select a View. It then provides the variable window which I fill in. Then it tried to load and gives the following error.
An exception occurred in one of the data sources.
SAP BI Add-in has disconnected all data sources. (ID-111007)
Nested exception. See inner exception below for more details:
SQL result set error
- Critical: | Application Exception (ID 103042) |
Nested Exception. See inner exception for details below.
at com.sap.ip.bi.pioneer.common.exceptions.CoNestedException.ThrowNestedException(Exception iInnerException, Object iExTag)
at com.sap.ip.bi.pioneer.core.exceptions.CrExceptionHelper.ThrowRestartException(Exception iEx)
at com.sap.ip.bi.pioneer.excel.views.EaViewManagerSession.OnProcessingFinished(Object iSender, CoProcessingFinishedEventArgs iEventArgs)
at com.sap.ip.bi.pioneer.common.commands.CoCommandProcessor.OnProcessingFinished(CoCommandBase iCommand)
at com.sap.ip.bi.pioneer.core.commands.CrCommandProcessor.OnProcessingFinished(CoCommandBase iCommand)
at com.sap.ip.bi.pioneer.common.commands.CoCommandProcessor.CommandPostprocessing(CoCommandBase iCommand)
at com.sap.ip.bi.pioneer.common.commands.CoCommandProcessor.InitialCommandExecute(CoCommandBase iCommand)
at com.sap.ip.bi.pioneer.common.commands.CoCommandProcessor.DoExecuteCommandInternal(CoCommandParameters iParameters)
at com.sap.ip.bi.pioneer.common.commands.CoCommandProcessor.DoExecuteCommand(CoCommandBase iCommand, CoCommandParameters iParameters)
at com.sap.ip.bi.pioneer.core.commands.CrCommandProcessor.DoExecuteCommand(CoCommandBase iCommand, CoCommandParameters iParameters)
at com.sap.ip.bi.pioneer.controls.ribbonControls.CnRibbonBaseMenu.OnDropDownControlAction(CnRibbonDropdownControl iCommandControl, String iSelectedItemId, Int32 iSelectedIndex)
at com.sap.ip.bi.pioneer.controls.ribbonControls.CnRibbonDropdownControl.OnAction(String iSelectedItemId, Int32 iSelectedIndex)
at com.sap.ip.bi.pioneer.shared.addin2007.Connect.OnDropdownAction(IRibbonControl iRibbonControl, String iSelectedId, Int32 iSelectedIndex)
>> Bali Exception:
SQL result set error
com.sap.ip.bi.bics.dataaccess.resource.impl.bae.sql.BAESqlResultSet.getDouble(BAESqlResultSet:200) | |||
com.sap.ip.bi.bics.dataaccess.resource.impl.bae.queryview.resultset.cache.CachedSQLResultSet.initCache(CachedSQLResultSet:131) | |||
com.sap.ip.bi.bics.dataaccess.resource.impl.bae.queryview.resultset.BAECrosstabDataSource.execute(BAECrosstabDataSource:260) | |||
com.sap.ip.bi.bics.dataaccess.resource.impl.bae.queryview.resultset.BAEResultSet.execute(BAEResultSet:89) | |||
com.sap.ip.bi.bics.dataaccess.resource.impl.bae.queryview.BAEQueryView.getResultSet(BAEQueryView:199) | |||
com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.ResultSet.getData(ResultSet:525) | |||
com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsResultSetManager.getResultSet(RsResultSetManager:238) | |||
com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsResultSetManager.getResultSet(RsResultSetManager:169) | |||
com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.resultset.RsResultSetManager.getResultSet(RsResultSetManager:57) | |||
com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.QueryView.getResultSet(QueryView:729) | |||
cli.com.sap.ip.bi.pioneer.core.models.CrQueryView.GetResultSet(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.core.models.CrQueryView.GetResultSetState(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.core.models.CrDataProvider.IsResultSetAvailable(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.core.models.items.CrModelItemDataProvider.IsResultSetAvailable(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.excel.models.EaItemGrid.DoIHaveResultLinesOrMoreThan0NewLines(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.excel.models.EaItemGrid.PrepareRedisplay(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.excel.models.EaModelWbApplication.Redisplay(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.excel.views.EaViewManagerSession.OnProcessingFinished(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.common.commands.CoCommandProcessor.OnProcessingFinished(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.core.commands.CrCommandProcessor.OnProcessingFinished(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.common.commands.CoCommandProcessor.CommandPostprocessing(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.common.commands.CoCommandProcessor.InitialCommandExecute(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.common.commands.CoCommandProcessor.DoExecuteCommandInternal(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.common.commands.CoCommandProcessor.DoExecuteCommand(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.core.commands.CrCommandProcessor.DoExecuteCommand(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.controls.ribbonControls.CnRibbonBaseMenu.OnDropDownControlAction(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.controls.ribbonControls.CnRibbonDropdownControl.OnAction(Unknown Source) | |||
cli.com.sap.ip.bi.pioneer.shared.addin2007.Connect.OnDropdownAction(Unknown Source) | |||
| 2014-11-07T11:54:04 | | com.sap.ip.bi.pioneer.common.messagehandling.CoMessenger.WriteToLog() () | ||
- Critical: | 111007 #msl.excp.norestart | | 2014-11-07T11:54:04 | | com.sap.ip.bi.pioneer.common.messagehandling.CoMessenger.WriteToLog() () |
It looks like this is a bug in Analysis around semantic type dates for input variables. The date is a BW date, so VARCHAR(8) e.g. '20130101'.
It's also an input variable in HANA, so has Semantic Type DATE and is mandatory because it's used inside the view for calculation purposes (this period vs last period).
If I type the correct date format in e.g. 20130101, then Analysis rewrites it to 2013-01-01 and then puts a red "exclamation" mark on the left. If I try to select a date then it wont let me click OK. Even weirder, it shows this:
I'm super-surprised by this because Analysis has been really reliable for me in recent months!
Thanks Diego, I have done this and created OSS messages for all 3 corresponding issues (installation, date, calculation)!
In addition, I found that the problem was in this case, I had huge measures as big as DECIMAL(34,3) with numbers as big as:
1,234,567,890,123,456,789.012
Yep that's 22 significant places. These are used because of a retail formula that requires the square of sales price, in rupees. It's an interim calculation that we were using for debugging so I removed it from the model and it all now works.
Thanks for the help
John
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.