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.

Similar Messages

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

  • 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

  • Com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException in sap pi

    Hi all,
    I am working on SAP PI 7.3.1 SP09. Currently we have interfaces which uses 50200 port. I have created a http destination from nwa pointing to https://....url. So all of a sudden all the interfaces went to error state. After debugging i found that the port 50200 is replaced with 50201which is https port. After changing the port to initial value ie., 50200 all interfaces are working fine except the one which were pointing to https url and they are showing the following error description.
    <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SAP:Category>XIAdapterFramework</SAP:Category>  
    <SAP:Code area="MESSAGE">GENERAL</SAP:Code>  
    <SAP:P1 />  
    <SAP:P2 />  
    <SAP:P3 />  
    <SAP:P4 />  
    <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException</SAP:AdditionalText>  
    <SAP:Stack />  
    <SAP:Retry>M</SAP:Retry>  
    </SAP:Error>
    The entire trace is as follows:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--
    Inbound Message
    --> 
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"> 
    <Trace level="1" type="T">Party normalization: sender</Trace>  
    <Trace level="3" type="T">Sender scheme external =</Trace>  
    <Trace level="3" type="T">Sender agency external =</Trace>  
    <Trace level="3" type="T">Sender party external =</Trace>  
    <Trace level="3" type="T">Sender party normalized =</Trace>  
    <Trace level="1" type="T">Determining the sender agreement</Trace>  
    <Trace level="3" type="T">##### DG: 3</Trace>  
    <Trace level="3" type="T">##### TO: 3</Trace>  
    <Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>  
    <Trace level="2" type="T">Request Line = POST /sap/xi/engine/?type=entry HTTP/1.0</Trace>  
    <Trace level="2" type="T">Host = 10.66.14.150:50200</Trace>  
    <Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>  
    <Trace level="1" type="T">Remote address = 10.66.10.160</Trace>  
    <Trace level="1" type="T">User = SFUSER</Trace>  
    <Trace level="1" type="T">Process ID: 760</Trace>  
    <Trace level="1" type="T">Work Process ID: 10</Trace>  
    <Trace level="1" type="T">Message ID = 53BEFE7146893BD5E10000000A420AA0</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"> 
    <Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>  
    <Trace level="3" type="T">##### DG: 3</Trace>  
    <Trace level="3" type="T">##### TO: 3</Trace>  
    <Trace level="1" type="T">Hop engine name = is.02.devpipd1</Trace>  
    <Trace level="1" type="T">Hop engine type = IS</Trace>  
    <Trace level="1" type="T">Hop adapter name = XI</Trace>  
    <Trace level="1" type="T">Hop adapter namespace = http://sap.com/xi/XI/System</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV"> 
    <Trace level="3" type="T">No triggers found. OK.</Trace>  
    </Trace>
    <Trace level="3" type="T">system-ID = PD1</Trace>  
    <Trace level="3" type="T">client = 001</Trace>  
    <Trace level="3" type="T">language = E</Trace>  
    <Trace level="3" type="T">user = SFUSER</Trace>  
    <Trace level="1" type="Timestamp">2014-07-10T08:56:37Z INDIA</Trace>  
    <Trace level="1" type="T">ACL Check is performed</Trace>  
    <Trace level="1" type="T">XML validation is executed</Trace>  
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />  
    - <!-- ************************************
    -->   
    <Trace level="1" type="T">PLNAME = CENTRAL</Trace>  
    <Trace level="1" type="T">QOS = BE</Trace>  
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />  
    - <!-- ************************************
    -->   
    <Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>  
    <Trace level="3" type="T">Pipeline-Elements for pipeline SAP_CENTRAL</Trace>  
    <Trace level="3" type="T">0001 PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    <Trace level="3" type="T">0002 PLSRV_RECEIVER_DETERMINATION</Trace>  
    <Trace level="3" type="T">0003 PLSRV_INTERFACE_DETERMINATION</Trace>  
    <Trace level="3" type="T">0004 PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>  
    <Trace level="3" type="T">0005 PLSRV_MAPPING_REQUEST</Trace>  
    <Trace level="3" type="T">0006 PLSRV_OUTBOUND_BINDING</Trace>  
    <Trace level="3" type="T">0007 PLSRV_VIRUS_SCAN_RQ_OUT</Trace>  
    <Trace level="3" type="T">0008 PLSRV_XML_VALIDATION_RQ_OUT</Trace>  
    <Trace level="3" type="T">0009 PLSRV_CALL_ADAPTER</Trace>  
    <Trace level="3" type="T">0010 PLSRV_VIRUS_SCAN_RS_INB</Trace>  
    <Trace level="3" type="T">0011 PLSRV_XML_VALIDATION_RS_INB</Trace>  
    <Trace level="3" type="T">0012 PLSRV_MAPPING_RESPONSE</Trace>  
    <Trace level="3" type="T">0013 PLSRV_VIRUS_SCAN_RS_OUT</Trace>  
    <Trace level="3" type="T">0014 PLSRV_XML_VALIDATION_RS_OUT</Trace>  
    <Trace level="3" type="T">system-ID = PD1</Trace>  
    <Trace level="3" type="T">client = 001</Trace>  
    <Trace level="3" type="T">language = E</Trace>  
    <Trace level="3" type="T">user = SFUSER</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST"> 
    <Trace level="2" type="T">Persisting original message</Trace>  
    <Trace level="3" type="T">Message-Version = 000</Trace>  
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>  
    </Trace>
    <Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Begin of pipeline processing PLSRVID = CENTRAL</Trace>  
    - <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB"> 
    <Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"> 
    <Trace level="3" type="T">Calling pipeline service: PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>  
    <Trace level="3" type="T">PLSRVTYPE =</Trace>  
    <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>  
    <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_VALIDATION</Trace>  
    <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>  
    <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>  
    <Trace level="3" type="T" />  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"> 
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV"> 
    <Trace level="3" type="T">Pipeline Service = PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    <Trace level="3" type="T">Skip Inbound Validation =</Trace>  
    <Trace level="3" type="T">Skip Outbound Validation =</Trace>  
    <Trace level="3" type="T">Area = XML_VALIDATION_INB</Trace>  
    <Trace level="1" type="T">Reading sender agreement</Trace>  
    <Trace level="1" type="T">Message does not contain a sender agreement</Trace>  
    <Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>  
    </Trace>
    </Trace>
    </Trace>
    <Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA End of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>  
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST"> 
    <Trace level="3" type="T">Persisting message after plsrv call</Trace>  
    <Trace level="3" type="T">Message-Version = 001</Trace>  
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>  
    </Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION"> 
    <Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"> 
    <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>  
    <Trace level="3" type="T

    HI,
    Thank you for your hint. Maybe I just forgot to mention one important fact. We have second SAP Netweaver PI 7.1 which is completely our system. The first one I mentioned in first message is the customer's one. The one we have extra is also connected to MAXIMO and GIS. Settings of this interface is completely same among one thing:
    Patch level of XIAF:
    1. customers SAP PI level is
    Adapter Common Library Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:29:47+0000)
    Adapter Application Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:30:00+0000)
    2. our SAP PI level is
    Adapter Common Library Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:21+0000)
    Adapter Application Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:31+0000)
    Both of them has Axis Version: Apache Axis version: 1.4 Built on Apr 22, 2006 (06:55:48 PDT)
    Also important to mention is fact that same problem happened in our SAP PI, but we implemented last patch of XIAF and it has suddenly started to work. I have suspicion it is somehow connected to this patch. Btw. this patch contains a lot of notes regarding  AXIS framework (i.e. 1435998, 1150375, 1048268), so obviously some bugs of the AXIS adapter has been resolved by this patch.
    What do you think ?
    Thanks

  • Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found

    In my 2006 biztalk application I have exposed web service to receive SAP input. It was working fine. After I have modified something in orchestration in that application . I am getting following error while SAP try to consume my web service. Can anyone please
    help me.
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found

    In my 2006 biztalk application I have exposed web service to receive SAP input. It was working fine. After I have modified something in orchestration in that application . I am getting following error while SAP try to consume my web service.
    HI Arivazhagan K,
    Could you give some explanation about what you modified? according the to error message, this is "resource is not found issue".
    Best regards,
    Angie
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • SOAP Sender Error - com.sap.engine.interfaces.messaging.api.exception

    Hi,
    I am testing a SOAP Sender Channel using a SOAP Client and getting the following error. I have read almost all the posts related to errors in SOAP Channel and also have checked my URL which is correct. AS mentioned in many of the posts, my url goes like
    https://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:DEMO:SOAP_s_GETLIST&version=3.0&SenderService=DEMO&interface=si_os_GETLIST&interfaceNamespace=<namespace>
    This is the error that I get when sending a message to the interface
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP:Body>
          <SOAP:Fault>
             <faultcode>SOAP:Server</faultcode>
             <faultstring>Server Error</faultstring>
             <detail>
                <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                   <context>XIAdapter</context>
                   <code>ADAPTER.JAVA_EXCEPTION</code>
    <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIProxy:PARSE_APPLICATION_DATA:
         at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)
         at sun.reflect.GeneratedMethodAccessor1044_10001.invoke(Unknown Source)*
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
                </s:SystemError>
             </detail>
          </SOAP:Fault>
       </SOAP:Body>
    </SOAP:Envelope>
    Has Anybody got this problem before? Is it any problem with the SOAP Adapter itself or with the data that is going in the message? If so, What is the possible solution for this?
    Thanks,
    Rashmi.

    Hi Rashmi,
    I also think your problem is data related.
    Check the response in your SAP PI message monitor (SXMB_MONI) when you trigger a request using SoapUI. It sometimes provides a bit more detail. You design (data types, message types, service interfaces etc.) was done in SAP PI 7 then an Abap Proxy was generated from the service interface?
    Sometimes there is an issue between the XSD data type declaration in SAP PI and the conversion to Abap data types that takes place when a proxy is generated from a PI Service Interface.
    Check the data that you pass in your request, especially those like datetime fields. Maybe even change some of the data type definitions (like datetime) to a string (request & response) & then test through SoapUI & see if you still get the error. Then you can work out how to best resolve it.
    Best Regards, Trevor

  • Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all

    Hello,
    I have an issue configuring a simple File Adapter Content Conversion, it will be great to give me some support as I'am new in the PO Environment.
    Iam reading a flat file and trying to write into an XML in the same FTP server
    I have a 1 to 1 Mapping as follows
    And my Content Conversion at Sender side Looks like this
    After running the configuration Iam getting following error message
    Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all
    My System is the SAP Netweaver Process Intgration 7.4 single Java stack
    Do you have any idea how to fix this issue?
    Many thanks in advance
    Khadim

    Hi evrybody
    I have enabled the tracing of ICO and have seen that my payload for the message mapping is ok,.
    <ns:hartgeldbest_ERP_KT xmlns:ns="http://xxxxxx.de">
    <Recordset>      
    <header> 
         <gesellschaft>03</gesellschaft> 
         <filiale>000</filiale>
         <satzart>11</satzart>
         <datum>00000000</datum>
         <kennzeichen>1</kennzeichen>
    </header>
    </Recordset>
    </ns:hartgeldbest_ERP_KT>
    The issue is on detrmining the RECEIVER in the Main-XML
    <sap:Main xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3"versionMinor="1" SOAP:mustUnderstand="1">
    <sap:MessageClass>ApplicationMessage</sap:MessageClass> 
    <sap:ProcessingMode>asynchronous</sap:ProcessingMode>
    <sap:MessageId>ae41678e-da87-11e3-cd0f-0000006831a2</sap:MessageId>
    <sap:TimeSent>2014-05-13T10:16:43Z</sap:TimeSent>
    <sap:Sender> 
    <sap:Party agency="http://sap.com/xi/XI" scheme="XIParty"/> 
    <sap:Service>CC_Hartgeldbest_File2Idoc</sap:Service>
    </sap:Sender>
    <sap:Receiver> 
    <sap:Party agency="" scheme=""/> 
    <sap:Service/>
    </sap:Receiver>
    <sap:Interface namespace="http://xxxxx.de">hartgeldbest_KT_async_out</sap:Interface>
    </sap:Main>
    Is it possible that the receiver is overwritten due to the Content Conversion? Because if I set my Message Protocol to "File" the receiver determination will work.
    Any idea?
    Thx
    Khadim

  • Transport Fail -com.sap.aii.utilxi.misc.api.ResourceException:Import

    Hi Experts,
    My Transports through Solution Manager is failing in Production PI. Transports are imported, deployed successfully in Test and Regression environments and working fine. Transport requests are of type Workbench and we are attaching '.tpz' files as Non abap objects. All contain ESR objects, no ID components. Import and Check version steps are good but failing at Deployment step in Production PI.
    Please find the log which I can see in SE10. All the transports failed with the same below error description.
    CTS Import Service - Version 0.94 04.04.2008
    ==============================================================
    Deploy Web service destination = CTSDEPLOY
    Directory = /usr/sap/trans/data
    SDM Deploy URL =
    SLD Deploy URL =
    XI Deploy URL = http://ABC2159161:50000
    Start import with id:4E8B872CA9F100F2E10080000A32109F
    DeployProxy (patch level:0) called with followingparameters:
    Deployable(0)
    Deployable-Type:1
    Deployable-Id:4E6E38F506B601AAE10080000A321063
    Deployable-TransportContainerId:DI1K900677
    Deployable-ContentLocator:/usr/sap/trans/data/DI1K900677/XI7_1
    >>>63.tpz
    Property(0)
    Property-key:TARGETSYSTEMID Property-value:PI1
    Begin CommunicationData-Type[0]:1
    CommunicationData-Address:http://ABC2159161:50000/rep
    CommunicationData-Host:ABC2159161
    CommunicationData-Port:50000
    CommunicationData-User:'filled'
    CommunicationData-Password:'filled'
    Importing archive:XI7_1_A_SAPPI_CM_1.0_of_ABC.com-objs_6
    com.sap.aii.ibtransportclient.XiTransportException: caused by:
    >>>rt failed: Internal error when importing object [Lcom.sap.a
    >>>aused by: com.sap.aii.utilxi.misc.api.ResourceException: Im
    >>>g object [Lcom.sap.aii.ib.bom.workspace.IWorkspace;@7ffc92d
    >>>ethodFault: caused by: ClientServerException exception:Impo
    >>>object [Lcom.sap.aii.ib.bom.workspace.IWorkspace;@7ffc92d c
    >>>sourceException: Import failed: Internal error when importi
    >>>IWorkspace;@7ffc92d
    End CommunicationData-Type[0]:1
    End import with returncode:'8'
    Deployment
    End date and time : 20111009003401
    Ended with return code:  ===> 8 <===
    Thanks,
    Nabendu.

    Hi,
    I have already informed Basis about these. But do we have any way to check the exact reason for this failure?
    All the above points can ensure the successful transport to Production or not, I am not sure.
    Thanks,
    Nabendu.

  • ERROR- com.sap.aii.utilxi.misc.api.BaseRuntimeException

    Hi All,
    In mapping i used udf's.  while testing the mapping i got runtime exception error as the following.i have refresh "SXI_CACHE" adn also executed the report  "SAI_REFRESH_CACHE" but i am facing same problem. i used "DateTimeFormat" udf in this mappping. Please help me to solve this.
    15:04:29 Start of test
    Compilation of MM_EAST successful Method DateTimeFormat1$ with 2 arguments not found in class com.sap.xi.tf._MM_EAST_ com.sap.aii.utilxi.misc.api.BaseRuntimeException: Method DateTimeFormat1$ with 2 arguments not found in class com.sap.xi.tf._MM_EAST_ at com.sap.aii.mappingtool.tf3.AMappingProgram.getMethod(AMappingProgram.java:437) at com.sap.xi.tf._MM_EAST_.getMethod(_MM_EAST_.java:574) at com.sap.xi.tf._MM_EAST_.__CreateStructures(_MM_EAST_.java:247) at com.sap.aii.mappingtool.tf3.AMappingProgram.preStart(AMappingProgram.java:171) at com.sap.xi.tf._MM_EAST_.preStart(_MM_EAST_.java:583) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:332) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInternal(ServerMapService.java:431) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:169) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.execute(MapServiceBean.java:52) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.execute(MapServiceRemoteObjectImpl0.java:259) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:146) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122) 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)  Method DateTimeFormat1$ with 2 arguments not found in class com.sap.xi.tf._MM_EAST_
    15:04:33 End of test
    regards
    Peera

    Hi Anand,
    while testing the mapping in test tab i got this error. and also i came back to design tab adn check the queue that time i got same error adn also it is not showing the queue.
    actually my scenario is RFC to file. in this, for one mapping condition i used DateTimeFormat    udf  .  i explained for what purpose i am using this udf.
    in rfc i have a field through which Date adn time values are passed. First this udf get date vaule adn wait for time value after getting time value the udf do concat with both values adn then send to target field in format yyyy-MM-ddTHH:mm:ss.
    i am giving javacode for DateTimeFormat adn classes which we are used for java code
    import java.awt.Container;
    import java.awt.TextComponent;
    import java.awt.TextField;
    import java.io.*;
    public String dateTimeFormat(String a,String b,Container container)
                String dateTimeString = "";
                if (a.length() == 8 && b.length() == 6)
                      //Substrings for extracting date
                        String year = "";
                        String mon  = "";
                        String day  = "";
                        //Substrings for extracting time
                        String hour = "";
                        String min  = "";
                        String sec  = "";
                      //Extracting date into year , month and day
                        year = a.substring(0,4);
                        mon  = a.substring(4,6);
                        day  = a.substring(6,8);
                      //Extracting time into hour , minute and second
                        hour = b.substring(0, 2);
                        min  = b.substring(2, 4);
                        sec  = b.substring(4, 6);
                      //Now constructing final date time string
                        dateTimeString = year"-"mon"-"day"T"hour"-"min"-"sec;
                return dateTimeString;
    Thanks adn regards
    Peera

  • Mapping Error: com.sap.aii.utilxi.misc.api.BaseRuntimeException

    Hi All,
    I am workign on a scenario, where i am getting dtaa from SQL server using sender JDBC adapter.
    I need to pass this data into a Z-RFC to update a ztable.
    While executing the scenario, the messages are populatingin SXMB_MONI with the following error and Red Flag.
    com.sap.aii.utilxi.misc.api.BaseRuntimeException
    thrown during application mapping
    com/sap/xi/tf/_pavan_mm_: RuntimeException in
    Message-Mapping transformatio~
    I have tested Message Mapping in Repository. Its working fine.
    But when i copy the payload from SXMB_MONI and paste the same payload in Message Mapping (Repository), the system is showing following Error.....
    Details
    java.lang.NullPointerException
    STACKTRACE:
    com.sap.aii.ib.core.mapping.exec.ExecuteException: java.lang.NullPointerException
        at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInternal(ServerMapService.java:477)
        at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:169)
        at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.execute(MapServiceBean.java:52)
        at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.execute(MapServiceRemoteObjectImpl0.java:301)
        at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:146)
        at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
        at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
        at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
        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)
    java.lang.NullPointerException
    STACKTRACE:
    java.lang.NullPointerException
        at com.sap.aii.mappingtool.tf3.AMappingProgram.exceptionCaught$(AMappingProgram.java:59)
        at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:182)
        at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:149)
        at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102)
        at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInternal(ServerMapService.java:431)
        at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:169)
        at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.execute(MapServiceBean.java:52)
        at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.execute(MapServiceRemoteObjectImpl0.java:301)
        at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:146)
        at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
        at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
        at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
        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)
    I have tested the Configuration in Integration Directory with the payload from SXMB_MONI... The error is same as above mentioned.
    In message mapping, the source message type is a data type similar to the selected fields from sql server.
    The target message type is the imported RFC.
    The RFC is working fine, when i enter the data manually in R/3.
    I am unable to trace out the error behind this kind of situation....
    Can any one guide me in this regard...??
    Regards
    Pavan

    The payload got from Message Mapping....
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:SENDER_MT xmlns:ns0="http:
    infotech-enterprises">
      <zkunnr>AB10</zkunnr>
      <zname1>PRATT</zname1>
      <zstras>412,DALAL STREET</zstras>
      <zadrnr>BGLR,FDFDFDF</zadrnr>
      <ztelf1>434343434</ztelf1>
    </ns0:SENDER_MT>
    The Payload got from SXMB_MONI as follows...
      <?xml version="1.0" encoding="utf-8" ?>
    - <ROW>
    - <row>
      <zkunnr>AB10</zkunnr>
      <zname1>PRATT</zname1>
      <zstras>412,DALAL STREET</zstras>
      <zadrnr>BGLR,FDFDFDF</zadrnr>
      <ztelf1>434343434</ztelf1>
      </row>
    If i paste the payload from sxmb_moni into message mapping, i am getting following error...
    java.lang.NullPointerException
    If i paste the payload from sxmb_moni into Tools--->Test Configuration in Integration Directory, the following errro occurs in Interface Mapping.
    java.lang.NullPointerException thrown during application mapping
    Any idea what need to be done to resolve this error?
    Regards
    Pavan

  • Where to find 'com.sap.tc.webdynpro.repository.api' file in EP server

    Hi All,
    I am getting below exception while deploying a custom component in sand-box server.
    Failed to deploy application freescale.com/c_uwl for deployment state listener com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.
    [EXCEPTION]
    com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to deploy the file '/usr/sap/RIA/JC30/j2ee/cluster/server0/./temp/webdynpro/public/freescale.com/c_uwl/webdynpro/ComponentInterfaces/com.sap.netweaver.bc.uwl.ui.UWLCustomDetail/UWLCustomDetail.xml' into the database. Reason: Development Object 'sap.com/tckmcbc.uwl.ui~wd_ui' contains already same repository content. Hint: fully qualified name of the repository VMO must be globally unique.
            at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.checkVMOsExistInOtherDC(RepositoryUpdateManager.java:504)
            at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.deployRepositoryContent(RepositoryUpdateManager.java:98)
            at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:232)
    It seems it is using checkVMOsExistInOtherDC method from RepositoryUpdateManager.java file.
    I want to remove this method from that java file.
    Can any one please tell me at which location in server i can find that RepositoryUpdateManager.java file.
    Or from where i can find 'com.sap.tc.webdynpro.repository.api'  file, so that i can trace that jave file.
    Regards,
    Sambaran Chakraborty

    Jiandong,
    Add the required jar webdynprobasesvrc.jar file from follwoing path and check if the imports are added correctly.
    C:\Program Files\SAP\IDE\CE\eclipse\plugins\com.sap.tc_.wd_.basesrvc_1.0.0.071030103936\lib
    Chintan

  • RuntimeException in Message-Mapping (com.sap.aii.utilxi.misc.api.BaseRunti)

    HI,
    We are facing a very strange problem , during runtime we are facing the below mapping problem ,
    <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
    <SAP:P1>com/sap/xi/tf/_MM_FILE_TO_IDOC_P~</S P:P1>
    <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
    <SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
    But when we have downloaded the XML from SXMB_MONI and tested the mapping it works fine , only in the run time we are facing this problem , funny part is the same scenario worked fine yester day itself (end-to-end).
    <b>Note</b>: <b>Chche is uptodate.
             Mapped all mandatory fields</b>
    Regards,
    Vijaya

    Hi
    please chech whether the data in the input file is according to the format or not.
    for this you go to sxmb_moni,take the input payload from the moni and test with that payload and you will come to lnow where is the error.
    if you still have the problem please relly me back
    Thanks
    Rinku

  • How to use the com.sap.tc.webdynpro.progmodel.api.IWDView?

    hi,
       In every view, the "com.sap.tc.webdynpro.progmodel.api.IWDView view" is the parameter of the mothed wdDoModifyView(). I wonder, if we can make type com.sap.tc.webdynpro.progmodel.api.IWDView parameter in other methods which are designed by ourself. Thank you!

    Hi Daniel,
    This method wdDoModifyView will be raised every time the view is changed or refreshed (i.e. button pressed, drop down selected). This should cover all cases where you need IWDView, personally I can't think of another case where you need this parameter.
    As far as I know it is not possible but even if it is it's not recommended.
    But perhaps I'm wrong, I'll be happy to hear more opinions from more experienced SDNers...
    Roy

  • File to RFC Error com.sap.engine.interfaces.messaging.api.exception.Messagi

    Hi ,
    I am doing File to RFC  Scenario.
    My file get picked and I able to view the audit log under RWB message monitoring.
    Here I am getting the error
    u201CTransmitting the message to endpoint dest://XI_INTEGRATION_SERVER using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message using HTTPTransmitter. Reason: java.net.MalformedURLException: unknown protocol: dest.
    Can any one tell me what is the  reason.
    Regards, Navneet

    Hi Prakasu,
    I am using PI 7.1 version .
    When I opened SMICM there I am finding the HTTP Port as 52000.and the BS at SLD are also using the same Port in URL..
    And when i verified with the Basis they confirmed that Exchange profile is set correctly.
    But My file adapter is still not able to send the data to IS.
    Than I configured a scenario file to file without IR object and in this case data is coming to IS and it is succesfull also.
    what is the reason that in this case file adapter not able to push the data to IS.
    I used File adapter with NFS protocol.
    regards,
    navneet

  • Integrated Configurations com.sap.engine.interfaces.messaging.api.exception

    Hi guys,
    we are using PI 7.11.
    With this release local processing on the advanced adapter engine is possible, when using integrated configurations.
    This works fine.
    Lately I faced an error situation in an RFC to JDBC scenario, when one field doesn´t meet the conditions of the database.
    I tried to dig deeper to identify the incorrect value by switch on the trace in the receiver JDBC channel, as I did several times before.
    Afterwards I treied to restart the message.
    Following error occurs.
    com.sap.engine.interfaces.messaging.api.exception.ConfigException: Unable to retrieve interface determination with object ID ab1bf720bf2711dea7d2020000000030 from CPA cache.
    I made some test with integrated configurations (FTP to FTP) and come to the result that errors, which require changes on the communication channel e.g. wrong password etc. result in an new object in the CPA cache
    trying restart the failed message ends up in the error specified aboce.
    Anyone faced the same issue already?
    Kind regards
    Jochen

    HI Jochen,
    I feel that you should once go for a CPA Cache refresh from Adapter Engine and try executing your failed messages once again in the adapter engine.
    To do a CPA Cache Refresh from the Adapter Engine:
    To trigger a cache refresh from the individual Adapter Framework, open a browser window and enter the following URL:
    http://<host>:<port>/CPACache/refresh?mode=delta|full
    The Monitoring url is like this:
    http://<host>:<port>/CPACache
    Check this How-to Guide on Cache, it will be useful:
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34&overridelayout=true
    Thanks
    Dhwani

Maybe you are looking for

  • OLE2_OBJECT AND DOCUMENT MANAGEMENT SYSTEM (DMS)

    Hi Experts. I'm trying to make a excel inform like a catalog with materials and images which are in a Document Management System. I'm using OLE2_OBJECT to make the inform in EXCEL, because I'm trying to do it with SMARTFORMS, and I cannot because I n

  • Adobe Reader XI Help

    So I have Adobe Reader installed on my laptop. When I try to open a PDF on Chrome it gives me a message saying that it is out of date. I go to the Adobe website to update it, everything runs great, but still can't open my PDF files. So I wanted to un

  • ERROR:-22905:ORA-22905: cannot access rows from a non-nested table item

    Hi. I have some code running on oracle 9i that gives me above error. Following are my type declarations. drop type_obj_tea_icore_glr; drop type_tbl_tea_icore_glr; create or replace type type_obj_tea_icore_glr as object ( ns_comp_id_parent number, ns_

  • Store an XMPPConnection (Smack chat library obj) in a session

    Hello all, I am attempting to develop a web based chat client (I have already seen jwchat and some others) using the open source Smack libraries. I want a way to maintain the XMPPConnection object in the session. Below is some code I am using: //here

  • Truncated filename when deploying

    I am using TestStand 4.2.1.  I am working on my second test sequence and am seeing something that I did not see on the previous test I did.   I get all the folders organized the way I want in the View Destination screen then Build it.  After it compl