2832543 - Error "500 Internal Server Error" when running transaction SOLMAN_SETUP in SAP Solution Manager 7.2

Symptom

Transaction SOLMAN_SETUP cannot be opened and returns error "500 Internal Server Error".

Symptom one:
The initial link reports the 500 error while the real link works to display the application. The same error occurs when accessing transaction LMDB, SOAMANAGER, and others with initial link.

The initial link  http(s)://<host>:<port>/sap/public/myssocntl?sap-client=<nnn>
The real working link    http(s)://<host>:<port>/sap/bc/webdynpro/sap/wd_sise_main_app

Symptom two:
The real link also reports the 500 error. Check transaction ST22, and get the following dump:

Category               ABAP Programming Error
Runtime Errors         XML_FORMAT_ERROR
Except.                CX_XSLT_FORMAT_ERROR
ABAP Program           CL_SISE_ACT_CUSTOM_NOTE=======CP
Application Component SV-SMG-INS-CFG

Error analysis
    An exception has occurred which is explained in more detail below. The
    exception is assigned to class 'CX_XSLT_FORMAT_ERROR' and was not caught in
     procedure
    "GET_NOTE_INFO" "(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.

IV_SMP_DESTINATION
SAP-SUPPORT_PORTAL

Symptom Three:
The real link reports the 500 error with the following dump:

Category               ABAP Programming Error
Runtime Errors         SAPSQL_PARSE_ERROR
Except.                CX_SY_DYNAMIC_OSQL_SEMANTICS
ABAP Program           CL_SISE_ACT_CUSTOM_AGS========CP
Application Component SV-SMG-INS-CFG

Error analysis
    An exception has occurred which is explained in more detail below. The
    exception is assigned to class 'CX_SY_DYNAMIC_OSQL_SEMANTICS' and was not
    caught in procedure
   "GET_SRV_BY_APP" "(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:
   The current ABAP program attempted to execute an Open SQL statement
   containing a dynamic entry. The parser returned the following error: "The
   elements in the "SELECT LIST" list must be separated using commas."

Symptom Four:
The real link reports the 500 error with the following dump:

Symptom Five:

The real link reports the 500 error with the following message error:

500 Internal Server Error
The read xml document had an invalid format.
Server time:

Environment

SAP Solution Manager 7.2

Product

SAP Solution Manager 7.2

Keywords

500 Internal Server Error, SOLMAN_SETUP, LMDB, SOAMANAGER, XML_FORMAT_ERROR, SAPSQL_PARSE_ERROR, CALL_FUNCTION_NOT_FOUND, CX_SY_DYN_CALL_ILLEGAL_FUNC, UPG_IS_BRIDGE_SYSTEM, The read XML document had an invalid format. , KBA , SV-SMG-INS-CFG , Setup and Configuration of the Solution Manager system , BC-MID-ICF , Internet Communication Framework , BC-SEC-SSL , Secure Sockets Layer Protocol , BC-UPG-TLS-TLA , Upgrade tools for ABAP , 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.