Another SOAP Sender adapter "com.sap.aii.af.mp.module.ModuleException" erro

I am working on a synchronous scenario SOAP <-> XI <-> RFC.
This worked fine, when I run it without SOAP adapter, direct via XI Pipeline.
Now I want to use the SOAP sender adapter, but get the error as described below this post.
As this is a real new XI installation, some patches or updates might be required to make it work. Or some adapter modules ?
Any suggestions on how to solve this problem will be rewarded.
What worries me a bit is the line " " in the error description.
Extra info: I use SoapSonar as a test webservice client. The error is the message as received in te test client.
<?xml version="1.0"?>

<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>ModuleUnknownException</code>
 <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException: either no channelID specified or no channel found for the specified party, service, and channel name, MessageServlet(Version $Id: //tc/xi/645_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#9 $)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:427)
 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)
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>

Hi Chandravadhana,
The colon should be there :
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
The inbound address for SOAP messages is: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel
Regards
Suraj

Similar Messages

SAP R/3 - XI: Commit fault com.sap.aii.af.mp.module.ModuleException

Hi -
We have an integration setup between SAP R/3 4.7C and SAP XI -
It uses background queues - and in our development environment, on the call to XI, we are receiving the error message:
Commit fault com.sap.aii.af.mp.module.ModuleException: call to messaging
The queue then goes into SYSFAIL status.
This is occurring on all of our integrations between R/3 and XI - which has been previously working -
I have been working w/ our Basis guy & he said that all his checks to both systems look ok.
Do you have any pointers on what to look at or check out?
Your help is very appreciated!
Thanks,
Michelle

Hi Michelle,
Please check if the background Xi database to which your transactions are committed is full. In case it is, you would need Basis help to archive them, before you proceed. Please check your dump for the same.
cheers,
Prashanth
P.S Please mark helpful answers.

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

Issue with the String return from com.sap.aii.af.mp.module.ModuleData

Hi Friends,
We are developing Adapter for XI using java, XI is giving String in the form of ModuleData, we r getting the String from ModuleData but in the logic we need to split the String in parts based on character '', but I observed that in the communication channel symbol is showing as ' '.
We have written the java code based on '' but splitting is not working, then I tried with the following code
String[] molecules = null;
if(filedata.indexOf(" ") != -1){               molecules = filedata.split(" ");
}else if(filedata.indexOf("?") != -1){
                molecules = filedata.split("?");
}else if(filedata.indexOf("") != -1){
                molecules = filedata.split("");
Still it is not working, please help in case of ModuleData text splitting..
Thanks in advance.
Satinder Saini

Check with a hex editor, what the ' '. really is.
Maybe it is a tab? Then you can use "\t" in a Java progam.
See also here:
http://en.wikipedia.org/wiki/ASCII#ASCII_control_characters
Regards
Stefan
Edited by: Stefan Grube on Mar 26, 2008 2:22 PM

Invocation of SOAP Sender Adapter using Apache SOAP

Hi,
I'm trying to invoke the XI SOAP Sender Adapter using the Apache SOAP API. It seems that my message header is missing a few parameters (see exception below). Does anybody know which to set?
Regards,
Heiko
==========
Exception:
<?xml version='1.0'?>

<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>Exception</code>
 <text><![CDATA[
com.sap.aii.af.mp.module.ModuleException
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:502)
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:227)
 at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
 at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:162)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:507)
 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:392)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged1(Native Method)
 at java.security.AccessController.doPrivileged(AccessController.java:321)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Caused by: java.lang.Exception: Bubble configuration error: parameter 'XI.InterfaceNamespace' is missing
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.getParaRequired(XISOAPAdapterBean.java:895)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.createDefaultMessageHeader(XISOAPAdapterBean.java:942)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.setup(XISOAPAdapterBean.java:214)
 at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:496)
 ... 22 more
 ]]></text>
 </s:SystemError>
 </detail>
 </SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>

Hi Heiko,
You are missing the Namespace Parameter in the sender soap adapter configuration in XI3.0
Thanks
Prasad

Com.sap.aii.messaging.util.URI$MalformedURIException: invalid port number

Experts,
My scenario is sync File to SOAP.
I am using File - bpm - soap - bpm - file.
I am trying to send a query to google in file with SOAP message and expecting a response back.
But in SOAP Adapter I am getting this error.
com.sap.aii.messaging.util.URI$MalformedURIException: invalid port number
2008-04-05 07:49:31 Success Message successfully received by messaging system. Profile: XI URL: http://xibox:50000/MessagingSystem/receive/AFW/XI Credential (User): XIISUSER
2008-04-05 07:49:31 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
2008-04-05 07:49:31 Success Message successfully put into the queue.
2008-04-05 07:49:31 Success The message was successfully retrieved from the request queue.
2008-04-05 07:49:31 Success The message status set to DLNG.
2008-04-05 07:49:31 Success Delivering to channel: CC_SOAP_Google
2008-04-05 07:49:31 Success MP: entering
2008-04-05 07:49:31 Success MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
2008-04-05 07:49:31 Success SOAP: request message entering the adapter with user J2EE_GUEST
2008-04-05 07:49:31 Error SOAP: call failed: com.sap.aii.messaging.util.URI$MalformedURIException: invalid port number:
Could you pls tell me which piece I missed?
Regards,
AV.

I'm sending below SOAP message.
<?xml version='1.0' encoding='UTF-8'?>
<soap11:Envelope
 xmlns="urn:GoogleSearch"
 xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/">
<soap11:Body>
 <doGoogleSearch>
 
<key>1</key>
 <q>shrdlu winograd maclisp teletype</q>
 <start>0</start>
 <maxResults>10</maxResults>
 <filter>true</filter>
 <restrict></restrict>
 <safeSearch>false</safeSearch>
 <lr></lr>
 <ie>latin1</ie>
 <oe>latin1</oe>
 </doGoogleSearch>
</soap11:Body>
</soap11:Envelope>

SOAP Sender Adapter

i work with some sender SOAP adapter in my xi project.
After installing SP19 all Communication channell gets error when i send message:
the error (in adapter monitoring) is following :
2006-12-15 15:29:01 Error Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: INBOUND_BINDING_ERROR:
2006-12-15 15:29:01 Error SOAP: call failed: com.sap.aii.af.ra.ms.api.DeliveryException: INBOUND_BINDING_ERROR:
2006-12-15 15:29:01 Error SOAP: call failed: com.sap.aii.af.ra.ms.api.DeliveryException: INBOUND_BINDING_ERROR:
Any suggestion?
Alessandro p.
Message was edited by:
Alessandro Pederiva

Hi,
1) Check out the XI pipeline url in the SLD>Business System><your integration server> and it should be http://<XI server>:8xxx/sap/xi/engine/?type=entry
Here port should be http port.
2) Also make sure that, all the Sender Agreement, Receiver Agreement are active.. otherwise change it and activate
3) Check put that XIISUSER is not locked ...
4) Refresh the cache- Go to XI homepage(Intgertaion Builder)>Administration>Cache Overview and refresh the all caches.. Also do the CPACache Refresh..
5) Restrating the Adapter engine from the visual admin may help u.
Hope this helps,
Regards,
Moorthy

Error in Component monitering com.sap.aii.af.ra.ms.api.ConfigException:

Hi Experts,
In XI(Exchange Infrastructure) i am trying to test the scenario , that is from XI to R/3 via IDOC
using XI Runtime workbench Component Monetoring Adapter Engine and setting up all the parameters which are required but it is throwing the following error
Error while sending message: Error while sending message: com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=SAP_XAPP_POC_GPD;TS=SAPR3_DE1_130;AN=ID1020_PurchaseOrderAccept_OB;ANS=http://com.sap.xapps/poc/collaboration;
I cleared the ACH cache and also activated all the objects i checked the receiver agreement twice to confirm the parameters but then it is throwing the error pls help me in this .
Thanks a lot in Advance .
Kelli.

Resolved in thread: com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol ha

When i send a test message throw the RWB for Http receiver adapter it is giving the error "Error in processing caused by: com.sap.aii.adapter.http.api.HttpAdapterException: ERROR_SOCKET_TIMEOUT, Read timed out"

when i send a test message throw the RWB for Http receiver adapter it is giving the error "Error in processing caused by: com.sap.aii.adapter.http.api.HttpAdapterException: ERROR_SOCKET_TIMEOUT, Read timed out"

Hi, Michal
I have read your Weblog. It makes sense to me. Thanks a lot for your help! However, I still have some questions and listed them as following. Could you please help to answer them?
Q1: I am new to SAP-XI. So I have no idea about TCODE-SXMB_ADM. Could you introduce more details about it?
Q2: The XI system I am using is running on SAP-ICC's machine. The tools I can use are:
1.Builder for Integration Repository
2.Builder for Integration Configuration
3.System Landscape Directory
4.Runtime Workbench
5.Administration System (for Repository, Directory, Runtime)
Please note that I do not have a complete control on this SAP-XI. Do you think whether or not I can set the timeout parameter by following the instructions provided in your Weblog?
For more details about my SAP-XI, please access the following Web page:
http://iccxi.sap.com:58000/rep/support/admin/index.html
Q3: The following messages are extracted from the SAP-XI. Wish they are hepful to solving my problem.
2006-06-19 05:12:16 Success The message was successfully received by the messaging system. Profile: XI URL: http://iccxi.sap.com:58000/MessagingSystem/receive/AFW/XI
2006-06-19 05:12:16 Success Using connection AFW. Trying to put the message into the request queue.
2006-06-19 05:12:16 Success Message successfully put into the queue.
2006-06-19 05:12:16 Success The message was successfully retrieved from the request queue.
2006-06-19 05:12:16 Success The message status set to DLNG.
2006-06-19 05:12:16 Success Delivering to channel: ValidationRequestHandlerServiceChannel
2006-06-19 05:12:16 Success SOAP: request message entering the adapter
2006-06-19 05:12:37 Success SOAP: call failed
2006-06-19 05:12:37 Error SOAP: error occured: java.net.ConnectException: Connection timed out: connect
2006-06-19 05:12:37 Error Exception caught by adapter framework: Connection timed out: connect
Thanks
Menghua Li

SAP PI Soap Send adapter is not available.

Hi Experts：
i encounter a issue when use Soap sender adapter. i configured soap sender adapter senario and generate wsdl in the id .
and then import wsdl document to the soapui to test the webservice. but throw some exception blow:
<!see the documentation>
<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>java.lang.NullPointerException
+ at com.sap.aii.af.sdk.xi.mo.xmb.XMBMessageOperator.getQualityOfServiceAsString(XMBMessageOperator.java:2109)+
+ at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:943)+
+ at sun.reflect.GeneratedMethodAccessor1126.invoke(Unknown Source)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
+ at java.lang.reflect.Method.invoke(Method.java:585)+
+ at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)+
+ 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:71)+
+ 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:38)+
+ at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)+
+ 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:21)+
+ 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:16)+
+ 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:133)+
+ at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)+
+ at $Proxy3087.process(Unknown Source)+
+ at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275)+
+ at sun.reflect.GeneratedMethodAccessor518.invoke(Unknown Source)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
+ at java.lang.reflect.Method.invoke(Method.java:585)+
+ at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)+
+ 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:71)+
+ 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:38)+
+ at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)+
+ 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:21)+
+ 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:16)+
+ 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:133)+
+ at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)+
+ at $Proxy330.process(Unknown Source)+
+ at com.sap.aii.adapter.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:175)+
+ at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:470)+
+ at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)+
+ at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)+
+ at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)+
+ at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)+
+ at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124)+
+ at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)+
+ at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:441)+
+ at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)+
+ at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)+
+ at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)+
+ at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)+
+ at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
+ at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)+
+ at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
+ at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)+
+ at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)+
+ at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)+
+ 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.MemoryStatisticFilter.process(MemoryStatisticFilter.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.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)+
+ 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:457)+
+ at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)+
+ at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)+
+ at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)+
+ at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)</text>+
 </s:SystemError>
 </detail>
 </SOAP:Fault>
 </SOAP:Body>
</SOAP:Envelope>
nd the find a note :sapnote_0001239995 can solve the problem in the pi 7.10 .but my pi is 7.11 .anybody know which note should be apply to solve the problem in the pi7.11 .thanks .

hi,
Either you are using an incomplete URL
you can however try with this URL format:
http://<IPAddress OR ServerName>:<PORT_No>/XISOAPAdapter/MessageServlet?channel=:<SenderBusinessService>:<SenderSOAPCC>&version=3.0&Sender.Service=<SenderBusinessService>&Interface=<SenderInterfaceNamespace>%5E<SenderMI>
refer blog related ur issue:
ADAPTER.JAVA_EXCEPTION: Sender soap adapter PI 7.11
thanks,

Could not process due to error: com.sap.aii.adapter.file.ftp.FTPEx: 550

Hi Experts,
We have many File to EDI scenarios wherein XI System pick up the XML and sent to customers via EDI. Recently we faced a problem so created a Back-up System (Production copy) and tested successfully. After sometime the messages were routed to this back-up system and when we notice it and then stopped the back-up system. All the messages that were routed to back-up system, we try to send the same messages from the actually Production system to our customers. Now the problem is XI system (Production system) is unable to pick these files and I check the communication monitoring and encountered the below error message.
Could not process due to error: com.sap.aii.adapter.file.ftp.FTPEx: 550.550
Can anyone let me know how to fix the issue or what needs to be done?
Your help is highly appreciated.
Regards
Faisal

Hi,
It seems to be problem with permission of files. Please ask your basis to do following:
1. Set the permissions to FTP User you are using as 777 rights(full access to read , write and delete)
2.If you have access to PI server, try to telnet /connect to ftp using command prompt (open ftp .....) the FTP server form there, you should see the same error there , inform this to your network guys.
3.Clear all the files places already in the ftp (take backup) and test afresh after permissions are set by basis team.
Regards
Aashish Sinha

Com.sap.aii.adapter.file.ftp.FTPEx: 550

Hi,
I have the below error in my sender file channel. I also read the following thread
FTP Error
Error:
An error occurred while connecting to the FTP server '10.12.12.101:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 C:Inetpubftproot: The filename, directory name, or volume label syntax is incorrect. '. For details, contact your FTP server vendor.
The above thread suggests me to change the setting in the IIS. Should do that settings in the PI server or the source FTP server.
Also does anybody have any other solution to this problem.
Rgds,
Mithun

HI,
If you're using an FTP server you need to know the path to the file on the FTP.
To do this I suggest to connect to the FTP using Internet Explorer and navigating the FTP folders until reaching the right one.
Then on the url bar you should got something like this: "ftp://server:21/path/to/file/". Use "/path/to/file" as value for the file adapter configuration.
Please refer below blogs:
unable to send file to FTP server
FTP to Windows Server
thanks,

Could not process file 'Input 110110b.txt': com.sap.aii.adapter.file.

I have a FILE Adapter using FTP as a transport that is generating a very odd error.
The FTP sender channel is giving the following error is set up to retreive all files (*) from a specific directory. If you look at the error, it indicates an error processing the file 'Input 110110b.txt' as a file -- the only way this filename woudl be visible is if the adapater interrogated the directory, or the filename was hard-coded in the file mask. But the error indicates it can't change to the directory. The only way it would have come up with the file is if it had already CD'd t that directory.
1/7/11 8:12:01 AM   Retry interval started. Length: 60.0 seconds
1/7/11 8:12:01 AM   Could not process file 'Input 110110b.txt': com.sap.aii.adapter.file.ftp.FTPEx: 550 Failed to change directory.
1/7/11 8:12:00 AM   Processing started
My first thought was a simple permission issue, so I opened a connection to server with FileZilla (an FTP client) and was able to retrieve the file without a problem. I was also able to drop a file in the directory. There is no permissions problem.

Hi
Please check the below points before processing any file
a) check the File placing by a Local Plant FTP owner is using the same authentification credentials It means both PI and source team needs to use same FTP User ID and login credentials otherwise if suppose if source team is placing with one User and PI cannot able to pick that file as this User cannot have permissions in this case also u will get 550 error
b) I know what ur telling is u manualy palced one file and able retrive...but do one thing u can login with same PI FTP login server credentials and then place the file with different name also I suggest lets test the channel by simply keeping
. not simply * if you keep simply * then u cna use in receiver chanel while using dynamic connfiguration.
Else give *.txt and then activate the channel and also please check the CACHE as well
Regards
Amar Srinivas Eli

File to File-CC 'error com.sap.aii.adapter.file.ftp.FTPEx: 550 Access deni'

Hi friend,
I am doing file to file scenario in which i wan to move one file from input folder to output folder.
I had created as FTP on one system that i am able to access and have full authorization to read and write.
and created that two input and output folder in it,n kept an xml file in input folder.
When i see sender communication channel in RWB it is showing error, "com.sap.aii.adapter.file.ftp.FTPEx: 550 Access denied'
I checked password,it correct also I tried to test it using Anonymous Login, but the same things.
SO i am not sure where i had done mistake.
Plz give ur suggestions.
Thanks

Hi,
Please Check below few steps:
Check if the username and the Password is created to write the file in the desired directory.
Check the username is provided the authorization to write the file in the desired directory. ... IS Guys will help you..
Confirm if the directory created have all the authorization to write the file.
ls - lrt
chmod 777 Directory Name
all the authorization will then be provided
Confirm if the directory is created with the root id then it there might be some problem with the user name u r trying to create..
Hope this will help.
Assign points for helpful answer..
Thanks
JAY.

Com.sap.aii.adapter.file.ftp.FTPEx: 421

Hi Guys,
I am getting these two error messages:
1) com.sap.aii.adapter.file.ftp.FTPEx: 421 Maximum session time exceeded - closing
2) com.sap.aii.adapter.file.ftp.FTPEx: 421 Too many users - please try again later
when XI Sender File Adapter tries to pick the files from the FTP server.
I have not set any limit to the number of session for the user that I have mantianied in the adapter. (Niether I know it -:) how to set.)
Any idea or help, how to resove this error.
Thanks in adavance,
Namadev

Hi Namdev,
Your this error is coming as your FTP server maximum allowed connection is reached. so as the solution I would suggest to change the Connection mode property of your communication channel as Per File Transfer as default property is Permanently which reserves connection forever.
So other communication channels cannot communicate. Make this changes to all the communication channel you have configured.
And your problem is solved.
enjoy....
Thanks & Regards,
Gaurav Patwari

Another SOAP Sender adapter "com.sap.aii.af.mp.module.ModuleException" erro

Similar Messages

Maybe you are looking for