How To Fix CNVMBT090 - RFC Destination &1 unlocked by user &2.

SAP Error Message - Details

• Message type: E = Error

• Message class: CNVMBT - Messages for MBT/API/PCL

• Message number: 090

• Message text: RFC Destination &1 unlocked by user &2.

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNVMBT090 - RFC Destination &1 unlocked by user &2. ?

  The SAP error message CNVMBT090 indicates that an RFC (Remote Function Call) destination has been unlocked by a specific user. This typically occurs in the context of data migration or conversion processes, particularly when using the SAP Migration Cockpit or similar tools.
  
  Cause:
  
  User Locking: The RFC destination is locked by a user, which prevents other users or processes from accessing it. This can happen if a user is currently using the destination or if there was an error in a previous session that left the destination in a locked state.
  Session Timeout: If a user session times out or is terminated unexpectedly, it may leave the RFC destination in a locked state.
  
  Configuration Issues: There may be configuration issues with the RFC destination itself, such as incorrect settings or permissions.
  
  
  Solution:
  
  
  Unlock the RFC Destination:
  
  You can unlock the RFC destination by using transaction SM59 (RFC Destinations). Locate the relevant RFC destination and check its status.