Detailed error messages with stack trace in Web Dynpro, SAP security note 962319

SAP security note 962319, "Detailed error messages with stack trace in Web Dynpro Java". Below are the symptom and the SAP recommended solution.

Description

Symptom

This SAP Security Note addresses the issue of insufficient detail in error messages generated by Web Dynpro for Java, a component of SAP NetWeaver. By default, error messages may not provide the necessary information, such as stack traces, which are essential for effective debugging and troubleshooting.

Users encounter generic error messages like "500 Internal Server Error" without detailed information, making it challenging to identify and resolve underlying issues within Web Dynpro for Java applications.

Solution

Error messages in Web Dynpro for Java can be configured to display varying levels of detail based on the system type and specific settings. The procedures differ slightly between lower and higher releases.

Procedure for Lower Releases (below 7.10):

• Check System Type: Navigate to Licensing Adapter → General → SystemType in the Visual Administrator. If set to DEVELOPMENT_MODE: Verbose error messages are displayed. If undefined: Proceed to the next step. If set to another value: Only exception IDs are shown. Use these IDs to search default traces for detailed information.
• Evaluate Development Mode: If SystemType is undefined, use the Config Tool to go to Configurations → webdynpro → sap.com → tc~wd~dispwda → Propertysheet default. Check the DevelopmentMode property. If true, verbose error messages are enabled.
• Enable Detailed Error Response: If verbose messages are needed but not displayed, the issue may originate from other NetWeaver components. In the Visual Administrator, set Properties → HTTP Provider → DetailedErrorResponse to true.
• Review Log and Trace Files: Detailed error messages and stack traces are logged in files such as usr\sap\<SID>\<instance>\j2ee\cluster\server<number>\log\defaulttrace.trc.<number>. Search for exception IDs or use timestamps/user IDs to locate relevant information.

Procedure for Higher Releases (7.10 onwards):

• Check System Type: In NW-A, navigate to Configuration → Infrastructure → Licenses → SystemType. If set to DEVELOPMENT_MODE: Verbose error messages are displayed. If undefined: Proceed to the next step. If set to another value: Only exception IDs are shown. Use these IDs to search default traces for detailed information.
• Evaluate Development Mode: If SystemType is undefined, go to Configuration → Infrastructure → Application Modules → sap.com/tc~wd~dispwda → Propertysheet default. Check the DevelopmentMode property. If true, verbose error messages are enabled.
• Enable Detailed Error Response: If verbose messages are needed but not displayed, the issue may originate from other NetWeaver components. In NW-A, navigate to Java System properties → services → HTTP Provider → Properties, and set DetailedErrorResponse to true.
• Review Log and Trace Files: Detailed error messages and stack traces are logged in files such as usr\sap\<SID>\<instance>\j2ee\cluster\server<number>\log\defaulttrace.trc.<number>. Search for exception IDs or use timestamps/user IDs to locate relevant information.

CVSS

Score 5.3 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References

• Web Dynpro error page, known error situations, error codes
• Hide detailed technical info in Web Dynpro Java error page