How To Fix RIN017 - Converter cache (CCC) could not be reset on all server.

SAP Error Message - Details

• Message type: E = Error

• Message class: RIN - RSCPINST

• Message number: 017

• Message text: Converter cache (CCC) could not be reset on all server.

What causes this issue?

During activation of a new I18n system configuration, the attempt to
reset the so called converter cache (CCC) failed. The reason is unknown.

System Response

Independent of the CCC the database tables which are relevant for the
I18n configuration were updated. But the CCC must be reset in order to
finish the activation of the new configuration.

How to fix this error?

To reset the CCC manually you can execute transaction /I18N , select
"Trouble Shooting -> CCC Cache" and press "Clear Cache" on the
subsequent screen. This needs to be done on all server. The CCC is reset
automatically whenever an application server is restarted.

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 RIN017 - Converter cache (CCC) could not be reset on all server. ?

  The SAP error message RIN017 indicates that the Converter Cache (CCC) could not be reset on all servers. This issue typically arises in the context of SAP systems that utilize the Converter Cache for handling data conversions, such as unit conversions or currency conversions.
  Cause:
  
  Network Issues: There may be network connectivity problems between the application server and the database server, preventing the reset command from being executed successfully.
  Server Configuration: The servers may not be properly configured to communicate with each other, or there may be inconsistencies in the configuration settings.
  System Load: High system load or performance issues may prevent the CCC from being reset in a timely manner.
  Database Locks: There may be locks on the database that prevent the CCC from being reset.
  Insufficient Permissions: The user executing the reset command may not have the necessary permissions to perform this action.
  
  Solution:
  
  Check Network Connectivity: Ensure that all servers can communicate with each other without any network issues. You can use tools like ping or traceroute to diagnose connectivity problems.
  Review Server Configuration: Verify that the configuration settings for the application servers and database servers are correct and consistent. Check the instance profiles and ensure that the necessary parameters are set.
  Monitor System Load: Check the system performance and load. If the system is under heavy load, consider performing the reset during off-peak hours.
  Check for Database Locks: Use database monitoring tools to check for any locks that might be preventing the CCC from being reset. Resolve any locks if necessary.
  User Permissions: Ensure that the user executing the reset has the appropriate permissions. You may need to consult with your SAP Basis administrator to verify this.
  Manual Reset: If the automatic reset fails, you may need to manually reset the Converter Cache. This can typically be done through transaction codes like SICF or RZ10, depending on your system configuration.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SICF (Maintain Services), RZ10 (Edit Profile Parameters), and SM51 (List of SAP Servers) for managing server settings and monitoring.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  System Logs: Review system logs (transaction SM21) for any additional error messages or warnings that may provide more context about the issue.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to escalate the issue to SAP support for further assistance.