SAP Knowledge Base Article - Preview

2589295 - RfcGetException - Client is not available in this system - AS Java node terminates with exit code 2150


The following entries can be found:

  • in dev_server<x> log file:

F  [Thr 139893759174400] *** LOG => SfCJavaVm: exit hook is called. (rc = 2150)

F Thu Aug 24 15:45:31 2017

F  ********************************************************************************
F  *** ERROR => Java node 'server0' terminated with exit code 2150.
F  ***
F  *** Please see section 'Java program exit codes'
F  *** in SAP Note 1316652 for additional information and trouble shooting advice.
F  ********************************************************************************

F  [Thr 139894930773856] *** LOG => exiting (exitcode 2150, retcode 1).

  • in std_server<x> log file:

Caused by: Client <XXX> is not available in this system
... 29 more

FATAL: Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [] failed to start]



Changing UMEBackendConnection parameters in configtool; SAP Netweaver Application Server for Java all versions


SAP NetWeaver Application Server for Java all versions ; SAP NetWeaver all versions


backend destinations, ume configuration, configtool, config tool, configuration editor, propertyhseet,, RfcGetException, service change, not applying, no effect, cluster config, expert mode, custom value, ume.r3.connection, jco.client.client, UMEBackendConnection , KBA , BC-JAS-SEC-UME , User Management Engine , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , BC-JAS-SF , Startup Framework , BC-JAS-ADM-ADM , Administration , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.