Solution : https://service.sap.com/sap/support/notes/581509 (SAP Service marketplace login required)
Summary :
The SAP Note addresses the failure in establishing a connection to an external RFC server or in calling a function module via RFC, resulting in a "timeout during allocate" message. For "Start on..." configured destinations, the error may display as "timeout during allocate of registered program" (related to Note 1333483). Errors arise from incorrect RFC server program operation, misconfigured destinations, overly short timeout intervals, or network issues. Solutions include verifying external RFC server programs, adjusting destination settings, optimizing timeout configuration considering system landscape, and addressing network errors. Furthermore, proper error management via transaction SMGW can isolate issues, with RFC traces needed for deeper analysis per Note 878860.
Key words :
external rfc server program works correctly, application programming interface reason, application-specific scenario permits, external rfc server program, external rfc program, rfc server program, rfc api rfcaccept, require rfc traces, registered server program, front-end workstation
Related Notes :
| 1501503 | RFC destinations of type 'T' do not work |
| 1333483 | Timeout during allocate of a registered program |
| 1033987 | Remote login using NAT or SAP router fails |
| 1032461 | MDX parser does not start |
| 944792 | Runtime analysis when you start external RFC servers |
| 878860 | RFC tracing for ABAP-to-external communication |
| 638701 | Starting RFC servers takes too long |
| 566566 | Timeout during allocate, syslog R49 CPICRC 027 SAPRC 456 |
| 500235 | Network Diagnosis with NIPING |
| 211365 | RfcAttach error with DNS or multiple host names |
| 101971 | 37527 Graphical full screen is not available (RFC) |
| 21151 | Multiple Network adapters in SAP Servers |