cancel
Showing results for 
Search instead for 
Did you mean: 

how to display the error message during the web dynpro application runtime

Former Member
0 Kudos

hi,

I'm a java developer,During i 'deploy and run ' a web dynpro application on server-1,if the application have some runtime errors. there are displayed many infomation about the runtime error,such as exception track,etc.

But when i do the same on server-2,there just show something like:

500 Internal Server Error

SAP NetWeaver Application Server 7.00/Java AS 7.00

Failed to process request. Please contact your system administrator.

but the server-1 will stop the j2ee engine.

how can do i make server-2 show detail error message as server-1. when i debug web dynpro application need these infomation.

Appreciate your inputs...

(Note:server-1 and server-2 have same software version)

Edited by: BingLin Zhong on Feb 18, 2008 2:13 AM

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

The Sap-Notes 962319:

1. Check in the Visual Administrator, "Licensing Adapter" -> "General" -> "SystemType" !

If it is set to "DEVELOPMENT_MODE", verbose error messages are shown.

If it is undefined, proceed with the next step.

If it is set to something else, only exception IDs are shown. In this case the only chance is to search for this exception ID in the default traces.

2. If the system type is undefined, then in the Config Tool "Configurations" -> "webdynpro" -> "sap.com" -> "tcwddispwda" -> "Propertysheet default" -> "DevelopmentMode" is evaluated. If it is "true", verbose error messages are shown.

3. If verbose error messages are required but still the short version is shown, you probably face an error message that is not raised by Web Dynpro but by other components of the NetWeaver. In the Visual Administrator set "Properties" -> "HTTP Provider" -> "DetailedErrorResponse" to "true".

4. In addition to the error page shown in the browser or client, important messages - including error messages and stack traces - are written to the log and trace files, e.g. to the default traces usr\sap\<SID>\<instance>\j2ee\cluster\server<number>\log\defaulttrace.trc.<number>.

a) In some cases, when an exception ID is included in the error message, the detailed error message can easily be retrieved in the log file.

b) When no exception ID is given, you have to search for the detailed error message in the log specifying time stamp and/or user ID.

Always consider restarting the system after making changes on the settings.

It is not recommended to switch the "SystemType" to an inappropriate value just for viewing verbose error messages. The system type potentially affects framework, applications and licensing in an perhaps unintended way.

In the past there was no distinction between different system types regarding error messages. For security reasons this distiction has been introduced. It is not intended to show stack traces in non-development systems in the future. SAP does not provide workarounds or patches to enable such a behaviour again.

Former Member
0 Kudos

To view the thread for the solution,visit: