Gate Way Connection dropped - Urgent

Question

Hi,
  We created TCP/IP RFC destination. Through which we are calling the .NET services. The Listener running at .NET side. We can able to call the .NET function module. At this point of time we can see the entry(RFC) in TCode SMGW -->Goto --> Logged on clients.
  But over the period when we call the .NET function we are getting the Dump as follows.
Runtime Errors : CALL_FUNCTION_OPEN_ERROR
"CPIC-CALL: 'ThSAPECMINIT'#Transaction program not registered ""
Error text........... "program TDF_INT not registered"
Description.......... "TP TDF_INT not registered"
AT this point of time we cant see the entry(RFC)in TCode SMGW.
<u>Note:</u> When we restart the Listener at .NET side, i can able to call .NET Function module.
We are able to see whether gate way is opened or not.
Is there any way to Connect the gate way programmatically? Or anybody could say me why we its breaking the connection after some time
Raja T

Answer 1

Hi
We’re also getting the similar kind of problem. We have .Net connector, but when it talks with SAP , its giving short dump . With "user name " does not exist . Finally we have posted the message to SAP.
What you can do to trace the problem :
You can also run the report: RSRFCTRC (TO Trace RFC ) OR  Tr. S_ALR_87101279.
FYI OSS note # 313971
Symptom
The "CALL_FUNCTION_SIGNON_REJECTED" runtime error occurred.
Dumps or RFC errors occur in the syslog or in the Developer Trace files (dev_w*) for the SAPSYS user in a dialog process.
These errors occur every 5 minutes.
The analysis displays the SAPMSSY8 report or certain function modules used by the monitor architecture as the error source.
CAUTION: Various system components may cause error messages for the SAPSYS (AB0) user. This note is limited to error messages from data collectors in the monitor architecture. Refer also to Note 487873.
Other terms
SXPG_COMMAND_EXECUTE, X_ERROR, CALL_FUNCTION_SIGNON_REJECTED, RZ20, sapdba, CONTROL_PERF_REQUEST, AB0, RZ03
Reason and Prerequisites
When restarting the system, certain reports (Startup methods) are executed in monitoring, to create subtrees for different subject areas in RZ20 (for example, database monitoring).
For these subtrees to be supplied with data in the current system, additional reports or function modules (data collective methods) must run on a regular basis.
You can start startup methods and data collective methods online or in the background. Online, they run on the SAPSYS user. The SAPSYS user only has limited rights, particularly with regard to RFC calls.
RFC error messages in the monitoring area can occur in customer-specific methods.
However, there are also some SAP standard methods for the database monitoring agent of RFC syslog messages.
An external command is executed via SXPG_COMMAND_EXECUTE on the database host in these data collective methods (function modules/reports). If they are not running on the database but rather on another application server, an RFC call is started, which causes the SAPSYS user to terminate.
The following methods should only run on the central instance:
CCMS_DB_Freespace_CT
CCMS_DB_Indices_CT
CCMS_DB_LogMgt_CT
CCMS_DB_OptStat_CT
Change this configuration for these methods:
New:
RZ21 -> method definition -> Control -> startup method
X Execute method immediately after monitoring segment start
X Only on central instance
Save the configuration.
Solution
The following applies for methods not provided in the SAP standard system:
Most RFC problems in the monitoring area (RZ20) can be solved by changing the configuration for the data collection methods and startup methods concerned.
1. To find out which data collective method generated an RFC error message, an RFC trace must be generated on the host on which the RFC syslog messages occur. For more information about this, see note 176277.
In transaction SM50, activate the trace for dialog processes until the error message has occurred in the syslog again. The syslog displays the affected work process (for example, dev_w0) and the related dev_rfc* (dev_rfc0) file displays the RFC initiator.
2. In some cases the RFC initiator in the dev_rfc file is a report or function module that is directly entered as a method in
RZ21-> Method definition
In other cases, only a where-used list for the RFC initiator leads to a method in RZ21. The following always applies:
3. You can always specify which host is to be used to execute the method.
RZ21 ->
  Method definition
       -> <Display/Change>
               -> Control -> Execute Method
                  Execution -> Execute Method on
Check whether for your site method (local server,
any server, etc.) and execution type (dialog or background) are set in such a way that in the case of RFC calls (if the method uses these) no authorization problems arise.
4. As of Release 4.6B
You can also specify an executing server for startup methods.
RZ21 ->
  Method definition
       -> <Display/Change>
               -> Control -> Startup Method
                   -> Execute Location of Startup Method.
Check to see whether this configuration is correct.
Up to Release 4.5B: (The problem is corrected as of Release 4.6B.)</>
CAUTION: Here, it is not yet possible to specify the application server to be used to execute a startup method.
In particular, methods that run as data collectors in the background, if they are simultaneously startup methods, are also executed once in the dialog during the system restart. This once-off execution in the dialog occurs on an any server (cannot be specified). If the startup method was unsuccessful, it is restarted the next time you start the interactive dispatcher (after 5 minutes).
! This means that even a method that should !
! actually run in the background, writes RFC !
! error messages in the Syslog every 5 minutes !
Possible workaround.
- Remove the startup indicator for this method
- For all application servers, delete the node
  CCMS Selfmonitoring
   -> MoniInfra<AppServer>
       -> Tooldispatching (short running tasks)
           -> STARTUP<XXXXXX>
that was created for the method affected (name of the method in the long text).
- Start the method manually (Transaction SE38 or SE37).
This bypasses the startup mechanism that causes the RFC error messages
<b>P.S award the points</b>
Thanks
Saquib Khan