After applying SP21 the web dynpro is not working (WDTypeNotFoundException)

[Former Member]

Hi

We have recently applied SP21 to our NW04 system.

The patch was successfully applied. But while accessing the Web Dynpro, we are getting WDTypeNotFoundException exception.

The Error Message is as follows :

+500 Internal Server Error

Web Dynpro Container/SAP J2EE Engine/6.40

Failed to process request. Please contact your system administrator.

Hide

Error Summary

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).

Root Cause

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

500 Internal Server Error

Web Dynpro Container/SAP J2EE Engine/6.40

Failed to process request. Please contact your system administrator.

Hide

Error Summary

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).

Root Cause

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

com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type jp.co.companyname.projectname.pp.fnp09.datapreparemodel.types.Ru_cnfind not found

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:224)

at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addAttribute(NodeInfo.java:517)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addAttribute(NodeInfo.java:530)

at jp.co.companyname.projectname.pp.fnp09.main.RawMaterialView.wdDoModifyView(RawMaterialView.java:191)

... 28 more

See full exception chain for details.

System Environment

Client

Web Dynpro Client Type HTML Client

User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322)

Version

DOM version

Client Type msie6

Client Type Profile ie6

ActiveX enabled

Cookies enabled

Frames enabled

Java Applets enabled

JavaScript enabled

Tables enabled

VB Script enabled

Server

Web Dynpro Runtime Vendor: SAP, Build ID: 6.4021.00.0000.20070905102710.0000 (release=630_VAL_REL, buildtime=2007-09-19:20:40:15UTC, changelist=460812, host=PWDFM026)

J2EE Engine 6.40 patchlevel 109749.313

Java VM Java HotSpot(TM) Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.

Operating system Windows 2003, version: 5.2, architecture: x86

Other

Session Locale ja

Time of Failure Mon May 17 18:35:52 JST 2007 (Java Time: 1197884152810)

Web Dynpro Code Generation Infos

companyname.co.jp/pp~fnp09

SapDictionaryGenerationCore 6.4010.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-12-09:22:23:41UTC, changelist=280522, host=PWDFM026.wdf.sap.corp) +

If you have any ideas please let me know.

thanks and Regards

Raghunahth L

[Former Member]

Hi raghu,

You can go to Visual administrator (/usr/sap/<SID>/JCxx/j2ee/admin--go.bat)

Give administrator credentials..

Cluster-Server-Services-webdynpro Runtime.

See if it is stopped.You can see red croos,if it is stopped.If it is,

Right click on Webdynpro Runtine and start.

One more option,you can give a try is start all teh srvices manually through

telnet

This can be done with "run' command on you system

telnet <IP adress> telnet port

telnet port will be http port ending with 8.

then give administrtaor credentials.

then go with these commands,

jump 0

add deploy

list_app

start_app-all

Try looki in for detailed error messages in default trace and application logs.

Loc : /usr/sap/<SID>/JCxx/j2ee/cluster/server0/log

Regards

Usha