Symptom
Job SAP_LMDB_NOTIFY_SAM aborts daily producing dump CX_LMDB_NO_TECHNICAL_SYSTEM
Category ABAP programming error
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_LMDB_NO_TECHNICAL_SYSTEM
ABAP: Program CL_LMDB_ABAP_MESSAGE_SERVER===CP
Application Component SV-FRN-INF-LDB
|What happened? |
| The exception of class "CX_LMDB_NO_TECHNICAL_SYSTEM" was triggered but not |
| caught anywhere in the |
| call hierarchy. |
| |
| Since exceptions represent error situations, and this error was not |
| adequately responded to, ABAP program "CL_LMDB_ABAP_MESSAGE_SERVER===CP" had |
| to be terminated.
|Error analysis |
| An exception has occurred in class "CX_LMDB_NO_TECHNICAL_SYSTEM". As this |
| exception was not |
| caught, a runtime error occurred. The reason for the exception |
| occurring was: |
| Cannot find a technical system in the LMDB |
| |
| The exception is related to the previous exception "CX_LMDB_NO_RESULT_FOUND" |
| that occurred in |
| program "CL_LMDB_API_FOR_CIM===========CP", in line 19 of include |
| "CL_LMDB_API_FOR_CIM===========CM004". The reason for this exception |
| was: |
| For class SAP_BCSystemMessageServer, a call of AssociatorNames of WBEM returned |
| no results |
| |
| The exception is related to the previous exception "CX_LMDB_NO_RESULT_FOUND" |
| that occurred in |
| program "CL_LMDB_API_FOR_CIM===========CP", in line 30 of include |
| "CL_LMDB_API_FOR_CIM===========CM001". The reason for this exception |
| was: |
| A WBEM call or query returned no results |
Read more...
Environment
SAP Focused Run
Product
SAP Focused Run 5.0
Keywords
KBA , SV-FRN-INF-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.