Run a web dynpro application encounter WDUMException exception...

Dear guys,
We currently encounter a error when we run a web dynpro application.
That is, once a user click a url which will redirect to the enterprise portal,
the com.sap.tc.webdynpro.services.sal.um.api.WDUMException is thrown.
I have checked the cause of the exception is that "if there is no user (neither authenticated nor anonymous user) attached to the current session"
The following is our situation:
When linking to EP domain(ex. http://sapep.xxx.com), single signed on wil automatically process.
The url which I mentioned above is something like "http://sapep.xxx.com/portal?doc=xxx&ver=2010"
Our web dynpro program will invoke the IWDClientUser api initially for get the currently logon user's information.
And this is caused the WDUMException.
We think that the error is because that the session is not created while loading the web dynpro application,
so that, the system can't get the cuurent user with a non-user session.
The situation is not often happened. We think this is because of the system service issue.
So we try to prevent this problem with the following mechanism:
When the excpetion is thrown, we invoke a waiting program to let the system has time to generate the require session.
So when invoke the IWDClientUser, this exception can be prevented.
Any suggestion.please advise, thanks.

Try using WDPortalUtils.isRunningInPortal() method to see if the session (somehow) disconnects
Hi,
We check the method you proposing, but seems it's not the method to check the session of the current user.
The API of WDPortalUtils.isRunningInPortal() is as follows:
public static boolean isRunningInPortal()
        Checks whether or not the Web Dynpro application is running the the portal environment or not.
        Returns:
              true if the Web Dynpro application is running in the portal environment, false otherwise.
Is there any other API which can check the current session alive or not?
thanks.

Similar Messages

  • Running ABAP Web Dynpro Application without host entry of web server

    Hi All,
    I am trying to run a web dynpro application, its working fine when I have done host entry (host nam.domain.extension) of web server.
    But when I remove this entry from host file it not runs.
    Can you tell me the posibility of running this application without host entry? Based on this possibility I have to proceed my work. Please guide me.
    Thanks and Regards
    Sudhir Gupta

    Hi Sudhir ,
    See the below link , its necessary to provide FQDN.
    http://help.sap.com/saphelp_nw70/helpdata/en/67/be9442572e1231e10000000a1550b0/frameset.htm
    Regards
    Yash

  • Getting error "Access via null" when running the web dynpro application

    Hi experts,
    I am getting the below error while executing my web dynpro application
    500 SAP Internal Server Error
    ERROR: Access via 'NULL' object reference not possible. (termination: RABAX_STATE)
    I am getting the error only when I am calling a method create manufacturer from my web dynpro program. If i comment this code my application works fine
    CALL METHOD wd_this->mo_ch_instance->create_manufacturer
      EXPORTING
        gi_manufacturer = ls_manufacturer
      IMPORTING
        lv_message      = lv_status
    i have created a attribute mo_ch_instance of type YSRM70CL_CH_SW_MD  where YSRM70CL_CH_SW_MD is the class which has the create_manufacturer method that i am using in my code.
    Kindly let me know whats the issue.
    Regards,
    Vinod

    Hi,
    if   wd_this->mo_ch_instance is not initial.
    CALL METHOD wd_this->mo_ch_instance->create_manufacturer
    EXPORTING
    gi_manufacturer = ls_manufacturer
    IMPORTING
    lv_message = lv_status
    endif.
    Check wether you have created the object for that class r not.
    Regards,
    Lekha.

  • How to run mobile web dynpro application

    Hi experts,
    I'm using NetWeaver Developer Studio for Mobile SP03.
    I create a mobile application for handhelds including 2 components:
    - Mobile Application.
    - Mobile UI Component (web dynpro component).
    I do follow the tutorial for creating the application. I can deploy and run the application on NWDS handheld emulator successfully.
    When I deploy it on my SAP Application server to test the web dynpro UI application via a web browser, it throws out a java.lang.ClassNotFoundException: the class <package name>/Internal<Application Name>Comp.class cannot be found by WD framework when I access it. It can be deployed without error and is alive in the web dynpro content admin.
    I found that the normal WD component the class Internal<Application Name>Comp is generated during the building process but it is not when developing mobile UI component.
    Can anyone tell me there is any difference between the two WD component types? Does my server need to install any extra component for running mobile UI component? Or do I need to configure my NWDS for Mobile to make the application work on SAP server?
    Thank you very much,
    Steven Linh Nguyen.

    Hi,
    Mobile webdynpro application for handheld cannot be deployed on SAP AS.
    To use the Mobile webdynpro application for handhelds follow the steps:
    1. Upload sda files of all DCs to the DOE server (Transaction SDOE_UPLOAD_ARCHIVE) which will be availabe at the location
    <workspace.jdi>\LocalDevelopment\DCs\demo.sap.com\<DC>\_comp\gen\default\deploy
    2. Install the simulator on laptop or client on PDA
    3. Deploy uploaded MCDS(from step1) to the client, after the device registration.
    Thanks and Regards,
    Suma

  • Error when running a Web Dynpro application

    I created a webdynpro component and created a service call to a FM with IMPORTING parameter as PSTLZ and in the MAIN view( the only view in the component) I created a label and an Input field, I binded the input field with the importing parameter of the FM( in the context of the view) and tried to run the application....but it gives me error as :
    Adapter error in &VIEW_ELEMENT_TYPE& "PSTLZ" of view "ZSERVICEREP_LOOKUP.MAIN": Context binding of property VALUE cannot be resolved: Node MAIN.1.INPUT does not contain any elements
    Thanks.
    Deepti Kaza

    Hi Deepthi,
    Dont map attribute of component controller  to attribute of view context.
    Now your problem is you are unable to map the controller context to view context.follow the below steps.
    1.Durectly drag and map the Controller context node (Importing)  to the view context node(INPUT).
    Then you bind the attribute I_ZIPCODE to the Input element in Layout.
    ( or )
    2. Right click on view context node INPUT and select define mapping then a pop up will comes with Controller nodes.select Importing node and then click ok.Thats all your view context node will mapped to controller context node.
    Thanks
    Suman

  • Not able to run web dynpro application from portal.

    Hi portal experts,
    I want to run my web dynpro application from portal.
    So created a seperate iview  and a role  for the purpose.
    Assigned the iview to the role and also mapped a abap user id to the new role created.
    But when I click on 'preview'  the iview , getting the following dump.
    Error when processing your request
    What has happened?
    The URL http://mnghcmsap:8000/sap/bc/webdynpro/sap/zhr_cp_admin/ was not called due to an error.
    Note
    The following error text was processed in the system HRM : Die URL enthält keine vollständige Domainangabe (mnghcmsap statt mnghcmsap.<domain>.<ext>).
    The error occurred on the application server mnghcmsap_HRM_00 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: CHECK of program CX_FQDN=======================CP
    Method: STARTUP_CHECKS of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP
    Method: HANDLE_REQUEST of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP
    Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
    Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
    Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
    Module: %_HTTP_START of program SAPMHTTP
    What can I do?
    If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system HRM in transaction ST22.
    If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server mnghcmsap_HRM_00 in transaction SM21.
    If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server mnghcmsap_HRM_00 . In some situations, you may also need to analyze the trace files of other work processes.
    If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http -c: 200 -u: INF51515 -l: E -s: HRM -i: mnghcmsap_HRM_00 -w: 0 -d: 20110209 -t: 121224 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team
    Please let me know if I am doing the process correctly and also let me know if I am missing somthing.
    Thanks,
    Aditya.

    Are you able to run teh web dynpro application independtly i.e. without creatin an iview.
    http://mnghcmsap:8000/sap/bc/webdynpro/sap/zhr_cp_admin/ by using this link.
    or there also you are getting the error.
    i guess there also you should be gettign the error.
    this is some problem with the FQDN settings in the abap system.
    in the host name of the web dynpro applciation server one .(dot) is must.
    so you might have to change the host name to some thing like mnghcmsap. from mnghcmsap
    thanks
    sarbjeet singh

  • Running Web Dynpro Applications in Different Browsers

    Hi,
    I runned an Web Dynpro Application in different browsers(Opera, Firefox and Internet Explorer). The problem is that in Firefox is running fine, but in Internet Explorer some controls are missing and in Opera I got an Error Page that say the following:
    An error has occurred:
    "Failed to process the request."
    Please contact your system administrator.
    This page was created by SAP NetWeaver. All rights reserved.
    Web Dynpro client:
    Nokia Series 80 Client
    Web Dynpro client capabilities:
    User agent: Opera/9.25 (Windows NT 6.0; U; en), client type: op6, client type profile: op6, ActiveX: disabled, Cookies: enabled, Frames: enabled, Java applets: disabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
    Accessibility mode: false
    Web Dynpro runtime:
    Vendor: SAP, build ID: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Wed Nov 14 08:48:35 GMT-03:00 2007
    Web Dynpro code generators of DC agile.com/pmg_bonefish~webdynpro:
    SapDictionaryGenerationCore: 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:42[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro: 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:00:50[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore: 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:23[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
    SapWebDynproGenerationCTemplates: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
    SapGenerationFrameworkCore: 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:44:42[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:26[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary: 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:54:53[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon: 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:30[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCore: 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:37[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates: 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:50[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    Web Dynpro code generators of DC sap.com/tcwddispwda: No information available!
    Web Dynpro code generators of DC sap.com/cafUIptn~common:
    SapDictionaryGenerationCore: 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:26:06[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro: 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:28:49[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore: 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:14:35[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:42:07[UTC], changelist=455669, host=pwdfm101)
    SapWebDynproGenerationCTemplates: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:42:07[UTC], changelist=455669, host=pwdfm101)
    SapGenerationFrameworkCore: 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:13:54[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:32:11[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary: 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:23:29[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon: 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:14:42[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCore: 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:32:21[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates: 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:26:13[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
    Web Dynpro code generators of DC sap.com/tcwdcorecomp: No information available!
    J2EE Engine:
    7.00   patchlevel 109044.44
    Java VM:
    Java HotSpot(TM) Server VM, version: 1.4.2_09-b05, vendor: Sun Microsystems Inc.
    Operating system:
    Windows 2003, version: 5.2, architecture: x86
    I don´t know is the problem I have in both browsers Internet Explorer and Opera are from the browser or from the layout I´m using in Web Dynpro.
    regards

    Hi Aida,
    For getting an information of the Web Browsers supported by SAP NetWeaver, check out the following link:
    [http://service.sap.com/pam|http://service.sap.com/pam]
    To access the Product Availability Matrix (PAM), you will need a sUser Login Name.
    For Reference,
    http://help.sap.com/saphelp_nw04s/helpdata/en/79/23c7410400c717e10000000a155106/frameset.htm
    Regards,
    Alka.

  • How to display the error message during the web dynpro application runtime

    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

    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.

  • Authentication Screen when accessing Web Dynpro Application

    Hi,
    We are encountering a situation wherein when we call the Web dynpro application, it asks for Authentication. The way we do is a bit tricky. We have the following set up;
    1. We access the CRM_IC ( Web Gui) in CRM and from where we try to create orders  in the backend system i.e., ECC6.0 (IS_Utilities).
    2. For creating orders we launch the FOP ( in our case it is DYNPRO) from CRM. So ECC screen is opened through ITS using SSO.
    3. In addition to this we built a web dynpro application to be called from the DYNPRO (step 2).
    4. When the Web dynpro application is accessed it asks for Login details though it has already logged into ECC using SSO.
    PROBLEM: CRM -- using ITS / SSO --> ECC --> Web dynpro ?? Authentication screen.
    Design:
    We are using WDY_EXECUTE_IN_PLACE to open the Web dynpro in SAPGUI. It is working fine when we run the Web dynpro application from SAPGUI, only the problem is when we do the above steps 1 - 4.
    Tried using the following logic as well but the same result.
    CREATE OBJECT viewer EXPORTING parent = empty_container.
    CALL METHOD viewer->enable_sapsso
    CALL METHOD viewer->DETACH_URL_IN_BROWSER
    EXPORTING url = urlc.
    cl_gui_cfw=>flush( ).
    So is it possible to over come the problem. Basically, we don't want the Authentication screen it should use SSO.
    SSO is already set up in the system.
    Any inputs will be highly appreciated.
    Thanks,
    Roopesh

    resolved!!!!
    CRM had wrong url to connect to web dynpro aplication
    Edited by: Aditya Deshpande on Mar 3, 2010 9:59 AM

  • Web Dynpro Application URL

    Hi All,
    I need to run a Web Dynpro application without using Portal, is there a was to do so? Can I run the application by calling it directly using a URL?
    Thanks,
    Rajiv

    Hi,
    you can. simply right click on your Web dynpro application and selecte deploy and run.
    other wise use this url to run
    http://hostname:portnumber/webdynpro/dispatcher/local/projename/wpplication name
    Regards,
    Naga

  • Access Web Dynpro application on different WAS ??????????

    Hi All,
    Current Scenario -
    We have deployed ESS & MSS Business package on one WAS and the iviews are present on another WAS.We have created a Dedicated R/3 system which is pointing to the WAS where these packages are deployed.
    All these things are working fine i.e. once the user maps the id pswd it directly runs the Web Dynpro applications in the iviews.
    That means, even if application is running on one WAS, and the user personalises data on another WAS, it still retrieves the credentials and shows the appropriate results for ESS MSS Packages.
    Query-
    Now i need to implement the same scenario in my Web Dynpro application
    Steps
    1) I have the WD application running on one WAS and portal on another
    2) In portal there is a R/3 system created
    3) The Web Dynpro application needs to know if the user has personalised mapping against that system created on portal(other WAS)
    4) If yes show him the home page else take him to the login page.
    Just as it is implemented for ESS MSS Packages.
    How can i pass the mapped data to the Web Dynpro iview ?
    Thanks and Regards,
    Samta Nichani

    Amol,
    as this questions existed twice, I've deleted one.
    As roles are in the UME, you can access them. But why do you want to do this? You could login to that user, but then the question is what you want to do....
    Regards,
    Benny

  • Error while running web dynpro application

    Hi Experts,
    I have a web dynpro application that is consuming web services from PI 7.1
    I have deployed the application on PI 7.1 server and created web service destination also.
    I have tested the web services and they are working fine.
    I am geting the following error when i am running the code,
    The initial exception that caused the request to fail, was:
    com.sap.engine.lib.xml.util.NestedException: Illegal conversion
    Detailed Exception Chain
    Caused by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination 'DEFAULT_WS_XYZ_METADATA_DEST' and WS interface ' XYZ_WSD_PI'. One possible reason is that the metadata destination 'DEFAULT_WS_XYZ_METADATA_DEST' has not been properly configured; check configuration.
    at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41)
    at com.dts.model.xyz.xyz.<init>(xyz.java:52)
    at com.dts.comp.DTCComp.wdDoInit(DTCComp.java:184)
    at com.dts.comp.wdp.InternalDTCComp.wdDoInit(InternalDTCComp.java:420)
    Caused by: com.sap.engine.services.webservices.espbase.configuration.ConfigurationMarshallerException: com.sap.engine.lib.xml.util.NestedException: -> com.sap.engine.lib.xml.util.NestedException: Illegal conversion
    at com.sap.engine.services.wssec.srt.features.configuration.SecurityConfigurationMarshaller.unmarshalAssertions_WSPOLICY_12_NS(SecurityConfigurationMarshaller.java:326)
    at com.sap.engine.services.wssec.srt.features.configuration.SecurityConfigurationMarshaller.unmarshalAssertions(SecurityConfigurationMarshaller.java:246)
    Caused by: com.sap.engine.lib.xml.util.NestedException: Illegal conversion
    at com.sap.engine.lib.xsl.xpath.xobjects.XObject.toXBoolean(XObject.java:63)
    at com.sap.engine.lib.xsl.xpath.xobjects.XBoolean.execute(XBoolean.java:72)
    I am getting error in component controller doInit() method and below is the code
              XYZ model = new XYZ ();
                 Request_XYZ  request= new Request_XYZ(model);
                 Zxyz details = new Zxyz(model);
                                              details.setLanguagecode("");
                 details.setZuser("");
              details.setMessagenumber("");
                 request_Zxyz.setZxyz(details );             
                  wdContext.nodeRequest_XYZ().bind(request);
    If anyone know the reason of this error please help.
    Regards,
    Shweta

    HI GLM,
    If i comment the code in component controller i get the screen, but when i initialize the model and parameters in doInit() method i get error. I am using 5 web service and getting same error for all, so i have commneted rest and currently dealing with one.Below is the code,
                EventDetails model = new EventDetails();
                 Request_ZcpexGetEventDetails request_ZcpexGetEventDetails = new    
                                               Request_ZcpexGetEventDetails(model);
                 ZcpexGetEventDetails getEventDetails = new ZcpexGetEventDetails(model);
                 getEventDetails.setLanguagecode("");
                 getEventDetails.setZuser("");
              getEventDetails.setMessagenumber("");
                 request_ZcpexGetEventDetails.setZcpexGetEventDetails(getEventDetails);             
                              wdContext.nodeRequest_ZcpexGetEventDetails().bind(request_ZcpexGetEventDetails);
    Below is the exception trace
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.engine.lib.xml.util.NestedException: Illegal conversion
        at com.sap.engine.lib.xsl.xpath.xobjects.XObject.toXBoolean(XObject.java:63)
        at com.sap.engine.lib.xsl.xpath.xobjects.XBoolean.execute(XBoolean.java:72)
        at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:110)
        at com.sap.engine.lib.xsl.xpath.XPathProcessor.innerProcess(XPathProcessor.java:56)
        at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:43)
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session ApplicationSession(name=com.dts.app.dtsapp.DTSapp, id=2370e7916c5711de8f22001e0b5c3568). The causing exception is nested. RID=236ffd306c5711de992e001e0b5c3568
      at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:638)
      at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:220)
      at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:232)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:205)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
      at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:93)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:105)
      at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
      at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
      at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
      at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
      at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
      at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:295)
      at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
      at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
      at java.security.AccessController.doPrivileged(Native Method)
      at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
      at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
    Caused
    by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException:
    Exception on creation of service metadata for WS metadata destination
    'DEFAULT_WS_EVENTDETAILS_METADATA_DEST' and WS interface
    'ZCPEX_GET_EVENT_DETAILS_WSD_PI'.
    One possible reason is that the metadata destination
    'DEFAULT_WS_EVENTDETAILS_METADATA_DEST' has not been properly configured; check
    configuration.<BR>  at
    com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:440)<BR>  at
    com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)<BR>  at
    com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)<BR>  at
    com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326)<BR>  at
    com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199)<BR>  at
    com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1034)<BR>  at
    com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248)<BR>  at
    com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.&lt;init&gt;(WSTypedModel.java:41)<BR>  at
    com.dts.model.eventdetails.EventDetails.&lt;init&gt;(EventDetails.java:52)<BR>  at
    com.dts.comp.DTCComp.wdDoInit(DTCComp.java:184)<BR>  at
    com.dts.comp.wdp.InternalDTCComp.wdDoInit(InternalDTCComp.java:420)<BR>  at
    com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:160)<BR>  at
    com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:230)<BR>  at
    com.sap.tc.webdynpro.progmodel.components.Component.initController(Component.java:249)<BR>  at
    com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:209)<BR>  at
    com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:513)<BR>  at
    com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1234)<BR>  at
    com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoPreprocessing(AbstractExecutionContextDispatcher.java:150)<BR>  at
    com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppPreprocessing.doService(DispatchHandlerForAppPreprocessing.java:35)<BR>  at
    com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)<BR>  at
    com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)<BR>  at
    com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoPreprocessing(ExecutionContextDispatcher.java:100)<BR>  at
    com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:75)<BR>  at
    com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:568)<BR>  at
    com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:588)<BR>  at
    com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:250)<BR>  at
    com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:635)<BR>  ...
    41 more<BR>Caused by:
    com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException:
    GenericServiceFactory initialization problem. [Problem with WSDL file parsing.
    See nested message.]<BR>  at
    com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:303)<BR>  at
    com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:234)<BR>  at
    com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:202)<BR>  at
    com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:181)<BR>  at
    com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:429)<BR>  ...
    67 more<BR>Caused by:
    com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException:
    Problem with WSDL file parsing. See nested message.<BR>  at
    com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.loadWSDLapi(ProxyGeneratorNew.java:704);at
    com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.generateAll(ProxyGeneratorNew.java:410);at
    com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.loadProxy(DGenericServiceImpl.java:130);at
    com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.&lt;init&gt;(DGenericServiceImpl.java:65
    ;at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:280)<BR>  ...
    71 more<BR>Caused by:
    com.sap.engine.services.webservices.espbase.configuration.ConfigurationMarshallerException:
    com.sap.engine.lib.xml.util.NestedException:
    com.sap.engine.lib.xml.util.NestedException: Illegal
    conversion;at
    com.sap.engine.services.wssec.srt.features.configuration.SecurityConfigurationMarshaller.unmarshalAssertions_WSPOLICY_12_NS(SecurityConfigurationMarshaller.java:326)<BR>  at
    com.sap.engine.services.wssec.srt.features.configuration.SecurityConfigurationMarshaller.unmarshalAssertions(SecurityConfigurationMarshaller.java:246)<BR>  at
    com.sap.engine.services.webservices.espbase.configuration.PolicyConvertor.processAlternative(PolicyConvertor.java:195)
    com.sap.engine.services.webservices.espbase.configuration.PolicyConvertor.unmarshal(PolicyConvertor.java:92);
    at com.sap.engine.services.webservices.espbase.configuration.PolicyConvertor.unmarshalAlternatives(PolicyConvertor.java:135);at
    com.sap.engine.services.webservices.espbase.configuration.ConfigurationBuilder.createBindingData(ConfigurationBuilder.java:376);at
    com.sap.engine.services.webservices.espbase.configuration.ConfigurationBuilder.createBindingData(ConfigurationBuilder.java:356);at
    com.sap.engine.services.webservices.espbase.configuration.ConfigurationBuilder.create(ConfigurationBuilder.java:193);at
    com.sap.engine.services.webservices.espbase.configuration.ConfigurationBuilder.create(ConfigurationBuilder.java:158);at
    com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.loadWSDLapi(ProxyGeneratorNew.java:699)
    84 more Caused by: com.sap.engine.lib.xml.util.NestedException:
    com.sap.engine.lib.xml.util.NestedException: Illegal conversion;at
    com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:377;at
    com.sap.engine.lib.jaxp.TransformerImpl.transformWithStylesheet(TransformerImpl.java:398;at
    com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:240);...
    85 more Caused by: com.sap.engine.lib.xml.util.NestedException: Illegal
    conversion;at
    com.sap.engine.lib.xsl.xpath.xobjects.XObject.toXBoolean(XObject.java:63;at
    com.sap.engine.lib.xsl.xpath.xobjects.XBoolean.execute(XBoolean.java:72;at
    com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:110;at
    com.sap.engine.lib.xsl.xpath.XPathProcessor.innerProcess(XPathProcessor.java:56;at
    com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:43;at
    com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:51;at
    com.sap.engine.lib.xsl.xslt.XSLVariable.process(XSLVariable.java:132;at
    com.sap.engine.lib.xsl.xslt.XSLTopVariable.process(XSLTopVariable.java:42;at
    com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:360;...
    Regards,
    Shweta

  • Web dynpro application not available when running iview wizard

    When I run the iview wizard to create a web dynpro iview I find the folder local/<MyProjectName.
    But when opening myProjectName folder the Application is missing, so I cannot create the iview.
    When running the web dynpro Content Administrator I find the application in the ProjectName folder, but when I try to run it I get the exception:
    com.sap.tc.webdynpro.repository.utils.RepositoryException: Did not find application 'MyTestApplication' in repository.
    What could be the issue?
    B.r
    Olof

    Hi Siva,
    I tried this but it still doesn't work for me:
    I get this error
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Cannot open repository for application 'MyApplication'.
         at com.sap.tc.webdynpro.serverimpl.wdc.um.ClientUserFactory.isAuthenticationRequired(ClientUserFactory.java:316)
         at com.sap.tc.webdynpro.serverimpl.wdc.um.ClientUserFactory.checkAuthentication(ClientUserFactory.java:244)
         at com.sap.tc.webdynpro.services.sal.um.api.WDClientUser.checkAuthentication(WDClientUser.java:217)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.checkAuthentication(RequestManager.java:626)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:144)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.tc.webdynpro.repository.utils.RepositoryException: Did not find application 'MyApplication' in repository.
         at com.sap.tc.webdynpro.serverimpl.core.repository.AbstractServerRepository.getApplicationInternal(AbstractServerRepository.java:167)
         at com.sap.tc.webdynpro.serverimpl.wdc.um.ClientUserFactory.isAuthenticationRequired(ClientUserFactory.java:307)
         ... 22 more
    Edited by: Olof Trönnberg on Aug 20, 2009 12:42 PM

  • Uncaught exception while executing web dynpro application

    Hello all,
    I'm getting run time error exception CX_WDR_RR_EXCEPTION not caught when running web dynpro application
    The error analysis shows the custom component is locked by the user and cannot be regenerated. But I checked in SM12 for locked entries and component was not listed there.
    The program terminated in the include LWDR_RUNTIME_REPOSITORYF12
    Please suggest how to resolve the isse?
    Regards,
    anil

    Hi Anil,
    I'm also getting the same run time error. When I try to activate the Web Dynpro component, I'm getting error that the component is locked by the user.
    Please let me know how you solved this issue.
    Thanks in advance for the quick response.
    Thanks & Regards,
    Jay

  • Exception not caught while executing web dynpro application

    Hello all,
    I'm getting run time error exception CX_WDR_RR_EXCEPTION not caught when running web dynpro application
    The error analysis shows the custom component is locked by the user and cannot be regenerated. But I checked in SM12 for locked entries and component was not listed there.
    The program terminated in the include LWDR_RUNTIME_REPOSITORYF12
    Please suggest how to resolve the isse?
    Regards,
    anil

    sorry...posted in wrong forum...

Maybe you are looking for