Skip to Content
In this my first blog i explain a solution about a problem that can be appear during the creation of a SAP NetWeaver BW connection on Xcelsius.

 

First at all, I would remember the basis requirement’s for create a SAP BW connection on Xcelsius:·        

  • on the client side : Xcelsius Enterprise Designer 2008 SP2 (trial or engage versions do not offer this connectivity) and SAP GUI patch 901 or above·        
  • on the server side : NW 7.0 EhP1 SP5 with ABAP and Java stacks. 

The problem that can be raised during the creation of SAP Netwever BW connection on Xcelsius is the popup window with the mysterious error message: #2032:

 

error

 

To find the cause of this error,  i have  monitored the HTTP request and  HTTP response during the creation of a SAP BW connection on Xcelsius by  freeware software Fiddler2  that it can download by this link: http://www.fiddler2.com/.  
By this software, I finded the reason behind the error message #2032:  Xcelsius wasn’t able to translate the host name of SAP BW application server to a valid IP address .

fiddler result

So as a workaround, i have written a map rule for the hostname used by Xcelsius ( that in the example image is server.ibi.it )  and the IP address of SAP BW application server in the hosts file. 

 

 

 

The hosts file’s is  a computer file used in an operating system to map hostnames to IP addresses and his location is: %SystemRoot%\system32\drivers\etc\. 

Then i created a  SAP Netweaver BW connection on Xcelsius with successful.

connection Xcelsius - SAP BW

To report this post you need to login first.

17 Comments

You must be Logged on to comment or reply to a post.

  1. Andrew Barker
    Hi, great blog with an approach I’ve never seen before.

    I had the same mysterious error and solved it through changing the default port of our SAP NetWeaver Portal in table RSPOR_T_PORTAL. I was accessing the queries through VPN and the port was internal only. I didn’t know it used the Portal to retrieve the data structure as well as runtime.

    (0) 
    1. Andrea Maraviglia Post author
      Hy Andrew,
      Xcelius to retrieve data from a SAP BW connection use the BICS remote web service that it’s publish on Java Application Server.
      Thank’s for your compliment’s.

      Regards
      Andrea Maraviglia

      (0) 
  2. Alexander Schuchman
    Any concerns about performance of these dashboards hitting the BI Java directly with no ability to cache the result?
    What about the additional load you are putting on the Java environment and it’s impact to BI traditional reporting?

    Just curious to hear your opionions on these questions.

    (0) 
  3. Rajendrakumar Gaikwad
    Hi
    My Portal is NW7 SP17.
    Do i need to Upgrade the Portal to EHP1 SPS5
    or i can just apply the BI Related Support Pack (BI-BASE-S ,BIWEBAPP) to the Portal to get the BICSRemote Service ?

    Regards
    Rajendra

    (0) 
  4. Amin HAJ KACEM
    Hi All,

    Well I am having this 2032 error on Xcelsius (Dashboard Design V 6.0 Build 14) when trying to setup a Neweaver BW Connection. I have added the crossdomain.xml in C:\Inetpub\wwwroot but stil getting the same error to enable security settings in flash player.

    For me friddler shows this and it is really weird.
    Result: 404
    Host: bicsremotecrossdomain.xml
    URL: /

    and few days ago, I’ve seen a note concerning this error and the webservice bicsremote stuff.

    Any help is really appreciated, because this error is blocking me.

    Many thanks,
    Amin.

    (0) 
      1. Avinash Verma

        Hi Andrea,

        I am trying to connect BW 7.3 -> Xcelsius SP4 enterprise edition, but getting same error #2031 with SAP BW connectivity even after following all mentioned steps. (hostfile entries done)

        Is there any other workaround to remove this error?

        Can you please upload all the screenshots again, as it is not available now.

        Regards,

        Avinash

        (0) 
  5. Emanuela Munich

    Hi everybody

    thanks for the replies

    I passed the issue to the Basis colleagues and actually there was with the portal configuration.

    They fixed it and it works

    thanks again:-)

    Manu

    (0) 
  6. Tarow W.

    Hi Andrea,

        I got the error #2032 and here are the messages from Fiddler. Do you have any idea on this?

    Response Header Tab

    HTTP/1.1 500 Internal Server Error

    Text View Tab

    1e04

    <SOAP-ENV:Envelope xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:xs=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” ><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Client</faultcode><faultstring>com.sap.engine.services.ejb.exceptions.BaseRemoteException: Exception in method com.sap.ip.bi.bics.remote.BicsRemoteObjectImpl0_0.getDesignTimeInfo(com.sap.ip.bi.bics.remote.elements.connection.WsConnectionInfo).&#xD;

    at com.sap.ip.bi.bics.remote.BicsRemoteObjectImpl0_0.getDesignTimeInfo(BicsRemoteObjectImpl0_0.java:368)&#xD;

    at com.sap.ip.bi.bics.remote.BicsRemote_Stub.getDesignTimeInfo(BicsRemote_Stub.java:326)&#xD;

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)&#xD;

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)&#xD;

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)&#xD;

    at java.lang.reflect.Method.invoke(Method.java:324)&#xD;

    at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)&#xD;

    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)&#xD;

    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)&#xD;

    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)&#xD;

    at SoapServlet.doPost(SoapServlet.java:51)&#xD;

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)&#xD;

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)&#xD;

    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)&#xD;

    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)&#xD;

    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)&#xD;

    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)&#xD;

    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)&#xD;

    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)&#xD;

    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)&#xD;

    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)&#xD;

    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)&#xD;

    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)&#xD;

    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)&#xD;

    at java.security.AccessController.doPrivileged(Native Method)&#xD;

    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)&#xD;

    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)&#xD;

    Caused by: java.lang.RuntimeException: com.sap.ip.bi.bics.remote.impl.rmi.ApplicationCreationException: Could not to create the application. This is probably due to a misconfigured Abap/Java connection.&#xD;

    at com.sap.ip.bi.bics.remote.impl.rmi.cc.AbstractConnectionContext.cleanup(AbstractConnectionContext.java:340)&#xD;

    at com.sap.ip.bi.bics.remote.BicsRemoteImpl.getDesignTimeInfo(BicsRemoteImpl.java:194)&#xD;

    at com.sap.ip.bi.bics.remote.BicsRemoteBean.getDesignTimeInfo(BicsRemoteBean.java:109)&#xD;

    at com.sap.ip.bi.bics.remote.BicsRemoteObjectImpl0_0.getDesignTimeInfo(BicsRemoteObjectImpl0_0.java:359)&#xD;

    … 26 more&#xD;

    &#xD;

    ; nested exception is:

    java.lang.RuntimeException: com.sap.ip.bi.bics.remote.impl.rmi.ApplicationCreationException: Could not to create the application. This is probably due to a misconfigured Abap/Java connection.</faultstring><detail><ns1:java.rmi.RemoteException xmlns:ns1=’http://sap-j2ee-engine/client-runtime-error‘>com.sap.engine.services.ejb.exceptions.BaseRemoteException: Exception in method com.sap.ip.bi.bics.remote.BicsRemoteObjectImpl0_0.getDesignTimeInfo(com.sap.ip.bi.bics.remote.elements.connection.WsConnectionInfo).&#xD;

    at com.sap.ip.bi.bics.remote.BicsRemoteObjectImpl0_0.getDesignTimeInfo(BicsRemoteObjectImpl0_0.java:368)&#xD;

    at com.sap.ip.bi.bics.remote.BicsRemote_Stub.getDesignTimeInfo(BicsRemote_Stub.java:326)&#xD;

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)&#xD;

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)&#xD;

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)&#xD;

    at java.lang.reflect.Method.invoke(Method.java:324)&#xD;

    at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)&#xD;

    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)&#xD;

    at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)&#xD;

    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)&#xD;

    at SoapServlet.doPost(SoapServlet.java:51)&#xD;

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)&#xD;

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)&#xD;

    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)&#xD;

    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)&#xD;

    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)&#xD;

    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)&#xD;

    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)&#xD;

    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)&#xD;

    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)&#xD;

    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)&#xD;

    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)&#xD;

    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)&#xD;

    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)&#xD;

    at java.security.AccessController.doPrivileged(Native Method)&#xD;

    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)&#xD;

    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)&#xD;

    Caused by: java.lang.RuntimeException: com.sap.ip.bi.bics.remote.impl.rmi.ApplicationCreationException: Could not to create the application. This is probably due to a misconfigured Abap/Java connection.&#xD;

    at com.sap.ip.bi.bics.remote.impl.rmi.cc.AbstractConnectionContext.cleanup(AbstractConnectionContext.java:340)&#xD;

    at com.sap.ip.bi.bics.remote.BicsRemoteImpl.getDesignTimeInfo(BicsRemoteImpl.java:194)&#xD;

    at com.sap.ip.bi.bics.remote.BicsRemoteBean.getDesignTimeInfo(BicsRemoteBean.java:109)&#xD;

    at com.sap.ip.bi.bics.remote.BicsRemoteObjectImpl0_0.getDesignTimeInfo(BicsRemoteObjectImpl0_0.java:359)&#xD;

    … 26 more&#xD;

    &#xD;

    ; nested exception is:

    java.lang.RuntimeException: com.sap.ip.bi.bics.remote.impl.rmi.ApplicationCreationException: Could not to create the application. This is probably due to a misconfigured Abap/Java connection.</ns1:java.rmi.RemoteException></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>

    0

    (0) 

Leave a Reply