How To Fix CNVMBTRFC123 - Destin. &1 deaktiv. oder in schlechtem Zustand; Verbind.-Prüf. nicht erl.

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 123

• Message text: Destin. &1 deaktiv. oder in schlechtem Zustand; Verbind.-Prüf. nicht erl.

Was verursacht dieses Problem?

It is detected a problem with the connection of a destination. Because
of this the connection state of this destination reflects this issue. E.
g. if a connection request don?t get the response in a specific period
of time then the destination get the connection state 'N'. If the
connection state inidcates that something is not OK with the destination
the RFC Management don?t do the connection check and the destination is
not used. This also applies to deactivated RFC destinations in a
package.
Destination is deactivated
In table CNVMBTDEST in field DEACTIVATED you find the information about
the deactivation state. Keep in mind that for each remote system the
state can be different for the destinations. Viewing deactiavation state
see heading 'Get destination and deactivaten state'.
No connection check explicitely choosen
When calling the function for checking the connection we have the import
parameter NO_CONNECTION_CHECK. If this parameter is set then no
connection check will be done.
Destination state doesn?t allow the check
In table CNVMBTDESTSTATE you find the state for a destination (also
called connection state). If there is no entry then it can be assumed
that the destination is OK. If there is an entry then all states with
exception of O (connection OK) and the initial entry indicating that
there is something not OK with the destination and no connection check
will be done untill the issue is fixed. For destinations in the control
system you find the destination state in the control system and for
destinations in the remote system accordingly in these systems. Viewing
destination state see heading 'Get destination and deactivation state'.

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?

Get destination and deactivation state
The destination and deactivation state in the different execution
targets of a package can be viewed in the RFC Management in tab
'Definition' with button 'State'. Before clicking on the button you have
to choose the destination from where you want to get the state. To
select the destination you have to mark a line in the table. If no line
is markt/selected then the Control Destination is choosen.
Reset destination state (connection state) in the RFC Management
Reset the destination state of several or all destinations. You can
reset the connection of several destinations by clicking on the refresh
button in the application toolbar. If one of the destinations with a bad
connection state then you are asked whether you want to do a full
refresh. With the full refresh all destinations will be checked. Without
the full refresh only the destinations without a bad connection state
checked. When during the full refresh the connection check of a bad
connection is successful then the state will be reset.
You can reset the destination state in the RFC Management in tab
'Definition' by clicking button 'State' after you have selected the
destination where you want to get the destination state. If no
destination is selected then automatically the Control destination is
choosen. You get a list with all destinations of the selected system. In
column 'Connection State' you see the connection state. If the field is
not initial or with state 'O' then the destination got a bad connection
state. Set the cursor on the line with the destination where you want to
reset the state. After pressing button 'Reset' the destination will be
reset.
Reset destination state (connection state) for each destination
You can reset the connection state for each destination with transaction
RESET_RFC_STATE. Call the transaction and enter or choose the
destination id. Press the button 'RESET' to reset the connection state.
If you want to reset the connection state of a destination in a remote
system you have to logon to this system and do the steps previously
described.
Activate destination
You can activate all destinations of a package at once with transaction
SET_RFC_STATE. Enter the package number in field 'Package' and press
button 'Activate'. All destinations of this package will be activated.
You can activate a single or several destinations in the RFC Management
in tab 'Definition' by pressing button 'State' after you have selected
the destination where you want to activate the destination. If no
destination is selected then automatically the Control destination is
choosen. In the list displayed in column 'Deactivated' you see the
deactivated state. If the field is initial then the destination is
active. To activate a destination you have to set the cursor on the line
with the destination you want to activate. After pressing button
'Activate' the destination will be active.
Set waiting time for response of asynchronous RFC check
If you get the connection status 'N' (System not available or no
connection possible) for one or several of your destinations and the
connection is OK but very slow then you can increase the waiting time
for the response of an asynchronous check with the Global Parameter
GLOBAL_ASYNC_WAIT_TIME. The default value is 60 seconds. You can
maintain the Global Parameters in your SAP LT/TDMS 4.0 project in tab
'Systems', in the Migration Server Overview for SAP TDMS (transaction
CNV_MBT_TDMS) or SAP Landscape Transformation Overview (transaction
CNV_MBT_SLOP) in the menu GOTO->GLOBAL PARAMETER, or with transaction
CNV_MBT_GP.

Vorgehensweise für Systemadministratoren

Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE