Error In EP RFC IVIEW

Dear Experts,
While executing a FM in EP RFC Iview I am getting this error. Can Anyone Help.
Function execution failed.
Exception message: Nested Exception.
Failure to execute native function. Connection Failed: Nested Exception.
Native connection to the back end system is broken.
Thanks & Regards
Rajiv Roshan

Whatever You have said is done.
Actually I want to open Microsoft Excel in EP. For this I created an RFC IView and there I am calling my RFC. The RFC name and parameters are coming fine. But While previewing I am getting this Error.
In The RFC I have written The following Code:
CALL METHOD cl_gui_frontend_services=>execute
  EXPORTING
    DOCUMENT               = iv_file
   APPLICATION            =
   PARAMETER              =
   DEFAULT_DIRECTORY      =
   MAXIMIZED              =
   MINIMIZED              =
   SYNCHRONOUS            =
    OPERATION              = 'OPEN'
  EXCEPTIONS
    CNTL_ERROR             = 1
    ERROR_NO_GUI           = 2
    BAD_PARAMETER          = 3
    FILE_NOT_FOUND         = 4
    PATH_NOT_FOUND         = 5
    FILE_EXTENSION_UNKNOWN = 6
    ERROR_EXECUTE_FAILED   = 7
    SYNCHRONOUS_FAILED     = 8
    NOT_SUPPORTED_BY_GUI   = 9
    others                 = 10
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
In Iv_file if we give 'Excel' in R/3 it opens a new Excel Sheet, but in EP it is giving that error.

Similar Messages

  • The RFC iview error

    Hi everyone, I want to created an iview with type of SAP RFC iview ,but after I Choose Function,I get the "Portal Runtime Error",
    I can serch the function,but the next step I get the error:
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : com.sap.portal.applications.enterprise.iviews.wizard.default
    Component Name : com.sap.portal.applications.enterprise.iviews.wizard.default
    com.sapportals.connector.metadata.structures.IStructureValue.
    Exception id: 05:11_17/05/07_0043_8171850
    See the details for the exception ID in the log file
    the log:
    #1.5#001125C0B174006A000002390013006C000430A5ACA4648B#1179388031023#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#HAN-CUIZHAO#8477##LGEDEV_LED_8171850#HAN-CUIZHAO#beb3d5e0044a11dc8b25001125c0b174#SAPEngine_Application_Thread[impl:3]_7##0#0#Error#1#/System/Server#Java###Exception ID:03:47_17/05/07_0037_8171850
    [EXCEPTION]
    #1#com.sapportals.portal.prt.runtime.PortalRuntimeException: iView not found: :.default
    at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1937)
    at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:222)
    at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
    at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
    at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:435)
    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:522)
    at java.security.AccessController.doPrivileged(AccessController.java:242)
    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:160)
    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(AccessController.java:215)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Message was edited by:
            cui zhao

    Hello Cui Zhao,
    Have you create a reference system for RFC ? If not ,you should create a reference system first.
    PS check this link for create reference system:
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/ed/845896b89711d5993900508b6b8b11/frameset.htm">Defining an SAP Reference System for User Data</a>
    PS: reward the points for helpful anwser.
    BR,
    Jianguo Chen

  • Unable to create RFC iviews - connection test of the system failed

    hello,
    I always try to configure my system to run an RFC iView...
    The connection of myt system is failed for 1 of the 4 tests.
    i don't know why.
    I have filled this fields :
    - application host
    - ITS host name
    - ITS path
    - ITS protocol
    - Logical system name (not sure it's correct)
    - Sap client
    - Sap system ID
    - SAP system number
    - Server port (not sure it's correct)
    - System type
    - Web as host name
    - Web as path
    - Web as protocol
    and i have this error :
    SAP Web AS Connection
      Test Details:
    The test consists of the following steps:
    1. Check the validity of the system ID in the system object
    2. Check if the system can be retrieved
    3. Check if a SAP system is defined in the system object
    4. Validate the following parameters: WAS protocol; WAS host name
    5. Check HTTP/S connectivity to the defined back-end application
      Results
    1. The system ID is valid
    2. Retrieval of the system was successful
    3. The system object represents an SAP system
    4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (wsapv49.dhcp.xxx.xx.xxxx:8045)
    5. HTTP/S connection successful
    ITS Connection
      Test Details:
    The test consists of the following steps:
    1. Check the validity of the system ID in the system object
    2. Check if the system can be retrieved
    3. Check if the system object has a valid system alias
    4. Check if a SAP system is defined in the system object
    5. Validate the following parameters: ITS protocol; ITS host name
    6. Check the validity of any user mapping in the system object
    7. Check HTTP/S connectivity to the defined back-end application
      Results
    1. The system ID is valid
    2. Retrieval of the system was successful
    3. Retrieval of the default alias was successful
    4. The system object represents an SAP system
    5. The following parameters are valid: ITS Protocol (http) ITS Host Name (wsapv49.dhcp.xxx.xx.xxxx:8045)
    6. HTTP/S connection successful
    Test Connection with Connector
      Test Details:
    The test consists of the following steps:
    1. Retrieve the default alias of the system
    2. Check the connection to the backend application using the connector defined in this system object
      Results
    Retrieval of default alias successful
    Connection failed. Make sure user mapping is set correctly and all connection properties are correct.
    Test Connection through the DQE
      Test Details:
    The test consists of the following steps:
    1. Checks the existence of a backend admin user ID/password in the system properties.
    2. Checks the existence of a default alias for the system.
    3. Checks the DQE connection.
      Results
    1. DQE admin user ID or password is missing in the system properties. Make sure those properties exist for this system object.
    2. Default alias of the system exists.
    3. DQE connection successful. If you continue to experience problems, verify the DQE admin user ID and password properties for this system object.
    can you help me to end this configuration?
    thanks a lot.
    (reward points for helful answers...)
    Adrien

    doesn't work, doesn't work... :o(
    I found this in "analysis" -> "Debug"
      error 3 mai 2007 16:49:32:168 Failed to get connection for system final
    /System/Server com.sap.portal.ivs.connectorService sap.com/irj admin ITEM-31892 Server 0 0_33638
      error 3 mai 2007 16:49:32:168 (R3/BW) Failed to get connection. Please contact your admin.
    /System/Server com.sap.portal.connectors.R3 sap.com/irj admin ITEM-31892 Server 0 0_33638
    i found too a -BIG- file in the directories, "last block" of the file
    #1.5#000D56D8CEA2005D0000001500000FC400042F9201A5E5D2#1178204046283#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.
    Exception id: [000D56D8CEA2005D0000001300000FC400042F9201A5E071]#
    #1.5#000D56D8CEA2005D0000001600000FC400042F9201A76132#1178204046383#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error##Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.)]. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.
         at com.sap.engine.services.servlets_jsp.server.runtime.client.GzipResponseStream.write(GzipResponseStream.java:209)
         at com.sap.engine.services.servlets_jsp.server.runtime.client.GzipResponseStream.write(GzipResponseStream.java:193)
         at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.writeError(HttpServletResponseFacade.java:952)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.sendError(HttpHandlerImpl.java:955)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleGeneralException(HttpHandlerImpl.java:860)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.processError(HttpHandlerImpl.java:851)
         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:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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)
    #1.5#000D56D8CEA2005D0000001800000FC400042F9201A765B7#1178204046383#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/System/Server/WebRequests#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.)].
    The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.
    Exception id: [000D56D8CEA2005D0000001600000FC400042F9201A76132]#
    and with another test connector
    #1.5#000D56D8CEA200600000001800000FC400042F921D02D625#1178204505301#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#SAPEngine_Application_Thread[impl:3]_14##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.
    Exception id: [000D56D8CEA200600000001600000FC400042F921D02D1AE]#
    #1.5#000D56D8CEA200560000001600000FC400042F921D39B77B#1178204508896#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoInit()-> enter#
    #1.5#000D56D8CEA200560000001700000FC400042F921D3AE547#1178204508977#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###connectToSystem()->Selected Systemnull#
    #1.5#000D56D8CEA200560000001800000FC400042F921D3BE964#1178204509037#com.sap.tc.lm.ctc.provider.configurationmanager.ConfigManagerReader#sap.com/tcwddispwda#com.sap.tc.lm.ctc.provider.configurationmanager.ConfigManagerReader#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###getElement(String, Filter, int):NamedLocatedElement!ConfigManagerReader.SEARCH_FOR!CTC#
    #1.5#000D56D8CEA200560000001900000FC400042F921D414CF2#1178204509397#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoInit()-> leave success#
    #1.5#000D56D8CEA200560000001A00000FC400042F921E69A639#1178204528816#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoModifyView()-> enter#
    #1.5#000D56D8CEA200560000001B00000FC400042F921E69A953#1178204528816#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoModifyView()-> success#
    #1.5#000D56D8CEA2006E0000010500000FC400042F9231C81C6F#1178204853786#com.sap.portal.connectors.R3#sap.com/irj#com.sap.portal.connectors.R3#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_9##0#0#Error#1#/System/Server#Plain###(R3/BW) Failed to get connection. Please contact your admin. #
    #1.5#000D56D8CEA204E70000000100000FC400042F9231C90EA8#1178204853846#com.sap.engine.services.dqe#sap.com/irj#com.sap.engine.services.dqe#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#Thread[Log_Worker_6,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server/DQE#Plain###mai 03, 2007 17:07:33.786 [SAP_HOST|4039|SAPEngine_Application_Thread[impl:3]_9] <CONNECTOR.ERROR> Error trying to establish connection to the EIS : final Connection Failed: Nested Exception. Failed to get connection. Please contact your admin. #
    #1.5#000D56D8CEA200690000001E00000FC400042F92335B4C9E#1178204880215#com.sap.portal.connectors.R3#sap.com/irj#com.sap.portal.connectors.R3#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server#Plain###(R3/BW) Failed to get connection. Please contact your admin. #
    #1.5#000D56D8CEA200690000002000000FC400042F92335B4FE3#1178204880215#com.sap.portal.ivs.connectorService#sap.com/irj#com.sap.portal.ivs.connectorService#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server#Java###Failed to get connection for system #1#final#
    i happy to carry my life's number one goal with another guy
    (thanks, again and again)
    Adrien
    Message was edited by:
            Adrien Loire

  • Create SAP RFC iView with a structure as import parameter

    Hello All,
    I'm creating a SAP RFC iView from Portal SAP 7.4.
    I try call a RFC that have as import parameter a structure with various fields, but the portal recognizes the structure as string field, then I cannot fill the fields values, and when  I do a preview the iview, the following error occurs:
    Function execution failed. Exception message: class java.lang.String:null incompatible with class com.sapportals.connectors.SAPCFConnector.execution.structures.RecordWrapper:sap.com/[email protected]MultiParentClassLoader@80d4ed6@alive
    And only is possible select a output object.
    Exists any way of receive a structure or a table as import parameter?, and as output parameters more of a element?
    Thanks for your collaboration.

    Hello All,
    I'm creating a SAP RFC iView from Portal SAP 7.4.
    I try call a RFC that have as import parameter a structure with various fields, but the portal recognizes the structure as string field, then I cannot fill the fields values, and when  I do a preview the iview, the following error occurs:
    Function execution failed. Exception message: class java.lang.String:null incompatible with class com.sapportals.connectors.SAPCFConnector.execution.structures.RecordWrapper:sap.com/[email protected]MultiParentClassLoader@80d4ed6@alive
    And only is possible select a output object.
    Exists any way of receive a structure or a table as import parameter?, and as output parameters more of a element?
    Thanks for your collaboration.

  • RFC iview

    Hi,
    I have created an RFC iview but I have a fatal error :
    " Could not connect to back-end application. Check your system. The server may  be down or there may be an error in a system parameter"
    thanks
    Dodo

    Hi,
    I guess you should check your portal connectivity with the R/3 backend. Do this in the system administration where one has to create a system. Plz check if the system created has the correct Backend details and test the connections.
    If successful only then continue with the creation of iviews.
    Regards,
    Akshay
    Reward if helpful.

  • Error on reviever RFC side

    Getting following error on reciever RFC side
    Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.af.rfc.util.bapi.BapiException: Parameter with name RETURN not found.
    The custom RFC used in this case has export parameter as a table containing list of matching entries. There is no export parameter by the name RETURN.
    Regards,
    Amol

    Hi Amol,
    go to your RFC receiver determination and uncheck under "Advanced Mode" the fields "Commit Handling for Single BAPI Calls" and "BAPI Advanced Mode".
    If you have BAPI and non-BAPI calls with the same R/3 system, you need seperate communication channels".
    Regards
    Stefan

  • Error while using XML Iview, please contact your system administrator.

    Hello everybody,
    I have already posted a detailed message for the XML iview problem sometime back but havent got any reply so far. All the replies had come from users who are also facing the same problem. I am trying to use a XML iview for fetching RSS feeds from one of the internet source, i have entered the proper URL and selected the proper RSS to XHTMLB transformer also and have entered the proxy settings in the http service and enabled it and restarted it also, but again when i am previewing the Iview its giving me the error <b>"Error while using XML Iview, please contact your system administrator."</b>. I am using
        Area           Version
        J2EE Engine    6.40 PatchLevel 98256.313
        Portal         6.0.14.0.0
    , can someone tell me whether its a bug in sp14 or i am missing something while creating this XML Iview. Expecting a proper reply.
    Thanks in advance,
    Regards,
    Sarabjeet.

    Hi Sarabjeet,
    The XML iView uses server-side fetching, so if you are having problems with a regular URL iView in server-side fetching mode, so the problem with the XML iVIew probably has to do with the proxy settings.
    And since you got a 407 error, it seems there is an issue with proxy settings or the proxy server, as mentioned in this description of 407 error:
    The HTTP 407 code only applies to users who are accessing the Internet behind a proxy server. This is common in government and corporate workplaces. The 407 code indicates that your computer must first authenticate itself with your company's proxy server. Check with your IT department or computer support group as to the exact reason why you may be getting this error. It may be possible that the proxy server does not allow downloads of specific files (exe, cab, com). You can also verify that your proxy server settings are valid.
    I will check if I can find out any more specific info.
    Daniel

  • Error while calling RFC when using BSP Web Interface

    Hi,
    we have a problem with the Authorization when we use an Web Interface for BSP. We have assigned all roles to the user which were mentioned in the SAP standard documentation:
    R_AREA   
    R_METHOD 
    R_PACKAGE
    R_PARAM  
    R_PLEVEL 
    R_PM_NAME
    R_PROFILE
    R_STS_PT 
    R_STS_SUP
    R_WEBITF 
    S_RS_ADMWB
    S_RS_AUTH
    S_RS_COMP
    S_RS_COMP1
    S_RS_DAS 
    S_RS_ICUBE
    but we still get the error message: "Error while calling RFC".
    When using a user with SAP_ALL, it works.
    What can we do?
    Thx for your time.
    Joerg

    Actually that's surprising - because BSP (Business Server Pages) and RFC (Remote Function Call) are not related; they use totally different transport protocols (http vs. RFC). Even if an BSP application is calling a function module remotely (acting as RFC client) no authorizations for S_RFC are required - in the calling system (but in the called system, i.e. the RFC server).
    Since assigning SAP_ALL seems to "cure" the problem, it seems to be an authorization issue, indeed. In that case it makes sense to use the authorization trace (ST01 - notice: that's specific to one single ABAP application server; you might have to activate the trace on multiple instances) to find out which authorizations are checked / demanded.

  • Getting error in XI"RFC Program Not Found"

    Hi All,
    I am getting error in SXMB_MONI "RFC Program not found via SAP XI".
    So please suggest me what is the problem behind this..For these SAP XI and R/3 i made 3 to 4 RFC program but only 1 RFC program name not getting Via SAP XI.
    Thanks
    Amit

    Hi,
    I am calling RFC FM via SAP XI.
    Main Records are coming from siebel and recevied by SAP XI and XI will do some changes in records and calling REC FM from SAP R/3.
    Problem is siebel to xi records coming fine but xi to sap R/3 error message coming "Program not Found".
    Thanks
    Amit

  • ERROR in the RFC communication when parabatch is set to more 3 (default)

    Hi experts,
    We have a 10 blades BIA system connecting to our BW Production. When we set the parabatch to more than the default 3 (we set to 4 or 5), We keep getting 'Batchpara Error' and 'Error in the RFC Communication: Error when opening an RFC Connection' during the initial index build. Here are what we do and what we see:
    1. set parabatch to 5 and build 1 initial index (cube is 46 mil rows, 22 GB in size) - Failed with the above errors
    2. set parabatch back to 3 and build 1 initial index (same cube as above)- successful but slow
    3. set parbatch back to 3 and build 2 initial indexes simultaneously (16 mil rows/4GB and 6 mil rows/2 GB) - Failed with the above errors.
    In the BIA index log I see the following error:
    Error in the RFC communication: Error when opening an RFC connection (TREX_BIP)
    Message no. STREX005
    In SM37 in one of the logs I see the followings:
    Parabatch Error
    Any light you can shed on why we are encountering this issue will be much appreciated. Also, I observed that there is a long idle time in all systems (BIA, DB2, BW) and seemed like their respective resources were not utilized at all. Once in a while I do see surge of cpu/memory usage in all systems but not too terrible. I'm puzzled by why there is such long interval of idle time in all systems while the initial index build is going on.
    BTW...we did the same thing (set parabatch to 5, and run parallel initial builds) in our non-prod BIA (2 blades) and QA BW landscape and do not have any issue at all.
    Thanks!
    Kee

    Hello
    PLease check the sapnotes and check the developer trace for more information.
    Note 314530 - Number of RFC/CPIC connections for external clients
    Note: 1070034
    It can also be because your system has reached it its max gateway connections...also check whether you are getting error message "Communication error, CPIC return code 017, SAP return code 450
    " in sm21  ???
    Regards
    Karthikeyan.K

  • Publish to portal error when creating a iview

    hi gurus,
    I have done complete BI-EP integration. SSO is also working fine. But when i publish a query from query designer to portal, i am geting a error when creating a iview for the query as show below.
    Error:
    Java system error: call FM RSRD_X_MAP_TO_PRTL_USERS_PROXY to ProgId EPD_PORTAL_B07 on host epdev with SSO not authorized: Authentication failed.
    when i manually create a BI Query iview,its working fine but to create a iview from publish to portal in query designer it is througing me error.
    Regards

    yes i have used that tool,,,i am getting below error.
      RED
    Web Template Validation failed due Java to ABAP communication problem (return code:ERSBOLAP018) Check Connector Connection of System Object in Portal System Landscape -
      RED
    Call ABAP->Java for function RSWR_RFC_SERVICE_TEST failed for destination 'SAP_EP' Check the data of the destination in transaction SM59. Check that the target host is running and has registered a program id in the gateway. -
      RED
    Call ABAP->Java for function RSRD_MAP_TO_PORTAL_USERS failed for destination 'SAP_EP' Check the data of the destination in transaction SM59. Check that the target host is running and has registered a program id in the gateway. -
      RED
    Web Template Validation failed due Java to ABAP communication problem (return code:ERSBOLAP018) Check Connector Connection of System Object in Portal System Landscape -
      RED
    Call ABAP->Java for function RSWR_RFC_SERVICE_TEST failed for destination 'SAP_EP' Check the data of the destination in transaction SM59. Check that the target host is running and has registered a program id in the gateway. -
      RED
    Call ABAP->Java for function RSRD_MAP_TO_PORTAL_USERS failed for destination 'SAP_EP' Check the data of the destination in transaction SM59. Check that the target host is running and has registered a program id in the gateway. -
      RED
    Calls from WebAS ABAP to WebAS Java will fail because the certificate of the BI mastersystem is not imported into J2EE ticket keystore Import the certificate to establish a trust relationship -
      RED
    The issuer DN of the imported ticket 'EPD_certificate' is the same as the issuer DN of SAPLogonTicketKeypair-cert Most likely, you are running an Add-In Installation. See note 917950, section 'Add-In Installation and importing Certificates with identical system ID (SID)' for details Display note 917950
    I have checked everything,,but still geting red lights
    Regards

  • Error Handling in RFC- JDBC sync

    Hi all,
    We are having scenario RFC<->XI<->JDBC(Sync),and its working fine also.
    Suppose  exception  occur in RFC->JDBC request mapping,Now is it possible to pass the error back to R/3 ?
    If parsing error occurs in JDBC adapter how to catch this error in error structure of rfc ?
    We observed that if any exception occurs on request side , response mapping will not get executed can anybody explain me why this is happening ?
    Thanks in advance,
    Tuhin

    Hi Gopesh,
    U should follow the steps as below.
    1.Create TCT/IP connection with t-code SM59
      in R/3 and give program id (it is case sensitive also).
    2.Give same program name in Sender RFc communication     channel.Check that this channel is register in your R/3 system with t-code SMGW(Gate way monitor)
    Only this much extra config I have done.
    Thanks,
    Tuhin

  • Error in executing RFC or CAF Application Service

    Hello Everybody,
    I am creating course approval process, in which I am calling RFC for user info and after course approval, calling CAF application service to persist this data.
    But, both services are not working in process. I have tested callable objects for these services and tested successfully.
    But, when I am attaching it in the process then process can't go forward from this point.
    I have checked in Log viewer and found following error:
    Path to object does not exist at com.sap.caf.eu.gp.model.pfw.local, the whole lookup name is sap.com/com.sap.caf.eu.gp.model.pfw.local/GPUWLBridge.
    What should be the problem in this?
    If I remove these services then whole process works fine.
    Thanks in advance,
    Bhavik

    Hello All,
    Is there any concept like, I call perticular backgound object first time then I cannot call that object for some period of time?
    I am getting same error in calling RFC callable object as well as CAF service callable object.
    I can execute these callable objects in the process first time successfully. But, When I execute this process second time, these callable objects won't execute.
    I can execute same process after 3 to 4 hours successfully once.
    What should be the reason behind this?

  • Error in BPM: "COMMUNICATION FAILURE" during JCo call. Error opening an RFC

    hello experts
    i am receiving the above error incase of BPM scenario where i am having a Transform step and synchronous RFC step.
    i referred to the few threads discussing such problems and was trying to find whether my mapping is correct and i tested my mappings using my payload which looks good.
    When looked into the Mapping trace of the BPM "Show container" i found error ""COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection" and it seems that when BPM is attempting to call interface mapping it is throwing this error.
    Thanks in advance.
    Regards
    rajeev

    hi,
    I think no problen with the mapping part,
    jco connection requird when xi try to stablish the connection with the adapter .
    please look the link provided.
    Setup and test SAP Java Connector outbound connection
    please also check the following parameter at the exchange profile
    com.sap.aii.rwb.server.centralmonitoring.r3.ashost
    com.sap.aii.rwb.server.centralmonitoring.r3.client
    com.sap.aii.rwb.server.centralmonitoring.r3.sysnr
    com.sap.aii.rwb.server.centralmonitoring.httpport
    these parameter must be given properly.
    if every thing is ok than and problem still exist than try to restart the system.
    for us after restarting its worked fine.
    regards,
    navneet

  • Error in Reciever RFC Adapter

    Hi All,
    While working with JDBCXIRFC, the only error with Reciever RFC Adapter is as
    follows.
    ZBAPICUSTOMER_DETAILS: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not get functionname from XML requst: com.sap.aii.af.rfc.RfcAdapterException: failed to read funtionname from XML document: missing namespace declaration(2)
    In SXMB_MONI, the messages are queued up.
    How to debug this error?
    Regards
    Pavan

    1. Map all the mandatory fields..
    I have mapped all the mandatory fields. If i enter same kind of values in the same fields of BAPI manually (in se37), the table gets updated.
    <b>how you can say that data is getting into the right tables...when you are sending the same data..</b>...may be the data is old only..
    <b>Perform the Message Mapping  and Interface Mapping test in IR only...</b>
    3. Kindly check the Sender_MM Mapping once more...If it is fine...reactivate and Update the cache..
    Its fine and reactivated and even updated cache.
    Now one doubt....
    In Message mapping, the sender mesage type is as follows.
    sender_mt 1:1
    ->Row element 1:unbounded
    > zkunnr element xsd:string 1: unbounded
    > zname1 element xsd:string 1: unbounded
    > zstras element xsd:string 1: unbounded
    > zadrnr element xsd:string 1: unbounded
    > ztelf1 element xsd:string 1: unbounded
    I have mapped ROW with ZBAPI_DETAILS.
    the root of sender message type SENDER_MT is left as it is....
    Is there anything need to be done (mapped) with this root of sender message type?
    <b>No i don't think so, what i can get from your approach is that you want to receive n similar type of records in a Message and want 2 create n different messages for each record from source structure..  </b>
    With this status, i have tested the Test Configuration in Integration Directory. Still getting same error message as follows...
    Kindly let me know the name of BAPI.
    <b>Perform the Message Mapping  and Interface Mapping test in IR only...</b>
    java.lang.NullPointerException thrown during application mapping com/sap/xi/tf/_sender_mm_:
    Regards,

Maybe you are looking for