Invalid http response: null - Error in SOAP sync receiver

Hi,
We are getting the following error in synchronous SOAP receiver connection.
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid http response: null
note: This inteface is working fine without error in the subsequent run.
Anyone please help me out in this...
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<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.io.IOException: invalid http response: null</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Hi Rajendra,
The same issue I am also facing in production system.
In my case the all the requests are failing after an IIS7.5 upgrade of the Application in production.
The strange thing is that except SAP rest all the applications are able to submit requests and getting proper response also.
We are using a https communication and private key certificate authentication in SAP PI.
Does it look like a PI issue or IIS upgrade is causing some issue.
Please suggest.
Thanks,
Ashish

Similar Messages

Invalid http response: null

Olá Masters,
Estou com esse erro abaixo, alguém pode me ajudar?
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid http response: null</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Este é o meu XML com erro:
<NFe xmlns="http://www.portalfiscal.inf.br/nfe">
     <infNFe versao="2.00" Id="NFe52110403485572000104550010000000611621476378">
          <ide>
               <cUF>52</cUF>
               <cNF>62147637</cNF>
               <natOp>Venda producao do estabelecimento /</natOp>
               <indPag>0</indPag>
               <mod>55</mod>
               <serie>1</serie>
               <nNF>61</nNF>
               <dEmi>2011-04-01</dEmi>
               <tpNF>1</tpNF>
               <cMunFG>5201108</cMunFG>
               <tpImp>1</tpImp>
               <tpEmis>1</tpEmis>
               <cDV>8</cDV>
               <tpAmb>2</tpAmb>
               <finNFe></finNFe>
               <procEmi>0</procEmi>
               <verProc>SAP NFE 2.0</verProc>
          </ide>
          <emit>
               <CNPJ>03485572000104</CNPJ>
               <xNome>GEOLAB INDUSTRIA FARMACEUTICA S/A MATRIZ</xNome>
               <enderEmit>
                    <xLgr>V PRINCIPAL 1-B</xLgr>
                    <nro>S/N</nro>
                    <xBairro>DAIA</xBairro>
                    <cMun>5201108</cMun>
                    <xMun>ANAPOLIS</xMun>
                    <UF>GO</UF>
                    <CEP>75132085</CEP>
                    <xPais>Brasil</xPais>
                    <fone>06240154000</fone>
               </enderEmit>
               <IE>103233270</IE>
               <IM>46305</IM>
               <CNAE>1234567</CNAE>
               <CRT>3</CRT>
          </emit>
          <dest>
               <CNPJ>00011976000160</CNPJ>
               <xNome>DROGARIA MAIS FORMOSA LTDA ME</xNome>
               <enderDest>
                    <xLgr>AV ANHANGUERA</xLgr>
                    <nro>33</nro>
                    <xBairro>CENTRO</xBairro>
                    <cMun>5208707</cMun>
                    <xMun>GOIANIA</xMun>
                    <UF>GO</UF>
                    <xPais>Brasil</xPais>
                    <fone>6932276622</fone>
               </enderDest>
               <IE>116476543112</IE>
          </dest>
          <det nItem="1">
               <prod>
                    <cProd>000000000000500134</cProd>
                    <cEAN>7899095201347</cEAN>
                    <xProd>POLTAX D 50MG CX C/ 20COMP DISP</xProd>
                    <NCM>30049037</NCM>
                    <CFOP>5101</CFOP>
                    <uCom>UN</uCom>
                    <qCom>1.0000</qCom>
                    <vUnCom>50.0000000000</vUnCom>
                    <vProd>50.00</vProd>
                    <cEANTrib></cEANTrib>
                    <uTrib>UN</uTrib>
                    <qTrib>1.0000</qTrib>
                    <vUnTrib>50.0000000000</vUnTrib>
                    <indTot>1</indTot>
               </prod>
               <imposto>
                    <ICMS>
                         <ICMS00>
                              <orig>0</orig>
                              <CST>00</CST>
                              <modBC>3</modBC>
                              <vBC>50.00</vBC>
                              <pICMS>17.00</pICMS>
                              <vICMS>8.50</vICMS>
                         </ICMS00>
                    </ICMS>
                    <IPI>
                         <cEnq>999</cEnq>
                         <IPINT>
                              <CST>01</CST>
                         </IPINT>
                    </IPI>
                    <PIS>
                         <PISNT>
                              <CST>07</CST>
                         </PISNT>
                    </PIS>
                    <COFINS>
                         <COFINSNT>
                              <CST>07</CST>
                         </COFINSNT>
                    </COFINS>
               </imposto>
               <infAdProd>+</infAdProd>
          </det>
          <total>
               <ICMSTot>
                    <vBC>50.00</vBC>
                    <vICMS>8.50</vICMS>
                    <vBCST>0.00</vBCST>
                    <vST>0.00</vST>
                    <vProd>50.00</vProd>
                    <vFrete>0.00</vFrete>
                    <vSeg>0.00</vSeg>
                    <vDesc>0.00</vDesc>
                    <vII>0.00</vII>
                    <vIPI>0.00</vIPI>
                    <vPIS>0.00</vPIS>
                    <vCOFINS>0.00</vCOFINS>
                    <vOutro>0.00</vOutro>
                    <vNF>50.00</vNF>
               </ICMSTot>
          </total>
          <transp>
               <modFrete>1</modFrete>
          </transp>
     </infNFe>
</NFe>
Edited by: Henrique Pinto on Apr 1, 2011 12:10 PM EDITADO pra remover assinatura e formatar XML

Error in SOAP receiver channel: java.io.IOException: invalid http response:

Hi experts,
I have a IDOC to SOAP scenario where SOAP receiver channel is sending data to web service. In the receiver channel I am getting error as below. Kindly help me to resolve this issue. Thanks.
"Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid http response: null"

Did you check this?
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
Regards
Pothana

Error with Proxy - Soap sync scenario - "invalid http response:HTTP/1.1 5"

Hello,
I'm working on a PI scenario as displayed below:
Proxy <-> ECC <-> Soap
I've already imported the WSDL provided by 3th party and mapped one of the actions of the interface.
In the PI configuration I`d created the Scenario, using a Soap Receiver communication channel, passing only the URL and the action (no more options used).
When I`m trying testing using SPROXY or Runtime Workbench, the error bellow is displayed, and no receive message is created:
"com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid http response: HTTP/1.1 5"
Someone knows the error cause?
Thanks,
Ana Paula Lavieri

Hello,
"com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid http response: HTTP/1.1 5"
HTTP 1.1 is not natively supported by standard SOAP or Plain HTTP Adapter, you should use SOAP Axis for that. See SAP Note 1039369 - FAQ XI Axis Adapter, under Receiver Adapter General -> 16. Can I use HTTP 1.1? Otherwise, you would have to ask the third-party to use HTTP 1.0 instead.
Hope this helps,
Mark

Message processing failed: Invalid http response: 220

Hi Experts,
I am working on FILE to SOAP scenerio. File is coming in XI properly. But in the SOAP CC its showing this error.
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: invalid http response: 220 (Name of the Interanet of the Company) Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at Thu, 23 Oct 2008 12:02:22 +0530 : java.io.IOException: invalid http response: 220 (Name of the Interanet of the Company) Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at Thu, 23 Oct 2008 12:02:22 +0530
Any ideas ?
-=Soniy

Hi Sonia,
Please go throgh the following links for use ofr XML SPY
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7ccd3e4e-0501-0010-95ae-afa58cb46b75
Re: Stand alone testing using XML Spy
WSDL frm Altova xml spy
Invoke Webservices using SAPXI
Testing XI exposed Web-Services
Regards
Sridhar Goli

Invalid http response: HTTP/1.1 200

Hi gurus!
I have a problem with an asynchronous interface.
We are calling a Webservice which we don't need any response. In sxmb_moni it's OK, but in our RWB we see it as failed, with this entry: invalid http response: HTTP/1.1 200.
I have search in logs, and in defaultTrace_00.0.trc we can see the following entry:
Marked transaction for rollback for meesage 4b4ed19f-bbe6-0062-e100-8000ac1f041d(INBOUND). Reason: java.io.IOException: invalid http response: HTTP/1.1 200
We have captured the HTTP header response, and is:
HTTP/1.1 200
Date: Thu, 14 Jan 2010 10:26:03 CET
Server: Mule/1.2
Connection: close
Expires: Thu, 14 Jan 2010 10:26:03 CET
Content-Type: text/xml
Content-Length: 508
X-MULE_CORRELATION_ID: d595447a-00ee-11df-a6a5-becd407b7daa
X-MULE_CORRELATION_GROUP_SIZE: 3
X-MULE_CORRELATION_SEQUENCE: -1
Could it be problem of the X-MULE_CORRELATION headers? Or Maybe PI needs an HTTP/1.1 200 OK?
Thak you!!!!

Hi Ignasi,
I personally donu2019t think you will have much luck getting XI to accept this response since itu2019s not an XI issue. Itu2019s true that the client (XI in this case) is not required to examine or display the reason-phrase, but that statement doesnu2019t negate the requirement on the server to provide it. The client has the option to look at it or not, but the server must still provide it either way.
I didn't notice the http header before, but the server you are connecting to is actually Mule version 1.2. This release dates back to 2005. I ran a quick test and reproduced the issue using Mule 1.2 (hello-http sample). This may not be the same exact issue, but I did observe the same issue with the missing reason-phrase. The issue is fixed in the Mule 1.3 release.
Perhaps they can request a patch for 1.2. This may not be possible since they are working on the Mule 3.0 version now, but I really donu2019t know. Itu2019s literally one line of code. I made one small change and was able to get the hello-http sample working (code is open source):
Class: org.mule.providers.http.transformers.UMOMessageToHttpResponse
From this:
httpMessage.append(status).append(HttpConstants.CRLF);
To this:
httpMessage.append(status).append(" ").append(org.apache.commons.httpclient.HttpStatus.getStatusText(status)).append(HttpConstants.CRLF);
org.apache.commons.httpclient.HttpStatus.getStatusText is the method they are using in 1.3 to resolve the reason-phrase using the status code.
Thanks,
-Russ

Dynamic Invocation: Error The SOAP PA receives a SOAP Fault from SOAP serve

Hi All,
I am trying to run the sample code "Dynamic Invocation of Oracle9i Web Services using Oracle UDDI registry"
I was able to run the web services, publish them, and inquiry them using local UDDI registry.
However, while invoking any method provided by the web services using the inovk method I get the following error
oracle.j2ee.ws.client.WebServiceProxyException: Invocation failed 5,100: The SOAP PA receives a SOAP Fault from SOAP server
Can anybody help me please?
Regards,
S.Al Shamsi

It looks like the problem is occuring on the server side. I guess you have included the stacktrace from the client, can you get hold of the server side stacktrace?

RFC to SOAP sync error

Hi All,
I am doing the RFC to SOAP sync scenario. request R3 data is coming to XI and its triggering to SOAP receiver.
Information SOAP: continuing to response message e9598290-a14f-11df-969a-00145e474044
Error SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault
i have tried to test the File to SOAP sync scenario to test the SOAP and its working fine. from file request to soap request and soap response to file response.
the same way i have done the RFC request to soap request and soap response to rfc response.
in sxmi_moni i can see the request from RFC but i did't find the request mapping to SOAP.
I have tested the test mapping and its working fine.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://www.webMethods.com/2001/10/soap/encoding">exception</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
the r3 request stacture is:
<filed1>
<filed2>
<filed3>
<ITEM>
<ITEM1>
<ITEM22>
</ITEM>
the soap request stacture is:
<filed1>
<filed2>
   <Header>
    <filed1>
    <filed2>
    <filed3>
   </header>
   <Item>
    <item1
    <item2>
    <item3>
   </Item>
</field2>
</field1>
is there any issue with mapping?
RFC sender CC error is Error in processing caused by: com.sap.aii.adapter.rfc.core.server.RfcServerException: got unexpected document type:DOC_TYPE_UNKNOWN
Can you pls let me know the some inputs to reslove this issue
Thanks,
Venkat

have tried to test the File to SOAP sync scenario to test the SOAP and its working fine. from file request to soap request
and soap response to file response. the same way i have done the RFC request to soap request and soap response to rfc
response.
FILE to SOAP Sync scenario....did you use RequestResponseBean and are you using the same to process RFC to SOAP Sync scenario? If yes, then you dont need the RequestResponseBean for RFC <--> SOAP.
in sxmi_moni i can see the request from RFC but i did't find the request mapping to SOAP. I have tested the test mapping
and its working fine. - - Application APPLICATION_ERROR application fault exception M the r3 request stacture is: the soap
request stacture is: is there any issue with mapping?
I hope you have included a mapping program for Request Mapping and also for Response Mapping in the Interface/ Operation Mapping and included the same in Interface Determination!
Regards,
Abhishek.

Microsoft VBScript runtime error '800a005e' Invalid use of Null: 'clng' /mc/functions/rpt_downline.asp, line 187

while I am in one of my sites I can access most pages except one and I get this message.

"samspram" <[email protected]> wrote in
message
news:fifhoq$cr7$[email protected]..
> Hi There
> Thanks for the reply.
> It is a MySQL DB, the fields I am referencing are TEXT
datatypes and I
> have
> tried referencing them both left and right.
> The data stored in the fields are comma separated
strings e.g. 1, 2, 3, 4,
> which I am loading into Session variables at login with
the following
> code:-
> Session("allowedsubmenus") =
> Left(rsLogin.Fields.Item("u_allowed_sub_menus").Value,
> (Len(rsLogin.Fields.Item("u_allowed_sub_menus").Value) -
1))
> Session("allowedtopmenus") =
> Left(rsLogin.Fields.Item("u_allowed_top_menus").Value,
> (Len(rsLogin.Fields.Item("u_allowed_top_menus").Value) -
1))
> Session("allowedempmenus") =
> Left(rsLogin.Fields.Item("u_allowed_emp_menus").Value,
> (Len(rsLogin.Fields.Item("u_allowed_emp_menus").Value) -
1))
> Session("allowedcoys") =
> Left(rsLogin.Fields.Item("u_allowed_companies").Value,
> (Len(rsLogin.Fields.Item("u_allowed_companies").Value) -
1))
>
> If I load the data into a variable before performing the
Left() function
> on
> the field then it goes past the lines OK but when I try
and use the
> Session
> variable it then throws the Invalid Use of Null error
again.
> i.e.
> Dim varNum
> varNum =
(Len(rsLogin.Fields.Item("u_allowed_top_menus").Value) - 1)
> Session("allowedsubmenus") =
> Left(rsLogin.Fields.Item("u_allowed_sub_menus").Value,
varNum)
> Code will execute past the loading of sessions in this
way but when I try
> to
> use the session later i.e. as with the Split() function
I get the same
> error
> again.
>
> Regards
> Brendan
You are referencing the Recordset Column Value multiple
times.
try putting it into a variable first
varValue = rsLogin.Fields.Item("u_allowed_sub_menus").Value
then proceed with your operations using that variable
Session("allowedsubmenus") = Left(varValue , (Len(varValue )
- 1))

HTTP 403 Service Error, HTTP 500 Internal Server Error

My scenario is:
Rfc adapter --> XI --> WebService
I am get the following error(403,500) at the Call adapter. I like to know whether the following error occurs due to the timing out occuring as the client is not sending back a response? Any suggestions/help would be appreciated.
<SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<Trace level="0" type="System_Error">HTTP-client: error response= <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Body><SOAP:Fault><faultcode>SOAP:Server</faultcode><faultstring>com.sap.aii.messaging.srt.BubbleException: Can't call the endpoint; Exception raised by com.sap.aii.messaging.net.TransportException: HTTP 403 Service Error</faultstring></SOAP:Fault></SOAP:Body></SOAP:Envelope></Trace>
<Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>
<Trace level="0" type="System_Error">System-Error: HTTP.HTTP_STATUS_CODE_NEQ_OK</Trace>
<Trace level="0" type="System_Error">HTTP status code 500 : Internal Server Error</Trace>
<Trace level="0" type="System_Error">HTTP-client: error response= <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Body><SOAP:Fault><faultcode>SOAP:Server</faultcode><faultstring>com.sap.aii.messaging.srt.BubbleException: Can't call the endpoint; Exception raised by com.sap.aii.messaging.net.TransportException: HTTP 403 Service Error</faultstring></SOAP:Fault></SOAP:Body></SOAP:Envelope></Trace>
<Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>
<Trace level="0" type="System_Error">System-Error: HTTP.HTTP_STATUS_CODE_NEQ_OK</Trace>
<Trace level="0" type="System_Error">HTTP status code 500 : Internal Server Error</Trace>
<Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>
<Trace level="0" type="System_Error">System-Error: HTTP.HTTP_STATUS_CODE_NEQ_OK</Trace>
<Trace level="0" type="System_Error">HTTP status code 500 : Internal Server Error</Trace>
</SAP:TraceHeader>

from SM59 I tested the connection of INTEGRATION_DIRECTORY_HMI(HTTP connection to ABAP system)
detail:
staus HTTP response 500
status text : internal server server
duration test call 17173 ms
Please help me out to resolve this issue

HTTP response code 500 : Error during parsing of SOAP header

Hi Experts,
I have a MAIL to IDOC scenario. An external third party emails invoices to our inbox - which we pick up and process the attachment. All is well when I test the scenario internally, but when the third party emails it fails with (see ERROR MESSAGE below).
When I look at the SOAP header of the failed message I see the values from the dump in this field:
<sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderTHREAD-INDEX">AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=</sap:Record>
Can anyone tell me what SHeaderTHREAD-INDEX does? Or what my problem is (Our email is Outlook)
ERROR MESSAGE.........
SOAPFault received from Integration Server. ErrorCode/Category: XIProtocol/WRONG_VALUE; Params: SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14), AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQAAV4L06ABZuwsAAK/f9vgAAF/GSAAAYmRYARIKwtQAV5R9SABMo5bsAGQQyvAAVqsjyABOh9uMAFXTa2QAWEjsfABaEvp4AFaL1NQAV5MnUABXiVbIAGc7LsQAYVN9SABLfYQIAEwF3nQAWSL2lABn5ZgIAEf/k8gAWeVgrAAJaSZIAAElM4gATZR0GA=協彎䅍䔾ਉ़䥎噏䥃䕟乏㸸㌱ㄵㄹ㰯䥎噏䥃䕟乏㸊उ㱁䵏啎呟䕘䍌彖䅔㸷⸵〼⽁䵏啎呟䕘䍌彖䅔㸊उ㱃啒剅乃失㹅啒㰯䍕剒䕎䍙ㄾਉ़䅍何乔彖䅔㸱⸴㜼⽁ꯃ䅢坡汫, ST: ST_XM; AdditionalText: An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC; ApplicationFaultMessage: ; ErrorStack: XML tag SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(14) (or one of the attributes) has the incorrect value AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1pEZAF500SsAYW46lgBgX2bGALyieMQAXw2oKgBYXf0WAGeueD0AAAHnhwBamTSaAGIUE0kAYZSYTQBgY5OTADunN0gAE3t/sQAWScBXADTQvvEAD4yNhQATdkKiAFr7DBMAGIXTZQAP2xJFABZ0YfoAGHYAuAAKlaeaACJ9xtUAEjcvQ An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC Data loss occurred when converting AcarCeJmJKHuV6wZSxm2UMoUeAjS1gALPExABtze/PACiUJDcAGS0DCwAmOOELAJlOzP0AFiOo8gCK1p
Transmitting the message to endpoint http://sdcxp1-ci.na.fmo.com:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header.

We work with Microsoft Outlook, but I'm sure this could work with any email system.
This error only came from external emails - what we did in the end is to get the third party to email a particular email (email1) in our company. This is set up as a regular email account. On this email put a forward rule to email2 for a particular sender/subject. email2 is set up as POP3 so that XD1 can poll it - we also block any emails except from email1.
Doing this accomplishes a couple of things:
1) We get around the error because XI polls email2 (which has adapter settings of IMAP4 so we can see MAIL adapter attributes ie. sender, subject etc...When we originally had as POP3 we were not able to see these - but setting as IMAP4 causes the error for external emailers)
2) We have a SPAM filter - the XI email is clean from SPAM and the adapter will not have errors, as it only receives valid emails to process
3) We have a central email (email1) which is used to archive all XI emails - we use this for all email scenarios (as we also save to folder and forward in the rule)
Hope this helps your situation.

PI 7.11 sp6 - SOAP error on INBOUND SYNC (BE) interface - No handler ...

Experts,
We're running a AIX 6.1 unix based PI 7.11 system patched to Stack SP6. We've got one instance...no web dispatcher or load balancing of any kind.
Our proxy system (sender) is an ECC6.0 EHP4 system. Our 3rd party system (receiver) system is non-sap.
In about a 2 hour timespan, we processed 9700 XML messages all in the SOAP adapter. almost all our traffic is BE (sync). Of those messages, we got 11 errors. And here is what we see in XSMB_MONI and in the java default trace:
#2.0^H#2011 08 29 15:40:08:183#0-500#Error#com.sap.aii.adapter.xi.ms.XIEventHandler#
#BC-XI-CON-AFW#com.sap.aii.af.lib#327C4279AB0F2E5C000000010019C0BE#3930552000000004#sap.com/com.sap.aii.af.ms.app#com.sap.aii.adapter.xi.ms.XIEventHandler.onRequest(Services, TransportMessage)#PIISUSER#8
546##875E5AD3D27311E0C8580000003BF9B8#875e5ad3d27311e0c8580000003bf9b8#875e5ad3d27311e0c8580000003bf9b8#0#Thread[HTTP Worker [@2008983637],5,Dedicated_Application_Thread]#Plain##
Message 4e5b07b7-8180-00ab-e100-80000ae201a4(INBOUND): was not delivered due to com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PA
RSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to process request. ---> No handler is registered for this service.#
#2.0^H#2011 08 29 15:40:08:081#0-500#Error#com.sap.engine.messaging.impl.spi.ServicesImpl#
#BC-XI-CON-MSG#com.sap.aii.af.ms.svc#327C4279AB0F2E98000000000019C0BE#3930552000000004##com.sap.engine.messaging.impl.spi.ServicesImpl.deliver(Message)#J2EE_GUEST#0##875E5AD3D27311E0C8580000003BF9B8#875e
5ad3d27311e0c8580000003bf9b8#875e5ad3d27311e0c8580000003bf9b8#0#MS Queue Worker [SOAP_http://sap.com/xi/XI/SystemRqst]#Plain##
Caught exception com.sap.engine.interfaces.messaging.api.exception.MessagingException from application code with msgKey: 4e5b07b7-8180-00ab-e100-80000ae201a4(INBOUND)#
So I've looked all over the marketplace and SDN/google. I could not find anyone else getting this type of error.
We have WILY introscope and all the diag tools. I am not seeing any bottlenecks on the threads for http or inbound/outbound queues.
I was hoping someone could point me in the right direction. I was thinking about bumping up all the default queue threads for the com.sap.aii.af.ms.svc service. It has the default "10" for all those.
We have done MAJOR tuning already on this instance. I think I've read all the notes/guides/HOW-TO...etc that there is for PI 7.11. So we are making progress.
Thanks,
NICK

Hi Nick,
From error message i could feel that, there is no problem from PI side and error is at the receiver system side where PI is posting the message. Why i am telling it's not PI issue and it's receiver's issue is that, error message you got is SOAP fault message. Fault message are raised by receiver system if any error occurs. If messgae is processed successfully then receiver system would send proper SOAP response message not a SOAP fault.
soap fault: Server was unable to process request. ---> No handler is registered for this service.#
So, in my view you better check at your receiver system (in your case it's no-sap sytem) why it's giving problem as 'No handler is register for the service'.
Rgards,
RK

Soap response mapping error

hi
i got payload of response from webservice as below;
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <m:requestResponse xmlns:m="http://tempuri.org/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<result xsi:type="xsd:string">20060911tt11</result>
</m:requestResponse>
when i test mapping with above contents in mapping test tab, i got mapping error as blow;
16:03:59 Start of test
Cannot produce target element /ns1:Rnumber_MT/rnum. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd Cannot produce target element /ns1:Rnumber_MT/rnum. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
16:03:59 End of test
source side in MM_response, comming from wsdl for MT.
result          xsd:string
target side in MM_response, i created DT, MT.
Rnumber_MT
         |__
             rnum xsd:string
i sent data to webservice succesfully, and i can see return value as well, but mapping error.
please guide me.
thanks in advance
venjamin

hi
in response procedure;
my scenario abap proxy 2 soap sync
1. response from webserivce --> r/3
there is no DT, MT due to coming from wsdl.
only i can see result xsd:string
2. data type for r/3
   Rnumber_DT
       rnum xsd:string
   message type Rnumber_MT
   Rnumber_MT
       |_
           rnum xsd:string
3. mapping for response
   1. source (webservice)
     external message : requestResponse
     result xsd:string
   2. target (r/3)
   Rnumber_MT
       |_
           rnum xsd:string
   i did map ,,, result ---> rnum..
here is payload for response from webservice....
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <m:requestResponse xmlns:m="http://tempuri.org/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<result xsi:type="xsd:string">20060911tt11</result>
</m:requestResponse>
please help me
thanks in advance
venjamin

Received HTTP response code 500 : Error during conversion of XI message

hi
Facing the error , "Received HTTP response code 500 : Error during conversion of XI message"
This is the fist time i am configuring the sender soap ( Axis Framework in the SOAP Adapter) (Quality of service Best effort) communication channel and i am getting the above error did any body face this error.
01.09.2011 12:02:32     Information     The message status was set to DLNG.
01.09.2011 12:02:32     Error     SOAPFault received from Integration Server. ErrorCode/Category: XIServer/ATTRIBUTE_INITIAL; Params: Manifest cid:6D90482BF678436D75928FC8B9930519; AdditionalText: null; ApplicationFaultMessage: null; ErrorStack: Attribute Manifest cid:6D90482BF678436D75928FC8B9930519 is initial
01.09.2011 12:02:32     Error     Transmitting the message using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Error during conversion of XI message.
regards
sandeep
Edited by: pendyalas on Sep 1, 2011 12:20 PM

I found a link with respect to similar error , sap note 1522630 has been used to resolve this error.
i will try and see if it works.
AXIS Sender Adapter Failure after upgrade to PI 7.11 SP06
regards
sandeep

Error capturing SOAP fault for Sync Messages

Hi
We have a Sync interface which makes a Proxy call from ECC to PI and then PI makes Soap Sync call to Web application. We are having issues when handling Exceptions. Sender is getting misleading errors in response, even though they are application errors the proxy sender is getting error like MappingObjectNotFound.
When debug the PI system, PI is truncating error info when it return the reponse.
Below is the scenario of Synchronous interface:
ECC(Proxy) -> PI(Soap Receiver Adapter) -> MasterDataApp-(Webserver)
Below is the actual response from Webserver (Extracted via TCPGW sniffer):
<?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>*java.rmi.RemoteException: No Messages Found*</faultstring>
<detail>
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">hostname.com</ns1:hostname>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
But PI receives this response payload like this :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">hostname.com</ns1:hostname>
and then Sync Request mesasge fails with below error because of the unexpected response payload as shown above:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID B0CC6B27847A368AA04F4171EF6460F4 Software Component 86524CE0304911DEAE48CC6C83461631</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID B0CC6B27847A368AA04F4171EF6460F4 Software Component 86524CE0304911DEAE48CC6C83461631</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also in the response message see this error message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please let me for any clues how to handle this error response.
Thanks,
laxman

Hi Laxman,
SOAP Adapter cannot handle fault responses. I understand your issue. You even want to send the errorneous response from the Webservice as a payload back to the sender. But because of application error from Webservice, you are getting an error in the response message (Mapping Not found). SOAP Adapter cannot handle application error (i.e you will not get the errorneous response in form of payload) . For details please read below:
The receiver adapter expects a SOAP message as response. For synchrnous calls, a successful response should be returned with HTTP 200. In this case, the content of the SOAP body will be returned to the caller as the response payload. When some error occurs, the SOAP message may contain the SOAP fault element. In this case, when the fault detail element is not empty, its content will be returned as the fault payload in an application error message. For others, a system error message will be returned to the caller.
HTTP/1.1 200 OK
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<m:GetLastTradePriceResponse xmlns:m="Some-URI">
<Price>34.5</Price>
</m:GetLastTradePriceResponse>
</SOAP:Body>
</SOAP:Envelope>
will result in an application response message with response payload
<m:GetLastTradePriceResponse xmlns:m="Some-URI">
<Price>34.5</Price>
</m:GetLastTradePriceResponse>
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:MustUnderstand</faultcode>
<faultstring>SOAP Must Understand Error</faultstring>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
will result in a system error message.
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<e:myfaultdetails xmlns:e="Some-URI">
<message>My application didn't work</message>
<errorcode>1001</errorcode>
</e:myfaultdetails>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
will result in an application error message with fault payload
<e:myfaultdetails xmlns:e="Some-URI">
<message>My application didn't work</message>
<errorcode>1001</errorcode>
</e:myfaultdetails>
In order to send the erroneous response as a payload to the sender, you should develop flow in below manner:
ECC(Proxy) -> PI --> ECC(Proxy)
In PI make a SOAP lookup. The response of the SOAP lookup will contain the response given by the WebService (it can be a vaid response or an application error in WebService). Now map this response to the proxy...In this way you can handle the application error msgs from webservice..
I hope this helps you...
Regards,
Rakesh Sharma

Invalid http response: null - Error in SOAP sync receiver

Similar Messages

Maybe you are looking for