Hello guys, ims having this 500 internal server error, please verify dump analisys and let me know
Categoría Error de programación ABAP
Programa ABAP /BOBF/CL_TRA_SERVICE_MGR======CP
Fecha y hora 03.10.2019 10:36:19
Texto breve An exception has occurred that was not caught.
¿Qué ha sucedido? Exception '/BOBF/CX_FRW_FATAL' 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 '/BOBF/CL_TRA_SERVICE_MGR======CP' had to be terminated.
¿Qué puede hacer? Note down which actions and inputs caused the error. To process the problem further, contact you SAP system administrator. Using Transaction ST22 for ABAP Dump Analysis, you can look at and manage termination messages, and you can also keep them for a long time.
Anál.errores An exception has occurred which is explained in more detail below. The exception is assigned to class '/BOBF/CX_FRW_FATAL' and was not caught in procedure "SET_CONFIGURATION_ERROR" "(METHOD)", nor was it propagated by a RAISING clause. Since the caller of the procedure could not have anticipated this exception, the current program was terminated. The reason for the exception is: Error de configuración de BO de comp.'Unknown or local'; véase info de aplicación This exception is closely related to a previous exception "/BOBF/CX_FRW_CORE", which was raised in program "/BOBF/CL_FRW_FACTORY==========CP", in line 153 of (include) program "/BOBF/CL_FRW_FACTORY==========CM00A". The reason for the exception occurring was: Error de configuración: Memoria compartida inconsistente: Elemento /BOBF/CL_CONF_READONLY========CP This exception is closely related to a previous exception "CX_SHM_INCONSISTENT", which was raised in program "CL_SHM_AREA===================CP", in line 2 of (include) program "CL_SHM_AREA===================CM017". The reason for the exception occurring was: La definición de un tipo de un objeto (de datos) que se encuentra en la instancia EHHSS_INCIDENT en mandante del área /BOBF/CL_CONF_SHARED no coincide con la definición del tipo utilizada en el programa de adjunción.
Notas para corregir errores The exception must either be prevented, caught in procedure "SET_CONFIGURATION_ERROR" "(METHOD)", or the possibility of it occurring must be declared in the RAISING clause in the procedure. To prevent the exception, note the following: 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" /BOBF/CX_FRW_FATAL "/BOBF/CL_TRA_SERVICE_MGR======CP" or /BOBF/CL_TRA_SERVICE_MGR======CM002 "SET_CONFIGURATION_ERROR" If you cannot solve the problem yourself, please send the following information to SAP: 1. This description of the problem (short dump) To do this, choose System -> List -> Save -> Local File (unconverted) on the screen you are in now. 2. A suitable system log To do this, call the system log in transaction SM21. Restrict the time interval to ten minutes before the short dump and five minutes after it. In the display, choose System -> List -> Save -> Local File (unconverted). 3. If these are programs of your own, or modified SAP programs: Source code of these programs To do this, choose More Utilities -> Upload/Download -> Download in the Editor. 4. Details regarding the conditions under which the error occurred or which actions and input caused the error.