How To Fix CONV172 - Incorrect program in RFC destination in CONVERTER-FTP_DEST

SAP Error Message - Details

• Message type: E = Error

• Message class: CONV - Messages in Connection with the Converter

• Message number: 172

• Message text: Incorrect program in RFC destination in CONVERTER-FTP_DEST

What causes this issue?

The entered <DS:DE.FTP_DESTINATION>RFC Destination</> is valid and
accessible, but the program installed there is niether <ZH>sapftp</>
nor <ZH>sapftp.exe</>.
The following entries could have caused the error:
You entered an incorrect RFC destination in Customizing.
The RFC destination is linked to the wrong RFC server.

How to fix this error?

Carry out work step: <DS:SIMG.V_CONVERTER>Maintain Converter</>
If the server is to be started using <ZH>ConvUtil</>, you do <ZH>not</>
need to make an entry here.
In the field <LS>FTP Destination</> enter an RFC destination where the
program <ZH>sapftp</> or <ZH>sapftp.exe</> can be reached.
Set the <DS:DE.CONVERTER_STATUS>Status of the Conversion Server</> to
<LS>Ready for Conversions</>.
For the <DS:DE.CONVERTER_MESSAGE_NUMBER>Error Number for Conversion</>
choose <LS>000 No Errors Occurred</>.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CONV172 - Incorrect program in RFC destination in CONVERTER-FTP_DEST ?

  The SAP error message CONV172 indicates that there is an issue with the program associated with the RFC (Remote Function Call) destination in the context of the FTP destination. This error typically arises when the system is unable to find or execute the specified program for the FTP destination.
  Cause:
  
  Incorrect RFC Destination Configuration: The RFC destination may not be correctly configured, leading to the system being unable to locate the program.
  Missing or Incorrect Program: The program specified in the RFC destination may not exist, or there may be a typo in the program name.
  Authorization Issues: The user or system may not have the necessary authorizations to execute the program.
  Network Issues: There may be network connectivity issues preventing the system from reaching the specified destination.
  Transport Layer Issues: If the program was recently transported, it may not have been activated or may have errors.
  
  Solution:
  
  
  Check RFC Destination Configuration:
  
  Go to transaction SM59 and check the configuration of the RFC destination.
  Ensure that the target program is correctly specified and that the connection parameters are correct.
  
  
  
  Verify Program Existence:
  
  Ensure that the program specified in the RFC destination exists in the system.
  You can check this by using transaction SE38 or SE80 to look for the program.
  
  
  
  Check Authorizations:
  
  Ensure that the user or system executing the RFC call has the necessary authorizations to run the specified program.
  You can check this using transaction SU53 after the error occurs to see if there are any authorization issues.
  
  
  
  Test Connectivity:
  
  Use the Connection Test feature in transaction SM59 to ensure that the RFC destination is reachable and that there are no network issues.
  
  
  
  Review Transport Logs:
  
  If the program was recently transported, check the transport logs for any errors or issues that may have occurred during the transport process.
  
  
  
  Check for Updates:
  
  Ensure that your SAP system is up to date with the latest patches and updates, as this may resolve known issues.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SM59: RFC Destination Configuration
  SE38: ABAP Program Execution
  SE80: Object Navigator
  SU53: Authorization Check
  
  
  SAP Notes: Check SAP Notes for any known issues related to the CONV172 error message. You can search for relevant notes in the SAP Support Portal.
  Documentation: Review the SAP documentation for RFC destinations and FTP configurations for best practices and troubleshooting steps.
  
  If the issue persists after following these steps, consider reaching out to your SAP Basis team or SAP support for further assistance.