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

Similar Messages

  • Uncaught exception when 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

    Dear Anil,
    What type of WD is it ?
    Do you get the error when you trigger some sort of event ?
    Is it when first launch the WD ?
    Can you be more specific and share with us the code where this is dumping ?
    You can also check this link
    [CX_WDR_RT_EXCEPTION' - How to catch it?;
    Kind Regards
    /Ricardo Quintas

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

  • 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

  • Error while creating web dynpro application

    Hi All
    I created one web dynpro application but while executing 1 encountered 1 error below :
    "Die URL enthalt keine vollstandige domainangabe (The URL does not contain full domain specification) (gcecc62 statt gcecc62.<domain>.<ext>)."
    Please help how to solve this issue..
    thanks in advance
    Regards
    Brillion

    Hi Brillion,
    Check FQDN Configuration..
    Go through this...
    <-- removed by moderator -->
    Also check this thresads similar ones..
    <-- removed by moderator -->
    Cheers,
    Kris.
    Moderator message: please do not just post links.
    Edited by: Neil Gardiner on Aug 5, 2011 3:40 PM

  • Authorization Missing error while creating web dynpro Application

    Hi experts,
        I am new to web dynpro and trying to learn it by myself. I am getting an authorization error while creating a web dynpro application. I am not getting any errors while activating Views or Windows. But when I created a web dynpro application and tried to save it, it thew me a warning saying that " You are not authorized to use function  Netzwerkadministration " . Still I could be able to create the application, but not able to run it.
       What  settings should be done to have this authorizations ?
    Any suggestion would be helpful.
    Thanks,
    RVSS

    Hi,
    Get your BASIS person to give you authorization to Tcode SICF and also authorization to create and activate services in Tcode SICF.
    You need authorization to object S_ICF_ADM apart from authorization to tcode SICF
    Regards,
    Ajay
    Edited by: ajay matam on Sep 9, 2009 12:04 PM

  • Error while testing web dynpro application

    Hi all,
    I am trying to test a webdynpro application, following error is being generated.
    The problem is, that I when I try to create a View for a Web Dynpro, the layout window reports the following error message:
    ERROR
    The requested URL could not be retrieved
    While trying to retrieve the URL:
    http://<url-of-remote-machine>:8000/sap/public/myssocntl?
    The following error was encountered:
    Connection to <ip-of-remote-machine> Failed
    The system returned:
    (110) Connection timed outThe remote host or network may be down. Please try the request again.
    Your cache administrator is webmaster.
    Please comment.
    Thanks,
    Rekha

    register fully qualified doamin in your ICM file.
    go to drivers->etc->hosts
    write your IP address and fully qualified doamin.
    thanks
    Suman

  • URL error while excuting web dynpro application for file upload  in IP

    The following error text was processed in the system DB1 : WebDynpro Exception: ICF service node for application /sap/public/bc does not exist
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: RAISE of program CX_WD_GENERAL=================CP
    Method: HANDLE_REQUEST of program CL_WDR_UCF====================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

    Hello,
    have you typed the web manually? try using transaction SICF and "test" the service so the URL is generated by the system. You should find the webdynpro application under /SAP/public/bc/
    If the error continues re-import the transports.
    Cheers,
    C

  • UNCAUGHT EXCEPTION while executing Open Hub

    Hi All,
    I have created Open hub destination in BI 7.0 on one custom cube. I am trying to create file on application server using this open hub. I have also created logical filename etc..
    When I ran the DTP for this open hub, I am getting following error:
    Runtime Errors UNCAUGHT_EXCEPTION
    Except. CX_RSB_WRITE_ERROR
    This was running fine on DEV and QA system but giving this error in PRD.
    Any clue about this error?
    Thanks in advance.

    Hello,
    it seems the logical path for logical filename is not correct. Could you please check it in t-code FILE?
    Kind Regards,
    Paula Csete

  • I am getting a error while executing the Web Dynpro Application Page.

    Hi All,
    I am getting a Error while executing a web dynpro application ::: 
    : Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered. Component: Z_WEP_PERSONAL_DATA, View: OVERVIEW, Window: Z_XXP_PERSONAL_DATA
    I have checked this error description in ST22  :
    What happened?
        The exception 'CX_WDR_RT_EXCEPTION' was raised, but it was not caught anywhere
         along
        the call hierarchy.
        Since exceptions represent error situations and this error was not
        adequately responded to, the running ABAP program
         'CL_WDR_CLIENT_APPLICATION=====CP' has to be
        terminated.
    Error analysis
        An exception occurred which is explained in detail below.
        The exception, which is assigned to class 'CX_WDR_RT_EXCEPTION', was not caught
         and
        therefore caused a runtime error.
        The reason for the exception is:
        Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered. Component:
        Z_XXP_PERSONAL_DATA, View: OVERVIEW, Window: Z_XXP_PERSONAL_DATA
    Can u plz help me regarding this error.
    Thanks,
    Deepika

    >Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered
    Looks to me like you are trying to fire a navigation plug within WDDOMODIFYVIEW. According to the rules of the WD Phase Model this is not allowed.

  • Error while implementing a web service in web dynpro application

    HI All,
    I am trying to use a webservice in a web dynpro application.
    Web service description:- This is a very simple application which takes two String inputs and when submitted displays the string in the concatenated form.
    Web dynpro:- I used this web service in the web dynpro as an adaptive web service model.
    The Layout design consists of two input fields which are mapped to the request fields
    ex : - Request_Add.Add.S1 and Request_Add.Add.S2
    A text area to display the response:- Request_Add.Response.AddResponse.Response
    And a button which invokes the execute method
    public void onActionWebserviceCall(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
        //@@begin onActionWebserviceCall(ServerEvent)
        wdThis.wdGetWebserviceCompController().executeRequest_Add();
        //@@end
    When I am trying to run the application I am getting error:-
    Exception on execution of web service with WSDL URL 'http://<Host>:<Port>/EjbWebservice/Config1?wsdl' with operation 'add' in interface 'EjbWebserviceVi_Document'
    Kindly reply.
    Thanks
    Neha

    Hi,
    Yes I have tested the web service in Navigator . The WSDL is also properly generated.
    I have not publish the web service in UDDI but as per my understanding this is not necessary. please correct me if I am wrong.
    Thanks
    Neha

  • Errors in While trying to Deopy Web Dynpro Application

    Hi,
      I have NetWeaver 2004S in My local System. I am facing one problem while deploying that Web Dynpro Application from NWDS. Error is pasted below. But i can deploy EP Application. I am facing the same problem when i tried to Deploy from Remote GUI.
      Can anyone help me in fixing this problem.
    Thanks,
    Sridhar
    <u>Exception i got while deploying.</u>
    Starting Deployment of SampleWD
    Aborted: development component 'SampleWD'/'local'/'LOKAL'/'0.2006.06.05.11.29.10':
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [H1B-2F241-HMY] with user name: [Administrator]                     Check your login information.                     Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
    Deployment of SampleWD finished with Error (Duration 2473 ms)

    Hi Sridhar,
    Please follow the steps below:
    1. Open ConfigTool ( drive:\usr\sap\J2E (your instance)\JC01\j2ee\configtool
    2. Go to Secure Store and change the password for the property admin/password/J2E (This password should same as the one you are trying to login to portal)
    3. Click Add
    4. Click Save and restart your server.
    Should be able to deploy your components.
    Happy deploying
    Best Regards,
    Shiva

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

  • Problem while navigating the different portal Web Dynpro application

    Hi .
    while navigating from one application to another.
    my IE browser stuck with the error.
    Can't execute the code from the freed script.
    it occurs:
    when i navigate from tree structure 's child to another web dynpro application.
    what to do ...
    Regards

    Hi John,
    How have you added the required jar files. For DC projects you cannot use project properties and add the jar files to the build path (In case you have followed this method).
    You will have to add the public part (i believe it is ejbclient.jar and is generated automatically when you create an EJB DC) of the EJB DC as used dc.
    Regards
    Sidharth

  • Error while deploying the Web Dynpro application

    HI All,
    I have developed a Web dynpro application. Now when I am deploying the application I am getting an error.
    Description
    Jan 8, 2008 2:14:12 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [002]Deployment aborted
    Deployment exception : Cannot determine sdm host (is empty). Please configure your engine/sdm correctly !
    Can any one please help me regarding this.
    Regards
    Neha

    Hi Neha,
    It seems that there is problem with your SDM server. It seems that during J2EE engine configuration SDM server is not configured. Actually this configuration is done by Basis Team.
    By the way try out your Server setting:
    Go To:: Windows -> Preferences -> SAP J2EE Engine
    [Mention the required details over there]
    And Check whether you are getting Active SDM Server under J2EE Engine.
    Regards,
    Nittin Garg

Maybe you are looking for