Symptom
Hash check report is being executed to ensure that the SLD is consistent, but the job is failing with these message errors and dump below.
Job started
Step 001 started (program RLMDB_CR_CONTENT_HASHER, variant &0000000000264, user ID <user>)
Report Version 3
Used WBEM Client is <hostname:port/sld/cimom (sld/active)
CIM Model Version: X.X.XX, CR Version: SAP_CR XX.X
Internal session terminated with a runtime error UNCAUGHT_EXCEPTION (see ST22)
Job cancelled
DUMP
Category ABAP Programming Error
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_WBEM_EXCEPTION
ABAP Program CL_LMDB_CR_CONTENT_HASHER=====CP
Application Component SV-SMG-LDB
----------------------------------------------------------------------------------------------------
|Short Text
| An exception has occurred that was not caught.
----------------------------------------------------------------------------------------------------
|What happened?
| Exception 'CX_WBEM_EXCEPTION' was raised, but it was not caught anywhere along the call hierarchy.
| Since exceptions represent error situations, and this error was not adequately responded to, ABAP program 'CL_LMDB_CR_CONTENT_HASHER=====CP' had to be terminated.
----------------------------------------------------------------------------------------------------
|Error analysis
| An exception has occurred which is explained in more detail below. The exception, which is assigned to class 'CX_WBEM_EXCEPTION' was not caught and therefore caused a runtime error. The reason for the exception is:
|Error in processing of HTTP request: (401)Connection closed
----------------------------------------------------------------------------------------------------
|How to correct the error
| If the error occurs in a non-modified SAP program, you might be able to find a solution in the SAP Notes system. If you have access to the SAP Notes system, check there first using the following keywords:
| "UNCAUGHT_EXCEPTION" CX_WBEM_EXCEPTION
| "CL_LMDB_CR_CONTENT_HASHER=====CP" or CL_LMDB_CR_CONTENT_HASHER=====CM005
| "GET_SORTED_INSTANCE_HASHES"
----------------------------------------------------------------------------------------------------
Read more...
Environment
SAP Solution Manager 7.2
Product
Keywords
(401)Connection closed, UNCAUGHT_EXCEPTION, CX_WBEM_EXCEPTION, CL_LMDB_CR_CONTENT_HASHER=====CP, CL_LMDB_CR_CONTENT_HASHER=====CM005, GET_SORTED_INSTANCE_HASHES, closed , KBA , SV-SMG-LDB , Landscape Management Database (LMDB) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview