SAP Knowledge Base Article - Preview

2435477 - Outside Discovery creates ABAP Dumps with error CX_LMUF_INVALID_PARAMETER - CL_LMDB_SERVICE_AUTHORIZATION

Symptom

The following ABAP Dumps is created every 15 minutes in the SAP Solution Manager System:

Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_LMUF_INVALID_PARAMETER
ABAP Program           CL_LMDB_SERVICE_AUTHORIZATION=CP

If you have access to SAP Notes, carry out a search with the following keywords:

"UNCAUGHT_EXCEPTION" "CX_LMUF_INVALID_PARAMETER"
"CL_LMDB_SERVICE_AUTHORIZATION=CP" or "CL_LMDB_SERVICE_AUTHORIZATION=CM004"
"CHECK_AUTH_HOST_BY_NAMESP"

Function Module..... "FM_DIAGLS_PUSH_PHYSICAL_HOST"

Chosen variables

IM_PHYSICAL_HOST

<AFFECTED_HOST>

In the ABAP Dump the variable IM_PHYSICAL_HOST will show the hostname of the Outside Discovery which is causing the ABAP Dump.

In the Outside Discovery logs (e2edcc_host.log or e2edcc.log) of the affected host, the following error is present:

Feb 28, 2017 4:50:24 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]] Error      [PhysicalHostPushJob] Exception calling DataEnrichmentManager.
[EXCEPTION] java.rmi.RemoteException: RfcExecutionException; nested exception is:
Caused by: com.sap.sup.admin.abap.rfc.exception.RfcExecutionException: An exception occured during the execution of the function 'FM_DIAGLS_PUSH_PHYSICAL_HOST': UNCAUGHT_EXCEPTIONnullnullnull
Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: An exception occurred that was not caught.

Finally, when checking the Outside Discovery logs in debug mode it is possible to see that variables 'Virtual FullHostname', 'Virtual Hostname' and 'Virtual IP Address' are empty for the affected instance:

Feb 28, 2017 5:01:06 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]] Debug      [PhysicalHostPushJob:getSAPInstances] SAP Instance:
Feb 28, 2017 5:01:06 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]] Debug      [PhysicalHostPushJob:getSAPInstances] Virtual FullHostname =
Feb 28, 2017 5:01:06 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]] Debug      [PhysicalHostPushJob:getSAPInstances] Virtual Hostname     =
Feb 28, 2017 5:01:06 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]] Debug      [PhysicalHostPushJob:getSAPInstances] Virtual IP Address   =
Feb 28, 2017 5:01:06 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]] Debug      [PhysicalHostPushJob:getSAPInstances] Sid                    = <Affected System ID>
Feb 28, 2017 5:01:06 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideDiscovery:ExecTG]] Debug      [PhysicalHostPushJob:getSAPInstances] SystemNbr              = <Instance Number>

To check the Outside Discovery logs in debug mode, check section 'Outside Discovery Log Files' of the Outside Discovery WIKI.


Read more...

Environment

  • SAP Solution Manager 7.10 and 7.20
  • SAP Solution Manager Diagnostics

Product

SAP Solution Manager 7.1 ; SAP Solution Manager 7.2

Keywords

KBA , SV-SMG-DIA-SRV-LSC , OS and DB Host Discovery (Outside Discovery) , 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.