How To Fix CNVMBTRFC142 - Schlechter Verbindungsstatus für Destination &1 - Ursache &2

SAP Error Message - Details

• Message type: E = Error

• Message class: CNVMBTRFC - Messages used in RFC Management and its objects

• Message number: 142

• Message text: Schlechter Verbindungsstatus für Destination &1 - Ursache &2

Was verursacht dieses Problem?

An RFC destination can have a connection state. If the destination got a
bad connection state, this is the connection check detects problems with
that destination, then no connection checks will be performed by the RFC
Management for that destination. For example the Destination to the
sender system in the control system has its connection state and the
Destination to the sender system in the sender system itself also has
its own connection state. So it can be that the connection state of the
sender destination in the control system is OK but in the sender system
the destination got a bad connection state.
The connection state represents the state of a destination at the time
where the last check were performed. It could be that the rfc check
found out that the password of the destination is not OK. In that case
the destination get the connection state 'P'. If the user fixed the
issue and the destination is working fine again then the state has to be
reset by the user. Resetting the state can be done in different ways.
Reset state in the System Landscape
In the system landscape you can press button 'Check state'. With the
check the destinations with bad connection state will be checked again.
If the reason for the bad connection state don?t exist anymore then the
status will be reset. In contrast to the 'Check state' the refresh
button won?t do the connection checks for the destinations with bad
connection state.
Reset the connection state of a single destination
The state for a single destination can be reset by transaction
RESET_RFC_STATE. This has to be done for each destinaton with bad
connection state in the system where the destination is created.
Reset connection state in the RFC Management
A prerequisite is the existence of a package. To call the RFC Management
you have to execute the activity 'Define RFC Destinations' in the phase
'Package settings'. You can reset the state in the RFC Management in tab
'Definition'. For example If you want to reset the state for the sender
destination in the sender system, mark the row where the system role
'Sender System'. Afterwards press button 'State'. You will see a table
with all the destinations the package needs in the sender system. Mark
the destination by clicking with the cursor on the row where you want to
reset the state and press button 'Reset'. If the reason for the bad
connection state doesn?t exist anymore then the connection state will be
reset.
The fastest way to reset the connection state is to do a refresh in the
RFC Management. If at least one destination got a bad connection state
then the refresh can be done with a full refresh. The full refresh means
that a connection check for the destinations with bad connection state
will be done. With a successful connection check the connection state
will be reset.
Reasons for a bad connection state:
RFC check timed out
The reason for the bad connection state was that the RFC connection
check exceeds a period of time. To avoid the calling program from
getting a time out we do the rfc checks asychronously. If the connection
check don?t respond in a period of time then the destination get the
connection state 'N'.
User/password issue
The reason for the bad connection state was that the RFC connection
check faced an issue with the user or password of the RFC destination.
In that case the RFC destination gets the connection state 'P'.
Analysing your destination in SM59
You get a lot of information about your destination in transaction SM59.
Start with checking the connection by pressing button 'Test connection'
or in the menu via Test->connection or press key <(><<)>F8>. It will be
checked whether it is possible to connect to the system. The user data
like user name and password won?t be checked. If you want to check the
validity of the user and password you have to do an authorization check.
You can execute it via the menu Test->authorization or pressing key <(>
<<)>F6>. In tab 'Logon/Security' you can see the settings for logon
which includes language, client, user, password. Dependend on the
different settings like Trusted Systems and Load Balancing the settings
can differ. E. g. you don?t have a password in a destination for Trusted
Systems.

Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.

Systemantwort

Wie behebe ich diesen Fehler?

Vorgehensweise für Systemadministratoren

Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE