MAM- NullPointer- com.sap.ip.me.smartsync.smartsynchronizationException

Hi,
The MAM 2.5 SR2 application is working fine on the desktop.But when I deploy the same application on  a Pocket PC 2003 PDA I get the following exception when performing synchronization.
com.sap.ip.me.smartsync.smartsynchronizationException
The MAM app is extracted successfully on the webapps directory of MI client
The device is a iPAQ Pocket PC 2003 with MI 2.5 SP11 and Creme jdk for Pocket PC 2003 SE

Hi ,
check the entries in settings ..if every thing is ok there then reinstall MI 2.5 client with device fully charged..
I have faced the same error with ME 2.1 on hand held devices when battery was low during installation of Mobile engine.
U can also switch on the trace which might be of further help..
cheers
Anand

Similar Messages

  • SMARTSYNC : com.sap.ip.me.smartsync.sync.InboundTransformException

    Hi experts,
    when i sync applications via smartsync i get this errormessage:
    "SMARTSYNC :com.sap.ip.me.smartsync.sync.InboundTransformException: Not wellformed nor collapsed xml".
    I get this message for each syncbo from MAM 2.0 and also for the syncbo from the MDK-Sample application.
    Can anyone help me?
    GenericSync applications are working fine.
    Clients: MI2.5 SP12P1, MI Server 2.5 SP11.
    Regards.
    Frank Brackmann

    Hi Frank,
      That SAP Note is specific to the error you are having but it also assumes that your system is uptodate with other required Notes and thats why it lists them. I am quite positive that if you apply the notes successfully your error will go away. I say this from experience, I have had so many errors but thankfully the SAP MI team have created the solutions that have fixed them. Everytime I do get an error of some sort I check to make sure that my System is uptodate with all upgrades/notes/patches. If it is, then I would start  an OSS note. Luckily for you a note is readily available.
    Oh one more thing Frank, I am using MI 2.5 sp13 client and server and its a major upgrade. I recommend you upgrade to sp13 soon it will resolve most if not all of your problems. The performance is way better, plus the new API's even though they are not documented well yet are definately much better than pre-sp13 .
    -wael

  • NullPointerException at com.sap.ip.me.smartsync.data.AbstractRow.getSyncKey

    Dear all,
    I have created one mobile application,with SyncBo,which
    contain the getlist , getdetail and create wrapper function modules.(Using MDK 2.5 , server SP 13,Studio SP 13)
    This create wrapper function module is internaly using some BAPI's , because of that , when the frame work calls the get detail  function module after the create ,
    the data coming is  not complete. The key field selection and mapping is perfect (Its is working fine).
    (one of the internally using function module has 10 second delay)
    Because of this or commit work associated with BAPI, i am not getting  sufficient data first, as i described above.
    but after some time , in the next syncronization  im getting the expected data.
    if not wait , after sync, i am getting unexpected exception at the time of viewing the newly created data.
    this is the Exception , that i got (below)
    ==============================================
    java.lang.NullPointerException
         at com.sap.ip.me.smartsync.data.AbstractRow.getSyncKey(AbstractRow.java:302)
         at com.sap.ip.me.smartsync.data.SyncBoProxy.getSyncKey(SyncBoProxy.java:178)
         at com.sap.ip.me.smartsync.data.SyncBoCollectionImpl.(SyncBoCollectionImpl.java:30)
         at com.sap.ip.me.smartsync.data.SyncBoListImpl.(SyncBoListImpl.java:30)
         at com.sap.ip.me.smartsync.data.SyncBoDataFacadeImpl.getSyncBos(SyncBoDataFacadeImpl.java:146)
    ==========================================
      please help me to resolve this problem
                                          Regards
                                          Kishor G

    hello kishor,
    did you apply any patch for sp13?
    patch 09 is the latest for sp 13. check on
    note number 905518.
    there are some fixes which could be related
    to this problem.
    regards
    jo

  • Nullpointer on com.sap.tc.webdynpro.progmodel.controller.MessageManager

    Dear all,
    i have two web dynpro components, say A and B.
    A is using component B.
    When i push a close button in B, i do the following things:
    1. wdComponentAPI.getMessageManager().reportWarning("Some warning!!!");
    2. wdThis.wdGetICLRequestDetailsController().leaveRequestDetails();
    This leaveRequestDetails() fires a plug (standard) to leave back to my component A and component A deletets the componentUsage when needed... ( if(hasActiveComponent()) )
    Component B has a view with an inputfield for an amount (bigdecimal). When this has valid input and i push the button and execute 1. and 2. everything works fine and i see the warning on the view of my comp. A.
    When i put invalid input in the amount field ( for example some characters) and i push the button, i see an error message on my view in comp. B. (automatic validation)
    When i correct the input and push the submit button again while the previous error message is still visible on the screen (so there's no event trigerred since the automatic validation), i get the following nullpointer exception on calling the deleteComponent method in component A:
    java.lang.NullPointerException
    +     at com.sap.tc.webdynpro.progmodel.controller.MessageManager.setAttributeValidbyContext(MessageManager.java:656)+
    +     at com.sap.tc.webdynpro.progmodel.context.NodeElement.clearPendingInput(NodeElement.java:297)+
    +     at com.sap.tc.webdynpro.progmodel.context.NodeElement.exit(NodeElement.java:132)+
    +     at com.sap.tc.webdynpro.progmodel.context.Node$ElementList.exit(Node.java:1859)+
    +     at com.sap.tc.webdynpro.progmodel.context.Node.clearElements(Node.java:1560)+
    +     at com.sap.tc.webdynpro.progmodel.context.Node.forgetDataNode(Node.java:1733)+
    +     at com.sap.tc.webdynpro.progmodel.context.Node.exit(Node.java:295)+
    +     at com.sap.tc.webdynpro.progmodel.context.Node.exit(Node.java:306)+
    +     at com.sap.tc.webdynpro.progmodel.context.Context.exit(Context.java:53)+
    +     at com.sap.tc.webdynpro.progmodel.controller.Controller.exit(Controller.java:161)+
    +     at com.sap.tc.webdynpro.progmodel.view.View.exitController(View.java:403)+
    +     at com.sap.tc.webdynpro.progmodel.view.View.exitController(View.java:435)+
    +     at com.sap.tc.webdynpro.progmodel.controller.Controller.exit(Controller.java:154)+
    +     at com.sap.tc.webdynpro.progmodel.view.ViewManager.exit(ViewManager.java:125)+
    +     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.exit(ClientComponent.java:211)+
    +     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.deleteComponent(ClientComponent.java:195)+
    +     at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.deleteComponent(ComponentUsage.java:199)+
    When i do the same again, but without reporting the warning before leaving comp B, i don't get the nullpointer exception and can continue interacting on my view in component A.
    Can anyone tell me what's the cause for this nullpointer? is it a bug?
    Kind regards.
    J.

    The following is a working solution for me:
    MessageManager mManager = (MessageManager)wdComponentAPI.getMessageManager();
    mManager.reset();
    I have put these lines right before i call the deleteComponent() method in my web dynpro component A.

  • Com.sap.aii.messaging.adapter.trans.TransformException:'java.lang.NullPoint

    Hi, This is Prasad
    We are using 7.0 with SP15, i am using MTB module at receiver side ,we are getting following error.
    Message processing failed. Cause: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'java.lang.NullPointerException'; nested exception caused by: java.lang.NullPointerException
    And we are passing following FCC Parameters
    Transform.Class = com.sap.aii.messaging.adapter.Conversion
    Transform.ContentType = text/xml;charset=utf-8
    xml.Record.fieldFixedLengths
    xml.Recordset.fieldSeparator
    xml.conversionType= StructXML2Plain
    xml.recordsetStructure  = Recordset,Record
    Please help me out ASAP

    Hi Stefan,
    I am a little bit confused with the parameter "Transform.ContentType".
    According to your post it should be "TransformContentType" but the document has not yet been updated. At least when I search within SDN for the document I still get the old version with the dot.
    In addition there is OSS note 1131655 from September 2008 (pretty new) and there SAP still refers to parameter "Transform.ContentType".
    So, I assume the parameter with the dot is the correct one, right?
    Klaus

  • MAM development on SAP NetWeaver Mobile 7.1?

    Hello world
    I did notice that SAP has released SAP NetWeaver Mobile 7.1. I was of course very curious if this would (finally) make MAM25 developments possible in the new SAP NetWeaver (Mobile ) Developer Studio 7.1, because the old SAP NetWeaver Developer Studio 7.0 is based on Eclipse 2.X while the new one is based on Eclipse 3.3 (which has some advantages compared to Eclipse 2.X).
    So I did download SAP NetWeaver Developer Studio 7.1 and SAP NetWeaver Mobile 7.1, and installed both of them on my system. I was positively surprised when I noticed a Mobile Infrastructure perspective. So I did download our customized MAM25 source code from the CVS server and I tried to let it compile and run on SAP NetWeaver Mobile Developer Studio 7.1.
    Compiling was not a problem: after including some required JAR files, the code did compile successfully, however when trying to export the project, it seemed that the JSP files were not compiled, however I did put the tick mark at the Add JSP as compiled classes option. In my NetWeaver Developer, a folder $jsp was created, but with nothing inside. And in the generated WAR-file, I couldn't find any compiled JSP file as well...
    In the 7.0 version, a file called mam25.jar was created and putted into the lib folder in the war archive file, which contained all the class files. This file was not created with version 7.1.
    When trying to run the MAM from within NetWeaver Mobile Developer Studio 7.1, I did get the following exception when launching:
    java.lang.NoClassDefFoundError: com/sap/tc/mobile/cfs/startup/Startup
    Caused by: java.lang.ClassNotFoundException: com.sap.tc.mobile.cfs.startup.Startup
    Is there anyone who can tell me whether or not SAP NetWeaver Mobile Developer studio 7.1 is able to compile, generate and run the MAM25 source? If not, why is there a perspective Mobile Infrastructure included?
    If it is compatible, does anyone have an idea why it didn't work with me?
    Thanks for your help!
    Best regards,
    Diederik

    Hi all,
    First of all, thanks for all the information!
    I think there is a little misunderstanding, or maybe I am wrong
    SAP NetWeaver is the web-application you can use to analyze, administrate, etc... your mobile applications?
    I am actually talking about the SAP NetWeaver Developer Studio 7.1, which is in fact just an extended Eclipse environment. There is some kind of mobile update pack which you can find here: [SAP NetWeaver Mobile 7.1 SP3|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0846cb5-59ec-2a10-46a2-cff9cd9b8fc3]
    My question was if you can maintain and develop in JAVA your MAM25 application with this version of the Netweaver Developer Studio? I did notice a perspective Mobile Infrastructure as in version 7.0, and I can compile the JAVA code, but I can't run the application (see error in original posting) and it seems that no JAVA files are generated from the JSP files.
    I guess it is just a matter of making the plugins compatible for Eclipse 3.X, because the plugin system of Eclipse 2.X is not compatible with the plugin system of Eclipse 3.X. But because of the Mobile Infrastructure perspective that I did notice, I was thinking that this was done. But this seems not to be the case, or I did do something wrong...
    So the only question is: can I use SAP NetWeaver Developer Studio 7.1 (aka Eclipse 3.X) to develop in JAVA the MAM25 application?
    Thanks for the help!
    Best regards,
    Diederik

  • NoClassDefFoundError: com/sap/sql/log/OpenSQLException

    I have developed a Java project. It consists of 2 SQLJ files and then a Java class. When I try to execute the Java program, I get a Java error:
    java.lang.NoClassDefFoundError: com/sap/sql/log/OpenSQLException
         at com.mbb.crrs.business.report.dao.ReportDAO.<init>(ReportDAO.sqlj:23)
         at com.mbb.crrs.business.report.dao.Test.main(Test.java:24)
    Exception in thread "main"
    I notice a similar problem on message: Re: Which jar to include com.sap.sql.log.OpenSQLException
    Is that something that I need to maintain for it to work? Thank you.

    Hi,
    the problem one year ago was that the SQLException class was not available through remote access. I don't know if that might have been changed meanwhile in the latest release.
    I implemented a simple work around: I caught every SQL-exception in the method where it was thrown, wrapped the exception message and any nested exception in a self written exception and threw this new exception. That worked fine.
    Regards, Astrid

  • SR Log Error - |  Message  : com.sap.esi.uddi.sr.api.exceptions.SRException

    Hi,
    We are getting below errors in /nwa/logs. We have our PI (7.11) and Service Registry configured on the same server. And have out CE (7.2) system connected to this service registry. Does any one has similar experience? Please let me know if you have any solution for the same.
    SR Log Error
    |  11-Nov-11  14:10:45.568
    |  Method   : getClassificationSystems()
    |  Class    : com.sap.esi.uddi.sr.api.ws.ServicesRegistrySiImplBean
    |  ThreadID : 146
    |  Message  : com.sap.esi.uddi.sr.api.exceptions.SRException: No classification system found for ID 'QName: Namespace= http://uddi.sap.com/classification; Name=  ConfigurationFlags'
    |
    |       com.sap.esi.uddi.sr.impl.common.Utility.cs2srException(Utility.java:122)
    |       com.sap.esi.uddi.sr.impl.ejb.ServicesRegistryBean.getClassificationSystems(ServicesRegistryBean.java:242)
    |       sun.reflect.GeneratedMethodAccessor1325.invoke(Unknown Source)
    |       sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    |       java.lang.reflect.Method.invoke(Method.java:585)
    |       com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
    |       com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
    |       $Proxy1087.getClassificationSystems(Unknown Source)
    |       com.sap.esi.uddi.sr.api.ws.ServicesRegistrySiImplBean.getClassificationSystems(ServicesRegistrySiImplBean.java:456)
    |       sun.reflect.GeneratedMethodAccessor1324.invoke(Unknown Source)
    |       sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    |       java.lang.reflect.Method.invoke(Method.java:585)
    |       com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_WS.invoke(Interceptors_WS.java:31)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
    |       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    |       com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
    |       com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod(DefaultImplementationContainer.java:203)
    |       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:512)
    |       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:486)
    |       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:256)
    |       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:176)
    |       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging(ServletDispatcherImpl.java:112)
    |       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:70)
    |       SoapServlet.doPost(SoapServlet.java:51)
    |       javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    |       javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    |       com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
    |       com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
    |       com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
    |       com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
    |       com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
    |       com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
    |       com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:245)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
    |       com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    |       com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    |       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    |       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
    |       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
    |       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    |       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    |       com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
    |       com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
    |       com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
    |       com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
    |       com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
    |       com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    |

    Hi,
    Refer Error:Service Registyr Configuration PI 7.11
    and http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8071b1b8-3c5c-2e10-e7af-8cadbc49d711?QuickLink=index&overridelayout=true
    Thanks,
    Chandra

  • Exception com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCException

    Hi Experts,
    I am getting following run time error message while running a Web Dynpro program:
    java.lang.ClassCastException: com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCException: List must contain AbstractList (ProxyList) of Type 'com.sasol.pr.create.Bapimereqitemimp$Bapimereqitemimp_List', not of 'class com.sasol.pr.create.Bapimereqitem$Bapimereqitem_List'!
    Detailed error message is:
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; InfoPath.1)
    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.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:18:32[UTC], changelist=434634, host=pwdfm101), build date: Thu Apr 12 16:35:25 IST 2007
    J2EE Engine No information available
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2 1.4.2.12-061213-10:06-IA64W IA64W, vendor: Hewlett-Packard Company
    Operating system HP-UX, version: B.11.23, architecture: IA64W
    Session & Other
    Session Locale en_US
    Time of Failure Tue Apr 17 14:05:49 IST 2007 (Java Time: 1176798949444)
    Web Dynpro Code Generation Infos
    local/Pr_Create_16042007_I
    SapDictionaryGenerationCore 6.4009.00.0000.20041026131628.0000 (release=630_REL, buildtime=2004-11-02:22:13:11[UTC], changelist=295793, host=PWDFM027.wdf.sap.corp)
    SapDictionaryGenerationTemplates (unknown)
    SapGenerationFrameworkCore 6.4009.00.0000.20041026132141.0000 (release=630_REL, buildtime=2004-11-02:22:05:28[UTC], changelist=295805, host=PWDFM027.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 6.4009.00.0000.20041026133106.0000 (release=630_REL, buildtime=2004-11-02:22:21:59[UTC], changelist=295820, host=PWDFM027.wdf.sap.corp)
    SapMetamodelCommon 6.4009.00.0000.20040909194107.0000 (release=630_REL, buildtime=2004-11-02:22:06:42[UTC], changelist=280398, host=PWDFM027.wdf.sap.corp)
    SapMetamodelCore 6.4009.00.0000.20040909194107.0000 (release=630_REL, buildtime=2004-11-02:22:06:29[UTC], changelist=280398, host=PWDFM027.wdf.sap.corp)
    SapMetamodelDictionary 6.4009.00.0000.20040805191532.0000 (release=630_REL, buildtime=2004-11-02:22:10:20[UTC], changelist=270520, host=PWDFM027.wdf.sap.corp)
    SapMetamodelWebDynpro 6.4009.00.0000.20041026132448.0000 (release=630_REL, buildtime=2004-11-02:22:17:25[UTC], changelist=295810, host=PWDFM027.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 6.4009.00.0000.20041102105304.0000 (release=630_REL, buildtime=2004-11-02:22:38:28[UTC], changelist=297524, host=PWDFM027)
    SapWebDynproGenerationCore 6.4009.00.0000.20041026133106.0000 (release=630_REL, buildtime=2004-11-02:22:22:31[UTC], changelist=295820, host=PWDFM027.wdf.sap.corp)
    SapWebDynproGenerationTemplates 6.4009.00.0000.20041102105304.0000 (release=630_REL, buildtime=2004-11-02:22:38:28[UTC], changelist=297524, host=PWDFM027)
    sap.com/tcwddispwda
    No information available null
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    java.lang.ClassCastException: com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCException: List must contain AbstractList (ProxyList) of Type 'com.sasol.pr.create.Bapimereqitemimp$Bapimereqitemimp_List', not of 'class com.sasol.pr.create.Bapimereqitem$Bapimereqitem_List'!
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClass.setRelatedModelObjects(DynamicRFCModelClass.java:807)
    at com.sasol.pr.create.Bapi_Pr_Create_Input.setPritem(Bapi_Pr_Create_Input.java:403)
    at com.sasol.pr.creation.PrCreationCust.executeBapi_Pr_Create(PrCreationCust.java:215)
    at com.sasol.pr.creation.wdp.InternalPrCreationCust.executeBapi_Pr_Create(InternalPrCreationCust.java:240)
    at com.sasol.pr.creation.ApplView.onActionSearch(ApplView.java:152)
    at com.sasol.pr.creation.wdp.InternalApplView.wdInvokeEventHandler(InternalApplView.java:258)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:759)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
    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:387)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Can you please have a look on it and suggest me the solution.
    Regards,
    RK

    Hi
    since u have shown only exceptions.. check this link.. u r also using PR i guess from the exception..
    WDDynamicRFCException: Please help
    n post ur code also.
    Thanks
    Puneet

  • Unable to login to IB - again com.sap.engine.services.rmi_p4.P4IOException

    We have installed a new PI 7.1 system and at he moment I have the problem that I can't login into the IB tools. I found a lot of threads with this problem but I can't find a solution for my specific problem. Have a look at the well known error log:
    com.sap.aii.utilxi.misc.api.ReconnectRuntimeException: Cannot connect to server using message server: ms://MYHOST:8100/P4
         at com.sap.aii.ib.clsif.login.EJBHomeFactory.getInitialContext(EJBHomeFactory.java:668)
         at com.sap.aii.ib.clsif.login.EJBHomeFactory.connect(EJBHomeFactory.java:461)
         at com.sap.aii.ib.clsif.login.EJBHomeFactory.initRemoteFactory(EJBHomeFactory.java:133)
         at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:176)
         at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:121)
         at com.sap.aii.ib.clsif.login.LoginServiceImpl.login(LoginServiceImpl.java:109)
         at com.sap.aii.ib.gui.login.SplashLoginFrame$LoginController.doTrial(SplashLoginFrame.java:960)
         at com.sap.aii.ib.gui.login.SplashLoginFrame$LoginAction$1.run(SplashLoginFrame.java:832)
         at java.awt.event.InvocationEvent.dispatch(Unknown Source)
         at java.awt.EventQueue.dispatchEvent(Unknown Source)
         at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.run(Unknown Source)
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext.
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:488)
         at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
         at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
         at javax.naming.InitialContext.init(Unknown Source)
         at javax.naming.InitialContext.<init>(Unknown Source)
         at com.sap.aii.ib.clsif.login.EJBHomeFactory.getInitialContext(EJBHomeFactory.java:653)
         ... 15 more
    Caused by: com.sap.engine.interfaces.cross.EXTstinationException: cannot establish connection with any of the available instances:
    MYHOST.DOMAIN.EXT:50104 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 172.24.205.193 and port: 50104
         at com.sap.engine.interfaces.cross.EXTstination.getNextAvailableBroker(Destination.java:59)
         at com.sap.engine.interfaces.cross.EXTstination.getRemoteBroker(Destination.java:35)
         at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:352)
         ... 20 more
    As you can see I call the IB via a pure hostname "MYHOST". But in the last step you can see the the FQDN  "MYHOST.DOMAIN.EXT"was used. That brings me into trouble because these are different IP's. I can't reach the MYHOST.DOMAIN.EXT IP and that's why I can't login into the IB.
    If I add an entry in my local host file for MYHOST.DOMAIN.EXT with the IP address I can reach all works fine but this solution is unacceptable.
    The key question is why the IB uses this FQDN. I can't find any setting where this FQDN is used. I have checked the complete exchange profile, the sld and and and u2026. I always find only the pure hostname MYHOST.
    Additionally I have to say that we have already a PI 7.1 system (DEV) whre I can use all tools. But this is a migrated system (from 3.0). I have only problems with that new installed empty system.

    Thanks Barry. I've checked all connections. They all use the short name and all work.
    Thanks Joel, but I think you get me wrong. That's why I will explain it a little bit better.
    I can use the IB if I manipulate my own hosts file but this is in my eyes not the right way. As I have written I can use my PI dev system without that kind of manipulation.
    My new PI system is at our computer centre. The PI machine has two network interface and I can use only one of these two. As you can see at the error log the full name points to 172.24.205.193 but I only can reach the 172.20.02.193 address. For this second IP we have an entry at our DNS server. The other one (FQDN) comes from the computer center DNS server. Of course I can overwrite it with an entry in my local hosts file but I think that isn't a good solution.
    The key question is: Why the full qualified domain name "MYHOST.DOMAIN.EXT" is used instead of the short name.
    I call the IB via the web page
    http://MYHOST:50100/dir/start/index.jsp
    And as you can se at the log the first call goes to this address. But then a second call goes to MYHOST.DOMAIN.EXT:50104. And I can find any setting (exchange profile and so on) where this full qualified domain name is specified.

  • Deployable cannot be retrieved from FILE_PROVIDER , stopping. Cause:com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Name or password is incorrect

    Hi All,
    After two years of CTS+ working without issue, in the last fortnight JCO_ERROR_LOGON_FAILURE has occurred. I have reviewed all the configuration  in document http://scn.sap.com/doc/DOC-30177, and it all looks fine. The user configured also checks out fine as well. The user id that is causing all the trouble is CTS_<SID>. We chose this option so we could determine which user in case of future issues. We have two development paths, Project and BAU. So at anyone time transports that have started in the BAU development system will need to be imported into the Project development system (using transport express) and vice versa.  Attached is the security authentication log from the system showing authentication failure. I have also checked the transport routes defined for the business systems in the SLD and these look fine as well. Roles assigned to the user are SAP_CTS_PLUS,
    SAP_J2EE_ADMIN, SAP_XI_CMS_SERV_USER, SAP_XI_CONFIGURATOR, SAP_XI_DEVELOPER, Z_CTS_PLUS_ADDITIONAL. I have also checked the permissions on the file at the operating system level.
    Any suggestions/advice gratefully received as this really has me scratching my head.
    Log:
    !REPOSITORY_ERROR_CHECK_STACKTRACE!
    [EXCEPTION]
    com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Name or password is incorrect (repeat logon) on DXI mshost strsap31
    at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:662)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect(MiddlewareJavaRfc.java:1364)
    at com.sap.conn.jco.rt.ClientConnection.connect(ClientConnection.java:731)
    at com.sap.conn.jco.rt.PoolingFactory.init(PoolingFactory.java:103)
    at com.sap.conn.jco.rt.ConnectionManager.createFactory(ConnectionManager.java:293)
    at com.sap.conn.jco.rt.DefaultConnectionManager.createFactory(DefaultConnectionManager.java:46)
    at com.sap.conn.jco.rt.ConnectionManager.getFactory(ConnectionManager.java:262)
    at com.sap.conn.jco.rt.RfcDestination.initialize(RfcDestination.java:509)
    at com.sap.conn.jco.rt.RfcDestination.getSystemID(RfcDestination.java:533)
    at com.sap.conn.jco.rt.RepositoryManager.getRepository(RepositoryManager.java:30)
    at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:603)
    at com.sap.conn.jco.rt.RfcDestination.getRepository(RfcDestination.java:27)
    at com.sap.cts.jco.tms.TmsJCoAdapter.initializeJCo(TmsJCoAdapter.java:76)
    at com.sap.cts.jco.tms.TmsJCoAdapter.<init>(TmsJCoAdapter.java:57)
    at com.sap.cts.jco.EpsFileReader.<init>(EpsFileReader.java:76)
    at com.sap.cts.jco.EpsFileReaderController.doImport(EpsFileReaderController.java:90)
    at com.sap.cts.core.ImportManager.execImport(ImportManager.java:102)
    at com.sap.cts.ejb.DeployBean.execImport(DeployBean.java:170)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:47)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
    at com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod(DefaultImplementationContainer.java:204)
    at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:710)
    at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:662)
    at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:322)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:199)
    at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:65)
    at com.sap.engine.services.webservices.servlet.SoapServlet.doPost(SoapServlet.java:61)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    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:78)
    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:78)
    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:78)
    at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: RfcException: [null]
      message: Name or password is incorrect (repeat logon) on DXI mshost strsap31
      Return code: RFC_SYS_EXCEPTION(3)
      error group: 103
      key: RFC_ERROR_LOGON_FAILURE
    at com.sap.conn.rfc.api.RfcApi.RfcOpen(RfcApi.java:219)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect(MiddlewareJavaRfc.java:1331)
    ... 87 more
    Caused by: RfcException: [DXI|strsap31]
      message: Name or password is incorrect (repeat logon)
      Return code: RFC_SYS_EXCEPTION(3)
      error group: 104
      key: RFC_ERROR_SYSTEM_FAILURE
    Exception raised by DXI|strsap31
    at com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcReceive(RfcIoOpenCntl.java:2034)
    at com.sap.conn.rfc.api.RfcApi.RfcOpen(RfcApi.java:187)
    ... 88 more
    Caused by: com.sap.conn.rfc.exceptions.RfcGetException: Name or password is incorrect (repeat logon)
    at com.sap.conn.rfc.engine.RfcImp.ab_rfcerror(RfcImp.java:1157)
    at com.sap.conn.rfc.engine.RfcGet.rfcget_run(RfcGet.java:131)
    at com.sap.conn.rfc.engine.RfcGet.ab_rfcget(RfcGet.java:23)
    at com.sap.conn.rfc.engine.RfcRcv.ab_rfcreceive(RfcRcv.java:33)
    at com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcReceive(RfcIoOpenCntl.java:1981)
    ... 89 more

    User id missing in client 000

  • 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

  • Publish of a Service over Service Registry -   com.sap.esi.uddi.sr.api.exce

    Hello
    I try to publish a Service over the Service Registry UI but this results in a  com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail message: java.lang.NullPointerException->java.lang.NullPointerException
    Is the problem the schema import or the two address locations ?
    We use ESR CE 7.1 SP3
    Kind regards
    Gerald Eder
    The WSDL looks like :
      <?xml version="1.0" encoding="utf-8" ?>
    - <wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://test.com/soa/" xmlns:i0="http://test.com/soa" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://test.com/soa/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
      <wsdl:import namespace="http://test.com/soa" location="http://pwwdev.test.com/Appl/Corp/Services/SOA/SOAServer/customerid.asmx?wsdl=wsdl1" />
    - <wsdl:types>
    - <s:schema targetNamespace="http://test.com/soa/">
      <s:import schemaLocation="http://pwwdev.test.com/Appl/Corp/Services/SOA/SOAServer/customerid.asmx?schema=schema1" namespace="http://test.com/soa" />
      </s:schema>
      </wsdl:types>
    - <wsdl:service name="CustomerID">
    - <wsdl:port name="CustomerIDBinding" binding="i0:CustomerIDBinding">
      <soap:address location="http://pwwdev.test.com/Appl/Corp/Services/SOA/SOAServer/customerid.asmx" />
      </wsdl:port>
    - <wsdl:port name="CustomerIDBinding1" binding="i0:CustomerIDBinding1">
      <soap12:address location="http://pwwdev.test.com/Appl/Corp/Services/SOA/SOAServer/customerid.asmx" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:de

    Hi Rajesh,
    Many thanks for your prompt reply, however this note 1267817 was already applied before posting message.
    B/W I have observed that in spite of the error the service published multiple times in the registry (perhaps each try to publish resulted a entry in SR).
    Really crazy error, any other suggestion??
    Regards, Immy.

  • Com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail messa

    Dear All,
    When we try to publish a Web Service using Service Registry, following error appears, even though my user has the roles UDDI_Admin and SERVICE_REGISTRY_READ_WRITE
    com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail message: com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.UDDIServerRemoteException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='DISPOSITION_REPORT_UDDI_SERVER', Arguments: ['http://host:port/uddi/api/inquiry/', 'http://host:port/uddi/api/publish/', 'Fatal: A serious technical error has occurred while processing the request. ']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en->com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.UDDIServerRemoteException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='DISPOSITION_REPORT_UDDI_SERVER', Arguments: ['http://host:port/uddi/api/inquiry/', 'http://host:port/uddi/api/publish/', 'Fatal: A serious technical error has occurred while processing the request. ']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en->com.sap.esi.uddi.server.proxy.depl.v3.DispositionReport
    Note: We have also configured the UDDI destination as described in sap help @ http://help.sap.com/saphelp_nwpi71/helpdata/en/45/c1ea61a1194432e10000000a155369/frameset.htm
    Thanks in Advance,
    Immy.

    Hi Rajesh,
    Many thanks for your prompt reply, however this note 1267817 was already applied before posting message.
    B/W I have observed that in spite of the error the service published multiple times in the registry (perhaps each try to publish resulted a entry in SR).
    Really crazy error, any other suggestion??
    Regards, Immy.

  • Adaptive RFC 2 gives error: com/sap/ide/jco/service/internal/R3Service

    Hi,
    I've run into the following problem about NWDS. This happens as I create a Model. It appears there is a new version of the Adaptive RFC Model, which is called Adaptive RFC 2 Model.
    1. Right click on Models, and select Create.
    2. Double Click on Adaptive RFC 2 Model
    3. The error pops up. It says "An error has occurred. See error log for more details. java.lang.NoClassDefFoundError". Then if you click details you get "An error has occurred. See error log for more details. com/sap/ide/jco/service/internal/R3Service "
    If you know which log to have a look, or what this error is about please let me know urgently. Any help if much appreciated.
    Thanks,
    Ogeday Isiklar

    Hi,
    I am also getting same problem. Waiting for solution
    Regards,
    Pradeep Kumar

Maybe you are looking for