BEx Web Analyzer error in Portal

Hi,
I'v integrated the BI 7.0 with Portal 7.0. Both systems (BI and Portal) running on different servers, SSO is configured both ways and RFC communication is configured from ABAP to J2EE. However when i run the BEx Web Analyzer iView under the Business Intelligence role, i get the following error:-
The initial exception that caused the request to fail, was:
     No logical system exists for client 800
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE:      No logical system exists for client 800
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1442)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3962)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3399)
at com.sap.ip.bi.base.application.service.rfcproxy.impl.jco640.Jco640Proxy.executeFunction(Jco640Proxy.java:255)
Caused by: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Jco exception thrown while executing function "RSWR_METADATA_GET" against system "BIXCLNT800"
at com.sap.ip.bi.base.application.service.rfcproxy.impl.RfcFunction.execute(RfcFunction.java:49)
... 44 more
Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE:      No logical system exists for client 800
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1442)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3962)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3399)
at com.sap.ip.bi.base.application.service.rfcproxy.impl.jco640.Jco640Proxy.executeFunction(Jco640Proxy.java:255)
at com.sap.ip.bi.base.application.service.rfcproxy.impl.jco640.Jco640Function.executeRfc(Jco640Function.java:73)
at com.sap.ip.bi.base.application.service.rfcproxy.impl.RfcFunction.execute(RfcFunction.java:47)
... 44 more
Any help on this would be greatly appreciated
-V

Hi Deepu,
All the parameters in the SAP_BW system is correct and i have tested the ITS, WebAS and Connector tests also and everything is green. In the BI diagnostic tool everything was green however in the RSPOR_SETUP the Maintain User Assignment was getting failed, so i removed the UME Master System (Reference system) from the Portal as i'm using the SAP Logon Tickets both ways. So there is no need for the reference system. After that RSPOR_SETUP is okay and in the BI Diagnostic tool one is red (UME Master system).
One thing i have noticed in the RSPOR_SETUP now that it tells me in the second step:-
com.sap.ip.bi Java classes with different versions.
Different ABAP and Java Support packages
ABAP support package 12
Java Support package 11
Vaib
Any clue??
Vaib

Similar Messages

BEx Web Analyzer error message

Hi,
I've integrated BI 7.0 with Portal 7.0. Both systems (BI and Portal) running on different servers, SSO is configured both ways and RFC communication is configured from ABAP to J2EE. However when i run the BEx Web Analyzer iView under the Business Intelligence role, i get the following error:-
The initial exception that caused the request to fail, was:
     No logical system exists for client 800
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE:      No logical system exists for client 800
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1442)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3962)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3399)
at com.sap.ip.bi.base.application.service.rfcproxy.impl.jco640.Jco640Proxy.executeFunction(Jco640Proxy.java:255)
Caused by: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Jco exception thrown while executing function "RSWR_METADATA_GET" against system "BIXCLNT800"
at com.sap.ip.bi.base.application.service.rfcproxy.impl.RfcFunction.execute(RfcFunction.java:49)
... 44 more
Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE:      No logical system exists for client 800
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1442)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3962)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3399)
at com.sap.ip.bi.base.application.service.rfcproxy.impl.jco640.Jco640Proxy.executeFunction(Jco640Proxy.java:255)
at com.sap.ip.bi.base.application.service.rfcproxy.impl.jco640.Jco640Function.executeRfc(Jco640Function.java:73)
at com.sap.ip.bi.base.application.service.rfcproxy.impl.RfcFunction.execute(RfcFunction.java:47)
... 44 more
Any help on this would be greatly appreciated
- V

Priya, ya its already there/..this is the SM50 trace
N dy_signi_ext: ticket expired
N Mon Jun 4 17:57:44 2007
N dy_signi_ext: SSO TICKET logon (client 800)
N mySAPUnwrapCookie: was called.
N HmskiFindTicketInCache: Trying to find logon ticket in ticket cache.
N HmskiFindTicketInCache: Try to find ticket with cache key: 800:BB1DDE5432D1DBECA778E0DC15AA6852 .
N HmskiFindTicketInCache: Couldn't find ticket in ticket cache.
N I don't need to ask RunningCompatibly to know: I'm >= 46C.
N mySAP: Got the following SSF Params:
N         DN     =CN=BIX
N         EncrAlg=DES-CBC
N         Format =PKCS7
N         Toolkit =SAPSECULIB
N         HashAlg =SHA1
N         Profile =/usr/sap/BIX/DVEBMGS20/sec/SAPSYS.pse
N         PAB =/usr/sap/BIX/DVEBMGS20/sec/SAPSYS.pse
N Got the codepage 4102.
N Got ticket (head) AjExMDAgAA9wb3J0YWw6ZXBfYWRtaW6IAAdkZWZh. Length = 492.
N MskiValidateTicket returns 0.
N Got content client = 000.
N Got content sysid = EPX     .
N Got date 200706042239 from ticket.
N Cur time = 200706042257.
N Computing validity in hours.
N Computing validity in minutes.
N CurTime_t = 1181084220, CreTime_t = 1181083140
N validity: 120, difference:   1080.000.
N *** ERROR => HMskiCheckValidity failed. [ssoxxkrn.c   856]
N dy_signi_ext: ticket expired
Vaib

BEx Web analyzer Error

hello,
This is the first time we are using the BEx Web Analyser thru portal
we are recieving following error message. Kindly comment on the same to get it resolved.
- Amit
Root Cause
The initial exception that caused the request to fail was:
More than one master system found: BI7_Alliase, SAP_BW
com.sap.ip.bi.base.service.connection.ConnectionException: More than one master system found: BI7_Alliase, SAP_BW
at com.sap.ip.bi.base.portal.connection.PortalConnectorLandscapeService.getMasterSystemAlias(PortalConnectorLandscapeService.java:137)
at com.sap.ip.bi.base.service.connection.impl.GenericConnectionPool.getMasterSystemAlias(GenericConnectionPool.java:78)
at com.sap.ip.bi.base.service.connection.impl.GenericConnectionPool.getMasterSystemConnection(GenericConnectionPool.java:60)
at com.sap.ip.bi.base.application.impl.Application.createService(Application.java:459)
at com.sap.ip.bi.base.application.impl.Application.getProperty(Application.java:679)
System Environment
Server
BI Java Release: 7 - Patch level: 0000000012 - Description: BI Web Applications Java - Additional info: - Production mode: true
BI ABAP unknown
Java Virtual Machine Java HotSpot(TM) Server VM - Sun Microsystems Inc. - 1.4.2_12-b03
Operating System Windows 2003 - x86 - 5.2
Full Exception Chain
Log ID 000E7F30E8DE0070000001A600003F1000043E0505810C6D
com.sap.ip.bi.base.service.connection.ConnectionException: More than one master system found: BI7_Alliase, SAP_BW at com.sap.ip.bi.base.portal.connection.PortalConnectorLandscapeService.getMasterSystemAlias(PortalConnectorLandscapeService.java:137) at com.sap.ip.bi.base.service.connection.impl.GenericConnectionPool.getMasterSystemAlias(GenericConnectionPool.java:78) at com.sap.ip.bi.base.service.connection.impl.GenericConnectionPool.getMasterSystemConnection(GenericConnectionPool.java:60) at com.sap.ip.bi.base.application.impl.Application.createService(Application.java:459) at com.sap.ip.bi.base.application.impl.Application.getProperty(Application.java:679) at com.sap.ip.bi.base.application.impl.Application.startApplicationStep(Application.java:279) at com.sap.ip.bi.base.application.impl.Application.initialization(Application.java:259) at com.sap.ip.bi.base.application.ApplicationFactory.createApplication(ApplicationFactory.java:172) at com.sap.ip.bi.base.application.ApplicationFactory.createApplication(ApplicationFactory.java:65) at com.sap.ip.bi.webapplications.runtime.impl.Page.constructPage(Page.java:857) at com.sap.ip.bi.webapplications.runtime.impl.Page.<init>(Page.java:734) at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.createPage(Controller.java:493) at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:886) at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:813) at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:456) at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:21) at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209) at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114) at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328) at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136) at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189) at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215) at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645) at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328) at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136) at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189) at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753) at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240) at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522) at java.security.AccessController.doPrivileged(Native Method) at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Looks like in the EP System Landscape you have 2 BI systems defined and both systems are defined as Master Systems. This is a property of the System. Make sure you set only one system as the Master system. There should be a one to one mapping between the EP and BI System.

Error while accesing Bex web analyzer from business planning

Hi all,
we   are using portal 7 sp 15   and   bi 7 sp 17 . we are able to view planning modeller and planning wizard through portal . but while accessing bex web analyzer it is giving following error
#1.5 #000BCD3C982F005C000001B600000BF800045C6B167F037F#1227514915483#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#redekarr#11320##n/a##f08aaf90ba0011dd8a39000bcd3c982f#SAPEngine_Application_Thread[impl:3]_13##0#0#Error#1#/System/Server#Java###Exception ID:01:51_24/11/08_0049_17771650
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : com.sap.ip.bi.web.portal.integration.launcher
Component class : com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent
User : redekarr
     at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: java.lang.NoClassDefFoundError: com/sap/ip/bi/base/application/message/MessageException
     at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:334)
     at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:24)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     ... 29 more
#1.5 #000BCD3C982F005C000001B800000BF800045C6B167F35A1#1227514915514#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#redekarr#11320##n/a##f08aaf90ba0011dd8a39000bcd3c982f#SAPEngine_Application_Thread[impl:3]_13##0#0#Error##Java###01:51_24/11/08_0049_17771650
[EXCEPTION]
#1#java.lang.NoClassDefFoundError: com/sap/ip/bi/base/application/message/MessageException
     at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:334)
     at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:24)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
can any body help?
Rajendra

Thanks.
This is the error i found in trace file for excepption id got while accessing from portal Business planning----Bex Web Analyzer iview.
Rajendra

Error message...while accessing the BEx Web Analyzer on EP7

hi experts,
i have deployed and configured BI java on portal server.and while accessing the roles from portal(ep7) ,for the BEx Web Analyzer getting the error message as shown below.but the other two i.e. planning wizard and planning modeller are running fine.is there is some problem while configuring or while deploying files on the portal server..please help me in this case.
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
Could not find portal application com.sap.ip.bi.km.base.
Exception id: 10:32_28/02/08_0069_19249950
See the details for the exception ID in the log file

Hi Rohini,
Let me know, have you got the right authorization to do this transaction. Check your profile, if you are using for a long while, check whether you have changed any user settings.
Good luck
Om
Reward it, if u feel helpful.

BI 7 Portal - BEx Web Analyzer- URL used is not fully qualified.

Hi folks,
I have a problem while accessing BEx Web Analyzer on BI 7 Portal. When I select "Business Intelligence" -> "BEx Web Analyzer". This is ending up with a 500 Internal Server Error
Error Description
com.sap.ip.bi.base.exception.BIBaseRuntimeException: URL +used, "http://sdndevsap01:51200", is not fully qualified. +
A fully-qualified URL has a schema with the format "<protocol>://server.company.com:<port>". URLs with the format "<protocol>://server:<port>" or "<protocol>://<ip address>:<port>" are not fully qualified. See SAP Notes 581329, 596698 and 654326
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest
+(Page.java:2535) at + com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:978)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:864)
Pls Note:
-The parameter "icm/host_name_full" is already set with full hostname with domain. (Hostname.domain)
-I have also checked the SAP notes mentioned in the error and did not find any answer from them.
As per my understanding there should be a parameter which holds the portal link in JAVA Engine.(http://hostname.domain:50000/)
Pls help me in finding answer to this.
Thanks
James.
Edited by: James Best on Mar 5, 2008 8:13 AM

ur questions 1 and 2 should be directed to portal administrator at ur firm..
as u r trying to change the lay out when user presses New analysis.
again in 2 u want to default the saving to favourites folders.
3. if u save a view and later u try to open or run another query ..
for e.g. in ur saved view of query1 the time period is 1/07-12/07
now u r running some query x which has time 1/08-4/08
and now if u try to open ur view of query-1 then it will take the time period of 1.08---4.08
but if u open bookmark it will bring it to u the xact screen and xact time variables with which u save query1

BEx Web Analyzer - runtime error

I am running a query on BEx Web analyzer on local test WAS and getting runtime error below. The WAS is in on SP8 and BI on SP11. Is SP mismatch the problem?
>
Exception in BI runtime
A:RSBOL:016 1 2
Log ID: C000C0A80065009C0000000A000000B8000425994A2836C9
Initial cause
Message:
Termination message sent ABEND RSBOL (016): A:RSBOL:016 1 2 MSGV1: 1 MSGV2: 2
Stack trace:
com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException: Termination message sent ABEND RSBOL (016): A:RSBOL:016 1 2 MSGV1: 1 MSGV2: 2

The error is because Java @ SP 8

Problem accessing BEx web analyzer

All,
I just created a new user in portal and assigned (only) three roles Business Explorer, Business Intelligence and Business Planning.
After logging in as this new user, when I open Business Explorer>BEx Web Analyzer, I get an error and after going through error trace, I found this detail.
05:16_06/04/09_0004_7654950
[EXCEPTION]
com.sapportals.portal.pcd.gl.PermissionControlException: Access denied (Object(s): com.sap.portal.system/security/sap.com/NetWeaver.BI/low_safety/com.sap.ip.bi.web.portal.integration/components/launcher)
     at com.sapportals.portal.pcd.gl.PcdFilterContext.filterLookup(PcdFilterContext.java:422)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1248)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookupLink(PcdProxyContext.java:1353)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookup(PcdProxyContext.java:1300)
     at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:1067)
     at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:68)
     at com.sapportals.portal.pcd.gl.PcdURLContext.lookup(PcdURLContext.java:238)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.sapportals.portal.prt.deployment.DeploymentManager.checkPermissions(DeploymentManager.java:2000)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:251)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
     at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
     at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:488)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Please help me solving this issue. What else are the roles I need to assign to this user?
Thanks.

No response.. and I dont need it now.

Can not work with BEx Web Analyzer correctly

Hi all,
When I go into the link of BEx web analyzer in portal, an error raised.
 URL used, 'http://<myhost>:<port>', is invalid;Distributed session management(DSM) cannot function. See sap notes 596698 and 654326.
And I've seen the notes in SAP, and got the reason why this error happens, but exactly I just install NW2004s in my local PC and did not have any domain name.
What should I do about this case?
Helpful info will be awarded.
BR
Bob

Hi,
Try to set RSADMIN parameter ALLOW_MULTI_DP_RESET=X
This note may give you some insight on the issue.
1581923 - BEx Web: Optimization on Back with Many Data Providers
Regards,
Suman

How to increase the number of rows to be displayed in BEx Web Analyzer

hi,
I am viewing reports using BEx Web analyzer option. It is displaying only 24 rows of data at a time. How to increase the number of rows? do i need to any kind of settings?
pls reply.

Hi,
I think the standard template in 2004s is named 0ANALYSIS_PATTERN. You can find it in Web Application Designer, open, and search for the technical name. If you want to change the number of rows or columns, you can find this setting near the bottom of the XHTML view of the template:
<bi:BLOCK_COLUMNS_SIZE value="4" />
<bi:BLOCK_ROWS_SIZE value="17" />
Then just save, and ignore the error messages.
Message was edited by:
vind Reinsberg

Error: BeX-Web Application Error

Hi All,
while running the dashboard which is integrated with Enterprise portal, we are getting the below error.These dashboards consumes data from the BEX query directly using the SAP Netweaver connection Type.
Error Desc: BeX-Web Application Error
Please find the more details in the attached sheet. can any one help me out to resolve this issue

Hi
Check weather BO system is up or not

Can you change the Graphs Colors in BEx Web Analyzer?

Dear All,
I have few queries I have developed via BEx Query Designer which I am opening from BEx Web Analyzer in portals. Unfortunately the colors in the Graphs are not very pleasant. I was wondering if there is a way we can customize the colors which is given by the standard.
I am aware that we can do this is BEx Report Designer. But I would like to do this is BEx Query Designer.
Please help..
Cheers,
Shanka

Hi Shanka,
There is no option as such in BEx Query Designer.
You can manipulate and play with colors only in Report designer or Web Application Designer.
In Bex Query designer, you will find only exceptions which are related to colors but chart colors cannot be manipulated in query designer.
If you are executing the report in workbook, you can change accordingly as it is excel.
Regards,
KK.

Using of Bex Web Analyzer as Adhoc query?

Hi,
can we use the Bex Web analyzer as a preferred tool for designing the Adhoc query?
Points willl be definitely assigned.

Hi Vasu,
You can create an appropriate ad hoc query to specify parameters for Web target iViews.
In logical SAP R/3 Systems of Release 4.6B or higher, transaction SPO0 contains an Ad hoc Query tab. This uses the concept of InfoSets, which are usually based on table joins or logical databases, to create abstract definitions for fields that the system can read. You have to enter parameters for the individual fields. The ad hoc query delivers values that can be passed to the portal.
Transaction SPO0 also contains a buffer for ad hoc queries. This improves system performance by avoiding the need to put together the query every time it is used.
You can delete the contents of this buffer by choosing Delete Buffer for AdHoc Query on the start screen of transaction SPO0. This removes the index entry and the generated queries from the system.
Hope this will help you.
Kind regards,
Praveen

BEx Web Analyzer - SAVE AS button

Hi,
When you click on SAVE AS button in the BEx Web Analyzer, a pop-up window brings up with 3 tabs (Favorites, BEx Portfolio and My Portfolio). When you click on the BEx Portfolio, it brings the Portal KM Folders under "Public Documents" folder. That means, the BEx Portfolio here is pointing to "Public Documents" folder.
Could anyone please let me know HOW TO CHANGE THIS CONFIGURATION?
I want to point this to a new KM folder. Is this configuration done in Portal or SAP BW?
Your help is really appreciated.
Thanks

I search a long time, I can say you can't ! Public Documents is hardcoded into the webanalyser.
As workoround, I made some link into 'Public Documents' to other folders into the KM folder's strucure. So for each project, people can save documents into their own folder with their own access rights
CU JM

Problem with '-' (dash) in BEx web analyzer

Hi All,
we are having a strange problem with 0BPartner and 0Material. Our BPartner and Material have '-'(dash) sign as part of key. While selecting this BPartner/Material in Bex Analyzer, we do not have any problem, but when we try to select the same Bpartner/Material in BEx Web Analyzer, it puts an escape char in from of the dash. For eg:
If i select the Bpartner "1234-5467" then in Web Analyzer selection box, it is displayed as "1234\-5467" in the selection screen.
If i do a search on 1234-5467, it returns zero value.But if i do a search on 1234\-5467, then i get the search hit.
If i enter the Bpartner in the selection window directly and If i do not put the escape char, then it considers the input as range 1234 - 5467 and returns me no value in the report output.
Has anyone had this type of issue? Please respond.
Thanks
Niveda

Thanks Olivier,
Sorry if you had misunderstood my question. They are 2 different Info objects. and i am having problem searching values in each one of these info objects.
Let me explain it with an example.
Scenario:
Let say company defines material in the following format.
"123", "456", "788", "345"....etc.
And I have a report which has material as input selection.
To run this report with single material i enter "123" in the selection screen
To run this report with a range of materials, I need to enter 123 - 456 in the selection.
I have no Issues
Scenario 2.
Consider a case if the materials are defined in SAP as "001-1234", "987-234"
"123-234" etc.
In this scenario, to run the same report for 1 material, i will enter 001-1234. But now the question is how will BW system interpret this material entry.
Is this 1 single material(001-1234) or a material range (001 - 1234)??
We have issue here. The system considers this material "001-1234" as a range (001 to 1234) instead of single material and gives me zero output.
Any help??
Niveda

BEx Web Analyzer error in Portal

Similar Messages

Maybe you are looking for