Program _____.MDS not registered..PI 7.1 EHP 1-MDM 7.1 Integration-ABAP API

Hi,
I am on the way of integrating ABAP API in PI 7.1 EHP 1 with MDM 7.1
I installed MDM ABAP API in PI system.
In transaction MDMAPIC, created MDM Server Connection with default port, DBMS Hosts and MDM Repository.
After I did the above tasks, I tested the RFC Connection, But its failed with the following error.
Connection Test MDM_API_GEN_DEFIANCEDEP  
Connection Type TCP/IP Connection  
Logon     Connection Error
Error Details     Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=67
Error Details     ERROR: program DEFIANCEDEP.MDS not registered
Error Details     LOCATION: SAP-Gateway on host DEFIANCEDPI / sapgw00
Error Details     DETAIL: TP DEFIANCEDEP.MDS not registered
Error Details     COMPONENT: SAP-Gateway
Error Details     COUNTER: 87
Error Details     MODULE: gwr3cpic.c
Error Details     LINE: 1714
Error Details     RETURN CODE: 679
Error Details     SUBRC: 0
Error Details     RELEASE: 711
Error Details     TIME: Sat Mar 12 13:53:55 2011
Error Details     VERSION: 2
Appreciated if replied with the proper resolution at the earliest.
Thanks in Advance
Pradeep Shetty

Hi Kanstantsin Chernichenka,
Thanks for your reply.
I tried the given suggestion. And even restarted the PI and MDM system.
Still, I am facing the same problem.
My allow.ip file contains
122.183.187.24;  
122.183.187.25;
115.242.211.112;
115.184.2.47;
My MDS.ini file contents are
[MDM Server]
XCS Ini Version=1
Accelerator Dir=E:\usr\sap\MDM\MDS02\mdm\accelerators
Log Dir=E:\usr\sap\MDM\MDS02\log
Report Dir=E:\usr\sap\MDM\MDS02\mdm\reports
Archive Dir=E:\usr\sap\MDM\MDS02\mdm\archives
Distribution Root Dir=E:\usr\sap\MDM\MDS02\mdm\distributions
Transport Dir=E:\usr\sap\MDM\MDS02\mdm\transport
Modifications Dir=E:\usr\sap\MDM\MDS02\mdm\modifications
Lexicon Dir=E:\usr\sap\MDM\MDS02\exe\Lexicons\
Extra DBConnection Validation=True
Log SQL Errors=True
String Resource Dir=E:\usr\sap\MDM\MDS02\exe\LangStrings\
Stemmer Install Dir=E:\usr\sap\MDM\MDS02\exe
Wily Instrumentation=False
Wily Instrumentation Level Threshold=10
SLD Registration=True
Skip Unchanged Records=False
Autostart=0
MDS Ini Version=1
RELEASE\UseAssert=True
Tracing Level=3
LogViewer Format Logging=False
LogViewer Format Tracing=False
Trusted SAP Systems=DPI
TrustFiles Dir=E:\usr\sap\MDM\MDS02\config
Max Threads Per Operation=Auto
Lock Account After Failed Password Attempts=5
Lock Account Duration=1800
Minimal Password Length=5
Password Expiration Days=90
Password Expiration Warning=7
Disable Read Access To Corrupt Repositories=False
MDS Scone=
Log SQL Modifications=False
Maximum DBMS Bind Count=512
Oracle\Dll=OCI.DLL
Allow Console to Retrieve Files=True
Oracle Tablespace Files=1
Default Interface Language Code=eng
Default Interface Country Code=US
Client Ping Timeout Minutes=0
Inactive Client Timeout Minutes=30
Value Retrieval Threshold=0
Protect Family Nodes With Locked Data=False
Number Of Stemmers Per Language=2
TrexDllPath=
Import Slice Size=2048
Bulk Import Silo=True
Safe Silo Mode=False
Enable Change Stamp Logging=False
Always Verify DBMS Connection Before Executing SQL Statements=False
Disable Read Access To Repositories That Require Restart=False
Family Retrieval Threshold=30000
Enable Client Dictionaries=False
Restricted Url For Client Export=
Index_Page_Margin=10
Default Slice Size=500
Default Slice Wait Time MS=300
Enable Slicing For Non-Bulk Operations=False
Multithreaded Matching=True
SAP RFC Gateways=
[MDM Server\Databases\MDM_1MDMORCL_5_3_4_3]
Port=2345
Login=SYSTEM
Password+=ES066H2NVHDCFSJ206LJ9I995SLBVSA21OMQPM0
Stemmer Language=
Stemmer Variant=
Valid Keyword Chars=abcdefghijklmnopqrstuvwxyz0123456789
Max Large Text Length=250000
Number of Rows Per Fetch=100
Max Initial MB to Retain=4
Max Send Failure MB to Retain=4
Workflow Detailed Report=False
Mail Server=
Mail SMTP Timeout=1
Here I am requesting you to send your valuable feedback at the earliest.
Thanks
Pradeep Shetty

Similar Messages

  • 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

  • Program dcs.sndsap not registered

    Hi,
    We're in the midst of integrate our SAP with 3rd Party WMS. I've registered the program -id using command:
    rfcexec -DSAP_SEND
    rfcexec -adcs.sndsap -gHOSTNAME -xsapgw00 &
    I've created RFC in SM59 using method T.
    I can see the registered program working fine in SMGW. The issue that i'm facing, the registered program process will terminate by it self after few minutes and when I test it via SM59, i'll receive message "program dcs.sndsap not registered". Is there any way that I can investigate why the process terminated? and how could i ensure that the program always registered?
    Thanks and Regards
    Tarmizee

    Hi,
    can you go to trace file of work processs and look at the errors(which are in red colour / latest errors).
    if u find any difficulties in analyzing those errors related to disconnection or any errors related to ur 3rd Party WMS server in trace files  paste those errors here.
    Also can u check r u getting any errors in sm21 logs. paste them here, if u need any help on that too.
    Also ask your 3rd Party WMS server admin to increase the gate way connection from their end too.
    Regards,
    Ravi

  • Program IGS.BW not registered  in IGS_RFC_DEST

    Hello,
    I want to enable Internet graphics display for my BW system for which i have already installed IGS on my system and created RFC Destination as IGS_RFC_DEST and entered relevant parameters,when i test this rfc connection following error message is displayed:
    ERROR        program IGS.BW not registered 
    LOCATION     SAP-Gateway on host BIWDEV / sapgw00       
    DETAIL       TP IGS.BWD not registered                  
    COMPONENT    SAP-Gateway                                
    COUNTER      18                                         
    MODULE       gwr3cpic.c   
    Can someone tell me wt might be the possible cause of this error and how to rectify it.Kindly revert at earliest.My Email Id is [email protected]
    Thanks,
    Saumya

    please ensure all the steps explained in the following link are followed.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/4b/72d43ac66e1f08e10000000a114084/frameset.htm
    particularly you should use the same program ID used in IGS in the RFC destination.
    Regards
    Raja

  • Program ID is not registered

    Hi all,
    The connection in SM59 , type T, with program id is not working. This program id refer to an interface that I developed in PI. I Put another program id in this connection and works. But my program id isn´t works. All Objects in Integration Builder - Configuration is active.
    Any Idea???

    The connection in SM59 , type T, with program id is not working. This program id refer to an interface that I developed in PI. I Put another program id in this connection and works. But my program id isn´t works. All Objects in Integration Builder - Configuration is active.
    program id needs to maintain in java stack  then it will work. Check with basis people.
    Thanks
    Siva

  • Program AI_RUNTIME_ SID not registered

    Hello,
    We're doing the post-installation tasks of XI 3.0
    We've created the following RFC destinations in the ABAP environment:
    AI_RUNTIME_JCOSERVER
    AI_DIRECTORY_JCOSERVER
    LCRSAPRFC
    SAPSLDAPI
    When we test the AI_RUNTIME_JCOSERVER everything is ok, but we get this error with the other three:
    "Error opening an RFC connection" and in the detailed error I get this --> "TP AI_RUNTIME_AAA not registered"
    If anyone can help with this we´ll be very glad
    Pablo

    We ran into this issue on a new XI system install and discovered that the SAP role that was assigned to SAPJSF (or PI_JCO_RFC) had not been generated yet.  The role in question was SAP_BC_JSF_COMMUNICATION_RO.  After our Security team generated the role - the install procedure worked as documented.
    FYI - we pulled the RFC authorization issue from the Visual Administrator log on UNIX.

  • Error Program not registered

    I get the following error when I test an RFC;
    Logon     Connection Error
    Error Details     Error when opening an RFC connection
    Error Details     ERROR: program BIS_TR9.TRFC not registered
    Error Details     LOCATION: SAP-Gateway on host cpsaput1 / sapgw61
    Error Details     DETAIL: TP BIS_TR9.TRFC not registered
    Error Details     COMPONENT: SAP-Gateway
    Error Details     COUNTER: 21389
    Error Details     MODULE: gwr3cpic.c
    Error Details     LINE: 1777
    Error Details     RETURN CODE: 679
    Error Details     SUBRC: 0
    Error Details     RELEASE: 700
    Error Details     TIME: Wed Aug 22 16:33:49 2007
    Error Details     VERSION: 2
    The Gateway monitor connections to clients has this entry:
    242     cpamhq-sbg04     BIS_TR9.TRFC     Registered Server     cpamhq-sbg04     10.5.1.141     Wed Aug 22 16:34:39 2007     Connection OK
    This is a copy of a previous system on the same server with a different system number.  It has support package stack 10 with kernel patch number 121.
    Thanks,
    Joe

    Hello Joe,
    From the error logs I can make out two things.
    Your SAP resides on cpsaput1  while external program resides on cpamhq-sbg04 .
    Now you have done a system copy on cpsaput1 from a SAP system which was connecting fine to the RFC. That connection was going through because SAP details for the old server were correctly maintained at cpamhq-sbg04  but the same has not been done for cpsaput1  . Ask the adminsitrators for cpamhq-sbg04  to make settings for cpsaput1  and then try RFC again.
    Regards.
    Ruchit.

  • Sap to non sap connection ( program not registered/cpic-call

    Hi all,
        Im trying to connect sap to siebel system.IN TCP/IP connections iv selected register program id & passed the parameters ...program id,gateway host and gateway service
    i followed michal krawczyk steps & also checked in smgw
    transaction also but program id is not registered there
            im getting error like program sapprog not registerd cpic/call
    <b>Detailed error</b>
         <b>Error</b> - program sapprog is not registsred
         <b>location</b> - sap gateway on host saple / sapgw01
         <b>detail</b> - Tp sapprog is not register
         <b>component</b> - gateway
         <b>counter</b> - 387
        <b> module</b> -gwr3cpic
         <b>line-</b> 1621
         <b>return code</b> - 679
         <b>subrc</b>  - 0
               please try to help me out in this issue. all inputs r rewarded. 
      Regards,
      Lavanya

    Hi
    Thanks prince,iv checked entries in sm59,  i checked smgw tranaction(gateway monitor) for logged on clients
    its showing like this
    number/luname/tpname/sys.type/hostname/hostaddres/last req
    0 /sapnav/sapgw00/local_r3/sapnav.sapdomain.com/192.158.3.219
    if i double click on above...
    read/write socket = 4
    handle = 4
    time = tue jan 26 16:54:13 2006
    socket = 1652
    stat = ni_connected
    type = stream ipv4
    out = 1122 messages 64 bytes
    in = 1 messages 64 bytes
    local =127.0.0.1:3300
    remote = 127.0.0.1:1848
    options =
    lu = sapnav
    tp = sapgw00
    lon lu = sapnav
    long tp = sapgw00
    ext program = 0
    no conversation = 24
    appc version = 6
    hostaddr[0] =
    hostaddr[1] = 127.0.0.1
    offset in = 0
    timeouts in = 0
    connected = tue jan 24
    last req = mon jan
    request block number in= -1
    connection out = -1
    target out = -1
    offset out = 0
    restlen out = 0
    timeouts out = 0
    request block number out = -1
    accept info = einfo
    snc forced = 0
    <b>just see gateway monitor 4 sapnav/parameters & attributes</b>Profile
    parameter              Value
    gw/max_sleep           20
    gw/conn_disconnect     900
    gw/conn_pending        60
    gw/gw_disconnect       1800
    gw/req_stack_size      30
    gw/max_conn            500
    gw/max_wp              0
    gw/max_conn_per_wp     10
    gw/cpic_timeout        20
    gw/deallocate_timeout  600
    gw/reg_timeout         60
    gw/reg_lb_level        1
    gw/reg_lb_default      20
    gw/side_info    C:\usr\sap\D01\DVMGS00\data\sideinfo.DAT
    gw/sec_info     C:\usr\sap\D01\DVMGS00\data\secinfo.DAT
    gw/startup     C:\usr\sap\D01\DVMGS00\data\gwstartup.DAT
    gw/stat                0
    gw/tcp_security        1
    gw/cpic_security       1
    gw/max_sys             300
    gw/max_shm_req         50
    gw/max_shm_req_per_conn 10
    gw/max_overflow_size    5000000
    gw/max_overflow_usage   10
    gw/keepalive            300
    gw/reg_keepalive        300
    gw/compatibility        0
    gw/monitor              1
    gw/netstat_once         1
    gw/close_routes         120
    gw/timeout              0
    gw/internal_timeout     0
    gw/nitrace              0
    gw/accept_remote_trace_level 1
    gw/resolve_timeout      0
    rdisp/max_gateways      100
    rdisp/max_comm_entries  500
    rdisp/sna_gateway       sapnav
    rdisp/sna_gw_service    sapgw00
    rdisp/TRACE_LOGGING     OFF
    gw/rem_start            REMOTE_SHELL
    gw/remsh rsh
    exe/gwrd           C:\usr\sap\D01\SYS\exe\run\gwrd.EXE
    snc/enable               0
    snc/permit_insecure_start 0
    Attributes
    Release 640
    Release no 6400
    internal version 2
    start time Tue Jan 24 16:53:47 2006
    build time Aug 17 2004 23:33:51
    build with Unicode TRUE
    build with Threads TRUE
    gateway hostname sapnav
    gateway service sapgw00
    req_sync_limit 24
    appc_ca_blk_size 34396
    gwreq_ln 34588
    appcdata_ln 34316
    overflow_size_limit 500000
    overflow_use 0
    trace level 1
    trace level external programs 2
    PID Gateway Reader 4952
    internal version 2
    Shared memory Sizes in bytes
    CONN_TBL entry 1748
    CONN_TBL total 874000
    STATISTIC area 1392
      iv changed some values for my safety.plz check it and let me know the error to register program id. Hope ull solve my issue this time.
    Thanks in advance,
    Lavanya.

  • 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

  • Program IGS. SID not registered in IGS_RFC_DEST

    Hi all,
    I want to enable Internet graphics display for my BW system for which i have already installed IGS on my system and created RFC Destination as IGS_RFC_DEST and entered relevant parameters. When I test this RFC connection, the following error message is displayed:
    ERROR              program IGS.BWA not registered                
    LOCATION         SAP-Gateway on host SAPDEV/ sapgw22
    DETAIL              TP IGS.BWA not registered                     
    COMPONENT    SAP-Gateway                                   
    COUNTER         96                                            
    MODULE           gwr3cpic.c                                    
    LINE                  1609                                          
    RETURN CODE  679                                           
    SUBRC              0                                         
    RELEASE          640                                           
    TIME                 Wed Dec 27 14:12:54 2006                      
    VERSION           2                                             
    The IGS is up and running including the PORTWATCHERS and the HTTP port. I tested it out using the http://IGSHOST:LISTENERHTTPPORT. I can see entries under the headings REGISTERED_PORTWATCHERS and REGISTERED_INTERPRETERS.
    The program I am using in the RFC connection is the same I have given in "igs.xml" file in the ./conf directory.
    Can someone tell me wt might be the possible cause of this error and how to rectify it?
    Thanks
    Abhi

    Hi Abhi,
    please make sure that the entry for the program ID in igs.xml must match exactly the one in IGS_RFC_DEST (case sensitive). As I guess that your IGS is integrated within Web AS make sure that the gateway host and gateway service in IGS_RFC_DEST are empty.
    Please also refer to note <a href="http://service.sap.com/sap/support/notes/454042">454042</a>.
    Regards
    Matthias

  • Essbase server is invalid. Not registered with Shared Services

    Hi,
    I am trying to deploy EPMA Essbase application after we upgrade to 11.1.2.2 from 11.1.2.0. I get this error.
    Application server '<Server>:1423' is invalid. It is not registered with Shared Services.
    URI: http://<Server>/awb/integration.verifyApplication.do
    Code: com.hyperion.awb.web.common.BaseServiceException
    Description: Application server '<Server>:1423' is invalid. It is not registered with Shared Services.
    Actor: noneAny specific post configuration task needs to be performed?
    Regards,
    Ragav.

    Hi,
    We were able to resolve the issue. The "Invalid Deployment Information" test in the application diagnostics failed. We had to synchronize the deployment data and later we were able to validate the application.
    Regards,
    Ragav.

  • Protocol handlers not registered

    JFW
    In some cases the protocol handlers will not be registered...we did multiple installations...no success...we tried to post register some dlls...no success...
    Appreciate any hint
    Andreas
    a little more....
    Analyzed the logs a little deeper there is a difference between working and non working installations...some error conditions occurring:
    INFO  protocol handlers not registered protocol handlers not registered protocol handlers not registered protocol handlers not registered - Setting registry settings
    2012-06-05 09:36:02,897 ERROR protocol handlers not registered protocol handlers not registered protocol handlers not registered protocol handlers not registered - Failed to create Software\Policies\Microsoft\Office\14.0\Common\PersonaMenu in 80000001 use64Bit: 0
    2012-06-05 09:36:02,897 ERROR protocol handlers not registered protocol handlers not registered protocol handlers not registered protocol handlers not registered - Failed to create SOFTWARE\Microsoft\Office\Outlook\Call Integration in 80000002 use64Bit: 0
    2012-06-05 09:36:02,897 ERROR protocol handlers not registered protocol handlers not registered protocol handlers not registered protocol handlers not registered - Failed to create CLSID\{8885370D-B33E-44B7-875D-28E403CF9270}\TreatAs in 80000000 use64Bit: 0
    How to avoid this?
    Regards
    Andreas
    Sent from Cisco Technical Support iPad App

    It seems like it's having trouble talking to the registry; perhaps the user authenticated to Windows doesn't have permissions?
    You could check to see if you have access to these Windows Registry keys:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Call Integration
    HKEY_CLASSES_ROOT\CLSID\{8885370D-B33E-44B7-875D-28E403CF9270}
    HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Common\PersonaMenu
    The error message included isn't really that useful.  Maybe if you can attach the entire logfile to this thread we can dig into it more.

  • KABA connection issue - program not registered

    I am trying to troubleshoot a connection error between SAP and KABA.  I have the RFC created in SAP and when I test the connection I get a program not registered.  The KABA "amsproc" service on the KABA side has been restarted, we have occasionally received a password locked message in the SAP system log after restarting the KABA service (I believe this means SAP and KABA are communicating).  We have since reset the password, but we can not successfully test the RFC and when attempting to send IDOC's out we get the program not registered error.  Is there something on the SAP side that needs to be done to register the program or is starting the service on the KABA side going to register the program with SAP?  Any assistance would be appreciated.

    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.

  • Gateway error - Program not registered

    Hello,
    We were getting the following error while doing a "Connection test" of a TCP/IP RFC destination:
    LOCATION    SAP-Gateway on host gisrxx / sapgw00
    ERROR       program SBCX not registered
    It's an ECC 6.0 system.
    I found SAP note - - 353597 - Registering a RFC program
    I executed the following command as sidadm
    rfcexec -aSBCX -ggisrxx -xsapgw00
    But the command keeps on running on teh command prompt.
    And for that duration the RFC works.
    But after sometime the command ends and comes back to command prompt and the RFC doesn't work any more.
    Could you tell what needs to be done to resolve this issue?
    Regards,
    Gautam.

    Hi Gautam,
    Please run the program in background (Unix) or as a service (Windows).
    Please go through the following forum post. This should help.
    Run rfcexec as service on windows
    Br,
    Venky

  • 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

Maybe you are looking for