cancel
Showing results for 
Search instead for 
Did you mean: 

500 Internal Server Error - Failed to process request. Please contact your system administrator.

former_member289698
Discoverer
0 Kudos

I am getting this below error. Did anyone face the same issue ?

Build is done in JRE 1.5.04 and RUNTIME JRE is 1.4.2. NWDS is being used for build + compile. The actual error is listed here:

-------------------------------------------------------------------------------

While processing the current request, an exception occured which could not be handled by the application or the framework.

If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).

For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811.

----------------------------------------------------------------------------------

The initial exception that caused the request to fail, was:

java.lang.NoSuchMethodError:

---------------------------------------------------------------------------------------------------

The currently executed application, or one of the components it depends on, has been compiled against class file versions that are different from the ones that are available at runtime.

If the exception message indicates, that the modified class is part of the Web Dynpro Runtime (package com.sap.tc.webdynpro.*) then the running Web Dynpro Runtime is of a version that is not compatible with the Web Dynpro Designtime (Developer Studio or Component Build Server) which has been used to build + compile the application.

----------------------------------------------------------------------------------------------------------

Any ideas on how to solve this ?

Accepted Solutions (0)

Answers (1)

Answers (1)

junwu
Active Contributor
0 Kudos

build with 1.4 and don't use the api which cause the issue.