Error on BEx Web Anallyzer over Portal (roles)

Hi gurus:
We ve implemented BI 7.0 with portal 7.0 , some queries r saved on a rol which is shown on Portal-BI-BEx Web Analyzer-New Analysis, it works ok so far, but something happened (looks like some queries were deleted from role) so every time I click on role (inside tab "Rol" on portall-bew web analyzer) it shows my queries but it also show a message saying :
You have attempted to open query BUYMEXC08A9T9TB4HV4VQR8N5 from the Query Designer. However, this query does not exist in the database in the system to which you have made a connection.
System Response
Opening the query was terminated.
Procedure
Make sure that you have connected to the correct BW system. Note: The query may have been deleted by another user.
It looks like porta is searching a query that doesnt exist anymore, what can I do to solve this? refresh or restart some service on portal ?
best regards
joker

Hi,
Is this query assigned to any web template. And have you assigned this web template to the Bex Web Application Query String property in the property editior for that iview, something like cmd=ldoc&TEMPLATE_ID=WAD_01
In case, if this template has been deleted, then you will have to re-create this template and assign the query string to this template.
How about the system given for BI connection ? Is it working fine.
Please test all of the above and let me know.
Thanks,
Nikhil

Similar Messages

ORA-28868 error when calling Web service over HTTPS from PL/SQL utl_http

I am getting error message ORA-28868 error when calling Web service over HTTPS from PL/SQL utl_http PL/SQL package,
when browsed through some of the messages they point to setting Oracle Wallet Manager.
I am trying to connect
Any idea on how to resolve this issue ?
your input is appreciated.
Thanks
Ravi

Duplicate post ... please ignore.

Error in BEx Web Application Iview in Portal

Hello All,
I am trying to access a query from the BI NW2004s (Ver 7.0)in EP 7.0 and i have created a BEx Web application Iview and have specified the proper Query/Template , but i am not able to preview the output on Iview and getting the following error in Iview
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
iView not found: com.sap.ip.bi.web.portal.integration.launcher.
Exception id: 05:52_11/10/06_0006_17835450
See the details for the exception ID in the log file
Further to add is that when i access the same BI application using the URL Iview, it's wokring absolutely fine. Can somebody identify the problem with the BEx Web Application Iview and suggest a suitable remedy for the same??.
Thanks in advance.
Regards,
Sarabjeet.

Hello,
You can download these components from Service Market Place (service.sap.com/swdc) and:
Download -> Support Packages and Patches -> Entry by Application Group -> "Support Packages and Patches" -> "SAP NetWeaver" -> "SAP NETWEAVER" -> "SAP NETWEAVER 2004S" -> "Entry by Component" -> "BI Java":
BI BASE SERVICES 7.00
BI WEB APPLICATIONS 7.00
You have to download the SP that equals your APAP SP.
Normally, these SCAs will be installed with installation of "BI Usage Type" of the J2EE engine.
Regards, Karol Kalisz
SAP BI Development

RSBOLAP 018 Java system error in BEx Web Application Designer

Hello,
while doing inside BEX Web Application Designer "validation of webtemplate" with
command "validate on server" I get following error message of WAD :
" Message RSBOLAP 018 description : Java system error : an Unknow Error occured during portal communication"
My procedure till now was ( please see results as screenshots in attachment) :
a) ckecking prerequisites for "Java template installer'" --> result "prerequisites.jng"
b) running "Java template installer" -> " result templateInstaller.jpg"
c) running Bex Web Application Designer as mentioned above results in error
message as mentioned above
d) running Diagnostic & Support Desktop Tool --> "result Diagnostic support desktop tool.jpg"
It says that something is wrong with "BI Mastersystem" because of failed connect to
message server.
Please advice me what I should do.
Thanks in advance
Regards,
Oscar

Hello
It is obvious that the connection between the ABAP and the Java is not working.
There should be a JCo RFC from the portal side to the ABAP stack set up and an RFC from the ABAP stack to the portal.
Check the entries of the table RSPOR_T_PORTAL
The RFC specified here should be the one mentioned above (ABAP - Java)
Check the name of the system should be SAP_BW
Is the parameter icm/host_name_full set on the ABAP stack with the domain name ?
Connect to the BI portal:
http://FQDN:5NN00/irj/portal
Navigate to system administration -> system configuration -> system landscape -> expand "portal content" -> systemlandscape -> SAP_BW
Right click on SAP_BW - Open - Object
Here you need to maintain these:
ITS Description - BW ABAP Logical System Name - Tx SCC4 or BD54
ITS Host Name - FQDN_OF_BW_ABAP:port - You can use the value of icm/host_name_full parameter and retrieve port number from Tx SMICM - Services
ITS Path - /sap/bc/gui/sap/its/webgui
ITS Protocol - Select http
Logical System Name - BW ABAP Logical System Name - Tx SCC4 or BD54
Logon Method -SAPLOGONTICKET
Message server - BW ABAP FQDN
SAP Client - BW ABAP Client Number
SAP System ID (SID) - BW ABAP SID
Server Port - 39NN
Web AS Description - BW ABAP Logical System Name - Tx SCC4 or BD54
Web AS Host Name - FQDN_OF_BW_ABAP:port - icm/host_name_full and retrieve port number from Tx SMICM - Services
Web AS Path - /sap/bw/BEx
If everything is set properly then do a test connection.
Good Luck
RB

Error exectuing BEx Web Application Designer

Hi All,
I am working with BEx in BI 7.0 and while creating and executing my web template i happened to get this error.
"Error in the communication with the Portal that may at least partly cause this issue.
This is likely to be caused by portal unavailability or a configuration issue."
Can anyone guide me how to solve this problem?
I need some help in this regard.
Regards
Andrew

Closed.Got it solved.

Error while consuming web service in portal component

Hi All,
I am working on a portal application which uses web services in portal component via web service.
I have tested the web service and then creted a relevant portal service to it .When using this portal service in the portal component and running it Im getting the following run time error
Portal Runtime Error
An exception occurred while processing a request for :
iView : Test_portal_service_app.Test_portal_service_app
Component Name : Test_portal_service_app.Test_portal_service_app
com.sap.portal.ivs.global.ume.UMECLient.
Exception id: 11:17_03/07/08_0028_2739150
See the details for the exception ID in the log file
I did not use any ume attributes or ume api methods in the portal component .
I have also added sharingreference= portalserviceapplication name in deploymentdescriptor of the portal application which has the portal component.
Please provide any suggestion for the possible cause of error .
Urgent!!!!
Thanks.

Hi all,
Please throw some light into this issue i am getting the following exception.
com.sap.engine.services.webservices.jaxm.soap.accessor.NestedSOAPException: Problem in server response: Proxy Authentication Required.
I have given the proxy settings in the com.sap.portal.ivs.httpservice in the portal and also
defined a proxy server in the Visual Administrator under Services -> Webservice Container -> HTTP Proxy Server
I am calling service in the following manner.
IPortalRuntimeResources runtime = PortalRuntime.getRuntimeResources();
   IService service = runtime.getService(IWS_P_Service.KEY);
   IWS_P_Service ws_service = (IWS_P_Service)service;
    Volumes from = new Volumes(Volumes.VOLUMES_KILOLITER_VALUE);
    Volumes to = new Volumes(Volumes.VOLUMES_LITER_VALUE);
    ChangeVolumeUnit cvu = new ChangeVolumeUnit(1200,from,to);
    // working upto here
     response.write("working");
     ChangeVolumeUnitResponse cvu_res = ws_service.ChangeVolumeUnit(cvu);
     double result = cvu_res.getChangeVolumeUnitResult();
     response.write(result+"");
It is working upto "working".
If any body has any solutions please post.
Thanks

BAD_CERTIFICATE error calling a web service over SSL in ALSB 2.6

We have a business service on an ALSB 2.6 server (running on WL 9.2.1) that connects to a web service over SSL. When we try to run it, we get the following exception:
<Sep 17, 2009 7:49:17 AM PDT> <Error> <ALSB Kernel> <BEA-380001> <Exception on TransportManagerImpl.sendMessageToService, com.bea.
wli.sb.transports.TransportException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
com.bea.wli.sb.transports.TransportException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
at com.bea.wli.sb.transports.TransportException.newInstance(TransportException.java:146)
at com.bea.wli.sb.transports.http.HttpOutboundMessageContext.send(HttpOu
tboundMessageContext.java:310)
at com.bea.wli.sb.transports.http.HttpsTransportProvider.sendMessageAsync(HttpsTransportProvider.java:435)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
Truncated. see log file for complete stacktrace
javax.net.ssl.SSLKeyException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
Truncated. see log file for complete stacktrace
This exception only occurs when hitting the web service through the bus. I have written a standalone Java application that posts to the web service and it works fine. I ran the application on the server where the ALSB is running using the same jdk (1.5.0_06 - the version that ships with 9.2.1) and the same cacerts file so I know it's not a problem with the certificate not being trusted. I have tried updating the cacerts file to the latest one distributed with JRE 1.6 and it still doesn't work.
After 8 hours of troubleshooting, I'm out of ideas. Does anyone have any suggestiosn?
Thanks.
Matt
Edited by: user6946981 on Sep 17, 2009 7:58 AM

Are you sure that your standalone application is using the same keystore (eg. cacert)? Default WebLogic configuration uses different keystore (demo).
I saw BAD_CERTIFICATE error only once and the cause was in keytool that somehow corrupted certificate during import. Deleting and importing certificate again helped me, but I doubt you have the same problem as your standalone application works.
Another idea ... Is hostname varification used? I know that the error message would look different if this was the cause, but try to add this parameter to your weblogic startup script: -Dweblogic.security.SSL.ignoreHostnameVerification=true
Last but not least, there is difference between your standalone application and ALSB runtime as WebLogic uses Certicom SSL provider. If you don't find the reason, contact Oracle support. Maybe they can help you to tweak Certicom provider in some way.

Error calling external web service over HTTPS

Hi everyone
I'm trying to call an external web service over HTTPS, and continually get the following error:
com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException: Peer sent alert: Alert Fatal: handshake failure
I haven't tried doing this before, so not quite sure where to start. I have a client certificate that must be used to access the remote web service, and I think the problem is associating the client cert with the web service call.
Has anyone else tried this before? Any suggestions of where to look?
I've had a brief look at Key Storage in NWA, but it's not something I'm familiar with - so not sure if it's even the right place to be looking.
Some help on this would be great!
Thanks
Stuart

Thanks Aleksandar
Here's the output from the trace. Unfortunately the SAP forums don't allow attachments, so it may be difficult to read. Please let me know if you see anything that may help.
Thanks
Stuart
Time Severity User Thread Location Message
09:18:23:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:23:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@fa1b67
09:18:24:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:24:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@4c8af
09:18:24:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:24:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@b6981b
09:18:25:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:25:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
09:18:25:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:25:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
09:18:26:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:26:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider [com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider] 'nonProxyHosts' are configured '10.|127.|192.168.*'.
09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider [com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider] 'nonProxyHosts' default value is '10.|127.|192.168.*'.
09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider Loadin mapping file from location :[c:/mapping.txt]
09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider Additional file for CTS configuration can not be found [c:\mapping.txt (The system cannot find the file specified)].
09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider >>>>>>>>> ERROR: Could not find mapping for service QName=vipSoapInterfaceService, class=class com.verisign._2006._08.vipservice.VipSoapInterfaceService
09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider: Creating client instance with WSDL URL [https://pilot-vipservices-auth.verisign.com:443/prov/soap/val/soap] (vipSoapInterfaceService) <com.verisign._2006._08.vipservice.VipSoapInterfaceService>
09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider: Using SAP JAX-WS Implemetation to create service delegate.
09:18:26:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:26:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@5586b0
09:18:26:687 Path Administrator HTTP Worker [0] ~s.espbase.wsdl.exceptions.WSDLException Exception : Peer sent alert: Alert Fatal: handshake failure
java.lang.Exception
at com.sap.exception.BaseExceptionInfo.traceAutomatically(BaseExceptionInfo.java:1230)
at com.sap.exception.BaseExceptionInfo.<init>(BaseExceptionInfo.java:147)
at com.sap.exception.BaseException.<init>(BaseException.java:89)
at com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException.<init>(WSDLException.java:34)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:140)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:91)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:80)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.loadWSDLDefinitions(SAPServiceDelegate.java:201)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.initWSDL(SAPServiceDelegate.java:159)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.<init>(SAPServiceDelegate.java:113)
at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createDelegate(CTSProvider.java:170)
at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createServiceDelegate(CTSProvider.java:151)
at javax.xml.ws.Service.<init>(Service.java:57)
at com.verisign._2006._08.vipservice.VipSoapInterfaceService.<init>(VipSoapInterfaceService.java:41)
at JEE_jsp_result_6740550_1225116575421_1225116585468._jspService(JEE_jsp_result_6740550_1225116575421_1225116585468.java:64)
at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:433)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:240)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
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:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: org.w3c.www.protocol.http.HttpException: Peer sent alert: Alert Fatal: handshake failure
iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: handshake failure
at iaik.security.ssl.r.f(Unknown Source)
at iaik.security.ssl.x.b(Unknown Source)
at iaik.security.ssl.x.a(Unknown Source)
at iaik.security.ssl.r.d(Unknown Source)
at iaik.security.ssl.SSLTransport.startHandshake(Unknown Source)
at iaik.security.ssl.SSLTransport.getOutputStream(Unknown Source)
at iaik.security.ssl.SSLSocket.getOutputStream(Unknown Source)
at org.w3c.www.protocol.http.g.markUsed(Unknown Source)
at org.w3c.www.protocol.http.HttpBasicServer.getConnection(Unknown Source)
at org.w3c.www.protocol.http.HttpBasicServer.runRequest(Unknown Source)
at org.w3c.www.protocol.http.HttpManager.runRequest(Unknown Source)
at org.w3c.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at org.w3c.www.protocol.http.HttpURLConnection.a(Unknown Source)
at org.w3c.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at java.net.URL.openStream(URL.java:1007)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:201)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:263)
at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:282)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:293)
at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:146)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:132)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:91)
at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:80)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.loadWSDLDefinitions(SAPServiceDelegate.java:201)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.initWSDL(SAPServiceDelegate.java:159)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.<init>(SAPServiceDelegate.java:113)
at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createDelegate(CTSProvider.java:170)
at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createServiceDelegate(CTSProvider.java:151)
at javax.xml.ws.Service.<init>(Service.java:57)
at com.verisign._2006._08.vipservice.VipSoapInterfaceService.<init>(VipSoapInterfaceService.java:41)
at JEE_jsp_result_6740550_1225116575421_1225116585468._jspService(JEE_jsp_result_6740550_1225116575421_1225116585468.java:64)
at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:433)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:240)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
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:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
09:18:27:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:27:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@20ba3c
09:18:27:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:27:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
09:18:28:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:28:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@26e3bf
09:18:28:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:28:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
09:18:29:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:29:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@f827f6
09:18:29:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:29:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@a8646a
09:18:30:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:30:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
09:18:30:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:30:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@c449f1
09:18:31:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
09:18:31:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
09:18:31:593 Info Administrator HTTP Worker [3] System.out SessionImpl::getContext():[ B E G I N ].timerId=15
09:18:31:593 Info Administrator HTTP Worker [3] System.out SessionImpl::getContext():[ E N D ].timerId=[id:#15, elapsed: 0 ms.]

How to assign a Bex Web template to a role?

Hi Guys,
How to assign a web template to a role? I have created a role from PFCG but i dont see this role when i open the Bex Web application designer to assign the role using the menu option
choose Web Template --> Publish --> In Role.
what needs to be done to make the role available under the above menu?

HI,
look into this....
http://help.sap.com/saphelp_nw04s/helpdata/en/43/8483a350b130f3e10000000a11466f/frameset.htm
Thanks

Bex error after launching Web Template to Portal

After execution of any Bex template from BW system . It launches it into portal but after login the result is displayed but with an error
:- The metadata data of ITE "TEMPLATE_PARAMETERS" are incorrect for parameter STARTSTATELESS_INTERVAL"
NW2004s , BI 7.0 level 12 ---in BW system
Portal 7.0 with BI-IBC, BI-BASE-S, BI-WEBAPP patched to SP 12 and rest of all the components are SP 11.
defaultTrace file
ERROR
The metadata of "ITE" "TEMPLATE_PARAMETERS" are incorrect for parameter "START_STATELESS_INTERVAL"
com.sap.ip.bi.metadata.impl.MdUtils MdUtils_0003
ITE
TEMPLATE_PARAMETERS
START_STATELESS_INTERVAL
The parameter "START_STATELESS_INTERVAL" in the metadata of "ITE" "TEMPLATE_PARAMETERS is not correctly defined:
<parameterList>
<param name="BODY_ONLY" value="X"/>
<param name="CHECK_POPUP_BLOCKER" value="X"/>
<param name="DATA_MODE" value="NEW"/>
<param name="DOCUMENT_SAVE_LEVEL" value="0"/>
<param name="ERRORS_VISIBLE" value="X"/>
<param name="INFORMATION_VISIBLE" value="X"/>
<param name="ITEMS_STATELESS" value="false"/>
<param name="MELT_VARIABLES" value="X"/>
<param name="REPORT_REPORT_DISPLAY_TARGET" value="X"/>
<param name="RRI_OPEN_MODE" value="OPEN_IN_SEPARATE_WINDOW">
 <param name="OPEN_IN_SEPARATE_WINDOW" value=""/>
</param>
<param name="START_STATELESS_INTERVAL" value="0"/>
<param name="STATELESS" value="false"/>
<param name="SYSTEM_MESSAGES_VISIBLE" value="X">
 <param name="SYSTEM_MESSAGES_DISPLAY_MODE" value="ALWAYS"/>
</param>
<param name="TEMPLATE_VERSION" value="1"/>
<param name="USE_CONTEXT_MENU_SNIPPETS" value="X"/>
<param name="USE_PERSONALIZATION" value="X"/>
<param name="USE_SPECIFIC_VARIANT_CATALOG" value="X"/>
<param name="WARNINGS_VISIBLE" value="X"/>
<param name="WINDOW_MODE" value="modal"/>
</parameterList>
com.sap.ip.bi.metadata.impl.MdUtils MdUtils_0002
ITE
TEMPLATE_PARAMETERS
START_STATELESS_INTERVAL
Wat is the cause of this error .How can it be resolved?
Please help.

Hi everybody,
I have the same problem:
" The metadata of "ITE" "TEMPLATE_PARAMETERS" are incorrect for parameter "START_STATELESS_INTERVAL"
NW2004s
ABAP BW SP 15
Portal SPS 13
What is the solution or explanation?
Thanks
Alexandre

Procedure to Publish BI Web Reports in Portal Roles

Hi,
I've created close to 20 Web Reports and need to make those available for Users through Portal. There are different sets of Users, such that one set can access only half, rest can access remaining. I know this can be achieved by creating separate Reporting User Roles, but need help with below points:
1. Our basis team are not familiar with BI7 Role maintenance, thus would anyone share the Reporting User Roles design (i.e. which authorization objects to assign).
2. When I open a Web Template in WAD, the menu Publish -> "in Role" is disabled. Should this be enabled to publish a web report in role or is there any other way?
Please let me know.
Regards,
Vikrant.

Hii Jazz,
Replying after a long time..
I think the following doc can be helpful to you : page - 5 Frameset similar scenario is implemented.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/1035ca90-0201-0010-13b7-9a35063d6a18
Hope this helps.
Sonal.....

Error while invoking web service over SSL

While making a SSL Connections to web service i am getting the below mentioned error in spite of configuring the certificate provided by the client onto WLS.
I tried adding the certificate to the default DemoTrust and DemoIdentity Keystores. The error still persisted.
I also tried importing the certificate(into cacerts keystore) as Java Standard Trust as well as tried pointing it to the custom keystores. None of it worked :(
Could somebody please give a solution to resolve this error ASAP.
The error is:
Message:exception occured, due to org.apache.axis2.AxisFault: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
org.apache.axis2.AxisFault: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
     at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:83)
     at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java:84)
     at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:499)
     at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2114)
     at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
     at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
     at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
     at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
     at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
     at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:542)
     at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:199)
     at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:76)
     at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:400)
     at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:225)
     at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:435)
     at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
     at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
     at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
     at com.intel.services.warrantyservice.Get_Warranty_Details_OutServiceStub.get_Warranty_Details_Out(Get_Warranty_Details_OutServiceStub.java:184)
     at com.intel.www.PortalServices.PortalServicesSOAPImpl.getWarrantyDetails(PortalServicesSOAPImpl.java:1865)
     at com.intel.www.PortalServices.PortalServicesSOAPSkeleton.getWarrantyDetails(PortalServicesSOAPSkeleton.java:213)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
     at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
     at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
     at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
     at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
     at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3590)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.xml.stream.XMLStreamException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at weblogic.xml.stax.XMLWriterBase.flush(XMLWriterBase.java:504)
     at org.apache.axiom.om.impl.MTOMXMLStreamWriter.flush(MTOMXMLStreamWriter.java:168)
     at org.apache.axis2.databinding.utils.writer.MTOMAwareXMLSerializer.flush(MTOMAwareXMLSerializer.java:79)
     at org.apache.axis2.databinding.ADBDataSource.serialize(ADBDataSource.java:94)
     at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerializeAndConsume(OMSourcedElementImpl.java:738)
     at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:966)
     at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:995)
     at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(SOAPEnvelopeImpl.java:254)
     at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:242)
     at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:995)
     at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:486)
     at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:79)
     ... 48 more
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1591)
     at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:187)
     at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:181)
     at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1035)
     at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:124)
     at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:516)
     at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:454)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:884)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1096)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:623)
     at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59)
     at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
     at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
     at org.apache.commons.httpclient.ChunkedOutputStream.flush(ChunkedOutputStream.java:191)
     at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:278)
     at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:122)
     at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:212)
     at java.io.BufferedWriter.flush(BufferedWriter.java:236)
     at weblogic.xml.stax.XMLWriterBase.flush(XMLWriterBase.java:502)
     ... 59 more
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:285)
     at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:191)
     at sun.security.validator.Validator.validate(Validator.java:218)
     at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:126)
     at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:209)
     at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249)
     at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1014)
     ... 74 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:174)
     at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:238)
     at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:280)
     ... 80 more

Which version/platform are you using?
The thing you need to consider here is that the JDev proxy settings do not affect the BPEL server.
So if the BPEL server cannot connect to your webservice, it will not be because of any Jdev setting.
Check the proxy settings on your BPEL server (on 10.1.2 developer install it will be in obsetenv.bat, on 10.1.3 it will be a commandline property of the JVM - see AS Control administration page for the JVM)

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

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.

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

Error on BEx Web Anallyzer over Portal (roles)

Similar Messages

Maybe you are looking for