Risk Terminator ECC 6 - CC 5.2 - RFC  Test: Program not registered

Dear board,
I am configuring the risk terminator functionality and stumble accross problems with the setup of the RFC destination from ECC to the CC. The connection test fails with "ERROR: program GRCRTTOCC5X not registered".
The RFC connection is of type TCP/IP, Registered Server Program, Default Gateway Value and Gateway host/service information I took from another working rfc connection.
The RFC connection is equal to the one set up in the RT configuration transaction, I have set up a dedicated connector on the CC with direction outound and GRCRTTOCC5X as report.
I have furthermore noticed that I am not able to active the SAP Adapter in the CC yet, a JCO error appears.
Any ideas?
Kind regards and many thanks,
Richard

Hi Richard,
I am sorry to bother you and distract with this query, but couldn't find your email in your profile.
Could you please contact me regarding your SPNego problem discussed in
SPNego - Windows integrated Single-Sign On not working - How to debug?
We are facing the same issue and I was curious whether you had a solution?
<b>Thanks so much</b>, Emir
My email is emirce at gmail dotcom.

Similar Messages

  • RFC : Transaction Program not Registered

    Hi Folks,
    We have registered the server program from the middleware onto SAP R/3 System and is successfully registered as per the logs. As a next step, we have logged into R/3 System, SM59, in the RFC destination (Type TCP/IP) after specifying the registered program, we have tested it(Connectivity test). The test is positive and connectivity is established successfully.
    The solution was working for months and suddenly connectivity is broken.
    To restore the connection, we have repeated the steps, registered the server program, tested and everything is fine.
    But when we have pushed a new message, then onwards the RFC destination shows an error. "TP is not registered", Return Code 679. That is when the first message is pushed, it is de-registering the server program and running into error. All the messages got stuck in SM58 with status 'Error when opening an RFC connection'.
    RFC trace shows
    ERVER> Caller transaction code:  (Caller Program: SAPLQOWK)
    ERVER> Called function module: ARFC_RUN_NOWAIT
    Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1501
    CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
    Transaction program not registered.
    Please let me know for any inputs.
    Thanks, Suraj

    My problem got solved. In the middleware, when TRFC connection is made, it has created a lock entry during the time, system was brought down for maintenance activity. When the system is brought up, then as the connection lock entry is available, then it deregistered the server program and not able to establish further connection.
    To resolve the issue, we have just deleted lock file and registered server program from middleware. This time the connection was established successfully and could able to restore the message flow.
    Thanks, Suraj

  • RFC Error: Program not registered

    Hi,
    We are presently facing issue with our GTS (Quality) and Seeburger system RFC connection. While doing the testing we are getting error as below:
    ======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
    Transaction program not registered
    ABAP Programm: RSRFCPIN (Transaction: SM59)
    User: TESTUSER (Client: 202)
    Destination: SEEBURGER_RFC (handle: 2, , )
    Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1501
    CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
    Transaction program not registered
    DEST =SEEBURGER_RFC
    HOST =%%RFCSERVER%%
    PROG =BIS_ABC_202_DEV
    GWHOST =ABC.XYZ.STU.com
    GWSERV =sapgw15
    I have checked RFC connection is fine. Also production systems connection are working fine.
    Can anyone please help me out where to look in GTS or Seeburger to check about this issue and correct it.
    Thanks & Regards,
    Manish

    Hi Sunny,
    Thank you  for your suggestion, actually we have tried registration using rfcexec and it works fine.
    BTW, we have managed to solve this issue by de-activate the IDoc receive & send modules of websap component and activate them again.
    Thanks and Regards,
    Nick

  • CPIC-CALL Transaction program not registered Error while creating RFC Desti

    Hi All,
    I am trying to create a new RFC Destination.
    Details I have provided are..
    1.RFC Destination Name
    2.Connection Type - TCP/IP
    3.Description
    4. Activation Type - Registered Server Program.
    5.Program Id.
    6. Gateway Host and Gateway Service.
    But When I Test the connection, I am getting the following error.
    <b>" program xyz not registered / CPIC-CALL: 'ThSAPECMINIT'# Transaction program not registered"</b>
    However I was able to create and connect RFC Destinations successfully previously.
    I am not SAP guy. Could someone help resolve this issue.
    Thanks,
    Phani

    hi Sekhar,
    I request you to please help me out in this issue. I am getting similar kind of problem. I am trying to replicate the customer from CRM to R/3 and i get a bdoc message in SMW01 that "RFC connection failed please press the save button again". When the basis team further investigated they came up with the below error..
    User: CRREMOTE (Client: 071)
    Destination: OCR (handle: 1, , )
    Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1462
    CPIC-CALL: 'ThSAPECMINIT'
    Transaction program not registered
    DEST =OCR
    HOST =%%RFCSERVER%%
    PROG =dpssrfc
    Trace file opened at 20061121 140451 EST SAP-REL 640,0,109 RFC-VER
    3 804778
    resize I/O buffer to 28000 bytes
    >>>> [2] MQ_LINK      : TCP  <ac: 3> K %%RFCSERVER%% >>> OPEN
      {45632F14-288E-0046-0000-0000A888A7AA}-
    ======> CPIC-CALL: 'ThSAPECMINIT'
    can you please tell me where can be probelm. Regarding your message, where can i get the communication channel to assign the program id.
    Awaiting your reply,
    Thanks & Regards,
    Yogesh

  • Error 'Program not registered' while testing RFC

    Hi
    I have created a RFC with type T. When I am testing the same through SM59, I am getting error:
    Logon     Connection Error
    Error Details     Error when opening an RFC connection
    Error Details     ERROR: program <program name>not registered
    Error Details     LOCATION: SAP-Gateway on host xxxxxx / sapgw01
    Error Details     DETAIL: TP <program name> not registered
    Error Details     COMPONENT: SAP-Gateway
    Error Details     COUNTER: 6268
    Error Details     MODULE: gwr3cpic.c
    Error Details     LINE: 1694
    Error Details     RETURN CODE: 679
    Error Details     SUBRC: 0
    Error Details     RELEASE: 700
    Error Details     TIME: Tue Jan 27 00:56:55 2009
    Error Details     VERSION: 2
    Can anybody help me in this?
    Thanks in advance

    Something helpful related to this
    The program in the above error should be registered in the gateway for this connection test to complete successfully. The server program rfcexec is responsible for its registration on the gateway.
    To register the program login into the OS level as sudo su - <sid>adm and execute the following command.
    rfcexec u2013g<program id> -a<gateway host name> -x<gateway service>
    rfcexec is the server program name, the <program id> can be obtained from SM59, it is case sensitive and should match with the entry in SM59. The <gateway host name> and <gateway service> can be obtained from the transaction SMGW. When this command is executed it goes to a hanging loop.
    The connection will fail once this command is terminated or the user executing this command logs off
    To avoid this, instead of using the above mentioned command an entry should be made in the file saprfc.ini
    To do this, execute the following command
    sudo su - <sid>adm
    rfcexec u2013D<destination name>
    <destination name> is the RFC destination name in SM59
    So now we are done with registering the server program, but how do we check it is registered, once a server program is registered it is displayed in the Logged on clients in SMGW.
    In transaction SMGW choose GOTO-> Logged on clients. There should be an entry for the server program in the screen that is displayed with system type Registered_TP (which indicates that the program is registered)

  • Error 'Program not registered' while testing RFC - SRM to MDM / TCP/IP conn

    Hello All,
    While testing RFC connection in SRM, we are getting this error. This connection between SRM to MDM. Any inputs will be highly appreciated.
    Error Details LOCATION: SAP-Gateway on host <hostname> / sapgw<instance no>
    our server OS : windows 2008 server
    We are getting error while doing connection test in SRM.
    This is sm59 connection (TCP/IP ) connection.
    Connection Type: T / RFC destination Name: MDM_API_CATALOG
    Registered server program: hostname.MDS
    I checked smgw transaction ..Logged on clients...Program id is not showing. Any hint will be helpful.
    I Checked this MDM setup also.
    MDS setup
    In mdm server go to folder F:\usr\sap\DM1\MDS00\config
    Open MDM.ini file in notepad
    Add the below 2 entries.
    SAP RFC Gateways= GWHOST=XXXX.hostnamexxx.xxx GWSERV=sapgw00
    Trusted SAP Systems= XXD
    This will enable gateway connection between SRM and MDM and will enable trusted connection.
    For trusted connections to work, we created a service user called SRM_MDM_API with SAP_ALL in SRM  and also created the same user in MDM with Default role.
    Error message:
    Logon  Connection Error
    Error Details    Error when opening an RFC connection
    Error Details    ERROR: program XXXXXXXXPRD.MDS not registered
    Error Details    LOCATION: SAP-Gateway on host XXXXXXXXprd.xx.xxxxxxhostname.xxx / sapgw00
    Error Details    DETAIL: TP XXXXXXXXPRD.MDS not registered
    Error Details    COMPONENT: SAP-Gateway
    Error Details    COUNTER: 77326
    Error Details    MODULE: gwr3cpic.c
    Error Details    LINE: 1778
    Error Details    RETURN CODE: 679
    Error Details    SUBRC: 0
    Error Details    RELEASE: 700
    Error Details    TIME:
    Error Details    VERSION: 2
    Procedure Tried
    1)  This procedure is for Linux OS - Similarly we tried in Windows OS ( If any procedure is wrong also, Please correct us)
    To register the program login into the OS level as sudo su u2013 <sid>adm and execute the following command.
    rfcexec u2013g<program id> -a<gateway host name> -x<gateway service>
    rfcexec is the server program name, the <program id> can be obtained from SM59, it is case sensitive and should match with the entry in SM59. The <gateway host name> and <gateway service> can be obtained from the transaction SMGW. When this command is executed it goes to a hanging loop.
    The connection will fail once this command is terminated or the user executing this command logs off
    2)
    To avoid this, instead of using the above mentioned command an entry should be made in the file saprfc.ini
    To do this, execute the following command
    sudo su u2013 <sid>adm
    rfcexec u2013D<destination name>
    <destination name> is the RFC destination name in SM59
    In order to do above step 2,  we could not find saprfc.ini in windows 2008 server. Please let us know path where it will be usually?
    3) Already checked the notes sapnote_0000684841
    I know that it is generic error..This is happening to specific one of system only.
    Thanks
    Edited by: saptest2011 on May 20, 2011 5:36 PM

    Hello SM,
    Thanks for your quick reply.
    Thanks for sharing link for document ie Configure the MDM Administration_cockpit. It is helpful. I read that document.
    But still issue remain there.
    The same RFC connection works between SRM sandbox to MDM sandbox.
    Only issue with SRM Prod to MDM Prod (newly built system)
    difference between MDM Prod and MDM sandbox.
    MDM Prod runs: Windows server 2008 OS
    MDM Sandbox runs: Windows server 2003 OS
    Landscape: PI7.1, MDM 7.1 and SRM 5.5, SRM-MDM Catalog 3.0
    Even i did os01 tcode ping test using host name (specific IP address) from SRM prod to MDM prod, it is fine.
    Thanks a lot for your help.
    I checked these notes also
    Note 353597 - Registering a server program
    Note 44844 - No connection to registered RFC program
    Note: in smgw tcode in SRM system, the required program id is not showing in logged on clients
    Thanks
    Edited by: saptest2011 on May 23, 2011 5:00 PM
    Edited by: saptest2011 on May 23, 2011 5:39 PM

  • Error 'Program not registered' while testing RFC connection PI_RFC

    Hi Basis Experts
    I am having problems while testing an RFC connection PI_RFC in one of our PI quality system.
    Here is the Error log
    Logon Connection Error
    Error when opening an RFC connection
    ERROR: program PI_RFC not registered
    LOCATION: SAP-Gateway on host bp1xeuaa202 / sapgw01
    DETAIL: TP PI_RFC not registered
    Details COMPONENT: SAP-Gateway
    COUNTER: 15866
    MODULE: gwr3cpic.c
    Details RETURN CODE: 679
    We tried restarting the JCO-RFC provider service in VA,also tried restarting the Gateway service, tried registering the RFC using below command
    rfcexec u2013g PI_RFC -a bp1xeuaa202 -x sapgw01
    rfcexec u2013D PI_RFC
    the command didnt gave any output also in SMGW tcode we didnt get the entry(PI_RFC) under system type as registered server.
    Also we tried changing the Gateway hostname and service name in SM59.
    Still we are facing the same issue, can anyone please help us in resolving this issue.
    Regards
    Syed

    Hi,
    It seems to like problem with your program is not registered.  As suggested by spantaleoni, you can go through.
    Here Program Id  must be case sensitive.  Once again check with your program Id.
    And, you have to register your program id in Visual Administrator.
    Goto  Visual Administrator:
    In that Select Cluster>Server>Services-->JCo RFC Provider
    Then enter the Program Id and gw host & service.
    Hope this helps to you.
    Regards,
    P.Rajesh

  • RFC error: transaction program not registered

    Hi gurus,
    I am facing one issue with RFC connection.
    I am creating one TCP/IP connection from ECC 6.0 (windows 2003) to EHS/WWI application. i am getting following error when i am doing connection test.
    error: Program <PROGRAM ID> not registered.
    Then i tried to register the program by running the following command at OS level.
    rfcexec u2013a program_ID u2013g ######id  u2013x sapgw00
    But still the error persists.
    Please guide me. also does this command creates entry in saprfc.ini file? i have tried adding it manually in that file also.

    I think you need change Activation Type Radiobutton.
    I believe that you have checked "Registered Server Program", and with this flag you have to identify a registered RFC program. With an SAP gateway, an RFC server program can be registered under this ID and then wait for RFC calls from different SAP Systems.
    Type T destinations are connections to external programs that use the RFC API to receive RFCs.
    If it is Start, you must specify the host name and the pathname of the program to be started.

  • Program not registered - RFC to J2EE (local machine)

    I have a local install of WAS on my laptop using MSSQL 2000. I am trying to integrate local portal into a BI system.
    1. I completed SLD configuration of local J2EE
    2. As part of local SLD config I specified a BW7 system as data supplier
    - entered  BW7 host & gateway
    - kept default settings for "configure data supplier targets" (i.e: sld/active=TRUE)
    3. In Visual composer I successfully triggered SLD data transfer
    4. In Visual Composer I specified a JCo RFC Provider to the BW7 system I want to access.
    5. If I go to BW7 and goto tcode SMGW -> GOTO -> Logged on client, I see 2 pair of entries for JCo RFC provider
    with the following settings
    - system type: Registered Server (REGISTER_TP)
    - state: connected
    - LU name & Host Name = J2EE Host name w/ last 4 characters truncated. Only first 8 characters appear.
    - TP Name: 2 entries = SLD_UC & 2 entries = SLD_NUC. So a total of 4 connections. My understanding is that TP Name is supposed to = Registered Server Program
    6. In BW7, I have an RFC w/ Registered Server Program setting and program ID = JCo RFC Provider program ID
    7. In BW7 RFC & JCo RFC the host & gateway settings are the same, they both refer to the BW7. THIS IS THE PART WHERE I AM UNSURE. I would have thought that the host & gateway settings of BW7 RFC would refer to Local J2EE engine. AND I DON'T KNOW WHAT THE GATEWAY IS FOR LOCAL J2EE.
    8. In BW7 when I try to test the RFC, I get errors:
    - Logon     Connection Error
    - program <...> not registered / CPIC-CALL: 'ThSAPOCMINIT' Tran
    - ERROR: program <...> not registered
    - DETAIL: TP <...> not registered
    - COMPONENT: SAP-Gateway
    - MODULE: gwr3cpic.c
    - RETURN CODE: 679
    - SUBRC: 0
    - RELEASE: 700
    - VERSION: 2
    9. I completed step 1 & 2 of RSPOR_SETUP
    - Step 1 <Create RFC Destination in J2EE engine> messages:
    No Authorization to SMGW
    Profile parameter login/create_sso2_ticket is not set to 2
    Check of RFC destination <...> with RFC_READ_TCPIP_DESTINATION successful
    - Step 2 <Create RFC destination to Portal> messages:
    No Connection
    Option Send SSO tickets not active (see documentation)
    RFC CALL RFC_PING, destination <...> failed with sy-subrc =2
    There a little something missing. Hope u gurus can help, lost a weekend over this.

    Hello,
    we get the same message (program ... not registered, COMPONENT: SAP-Gateway) in sm59, when checking the TCP/IP connection. We got it, after we changed the user name in the Visual Administrator.
    Does anyone know with which tool and where the program can be registered. (The connection has no user name (connection by SAP ticket)).
    Best regards,
    Thomas

  • Problem with RFC connection - tp program not registered

    Hello everyone
    recently there  has appeared a problem with the RFC connection on our system - we received the following set of messages:
    Trace file opened at 20101221 130738 Central European Standard Time, SAP-RE
    ======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
    Tp program is not registered.
    ABAP Programm: RSRFCPIN (Transaction: SM59)
    User: xxx(Client: 100)
    Destination: SIDRFC_IFSAPHRCZPKCP (handle: 2, , )
    Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1501
    CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
    Program transakcji nie jest zarejestrowany
    DEST =SIDRFC_IFSAPHRCZPKCP
    HOST =%%RFCSERVER%%
    PROG =IFCZPKCP
    GWHOST =ssapprod
    GWSERV =sapgw21
    I tried to register program with a command:
    rfcexec -aIFCZPKCP -gssapprod -xsapgw21
    but with no success - the program didn't appear on the list of logged clients on the system in gateway monitor. Frankly speaking we do not know now what else we can do - please help!
    We have ECC 6.0 (SAP_BASIS 700 SP18) on Windows Server 2003 R2 x64.
    Thanks in advance for any help.
    Regards
    Peter

    Hi Salim
    thanks for your reply.
    ./rfcexec -a(PROG_ID) -gssapprod -xsapgw21 &
    The syntax you're providing refers to UNIX systems, but I did similar thing on our Windows system - I tried all of the following methods (unfortunatelly without success):
    rfcexec -a(PROG_ID) -gssapprod -xsapgw21
    full_path_to_rfcexec.exe -a(PROG_ID) -gssapprod -xsapgw21
    rfcexec -a(PROG_ID) -gssapprod.domain -xsapgw21
    full_path_to_rfcexec.exe -a(PROG_ID) -gssapprod.domain -xsapgw21
    Can you advise me what to do now?
    Thanks
    Piotr

  • BOEDGE - SM59 Connection RFC = Program Not Registered

    Hello,
    I installed on a server Windows Server 2003 SP1 32bit:
                   - BO Edge 3.1 (BuildVersion = 12.1.0.914)
                   - Java Connector 2.1.9
                   - Integration Kit for SAP 3.1 SP3 (BuildVersion = 12.3.0.601)
    I see on the CCM (Central Configuration Manager) my services correctly started:
              Apache Tomcat                     --      Running
              BW Publisher Service           --      Running
              Server Intelligence Agent      --      Running
    I installed on the BW server the transport order of BOBJ INTG for "BOBJ INTG for SAP XI 3.1 FixPack 3.1" (BuildVersion=12.3.1.684).
    I created a RFC connection type TCP/IP and test my new connexion and I have a error message:
    Connexion     Erreur connexion
    Détails err.     Error when opening an RFC connection
    Détails err.     ERROR: program BW_PUBLISHING not registered
    Détails err.     LOCATION: SAP-Gateway on host myserver.com / sapgw10
    Détails err.     DETAIL: TP BW_PUBLISHING not registered
    Détails err.     COMPONENT: SAP-Gateway
    Détails err.     COUNTER: 51016
    Détails err.     MODULE: gwr3cpic.c
    Détails err.     LINE: 1812
    Détails err.     CODE RETOUR: 679
    Détails err.     SUBRC: 0
    Détails err.     RELEASE: 700
    Détails err.     TIME: Fri Sep -
    Détails err.     VERSION: 2
    An idea?

    Hi,
    In Central Management Console ie, Admin application of BOE, you need to configure the BW system. Use the below URL,
    http://<serverhostname>:<port>/CmcApp
    After logging in Select the Authentication and SAP as authentication type.  Regarding how to configure, follow the configuration steps mentioned in the below article:
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a00ee3b2-5283-2b10-f1bf-8c6413e0898f
    Once you import the roles with the above configuration, the user with which you are validating the RFC connection will be imported in the BOE.
    Now, verify the RFC in the BW system.
    Regards,
    Noor.

  • Idoc - XI - File scenario:  R3 RFC Program Not Registered

    I have been going through all of the outbound idoc guides and other forum messages, but still cannot figure out how to get my rfc registered.  This is my SM58 error on R/3.
    Connection error        program SAPXI_IDOC not registered / CPI-C error CM_ALLOCATE_FAILURE_RETRY.
    I have SM59, IDX1, and IDX2 set up on XI, but cannot get them registered.  Is there some sort of activation or cache refresh I need to do?
    More details-
    (my R/3 system is RD0-120 and my XI system is XD0-110)
    R/3 TCP RFC: SAPXI_IDOC
    R/3 tRFC Port: SAPXI_IDOC
    R/3 BD54: RD0120 and XD0110 are set up (wasn't sure which system)
    XI SM59:RD0120 (tests ok)
    XI IDX1:SAPRD0 (client of 120, RFC destination of RD0120)
    XI IDX2:(SAPRD0 metadata, my 2 idoc types, and client 120)
    Thanks

    Hi Keith,
    >>>R/3 TCP RFC: SAPXI_IDOC
    why did you call tcpip connection IDOC?
    you have to use R3 type connection
    in order to send idocs to the XI
    you don't need tcpip - so delete it and try again
    Regards,
    michal

  • Java communication error: Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679 Transaction program not registered ).

    There is a RFC connection not working connection test fails.
    I found out the RFC is using a a program id that is not registerd.
    When I register the program on os level like rfcexec -r -a <program_id> -g <hostname> -x <sapgw> the connection test on the rfc works.
    The problem with the rfcexec is that it just works as long as the os session is active.
    From what I´ve read I need to configure this on java side in the web dynpro content administrator.
    Can you help me with that ? When I try to click Create jco destination I get an error.

    Hello Vioar,
    rfcexec is only a standard program for testing, you sould not register it for your application on the gateway.
    Since you are getting "User is not allowed to read any data..." - did you logon with the correct user? Does this user have enough authorizations?
    Regards,
    Alwina

  • RFC error: SLD_UC program not registered

    Hello,
    I am having a problem connecting my Abap system to SLD.
    When I test the SLD_UC RFC connection, I get the error that the program is not registered.
    I did see other postings on this, but no real answers that I can tell.
    How can I troubleshoot the problem to get this program registered?
    Thanks
    Doug

    Hi Doug,
    Can you confirm the parameters specified under tab Technical setting --> Gateway Options(This should be your ABAP system gateway and host)
    Also check whether server name and gateway host you can see using tcode smgw.
    Hope this will help.
    -Pinkle

  • RFC issue in RAR 5.3 Risk Terminator

    Hi,
    We have RAR 5.3 with Risk Terminator configured. Since last couple of days, Risk Terminator is not working for one of our back end system.
    Getting below error message :
    "SAP Adapter has a problem, SOD violations will not be checked !!!
    Please check with your system Administrator
    Technical Info:
    senderAgreement not found: lookup of binding via CPA-cache failed for AdapterTyp"
    I have verified the configuration setting and confirmed below things:
    1. Config program do have RFC destination which is defined with registered program GRCRTTOCC5X
    2. The same program name is defined in the RAR connector with Outbount selected
    3. The SAP Adapter is Green. I have turned it off / on
    It was working well till few days back.
    Any suggestion would help a lot.
    Adeep

    Hi Deepak,
    Can you change your Program ID (GRCRTTOCC5X)  to any other name in your back end as well as RAR Report name  also.
    It will work.
    Regards
    Shiva.
    Edited by: Siva K Kumar on Jul 27, 2010 7:36 PM

Maybe you are looking for