on 2013 Oct 07 2:27 AM
Hi ,
I am trying to create a webi report based on SP bEX query directly on BO 4 SP 6 FP 3
1) When i m creating report in BI launch pad getting below error
"while trying to invoke the method com.sap.ip.bi.bics.dataaccess.consumer.queryview.IQvDataCell.getStructureMember(com.sap.ip.bi.bics.dataaccess.consumer.queryview.IQvStructure) of a null object returned from com.sap.ip.bi.bics.dataaccess.consumer.queryview.resultset.IRsDataCell.getDataCell() (WIS 00000)"
2) When i try from WEb I rich cleint get below error
"
com.businessobjects.sdk.core.server.CommunicationException$UnexpectedServerException: CORBA error while communicating with the SL Service: IDL:omg.org/CORBA/NO_RESPONSE:1.0
at com.businessobjects.sdk.core.exception.ExceptionBuilder.make(ExceptionBuilder.java:144)
at com.businessobjects.sdk.core.exception.ExceptionBuilder.make(ExceptionBuilder.java:101)
at com.businessobjects.sdk.core.server.common.CommonRequestHandler.afterProcessing(CommonRequestHandler.java:127)
at com.businessobjects.sdk.core.server.internal.AbstractServer.processIt(AbstractServer.java:178)
at com.businessobjects.sdk.core.server.internal.AbstractServer.process(AbstractServer.java:133)
at com.businessobjects.sdk.core.server.internal.InstanceServer.process(InstanceServer.java:94)
at com.sap.sl.sdk.services.util.ServerRequestProcessor.processServerRequest(ServerRequestProcessor.java:49)
at com.sap.sl.sdk.workspace.service.internal.WorkspaceLoadingService.processWorkspaceRequest(WorkspaceLoadingService.java:99)
at com.sap.sl.sdk.datasource.service.internal.DataSourceLoadingService.loadDataSourceFromServer(DataSourceLoadingService.java:221)
at com.sap.sl.sdk.dataprovider.service.DataProviderServiceImpl.loadDataSource(DataProviderServiceImpl.java:108)
at com.sap.sl.sdk.dataprovider.service.DataProviderServiceImpl.getDataSource(DataProviderServiceImpl.java:76)
at com.sap.webi.qp.abstractlayer.AbstractLayer.loadDataSourceFromDataProvider(AbstractLayer.java:1476)
at com.sap.webi.qp.abstractlayer.AbstractLayer.getDataSource(AbstractLayer.java:363)
at com.sap.webi.ui.data.UniverseQuerySheet.getSheetPanel(UniverseQuerySheet.java:165)
at com.sap.webi.ui.workbench.datamanager.qpframe.QueryTabbedPane$QueryComponent.<init>(QueryTabbedPane.java:108)
at com.sap.webi.ui.workbench.datamanager.qpframe.QueryTabbedPane.addQuery(QueryTabbedPane.java:33)
at com.sap.webi.ui.workbench.datamanager.qpframe.QPWorkBench.addSheet(QPWorkBench.java:178)
at com.sap.webi.ui.workbench.datamanager.qpframe.QPFrame.addSheet(QPFrame.java:304)
at com.sap.webi.ui.workbench.datamanager.qpframe.QPFrame.showQueryPanel(QPFrame.java:233)
at com.sap.webi.ui.context.managers.DataManager.showQueryPanel(DataManager.java:2596)
at com.sap.webi.ui.context.managers.DataManager.editDataProvider(DataManager.java:467)
at com.sap.webi.ui.tasks.workflows.EditDataProviderUITask.doneProcess(EditDataProviderUITask.java:91)
at com.sap.webi.toolkit.ui.tasks.WebITask$PrivateWorker.done(WebITask.java:367)
at javax.swing.SwingWorker$5.run(Unknown Source)
at javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.run(Unknown Source)
at sun.swing.AccumulativeRunnable.run(Unknown Source)
at javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.actionPerformed(Unknown Source)
at javax.swing.Timer.fireActionPerformed(Unknown Source)
at javax.swing.Timer$DoPostEvent.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$000(Unknown Source)
at java.awt.EventQueue$1.run(Unknown Source)
at java.awt.EventQueue$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: com.businessobjects.sdk.core.server.ServerException: CORBA error while communicating with the SL Service: IDL:omg.org/CORBA/NO_RESPONSE:1.0
at com.businessobjects.sdk.core.server.common.CommonRequestHandler.newServerException(CommonRequestHandler.java:260)
at com.businessobjects.sdk.core.server.common.CommonRequestHandler.createAllServerExceptions(CommonRequestHandler.java:238)
at com.businessobjects.sdk.core.server.common.CommonRequestHandler.afterProcessing(CommonRequestHandler.java:121)
"
any suggestion
Thank s
Parul
Hi Paul,
I got the same error yesterday while creating a webi report with Calendar Day Input. It got resolved when I login with Administrator user. The problem was with calendar day format. The calendar day format for my user and admin was different. If you check that calendar day format in our BI User and correct it, then it works fine.
Also check whether all the Web Intelligence Services and Connectivity Services are up in CMC and CCM.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Parul,
As stated by Shabam, Corba Error comes when we have communication dropout between BOE services.
So to narrowdown this problem please share some additional information:
-Does it ever working before or you trying to create WebI report on this BEX for the first time?
-Is the problem same when trying to create the report on any BEX?
-As Ingo asked, do BEX run fine in BW using RSRT T-Code?
-Since the error is coming while creating the report, means Query Panel is also not loading try increasing the XMX of the DSL Bridge APS.
-If my understanding is wrong and problem is coming with refreshing the already created report, add -requestTimeout switch inn WIPS and set its value to an hour or two and observe the behavior.
Hope it will help you.
-Abhi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
RSRT: Bex query is able to run in RSRT
Data Set : not too large
First time creating Webi report on this Bex query
Bex Query is running fine is RSRT and BEx Web
Webi report on other Bex queries are working fine.
My Investigation
=============
While creating Webi report all dimesion are working fine and giving data
in Webi. The moment I include any measure value in Webi Launch Pad i get “invoke the method com.sap.ip.bi.bics. error WIS 00000”.
Regarding BEx query
================
Bex query contains 2 “structure” in column and usage of “cells“
Hi Parul,
I had a similar issue. The problem in my case was, i was not using the BEX Structures in WebI report. If you look at the BEX query in RSRT, you will find that you do not have an option to remove the structures from the drill down. So even in your WebI, you need to follow the same: i.e. you need to keep the dimensional structure (non-key figure structure) mandatorily in the report. If this is missing then you will get the error. After i kept the dimensional structure in my layout, i got the output properly.
P.S. If query stripping is on, then make sure dimensional structure is part of the layout as well and not only in the available objects.
Also, the cell based calculations of BEx can not be consumed in WebI.
Regards,
Piyush
Message was edited by: Piyush Jha
Hi,
are you able to run the BEx query in transaction RSRT in BW ?
Ingo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI parul,
Check Configuration From BI to BO once.
Corba Erorr:
Got hrough below link:
http://scn.sap.com/thread/3352700
http://kb.ivls.nl/index.php?action=artikel&cat=4&id=31&artlang=en
Regards,
Giri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Parul
We get CORBA error when try to fetch huge data from Bex query. Is your bex query fetching huge number of records. Try to filter data at bex query level and try running same report. Run for smaller selection and try.
Please check 1774121 - BI 4.0: CORBA error with Web Intelligence document based on large BEx query (BICS) KBA. We were also getting COBRA error for one of our bex query after splitting bex query output error was resolved.
Regards
Shabnam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
11 | |
10 | |
10 | |
10 | |
8 | |
7 | |
7 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.