SAP Knowledge Base Article - Preview

2665338 - Exception CX_MSC_RUNTIME_ERROR in Managed System Configuration step Maintain RFCs - Solution Manager 7.2

Symptom

The following symptoms have been  encountered while proceeding with the Set Up for Step 3 Maintain RFCs of Managed System Configuration scenario:

Symptom 1:

500 Internal Server Error

An exception was raised
Server time:

Symptom 2:

Category               ABAP Programming Error
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_MSC_RUNTIME_ERROR
ABAP Program           CL_MSC_SECURE_PROP============CP
Application Component  SV-SMG-INS-CFG-MNG

Short Text

An exception has occurred that was not caught.

What happened?

Exception 'CX_MSC_RUNTIME_ERROR' 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_MSC_SECURE_PROP============CP' had
to be terminated.

What can you do?

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.

Error analysis

An exception has occurred which is explained in more detail below. The
exception, which is assigned to class 'CX_MSC_RUNTIME_ERROR' was not caught and
therefore caused a runtime error. The reason for the exception is:
An exception was raised

This exception is closely related to a previous exception "CX_SISE_GS", which
was raised in program "CL_SISE_GS_OBJECT=============CP", in line 46 of
(include) program "CL_SISE_GS_OBJECT=============CM00C". The
reason for the exception occurring was:
Secure storage migration should be performed: Apply SAP Note 816861, and re-run
the activity (Cannot find entry /SOLMAN_SETUP/<RANDOM HEX HERE>
in secure store)

OR

An exception has occurred which is explained in more detail below. The
exception, which is assigned to class 'CX_MSC_RUNTIME_ERROR' was not caught and
therefore caused a runtime error. The reason for the exception is:
An exception was raised

This exception is closely related to a previous exception "CX_SISE_GS", which
was raised in program "CL_SISE_GS_OBJECT=============CP", in line 46 of
 (include) program "CL_SISE_GS_OBJECT=============CM00C". The
reason for the exception occurring was:
Secure storage read exception: Access to entry
/SOLMAN_SETUP/<RANDOM HEX HERE> in the secure storage denied


Read more...

Environment

SAP Solution Manager 7.2

Product

SAP Solution Manager 7.2

Keywords

Secure storage migration should be performed: Apply SAP Note 816861, and re-run the activity, UNCAUGHT_EXCEPTION, CX_MSC_RUNTIME_ERROR, CL_MSC_SECURE_PROP, CL_SISE_GS_OBJECT , KBA , SV-SMG-INS-CFG-MNG , Managed System Configuration , 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.