rfc communications error with system destination dom_ctl

Solution

1. Solution by migrating the invalid SECSTORE entry /HMAC_INDEP/RFC_EXTERNAL_TICKET_4_TRUSTED_SYSTEM, provided that SAP Note 1491645 was implemented.

              The validity check and the migration of an SECSTORE entry are described in SAP Note 816861.

2. Solution by manually deleting two SECSTORE entries (as of Release 7.00):

• Call transaction SECSTORE.

• Choose "Execute" (F8).

• In the entries that are displayed, delete the entry /HMAC_INDEP/RFC_INTERNAL_TICKET_4_TRUSTED_SYSTEM if it is marked with a red traffic light.

• In the entries that are shown, delete the entry /HMAC_INDEP/RFC_EXTERNAL_TICKET_4_TRUSTED_SYSTEM if it is marked with a red traffic light.

• In transaction SE37, execute the function module RFC_PING with the destination NONE. If the system displays an error message, execute the function module RFC_PING again; the error message cannot appear a second time in this case.

3. Solution by executing a report (as of SAP Basis Release 620):

• Execute the report RS_TT_CLEANUP_SECSTORE. If you cannot implement the report using transaction SNOTE (due to the RFC problem), copy the source code of the report for the relevant release from the attachment of this note.