Skip to Content
author's profile photo Former Member
Former Member

DiagSetup - Failed to create TCP/IP RFC on ABAP side (SM59)

Hello Gurus,

we try to setup our SMD. Its fine but one point gives a error in DiagSetup.

Thu Oct 07 10:22:42 2010 RFC Failed to create TCP/IP RFC on ABAP side (SM59)

Step RFC Details 
 
Failed to create TCP/IP RFC on ABAP side (SM59)
!! Exception :      Source system cannot be set to Unicode                              , error key: RFC_ERROR_SYSTEM_FAILURE
 
 Exceptions 
com.sap.aii.proxy.framework.core.BaseProxyException:      Source system cannot be set to Unicode                              , error key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
at com.sap.sup.admin.setup.abapproxy.tcpiprfc.TcpIpRfcProxy_PortType.inst_Create_Tcpip_Rfcdest(TcpIpRfcProxy_PortType.java:16)
at com.sap.sup.admin.setup.ManagingServices.createTcpIpRFC(ManagingServices.java:939)
at com.sap.sup.admin.setup.ManagingServices.createTcpIpRFC(ManagingServices.java:913)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:376)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:335)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:549)
at com.sap.sup.admin.setup.wizard.monitoring.ConfirmationView.setupSMDServer(ConfirmationView.java:389)
at com.sap.sup.admin.setup.wizard.monitoring.ConfirmationView.onActionSetupServer(ConfirmationView.java:211)
at com.sap.sup.admin.setup.wizard.monitoring.wdp.InternalConfirmationView.wdInvokeEventHandler(InternalConfirmationView.java:285)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

have someone a suggestion for this issue?

regards

Chris

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Oct 07, 2010 at 11:26 AM

    Hi Christian,

    Failed RFC has to be created manually, please try this workaround:

    Creation of the RFC destinations on ABAP side

    This step has to be done on the Solution Manager side in order to connect the ABAP side of solution manger 4.0 to the java side (SMDserver).

    Define RFC to connect to SMD

    In the solution manager 7.0 ABAP stack, create an RFC connection (Transaction SM59) with the following values:

    -RFC Destination = SOLMANDIAG

    -Connection type = T

    -Description = Solution Manager Diagnostics

    In the Technical Settings tab:

    -Activation type = Registered server program

    -Registered server program = WEBADMIN

    -External program call type = Gateway default value

    -CPIC Timeout = Gateway default value

    Prerequisites for End to End Diagnostics is SAP Note: 1010428.

    Hope this helps.

    Thanks & Best Regards,

    Raghavendra.

    Edited by: Raghavendra B Deshpande on Oct 7, 2010 1:27 PM

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Chris,

      Actually the TCP/IP RFC task creates 2 RFC Connections SOLMANDIAG & WEBADMIN. Please check if the 2 connections are existing, if not create manually. If existing and there are no other errors than this, then the configuration is successfull. If you want to run the task again then you have to deselect the TCP/IP RFC task and then execute. After this all the tasks will be successfully excuted.

      Concerning the Support for E2E Diagnostics on non-Unicode ABAP please check SAP Note No. 1082681.

      Hope this helps.

      Thanks & Best Regards,

      Raghavendra.

  • author's profile photo Former Member
    Former Member
    Posted on Oct 11, 2010 at 09:58 PM

    Hi There

    You are getting this error above because your solman system is nounicode which is wrong

    The solution manager must be unicode for E2E functions. And that's why you got the error as above.

    Please change your solution manager to unicode as a prerequisite and then refer to SAP Notes 1061383 and

    1010428 during installation.

    I am sure after that you wont be having this error any more

    Best Regards

    Jai Wardhan

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello,

      in Note 1061383 i read that "SAP will support End-to-End Root Cause Analysis with an ABAP stack on non-Unicode as of SAP Solution Manager 7.0 SP13, until the customer has completed the Unicode conversion"

      We are at stack 701 sp06.

      regards

      Chris

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.