Sap Sm59 Registered Program
Apr 28, 2016 Purpose. Help you to understand the allocation of the external programs registered to the Gateway of an SAP instance. This page contains information about the allocation of external programs in the Gateway of an SAP instance, aiming to demonstrate the. See Maintaining RFC Destinations and their SNC Options Using Transaction SM59. Acceptor (Registered Program) To apply SNC protection to registered programs that communicate with AS ABAP systems using RFC, you need to specify the SNC options in either the saprfc.ini file or using the program interface in rfclib.
Skip to end of metadataGo to start of metadataPurpose
Help you to understand the allocation of the external programs registered to the Gateway of an SAP instance.
Overview
This page contains information about the allocation of external programs in the Gateway of an SAP instance, aiming to demonstrate the analysis behind their usage and common errors.
RFC Error 'Timeout during allocate'
The most common error related to the allocation of Gateway registered programs is the error 'timeout during allocate'. This error is described in the SAP Note 1333483 in details. One of the possible causes mentioned is the fact that the affected program is not registered multiple times in the Gateway and the only registration performed is already in use, causing the below timeout if the program is attempted to start more than once. The analysis behind this aspect of the 'timeout during allocate' error will be explained in details in the next chapters of this wiki page.
Analyzing the RFC Destination Configuration
In order to check how exactly the RFC destination for this program is configured, you will need to access transaction SM59 and open the RFC destination responsible for starting the TP you want to analyze (ExampleWiki as per the above image). After selecting the RFC destination, in the Technical Settings tab as per the image below, one specific Gateway to communicate with the External Server can be defined in box 'Gateway Options'.
Gateway Options is Specified in the RFC Destination
If the Gateway Host and Gateway Service are specified in the Gateway Options box as per the below image, it means the communication with this External Server where this External Program is started will only be performed by the defined Gateway (sapgw00 running in the host hostexample1).
Gateway Options is Not Specified in the RFC Destination
If the Gateway Host and Gateway Service are not specified in the Gateway Options box as per the image below, the local Gateway will communicate with the External Program (E.g. Application Server where the user is currently logged on or where the job is running). In this scenario, the External Program has to be registered in all the instances of this SAP system, otherwise the error 'program not registered' will be triggered as per the SAP Note 1893014.
Gateway Registrations of the External Program
The next step of this analysis which follows the analysis of the RFC destination is the analysis of the Gateway registrations of this External Program. For this, you must access the transaction SMGW and use the meny GoTo, selecting the option 'Logged on Clients'. This is shown in the below image. The SMGW transaction should be accessed in the instance defined in the Gateway Options box, in case it was defined, or all the instances of the SAP system should be analyzed, in case the fields were not defined.
In the Logged-On Clients screen of the SMGW transaction, you can order the 'TP Name' column in Descending or Ascending order in order to make it easier to visualize all the registrations for the External Program you are analyzing. After this you can search for the External Program name and you will find them as shown in the below image.
You can count now the number of lines reporting the TP Name which corresponds to the External Program you are analyzing and this is indicating the maximum number of simultaneous communications that can be started with this External Program from this Gateway.
Gateway External Program Current Connections
In the initial screen of the SMGW transaction, you can order the column called 'Sym. Destination' in ascending or descending order and after this search for the name of the External Program you are analyzing. After you find the connections started with this program as per the below image, you can check the number of active connections which are performed with this External Server. The maximum number of connections possible is equal to the number of registrations this program has with this Gateway, as per the previous step of this analysis. In the below image, you can see the last line of this External Program reporting the Status 'connecting'. This connection can time out with the error 'timeout during allocate' since all the registrations of this External Program are already in use (status Connected).
In summary, you have to make sure the External Program is registered enough times to the Gateway (in case it is possible to register this program more than once, since this is defined by the program designers itself). In case the program is started for more times than it was registered in the Gateway, the error 'timeout during allocate' can happen, depending on the value of the time out parameter gw/reg_timeout (as mentioned in SAP Note 1333483), since a connection can be freed before the time out period is reached, allowing the connection under 'connecting' status to be established and changed to 'Connected' status, consequently avoinding the error.
It is important to note that you can see this dump when the external program is hanging or does not respond fast enough as well. You can identify this behavior if you can see the 'Timeout during allocate of a registered program' occurring without any active connection to the external program or if just a few active connections are reported when you have a greater number of registrations performed for this external program in the Logged On Clients screen.
Related Documents
Related SAP Notes/KBAs
SAP Note 1333483 - Timeout during allocate of a registered program
SAP KBA 1893014 - program not registered
محمد عبد الرحمن الطوالبة. د. Sahih al bukhari bangla free download.
The Purpose of this wiki is to rovide details on the Return code 679 which indicates a 'Program not registered' error.
Overview
This wiki provides details on how to determine the RFC destination that is reporting the error, explains how a test program can be registered the gateway and also provide details on who is responsible for registering the server program.
Identifying the issue
Communication error 679 is reported in the system log (SM21):
All CPIC return codes are mentioned in note 63347. Return code 679 means 'Transaction Program is not registered':
TP_NOTREGISTERED 679 TP not registered
To find out more detail on which program is causing the error the corresponding rfc trace file must be checked.
Determining the failing RFC destination
In the example above, the work process number (Nr) is 01 so the dev_rfc1 (St11) will contain more details. Search this file for the timestamp reported in sm21, in this case it is 171012.
You will see something like the following:
This shows that the problem is related to RFC destination REGTEST and program 'Program1'. If you
go to transaction SM59 and test the destination REGTEST the 'program not registered' error will
be returned:
Example of registering test program rfcexec
Note 353597 provides details on how to register a server program:
<program name> -a<program ID> -g<SAP gateway hostname> -x<gatewayservice>
So, for our example above 'Program1 'needs to be registered:
<program name> -aProgram1 -gy52tdc00 -xsapgw52
<program name> is the name of the program you are trying to run.
Program1 is the name given in SM59 (ProgramId).
Y52tdc52 is the gateway host (from the dev_rfc1 trace above) and sapgw52 is the gateway service (from the dev_rfc1 trace).
If the program has been registered on the local gateway you should see an entry for it in
SMGW > 'Logged on Clients', it will be shown as a REGISTERED_TP / REGISTERED SERVER.
The example given in note 353597 is:
rfcexec -atest -gHOST -xsapgw00
Please note that 'rfcexec' is a sample program delivered with the RFCSDK. If you do the following:
rfcexec -aProgram1 -gy52tdc00 -xsapgw52
This means that you are trying to register the sample program 'rfcexec' with ID 'Program1' on the gateway.
If you are not trying to connect to program rfcexec, the developer of the program you are trying to run should be contacted to advise how to correctly register their program.
In some cases, a particular service may need to be started.
You should know the name of the program you are trying to register. There is no direct possibility to find out the name of the backend program which is associated with the Program ID used for a registered connection in SM59. The only possibility is to do a level 3 trace of the gateway to get the IP and remote number of the program that registers.
With this information you need to remotely execute a netstat and search for the pid of the program that is running on that port. With this pid you goto the ps command to get the name and location.
Checklist
For a checklist of what to do in case of Program not registered error (RC 679) see the following note:
Knight Rider 2 free download video game for Windows PC. Download free full version “Knight Rider 2” from Gameslay. The game setup is tested and 100% fully working PC Game for free Download. The direct/torrent download from Gameslay.net is highly compressed and free of any virus, spyware or adware. Knight Rider 2 (Video Game) Review Knight Rider 2 is racing video game. 
2104408 - Checklist for 'program not registered' errors
Related Documents
Related SAP Notes/KBAs
353597 Registration of RFC server programs
1408081 Basic settings for reg_info and sec_info
1305851 Overview note: 'reg_info' and 'sec_info'