Com.sap.caf.mp.base.exception.EngineException: Problem in server response:

Hi,
I have created one CAF application,which is having one external webservice and one application service.Webservice takes two input parameters(string,boolean) and it returns an arraylist.
So when i test the CAF application on the CAF service browser it is giving me error like " com.sap.caf.mp.base.exception.EngineException: Problem in server response: [Bad Request]."
I am getting this error while creating object of web service.
Can anybody help me on this issue..
Thanks in Advance

It looks like you are not authorized to execute the webservice. Check the webservice authentication settings.
Peter

Similar Messages

  • Com.sap.tc.cm.base.exception.BaseModelRuntimeException: No object for....

    Hi Experts,
    Iam using adaptive webservice model, for this when i run the application it shows the below exception,
    Connection IO Exception. Check nested exception for details. (Connection Exception; nested exception is:
    com.sap.tc.cm.base.exception.BaseModelRuntimeException: No object for mandatory target role 'RequisitionItems' of model class 'com.sap.demo.sampleapplication.wd.models.samplemodel.RequisitionGetitems' with cardinality 'ONE' maintained).
    [EXCEPTION]
    com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Connection Exception; nested exception is:
    com.sap.tc.cm.base.exception.BaseModelRuntimeException: No object for mandatory target role 'RequisitionItems' of model class 'com.sap.demo.sampleapplication.wd.models.samplemodel.RequisitionGetitems' with cardinality 'ONE' maintained).
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.serializeRequest(SOAPTransportBinding.java:1705)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.writeSOAPRequestMessage(SOAPTransportBinding.java:257)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1280)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:960)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:915)
    at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
    at com.sap.tc.webdynpro.model.webservice.model.WSGenericModelClassExecutable.execute(WSGenericModelClassExecutable.java:73)
    Thanks in advance
    Regards,
    Pradeep Kumar G

    Hai abhinav,
    Thanks for reply,
    Detailed description of my scenario:
    Iam using Adaptive webservice model for accessing some data based on some input values.
    In web service navigator it is working fine. when i give any input values based on that input the output records are available.
    But when i used it in webdynpro java, it gives an exception and asks for manadatory input values but actually in that webservice there are no mandatory input values, ok i provided that input values based on that exception, then it gives the below exception
    Connection IO Exception. Check nested exception for details. (Connection Exception; nested exception is:
    com.sap.tc.cm.base.exception.BaseModelRuntimeException: No object for mandatory target role 'RequisitionItems' of model class 'com.sap.demo.sampleapplication.wd.models.samplemodel.RequisitionGetitems' with cardinality 'ONE' maintained).
    [EXCEPTION]
    com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Connection Exception; nested exception is:
    com.sap.tc.cm.base.exception.BaseModelRuntimeException: No object for mandatory target role 'RequisitionItems' of model class 'com.sap.demo.sampleapplication.wd.models.samplemodel.RequisitionGetitems' with cardinality 'ONE' maintained).
    I used the code in the link you have mentioned, but it cannot solved my problem. Same exception is occurring.
    Share whether you have any idea on this..
    Regards,
    Pradeep Kumar

  • Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException

    Dear All,
    please help me, now i'm facing some problem when running BEX broadcaster to generate HTML file in BW Portal,
    every time i rum BEX Broadcaster for schedule, it will took very long running time (+- 3600 second) with no file HTML generated
    when i check to tcode rsrd_log :
    Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException
    Message no. RSBOLAP014
    is any one have any solution for my problem..
    Thanks
    -Luqman

    Hi Luqman,
    Since issues with Message no.: RSBOLAP are basically JAVA Configuration issues, I would suggest you to run the SAP NetWeaver BI Diagnostics & Support Desk Tool as described in Note 937697 to verify your installation.Please use the Latest version of this NOTE. In the "Advanced mode" of the tool, go to the "Configuration checks" tab and check for potential red traffic lights. To resolve the issues shown there, check the "Remedy" column and follow the instructions given there.
    Also do implement all the correction instructions attached to the NOTE.
    Also to avoid encountering already known issues within the area of BI Java itself, make sure to deploy the latest patches for SCAs BI-BASE-S and BIWEBAPP.
    Also you may refer NOTE 917950 ('SAP NetWeaver 2004s: Setting up BEx Web') .
    Hope this info helps you with the issue.
    Kind Regards,
    Robin.

  • Com.sap.mw.jco.JCO$Exception starting the J2EE server 620

    We are using J2EE 620 pl26, with the latest JCO, but often trying to acces the J2EE services like Mobile Engine Webconsole 21 or the WebEnabled Sapconsole 640 we recive the message:
    'Dispatche runningbut no server connected'.
    The J2EE dispatcher and server are started at Sap startup. Just after that time the J2EE is working fine, but after some time the J2EE server get down.
    We found this message into the J2EE console_logs:
    "RFCEngine: Server startup error, stopping "SAPProfile:F:\usr\sap\CAM\SYS\profile\CAM_DVEBMGS00_itmif089" :
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Fri Oct 15 09:58:20 CEST 2004.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 2 seconds.
    Could not establish the lcom accepted connection: lcomListenCreate failed with rc 9"
    We do not find any Oss notes for that.
    Any advise is wellcome.
    Regards

    Hi Mauro,
    normally when you apply a new SAP Kernel a frfclib.sar file is delivered. This frfclib file need to be copied to the J2EE directory /os_libs and need to be extracted there. This frfclib version must always match to the SAP Kernel version.
    Ciao
    tc

  • Com.sap.engine.services.dbpool.exceptions.BaseResourceException:

    Hi
    Jcontrol.exe is stopped. I checked in server0 log file. 
    Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection:
    Caused by: com.ibm.db2.jcc.b.DisconnectException: [ibm][db2][jcc][t4][2043][11550] Exception java.net.ConnectException: Error opening socket to server
    Caused by: java.net.ConnectException: Connection refused: connectCommunication API being used: SOCKETS.  Location where the error was detected: T4Agent.sendRequest().
    Communication function detecting the error: OutputStream.flush().  Protocol specific error codes Software caused connection abort: socket write error, *, 0.  Message: Software caused connection abort: socket write error
    com.sap.caf.eu.gp.mail.cf.core.exceptionhandling.MailCFExceptionHandler.throwMailCFRuntimeException(MailCFExceptionHandler.java:92)
    #1.5 #0022198E9491001F000000130000390C00046999A2B0692D#1242008487314#com.sap.jms##com.sap.jms####n/a##6e72d7203dd211decd7d0022198e9491#SAPEngine_System_Thread[impl:5]_90##0#0#Error#1#/System/Server#Plain#JMSServerContainer.onServiceJoin##Configuration problem occurred while accessing JMS configuration resources.#
    #1.5 #0022198E9491008E000000010000390C00046999A5B43D17#1242008537907#com.sap.sql.jdbc.direct.DirectPreparedStatement##com.sap.sql.jdbc.direct.DirectPreparedStatement#Guest#0##n/a##8c9ab8303dd211de99680022198e9491#SAPEngine_Application_Thread[impl:3]_2##0#0#Error#1#/System/Database/sql/jdbc/direct#Java#com.sap.sql_0003##SQL error occurred on connection apsgdc01hwebd:BPE:SAPBPEDB: code=-4,499, state="null", message="[ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
    Communication API being used: SOCKETS.  Location where the error was detected: T4Agent.sendRequest().
    Communication function detecting the error: OutputStream.flush().  Protocol specific error codes Software caused connection abort: socket write error, *, 0.  Message: Software caused connection abort: socket write error";
    SQL statement is "SELECT "RESEND_INFO_UUID","SENT_MAIL_UUID","RI_START_TIME","RI_DELAY" FROM "CAF_GP_RESEND_INFO" ORDER BY 4".
    [EXCEPTION]
    #6#-4499#<null>#[ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
    Communication API being used: SOCKETS.  Location where the error was detected: T4Agent.sendRequest().
    Communication function detecting the error: OutputStream.flush().  Protocol specific error codes Software caused connection abort: socket write error, *, 0.  Message: Software caused connection abort: socket write error#apsgdc01hwebd:BPE:SAPBPEDB#SELECT "RESEND_INFO_UUID","SENT_MAIL_UUID","RI_START_TIME","RI_DELAY" FROM "CAF_GP_RESEND_INFO" ORDER BY 4#com.ibm.db2.jcc.b.DisconnectException: [ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
    Communication API being used: SOCKETS.  Location where the error was detected: T4Agent.sendRequest().
    Communication function detecting the error: OutputStream.flush().  Protocol specific error codes Software caused connection abort: socket write error, *, 0.  Message: Software caused connection abort: socket write error
    Regards
    Rao

    Hi, Please let me know if you managed to solve the problem.. We are facing the same issue
    Regards
    PN

  • SSO issue in the production server,com.sap.mw.jco.JCO$Exception: (103)

    com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: This system rejects all logons using SSO tickets
    in the production server.....
    while testing the jco maintained for Ess applications.
    if i go for uidpw method for modeldata destination i am getting the error. in the Ess pages that administrtor not in this peroid(administrator with which id i maintained jco destination)
    if i assign one employee to the admin in pa30......for every employee getting the same details of admin)
    I guess this problem with modeldata ......i should maintain the usermanagement method for modeldata jco destination is logon ticket.
    while maintainig that ping is successfull but getting the above error.
    it is the problem with production server.......of E.P
    in dev and quality everything is working fine.
    plz help me out.
    thankyou
    swapna

    Hi Swapna,
    Please check the logon group properties for SAP system in t-code SMLG. If there is any issue with logon group then it might cause for this issue.
    Refer to [Click here|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/wd%20java/7.0/portal%20integration/how%20to%20configure%20the%20jco%20destination%20settings.pdf] and [System Landscape Directory Process and JCo Configuration|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5?QuickLink=index&overridelayout=true]
    Hope it will helps
    Regards, Arun Jaiswal

  • ERROR:com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException

    Dear All,
    We have taken a par file from another project and deployed in the J2EE engine using SDM.It was succesfully deployed with out any warnings.I have created an iview also.When we are trying to access that i view i am getting an error 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:
       com.sap.dictionary.runtime.DdException: Type com.bel.holidaycal.model.types.Zhrt029 does not exist
        at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
        at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
        at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
        at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
        at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
        ... 51 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.1; SV1)
    Version     null
    DOM version     null
    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: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:41:58[UTC], changelist=413534, host=pwdfm101), build date: Mon Mar 03 21:11:10 GMT+05:30 2008
    J2EE Engine     7.00 patchlevel
    Java VM     Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
    Operating system     Windows 2003, version: 5.2, architecture: ia64
    Session & Other
    Session Locale     en
    Time of Failure     Thu Apr 10 14:31:31 GMT+05:30 2008 (Java Time: 1207818091497)
    Web Dynpro Code Generation Infos
    local/WDHolidayCalendar
    SapDictionaryGenerationCore     7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:24:21[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates     (unknown)
    SapGenerationFrameworkCore     7.0009.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:12:57[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer     7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:30:00[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon     7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:13:46[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore     7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:13:38[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary     7.0009.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:21:59[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro     7.0009.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:26:52[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates     7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:45:29[UTC], changelist=413534, host=pwdfm101)
    SapWebDynproGenerationCore     7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:30:11[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates     7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:45:29[UTC], changelist=413534, host=pwdfm101)
    sap.com/tcwddispwda
    No information available     null
    sap.com/tcwdcorecomp
    No information available     null
    Detailed Error Information
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type extern:com.bel.holidaycal.model.types.WDModelHolical:com.bel.holidaycal.model.types.Zhrt029 could not be loaded: com.sap.dictionary.runtime.DdException: Type com.bel.holidaycal.model.types.Zhrt029 does not exist
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:305)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:234)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:448)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:386)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:415)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:79)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:121)
         at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:117)
         at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:212)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         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:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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.dictionary.runtime.DdException: Type com.bel.holidaycal.model.types.Zhrt029 does not exist
         at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
         at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
         at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
         at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
         at com.sap.dictionary.runtime.DdBroker.getStructure(DdBroker.java:180)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:303)
         ... 49 more
    I have created the JCO connections also ,i am able to test them also.I have imported the same into NWDS and deployed the application , its deploying but the out put is the same error.
    I have cross checked the models and found that the Model is there in the model types.
    Can any one help me regarding this.
    Waiting for the response ASAP.
    Thanks
    Ravi.S

    Hi,
      I think you mean ear file and not par file. Check these threads. The exception is mentioned to be because of JCo problems only.
    Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
    WDTypeNotFoundException: type model.types.Zbtr_Wbselement could not be load
    WebDynpro using BAPI has an error
    Regards,
    Harini S

  • FPN error: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException

    Hi, all.
    I am trying to initiate a webdynpro page from the producer to the consume portal via RDL. It works fine for a day. Then it starts giving me the error:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load page ...
    This error cannot be cleared by clearning the FPN cache or synchronize with the producer. Of course, you can also delete the page from the consumer and copy it over from the producer again. It will work. But this is not a good workaround for a production system. We also don't know the cause either. Here is the stack trace:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load page
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:528)
         at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
         at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         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:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.sap.portal.fpn.exception.unchecked.FpnUnMarshallingException: Could not find a marshaller for 'com.sapportals.portal.page' from path 'pcd:consumer_content/DEP/portal_content/ca.ottawa.sap.supportcentre/ca.city.ottawa.OttawaRoles/ca.city.ottawa.ManagerInfo/ca.city.ottawa.ManagerInfo-FinanceOnly/ca.city.ottawa.ManagerInfo_MSS_Finance/ca.city.ottawa.Mileage_Parking_Managers'
         at com.sap.portal.fpn.marshal.ContentMarshallerService.unMarshallDLChain(ContentMarshallerService.java:323)
         at com.sap.portal.fpn.entrypoint.RuntimeFederatedPersistance.retrieveDLRemoteState(RuntimeFederatedPersistance.java:103)
         at com.sap.portal.fpn.FpnRuntimeService.bringRemoteState(FpnRuntimeService.java:134)
         at com.sap.portal.fpn.FpnRuntimeService.doFpnLookup(FpnRuntimeService.java:97)
         at com.sap.portal.fpnprovider.fpn.GenericContext.lookup(GenericContext.java:49)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sap.portal.pb.data.PcdManager.doInit(PcdManager.java:72)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:526)
         ... 31 more
    Caused by: com.sap.portal.pcm.OperationFailedException: Creating DL outside the PCD
         at com.sap.portal.pcm.iviewserver.CiViewSLObjectsManager.instantiateDescriptor(CiViewSLObjectsManager.java:687)
         at com.sap.portal.pcm.page.PagesSrv.instantiateDescriptor(PagesSrv.java:79)
         at com.sap.portal.pcm.page.PagesSrv.instantiateDescriptor(PagesSrv.java:71)
         at com.sap.portal.fpn.marshal.IViewMarshaller.instantiateRelatedItemDescriptor(IViewMarshaller.java:582)
         at com.sap.portal.fpn.marshal.IViewMarshaller.performSemanticActions(IViewMarshaller.java:506)
         at com.sap.portal.fpn.marshal.PageMarshaller.performSemanticActions(PageMarshaller.java:499)
         at com.sap.portal.fpn.marshal.IViewMarshaller.unmarshalResolvedDLChain(IViewMarshaller.java:715)
         at com.sap.portal.fpn.marshal.PageMarshaller.unmarshalResolvedDLChain(PageMarshaller.java:328)
         at com.sap.portal.fpn.marshal.ContentMarshallerService.unMarshallDLChain(ContentMarshallerService.java:320)
         ... 38 more
    So far I found nothing on OSS or SDN on this FpnUnMarshallingException. Has anyone seen this error before?
    Thanks.
    Jonathan.
    Edited by: Jonathan Ma on Apr 23, 2009 12:25 AM

    Hi Jonathan,
    you may deactivate the GPN cache as well as the old navigation cache. About the GPN there is note 1172433. Both caches are not used in FPN scenario and can lead to such strange problems. If this won't help please open a support message for this that we can analyse further.
    Cheers,
    Anja

  • Error : com.sap.tc.webdynpro.services.exceptions.WDRuntimeException

    Hi
    Just got the portal EP7.0 configured to my already existing HCM server ECC6. But on clicking any link i get this error :
    Application error occurs during processing the request.
      Details:   com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create deployable object 'sap.com/mss~pcr' since it is not a Web Dynpro object.  The ID of this error is
    Exception id: [001517258E860068000000B2000019D80004627960F883DF].
    I searched the forum but could not get a solution though mnay have faced this problem. This is for all applications and not only PCR.
    Thanks and regards
    Pamela

    Hi,
    Check JCO destinations are active?
    check the below link for further investigation
    http://help.sap.com/saphelp_nw04/helpdata/en/1f/1b1041a0f6f16fe10000000a1550b0/frameset.htm
    Koti Reddy

  • Com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Instance of vi

    I am getting the following exception when I trying to go to Details view from my results view.
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Instance of view controller ResultsView does not exist.
         at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:356)
         at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.handleUIElementEvent(HtmlClient.java:832)
         at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.updateEventQueue(HtmlClient.java:763)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.initEvents(AbstractClient.java:131)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.prepareTasks(AbstractClient.java:99)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:250)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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)
    To explain further, I have 3 views in my webdynpro project, list view, results view and detail view that is embedded in the same window.
    In the list view, I have a table of materials with linktoaction event that when clicked will go to detail material view to display material information. In this scenario this is working with no problems for all the items in the list.
    When I do the same thing from the result view as the list view, only the first url link action works to display the detail view , the others fail with the above exception.
    Any help on resolving this issue is appreciated.
    Thanks,
    Sunitha.

    Ayyapparaj,
    The lifespan of ResultsView is "FrameworkControlled".
    Following is the code snippet for onclick of a row in the table in the results view,
         IWDMessageManager messageMgr =     wdThis.wdGetAPI().getComponent().getMessageManager();
    //     getting the user's assigned SoldTo from the UME profile
          String[] customer = null;
          String SoldTo = null; 
          try
                    IUser user = WDClientUser.getLoggedInClientUser().getSAPUser(); 
                    IUserAccount[] acct = user.getUserAccounts();      
                    customer = user.getAttribute(AvailabilityApp.NAMESPACE_LENNOX,AvailabilityApp.ATTR_SOLDTO);                     
                    SoldTo = customer[0];
               } catch (UMException e)
                         // TODO Auto-generated catch block
                         messageMgr.reportException(e.getMessage(),false);
         //create the instance and pass parameters for RFC Z_RFC_HRP_MATERIAL_INFO_Input     
         Z_Rfc_Hrp_Material_Info_Input input = new Z_Rfc_Hrp_Material_Info_Input();
         wdContext.nodeZ_Rfc_Hrp_Material_Info_Input().bind(input);
        input.setMatnr(wdContext.currentATP_To_AtpElement().getMatnr().toUpperCase());
        input.setUser_Id(SoldTo);
         //executing the RFC Z_Rfc_Wwhc_Zatp
         wdThis.wdGetAvailabilityAppController().ExecuteZ_RFC_HRP_MATERIAL_INFO();      
         wdContext.currentContextElement().setReturnTextDisplay("Availability Results");
         wdThis.wdFirePlugToDetailView();
    When it goes to Detail view and try to display the UI bound to the output from the above
    Z_RFC_HRP_MATERIAL_INFO() , it shows this error.
    Please note that the above code does not fail for the first row of the results table in the results view, but it does for all the others.  Is there something that I am missing here ?
    Thanks,
    Sunitha.

  • Com.sap.tc.webdynpro.services.exceptions.PDFDocumentCreationException

    Hi all
    1. I am trying to deploy my first adobe interactive app.
    2. When I do that I get:
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.PDFDocumentCreationException: ../../local/TutWD_OnlineInteractiveForm_Init/OnlineInteractiveFormApp/~wd_key2_1187812822296/Error+PDF.pdf?sap-wd-download=1&sap-wd-dl_behaviour=1&sap-wd-cltwndid=5002ea9150ea11dca0b4000d606545db&sap-wd-appwndid=5002ea9250ea11dc97bd000d606545db&sap-wd-norefresh=X
        at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:383)
        at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:1132)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.afterApplicationModification(ClientComponent.java:887)
        at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRespond(WindowPhaseModel.java:573)
        at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:152)
        ... 25 more
    com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Failed to  UPDATEDATAINPDF
    2. I have checked my credentails and they look ok.
    3. I have run the Adobe Test on http:
    server:port\AdobeDocumentServices/Config
       and I get a response.
    I am going crazy.
    Any help wl be appreciated
    yuval

    Hello Dezso
    1. Where do you define ADSProxy? I underatand it must be in the Visual Adminin.
    2. I managed somehow to run my application I can see the form now but  get
        this message box when the PDF is inserted into the browser:
        This document contains certain rights to enable special features in Adobe
        Reader. The document has been hanged since it was created and these
        rights are no longer valid. Pls contact the author for the original version of this
        document.
    3. Are you familiar with this message? What can be done?
    Tks
    yuval

  • Java.lang.NullPointerException   at com.sap.caf.eu.gp.ui.inst.CInstantiation.getProcessTemplate(CInstantiation.java:732)

    Hi I am getting the following error on link related to Guided procedure step only for few people not for every one. Once  i delete the browser cookies are cache it is working fine. Please  let me know , if any one could had same issue or if any one know the reason, it is completely showing related to Standard GP service related exception. Also this errors are not coming all the time consistently, it is happening randomly. but when u get the error if you delete the cookies from browser and log off and login again from portal it is working fine.
    Path to object does not exist at com.sap.nw.eu.gp, the whole lookup name is sap.com/com.sap.nw.eu.gp/GPService.
    com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at com.sap.nw.eu.gp, the whole lookup name is sap.com/com.sap.nw.eu.gp/GPService.
    at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:278)
    at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:627)
    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
    at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
    at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at com.sap.caf.eu.gp.ui.inst.CInstantiation.wdDoInit(CInstantiation.java:161)
    at com.sap.caf.eu.gp.ui.inst.wdp.InternalCInstantiation.wdDoInit(InternalCInstantiation.java:148)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
    at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:864)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
    at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1362)
    at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
    at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
    at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
    at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    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:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1064)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    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:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176) 
    Exception occured during processing of Web Dynpro application sap.com/caf~eu~gp~ui~inst/AInstantiation. The causing exception is nested.
    [EXCEPTION]
    java.lang.NullPointerException
    at com.sap.caf.eu.gp.ui.inst.CInstantiation.getProcessTemplate(CInstantiation.java:732)
    at com.sap.caf.eu.gp.ui.inst.wdp.InternalCInstantiation.getProcessTemplate(InternalCInstantiation.java:203)
    at com.sap.caf.eu.gp.ui.inst.VInstantiation.dispatch(VInstantiation.java:182)
    at com.sap.caf.eu.gp.ui.inst.VInstantiation.onEventShowInstantiationView(VInstantiation.java:564)
    at com.sap.caf.eu.gp.ui.inst.wdp.InternalVInstantiation.wdInvokeEventHandler(InternalVInstantiation.java:291)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
    at com.sap.tc.webdynpro.progmodel.controller.Component.fireEvent(Component.java:285)
    at com.sap.caf.eu.gp.ui.inst.wdp.InternalCInstantiationInterface.wdFireEventShowInstantiationView(InternalCInstantiationInterface.java:174)
    at com.sap.caf.eu.gp.ui.inst.CInstantiationInterface.setTemplateId(CInstantiationInterface.java:116)
    at com.sap.caf.eu.gp.ui.inst.wdp.InternalCInstantiationInterface.setTemplateId(InternalCInstantiationInterface.java:129)
    at com.sap.caf.eu.gp.ui.inst.WInstantiationInterfaceView.onPlugDefault(WInstantiationInterfaceView.java:83)
    at com.sap.caf.eu.gp.ui.inst.wdp.InternalWInstantiationInterfaceView.wdInvokeEventHandler(InternalWInstantiationInterfaceView.java:105)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingInterfaceView.invokeEventHandler(DelegatingInterfaceView.java:85)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:162)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:375)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
    at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:864)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
    at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1362)
    at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
    at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
    at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
    at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    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:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1064)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    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:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

    Govardan,
    Thanks for the reply. We don't have any custom code related to GP or CAF. We created the GP Process and in the process, we attached the PCD objects to the callable object to call.
    In the entire error trace it is referring only sap standard classes only. Also we haven't done any customization Except GP Process creation as i mentioned above.
    com.sap.caf.eu.gp.ui.inst.CInstantiation.getProcessTemplate(CInstantiation.java:732),
    if you look at my initial report , there are two exceptions i have mentioned. before coming the above error i have observed the following error in the log file, First it is logging the following error and then next showing the above error. Looks like GPService is not able to lookup .
    Path to object does not exist at com.sap.nw.eu.gp, the whole lookup name is  sap.com/com.sap.nw.eu.gp/GPService.
    com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at com.sap.nw.eu.gp, the whole lookup name is sap.com/com.sap.nw.eu.gp/GPService.
    at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:278)
    at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:627)
    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
    at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
    at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at com.sap.caf.eu.gp.ui.inst.CInstantiation.wdDoInit(CInstantiation.java:161)
    at com.sap.caf.eu.gp.ui.inst.wdp.InternalCInstantiation.wdDoInit(InternalCInstantiation.java:148)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
    at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:864)
    at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
    at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1362)
    at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
    at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
    at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
    at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:185)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    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:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1064)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    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:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176) 
    Thanks

  • Com.sap.mw.jco.JCO$Exception:JCO_ERROR_XML_PARSER

    Hi all,
    I try to send data from RFC to XI, but I get error in adapter like :
    After a value an end tag must follow. That did not happen in "ATTR_SET>- Error: 2006-08-10 11:12:56 GMT+02:00: com.sap.mw.jco.JCO$Exception: (130) JCO_ERROR_XML_PARSER: After a value an end tag must follow. That did not happen in "ATTR_SET>-
    I use 3 tables(deep structures)...
    Anybody any idea?
    Thanks

    Thanks for your rapid answer
    Very funny thing - after I made cold backup (stopping XI) it started to work(I saw my XML in SXMB_MONI), but when I did this the next time(adding fields to my RFC) the same happened...
    Full cache refresh didn't solve the problem...
    Any idea?
    Thanks a lot

  • Failure in Model Create Step: com.sap.mw.jco.JCO$Exception: Missing R3NAME=

    Hi,
    I am running NW04sp10 and am trying to connect my WebDynPro to my R/3 backend app server - am running through the FlightChecking example using DevStudio 2.0.10.
    Have successfully created my meta + app data JCo's, they test and ping OK from the Content Manager.  SLD is fine, connecting happily to the NW and R/3 boxes.  One is message server, one central instance.
    When the 'create model' wizard tries to build the java proxies though, it comes back with this:
    [Fatal]:     com.sap.mw.jco.JCO$Exception: Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx
    Can anyone help?
    Cheers guys,
    Andy

    Hi Wael,
    I'm using the tutorial 'Handling Transactions with BAPIs in Web Dynpro' [part of SAP Online Help].
    The BAPI does work in se37, it's just a standard SAP delivered BAPI, and I've tried a few different ones to make sure it wasn't a BAPI specific problem.
    In the content admin I've navigated through the local/FlightChecking/Applications/FlightCheckingComp and then used the wizard to add the 2 JCOs [I've kept the default names for now after your previous advice]
    The data is like this:
    WD_MODELDATA_DEST:
    Name                  WD_MODELDATA_DEST
    Client                800
    J2EE Cluster Name     NW1 on chippy
    USER                  USER1
    Password              <password>
    Application Server    nero
    System ID             00
    WD_RFC_METADATA_DEST:
    Name                  WD_RFC_MODELDATA_DEST
    Client                020
    J2EE Cluster Name     NW1 on chippy
    USER                  USER1
    Password              <password>
    Application Server    chippy
    System name           NW1
    Logon Group           PUBLIC
    My landscape here is of 2 servers:
    'Nero'    SAP r/3 4.7 Application Server System ID ACI
    'Chippy'  SAP WebAS640 NW04 System ID NW1 ABAP+J2EE stack
    The JCOs 'test' and 'ping' successfully.  My WD_RFC_METADATA_DEST connection is to a message server, the WD_MODEL_DEST is to a central instance.
    Here's the full log from the create model wizard [I used a random BAPI for testing, BAPI_GET_PAYSLIP, so don't worry about that]:
    [Warning]:     Creating a connection with Metamodel language <en_GB> failed.  Continuing with language <EN>
    [Fatal]:     com.sap.mw.jco.JCO$Exception: Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx
    [Info]:     Creating Model: FlightChecking
    [Info]:     Creating Model Class: Bapi_Get_Payslip_Input
    [Info]:     Creating Model Class: Bapi_Get_Payslip_Output
    [Info]:     Creating Model Class: Bapireturn1
    [Info]:     Creating Model Relation: Bapi_Get_Payslip_Output:Return
    [Info]:     Creating Model Class Property: Type
    [Info]:     Creating Model Class Property: Id
    [Info]:     Creating Model Class Property: Number
    [Info]:     Creating Model Class Property: Message
    [Info]:     Creating Model Class Property: Log_No
    [Info]:     Creating Model Class Property: Log_Msg_No
    [Info]:     Creating Model Class Property: Message_V1
    [Info]:     Creating Model Class Property: Message_V2
    [Info]:     Creating Model Class Property: Message_V3
    [Info]:     Creating Model Class Property: Message_V4
    [Info]:     Creating Model Class Property: Employeenumber
    [Info]:     Creating Model Class Property: Payslipvariant
    [Info]:     Creating Model Class Property: Sequencenumber
    [Info]:     Creating Model Class: Bapi7004_Payslip
    [Info]:     Creating Model Relation: Bapi_Get_Payslip_Input:Payslip
    [Info]:     Creating Model Class Property: Format_Col
    [Info]:     Creating Model Class Property: Text_Col
    [Info]:     Creating Model Relation: Bapi_Get_Payslip_Output:Payslip
    [Info]:     Creating Model Relation: Bapi_Get_Payslip_Input:Output:Bapi_Get_Payslip_Output
    So it seems to actually be able to retrieve the metadata for the BAPIs, but not to make the relevant JCo's.  I've not gone on and completed the tutorial, assuming it won't work until I can sort out the above 'fatal' error.
    Thanks again for all of your good advice.
    Cheers,
    Andy

  • Com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP

    For reason to change server IP address,
    EP: 192.168.2.21 to 192.168.2.41
    BW:192.168.2.22 to 192.168.2.42
    and fix system by steps:
    1,logon bw system,using tcode sm59 to modify tcp/ip connection.
    2,logon ep system using visual administrator,and modified jco parameters.
    3,logon ep system using ie,and modified sld,datasupplier.
    4,restart bw and ep system.
    after changed,the BEx Web did not work,
    enter Maintain Jco destination
    select jco destination: mete_data
    click test
    raise the error:
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM  TYPE=B MSHOST=bw GROUP=public R3NAME=BW1 MSSERV=sapmsBW1 PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       partner '192.168.2.22:sapgw00' not reached TIME        Tue Dec 18 15:39:34 2007 RELEASE     700 COMPONENT   NI (network interface) VERSION     38 RC          -10 MODULE      nibuf.cpp LINE        4601 DETAIL      NiBufIConnect: connection pending after 60000ms SYSTEM CALL connect ERRNO       55 ERRNO TEXT  A connect operation on a socket is not complete. COUNTER     1
    would someone tell me how to resolve this problem.
    regards

    Hi,
    It seems that the SAP gateway host is deactivated or the TCP/IP port 33xx (where xx corresponds to the system number) is not open.
    First try pinging <IP address>.  If there is no reply, then Boot SAP Gateway host required.
    Check whether the TCP/IP port 33xx is open (where xx corresponds to the system number) and start the SAP gateway
    The TCP/IP port is also partially defined in the services file as an sapgw<SID> or sapgwxx entry (where xx corresponds to the system number). The services file is in the Windows directory or in WinNT/System32/drivers/etc.
    Hope this helps.
    Regards
    Srinivasan T

Maybe you are looking for

  • Any hope for OpenMP with Xcode / Obj-C?

    I've been compiling command-line OpenMP C-based stuff, but it uses the gcc 4.3 from hpc.sourceforge.net, and I don't believe this can be made to work with Xcode 3 / Objective-C. I presume I either have to wait for Apple to support OpenMP in their gcc

  • Internal concurrent manager is not up

    HI db : 11g apps : 11.5.10.2 I found this error in internal conc mgr log file. APP-FND-01564: ORACLE error 1 in insert_icm_record Cause: insert_icm_record failed due to ORA-00001: unique constraint (APPLSYS.FND_CONCURRENT_PROCESSES_U1) violated. The

  • HT201317 Photo stream not working on all photos

    Why does the iPhone not always send photos I ve taken to iCloud or to my iPad ? Does iCloud/photo stream really work? Never worked properly for me..... Some do and most of time don t . Both have been in the same room to pick up wifi for over 48 hours

  • Static Credit Checks - Open orders - Confirmed quantity vs total quantity

    We are using static credit checks. Credit currently only sees open orders with a confirmed quanitity. Customer orders 10 items we have 5 in stock. Credit check runs, credit is evaluated basd on the confirmed open quanitity of 5. The order gets a cred

  • Error in importing objects in STMS_IMPORT

    Hi Experts, Urgent!! I have exported IR & ID objects under one TR (using CTS organizer) from DEV environment. While importing  by using STMS_IMPORT in PI QTY system I got the following error. RFC communications error with system/destination %%ashost=