Status codes description.

hi,
in t.code inbound and out bound status codes description was
available.
thanks.

HI Friend,
if it help full to u please give me reward point.
                        Display Status
SM58     DISPLAY TRANSACTIONAL RFC
WE08     DISPLAY VIEW FILE STATUS
WECP     DISPLAY VIEW RECEIVED IDOC FROM R/2

Similar Messages

Note of Fiscal for Brazil - Status code descriptions required.

Hi,
I am looking for the Brazil - Note of Fiscal - Status code descriptions for the codes 542, 523 etc.. Please provide us the same. Thanks in advance.
For Example - status code 100 - Autorizado o uso da NF-e
Rgds
Siva

Hi Siva,
Please look at these pages:
http://wiki.sdn.sap.com/wiki/display/BPX/NF-eStatusonSAPNotaFiscalElectronicaSolution%28ERPxGRCxPI%29#NF-eStatusonSAPNotaFiscalElectronicaSolution%28ERPxGRCxPI%29-SC1
and
http://www.nfe.fazenda.gov.br/portal/docs/Manual_Integracao_Contribuinte_versao_4.01-NT2009.006.pdf
It can help you regarding the status of NF-e.
regards
Ruy Castro

How to get status codes of field?

For every document type or status field which we can see on front end, there is code which is finally stored in table.
e:g: Go to transaction /nme53n
 Select any purchase req.
 Select status tab from item.
 See processing status field.
 These processing status saves as N,B, etc in table.
I know there is way to see these codes followed by full description on front end screen itself. I think using personal settings, but dont know how to set this. Please let me know how to see status codes + description on front end.

You gui status should be implemented in the main screen which the subscreen resides, all function codes should be handled at that level. I believe you will need to set the F2 funciton code in your gui status, set the function code to PICK and then handle this function code in your PAI user command module. Should work.
subscreen cannothave their own pf-status.....so create a pf-status for a screen in which ur subscreen is called...include 'pick' or f2 as onre of the functions code for the choose option.
to differentiate the field u have to use get cursor field fldname.
if it is a table control field u have to use
get cursor field <fldaname> line <n> value <fval>

HTTP response contains status code 415 with the description Unsupported

Hi All,
While transferring the data from SRM to CCM , We are getting following error,
HTTP response contains status code 415 with the description Unsupported Media Type Error while sending by HTTP (error code: 415, error text: Unsupported Media Type
Where need to check on this?
Thanks ,
NR

415 Unsupported Media Type
The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.

Error status code 400 with the description Message mapping failed

Hi,
I tried to build RFID outbound scenario using ECC 5.0, XI and AII 2.1.
When I send IDOC message:AIDOPMSG.AIDOP01 from ecc 5.0 to XI(ouput message type is OperationalIn and message mapping is OperationalInTo), i get following error:
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>Message mapping failed</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>Message mapping failed</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 400 with the description Message mapping failed Boundary SAP_57D7D47469E09543A1EA0002CBDA0492_END could not be found</SAP:Stack>
I am using standard AUTO-ID 2.1 XI contents. If any of you have encountered such error message, then could you please help me understand the meaning and how to fix it.
thanks in advance,
Ashit

hi Ashit,
take a look at my weblog on how to test your mapping:
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
maybe with this you'll be able to find out the error
Regards,
michal

HTTP response contains status code 403 with the description Forbidden

Hello all,
I have configured a simple scenario like this:
File ftp Adapter -> XI -> File ftp Adapter
I activate the communication channel to start the message processing. Then I am able to see my messages in transaction SXMB_MONI in the XI Integration server but I get the error message mentioned in the subject of this thread.
When I look at the message processing details I got the following informtion in Call Adapter -> SOAP Header -> Error:
<?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="">
 <SAP:Category>XIServer</SAP:Category>
 <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
 <SAP:P1>403 </SAP:P1>
 <SAP:P2>Forbidden</SAP:P2>
 <SAP:P3/>
 <SAP:P4/>
 <SAP:AdditionalText>&lt;!DOCTYPE HTML PUBLIC &quot;-//W3C//DTD HTML 4.0 Transitional//EN&quot;&gt;
 &lt;html&gt;
 &lt;head&gt;
 &lt;title&gt;Error Report&lt;/title&gt;
 &lt;style&gt;
 td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;}
 A:link
 A:visited
 A:active
 &lt;/style&gt;
 &lt;/head&gt;
 &lt;body marginwidth=&quot;0&quot; marginheight=&quot;0&quot; leftmargin=&quot;0&quot; topmargin=&quot;0&quot; rightmargin=&quot;0&quot;&gt;
 &lt;table width=&quot;100%&quot; cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; align=&quot;left&quot; height=&quot;75&quot;&gt;
 &lt;tr bgcolor=&quot;#FFFFFF&quot;&gt;
 &lt;td align=&quot;left&quot; colspan=&quot;2&quot; height=&quot;48&quot;&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;4&quot; color=&quot;#666666&quot;&gt;&lt;b&gt;&amp;nbsp;&amp;nbsp;403 &amp;nbsp Forbidden&lt;/b&gt;&lt;/font&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr bgcolor=&quot;#3F73A3&quot;&gt;
 &lt;td height=&quot;23&quot; width=&quot;84&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt;
 &lt;td height=&quot;23&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt;
 &lt;td align=&quot;right&quot; height=&quot;23&quot;&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;2&quot; color=&quot;#FFFFFF&quot;&gt;&lt;b&gt;SAP J2EE Engine/6.40&amp;nbsp;&lt;/b&gt;&lt;/font&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr bgcolor=&quot;#9DCDFD&quot;&gt;
 &lt;td height=&quot;4&quot; colspan=&quot;3&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/table&gt;
 &lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;
 &lt;p&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;3&quot; color=&quot;#000000&quot;&gt;&lt;b&gt;&amp;nbsp;&amp;nbsp;You are not authorized to view the requested resource.&lt;/b&gt;&lt;/font&gt;&lt;/p&gt;
 &lt;p&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;2&quot; color=&quot;#000000&quot;&gt;&lt;table&gt;&lt;tr&gt;&lt;td valign=&quot;top&quot;&gt;&lt;b&gt;&amp;nbsp;Details:&lt;/b&gt;&lt;/td&gt;&lt;td valign=&quot;top&quot;&gt;&lt;PRE&gt;No details available&lt;/PRE&gt;&lt;/font&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&lt;/font&gt;&lt;/p&gt;
 &lt;/body&gt;
 &lt;/html&gt;
</SAP:AdditionalText>
 <SAP:ApplicationFaultMessage namespace=""/>
 <SAP:Stack>HTTP response contains status code 403 with the description Forbidden
 XML tag Envelope missing in SOAP message header (SAP XI Extension)
</SAP:Stack>
 <SAP:Retry>M</SAP:Retry>
</SAP:Error>
Does anyone have a hint for me how to solve this issue?
Thanks in advance
Fabian

Hi,
This error may be because of Inactive Services in internet communication framework-
Go to SICF transaction and activate the services. Have a look into SAP note-517484
SO because of huge message this may be the reason.
Hope this helps,
Regards,
Moorthy

HTTP response contains status code 401 with the description Unauthorized

Hi,
I have an IDOC-XML mapping,when the IDOC is sucessfully passed on to the XI but in XI I encounter an errror
"HTTP response contains status code 401 with the description Unauthorized".Could somebody let me know what
could be the reson for this error.
Regards,
Arun

Dear Arun,
1) This might cause due to wrong permissions.
2)Try with this Login XIISUSER
3)Tcode SICF -> Default_host -> sap -> xi
( Check right password for the user id )
Regards
Agasthuri Doss

HTTP response contains status code 401 with the description Unauthorized Er

Hi All,
I am getting the below error, i have reset the password and username also but i am not getting where exactly it is failing out.

<?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="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>Enter User Name and Password</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 401 with the description Unauthorized Error when sending by HTTP (error code: 401, error text: Unauthorized)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Can anyone have the idea how can i check it out...??
Thanks in advance.

I have changed every password and username from XIAPPLUSER to XIAPPLTEST, but still in MONI--->oubound binding ..,, i am getting the logon user as the XIAPPLUSER... I check the perticular communication channel it is maintained XIAPPLTEST but still i am getting XIAPPLUSER.....
Do i have to refresh somewhere.
Can anyone have the idea is there anywhere else it is maintained..
================================================
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SAP:OutboundBindingEntry version="30">
<SAP:OutboundBindingObjectId>041B892AC87B38A4AE46D4E443C88E55</SAP:OutboundBindingObjectId>
<SAP:FromPartyName />
<SAP:FromServiceName>BS_PSEWC</SAP:FromServiceName>
<SAP:ToPartyName />
<SAP:ToServiceName>BS_SAPRP1</SAP:ToServiceName>
<SAP:ToInterfaceName>sub_MeterReading</SAP:ToInterfaceName>
<SAP:ToInterfaceNamespace>urn://WCM_SR3_02/SAP/Meterreading</SAP:ToInterfaceNamespace>
- <SAP:OutboundBindingAttributes>
<SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:OutboundBindingAttributes>
- <SAP:HeaderMapping>
<SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:HeaderMapping>
- <SAP:ChannelEntry version="30">
<SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">BS_SAPRP1</SAP:ServiceName>
<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">CCO_Proxy_WCM_MeterReading</SAP:ChannelName>
<SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">XI</SAP:AdapterName>
<SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
<SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">3B787A8035C111D6BBE0EFE50A1145A5</SAP:AdapterSWCV>
<SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">IS</SAP:AdapterEngineType>
<SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">XI</SAP:MessageProtocol>
<SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">2.0</SAP:MessageProtocolVersion>
<SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">HTTP</SAP:TransportProtocol>
<SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">1.0</SAP:TransportProtocolVersion>
<SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
<SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
- <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:Attribute>
<SAP:Name>addressingMode</SAP:Name>
<SAP:Value>url</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>authenticationModeBasicAnon</SAP:Name>
<SAP:Value>basicSAP</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>host</SAP:Name>
<SAP:Value>drprd-db1</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>httpDestination</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonClient</SAP:Name>
<SAP:Value>300</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonLanguage</SAP:Name>
<SAP:Value>E</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonPassword</SAP:Name>
<SAP:Value isPassword="true" />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonUser</SAP:Name>
<SAP:Value>XIAPPLUSER</SAP:Value> </SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>path</SAP:Name>
<SAP:Value>/sap/xi/engine?type=receiver</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>port</SAP:Name>
<SAP:Value>8001</SAP:Value>
</SAP:Attribute>
</SAP:AdapterTypeData>
</SAP:ChannelAttributes>
</SAP:ChannelEntry>
</SAP:OutboundBindingEntry>
</SAP:OutboundBinding>

HTTP response contains status code 503 with the description

<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 503 with the description
Service Unavailable Error when sending by HTTP (error code: 503, error
text: Service Unavailable)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Please advice. Initially we thought the J2EE services were unavailable . But now even when the services are running we still have the same issue when there is a http call from an external application to XI . The message get posted but there is an error on the response back to the external application.
Even the contract which was supposed to be created in ERP from the external application did not get created.
Please advice.
Thanks,
Nivedita

Hi Nivedita,
503 means Service Unavailable
just check whether you cn ping the HTTP server host and port is open.
if not then consult the vedor and make both open first.
Also if you want to restart the java engine
then run T-code SMICM
Then go to administration then JAVA restart soft.
it will help you.
Regards,
Sumit Gupta

Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5015. SQL 2012 SP1

Hi,
Please help. I was trying to remove a SQL 2012 SP1 two node clustered instance using setup (Mantenance -> Remove Node)
I started by doing this on passive node (and was successful) but when I ran setup on active node just before finishing successfully I got this error:
TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
The following error has occurred:
The resource 'BCK_SG1DB' could not be moved from cluster group 'SQL Server (SG1DB)' to cluster group 'Available Storage'.
Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5015.
Description: The operation failed because either the specified cluster node is not the owner of the resource, or the node
is not a possible owner of the resource.
For help, click:
http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=0xE8049925%25400x42B4DED7
BUTTONS:
OK
I noticed that SG1DB instance was removed on both nodes but on Failover Cluster Manager -> Services and Applications the SQL server instance for SG1DB is still there. So I tried to delete it but got the error:
Failed to delete SQL Server SG1DB. An error was encountered while deleting the cluster service or
application SQL Server SG1DB. Could not move the resource to available storage. An error occured
while moving the resource BCK_SG1DB to the clustered service or application Available Storage
Any ideas why it failed or how could I delete the SQL server instance from Clauster?
Thx

Hello,
Please read the following resource.
https://support.microsoft.com/en-us/kb/kbview/313882?wa=wsignin1.0
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

HTTP response contains status code 404 ...

Hello,
My system sceanrio is:
R/3 -> idoc -> XI-1 -> xi adapter -> XI-2 -> idoc -> R/3.
When the message sent, I get a red flag in SXMB_MONI transaction of "XI-1" system :
'HTTP response contains status code 404 with the
description Not Found'
Here is the SOAP adapter of the Call Adapter:
=============================================
td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active </style> </head> <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0"> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"> 404 &nbsp Not Found</td> </tr> <tr bgcolor="#3F73A3"> <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td> <td height="23"><img width=1 height=1 border=0 alt=""></td> <td align="right" height="23">SAP J2EE Engine/6.40 </td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> The requested resource does not exist. <table><tr><td valign="top"> Details:</td><td valign="top"><PRE>Go to <A HREF="/" target="_parent">main page</A> of this application!</PRE></td></tr></table> </body> </html></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 404 with the description Not Found XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2005-04-12T06:52:37Z" wasRead="false">
<SAP:Engine type="IS">is.50.weaver</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">IDoc</SAP:Adapter>
<SAP:MessageId>550806B7-DEED-FF42-96B1-6F33852373F1</SAP:MessageId>
<SAP:Info>MATMAS.0000000000214059:20050412085231</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2005-04-12T06:52:37Z" wasRead="false">
<SAP:Engine type="IS">is.50.weaver</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>550806B7-DEED-FF42-96B1-6F33852373F1</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:IDocInbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>200</SAP:MANDT>
<SAP:DOCREL>46C</SAP:DOCREL>
<SAP:DOCNUM>0000000000214059</SAP:DOCNUM>
<SAP:DIRECT>1</SAP:DIRECT>
<SAP:IDOCTYP>MATMAS04</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>MATMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPDEV</SAP:SNDPOR>
<SAP:SNDPRN>LOGDEV200</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>XI-TEST</SAP:RCVPOR>
<SAP:RCVPRN>LOGXID700</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL>20050412085231</SAP:SERIAL>
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS>30</SAP:STATUS>
<SAP:OUTMOD>2</SAP:OUTMOD>
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>2005-04-12</SAP:CREDAT>
<SAP:CRETIM>08:52:31</SAP:CRETIM>
<SAP:ARCKEY />
</SAP:IDocInbound>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20050412</SAP:Date>
<SAP:Time>085237</SAP:Time>
<SAP:Host>weaver</SAP:Host>
<SAP:SystemId>XID</SAP:SystemId>
<SAP:SystemNr>50</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>MSSQL</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>014</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>ANNA</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>002</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
<SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
<SAP:QIdInternal>XBTO3___0000</SAP:QIdInternal>
<SAP:CommitActor>A</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="700">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">DF010AB7129C425B7035011D</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID">DF013D07020C425B70300B0A</SAP:EOReferenceInbound>
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>16517</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>0</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>16517</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>16527</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>IDOC</SAP:AdapterInbound>
<SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
<SAP:RandomNumber>71</SAP:RandomNumber>
<SAP:AckStatus>071</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.471</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.471</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.471</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.642</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.642</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.658</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.658</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.658</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.658</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.674</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.674</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.814</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.814</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.939</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.939</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end" host="weaver">20050412065237.971</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin" host="weaver">20050412065237.971</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SAP:OutboundBindingEntry version="30">
<SAP:OutboundBindingObjectId>B0E25658819A3AE888B48BAD55537C5E</SAP:OutboundBindingObjectId>
<SAP:FromPartyName />
<SAP:FromServiceName>DEV</SAP:FromServiceName>
<SAP:ToPartyName />
<SAP:ToServiceName>XIT</SAP:ToServiceName>
<SAP:ToInterfaceName>MATMAS.MATMAS04</SAP:ToInterfaceName>
<SAP:ToInterfaceNamespace>urn:sap-com:document:sap:idoc:messages</SAP:ToInterfaceNamespace>
- <SAP:OutboundBindingAttributes>
<SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:OutboundBindingAttributes>
- <SAP:HeaderMapping>
<SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:HeaderMapping>
- <SAP:ChannelEntry version="30">
<SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">XIT</SAP:ServiceName>
<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">GeneratedReceiverChannel_XI</SAP:ChannelName>
<SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">XI</SAP:AdapterName>
<SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
<SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">3B787A8035C111D6BBE0EFE50A1145A5</SAP:AdapterSWCV>
<SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">IS</SAP:AdapterEngineType>
<SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">XI</SAP:MessageProtocol>
<SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">3.0</SAP:MessageProtocolVersion>
<SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">HTTP</SAP:TransportProtocol>
<SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">1.0</SAP:TransportProtocolVersion>
<SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
<SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
- <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:Attribute>
<SAP:Name>addressingMode</SAP:Name>
<SAP:Value>url</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>authenticationModeBasicAnon</SAP:Name>
<SAP:Value>anonymous</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>host</SAP:Name>
<SAP:Value>victor</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>httpDestination</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>isMessageSecurity</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonClient</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonLanguage</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonPassword</SAP:Name>
<SAP:Value isPassword="true" encryption="hw">AQ==</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonUser</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>passHopList</SAP:Name>
<SAP:Value>1</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>path</SAP:Name>
<SAP:Value>/sap/xi/engine?type=entry</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>port</SAP:Name>
<SAP:Value>56000</SAP:Value>
</SAP:Attribute>
</SAP:AdapterTypeData>
</SAP:ChannelAttributes>
</SAP:ChannelEntry>
</SAP:OutboundBindingEntry>
</SAP:OutboundBinding>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="1" type="T">Syntax-Check-Flag X</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPDEV</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
<Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 700</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = ANNA</Trace>
<Trace level="1" type="Timestamp">2005-04-12T06:52:37Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 550806B7DEEDFF4296B16F33852373F1</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0010</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0010</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 700</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = ANNA</Trace>
<Trace level="1" type="Timestamp">2005-04-12T06:52:37Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTO3___0000</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XID</Trace>
<Trace level="1" type="T">client = 700</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = ANNA</Trace>
<Trace level="1" type="Timestamp">2005-04-12T06:52:37Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="1" type="T">Interface Mapping urn:XI_to_XI_Simulation MATMAS04_MATMAS04</Trace>
<Trace level="1" type="T">*** APPLICATION TRACE TRUNCATED (for more details see LogViewer)***</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="1" type="T">processing the outbound binding</Trace>
<Trace level="1" type="T">search outbound bindings</Trace>
<Trace level="1" type="T">outbound bindings found</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="1" type="T">Sender: Header mapped to</Trace>
<Trace level="1" type="T">Party =</Trace>
<Trace level="1" type="T">Agency =</Trace>
<Trace level="1" type="T">Scheme =</Trace>
<Trace level="1" type="T">Service = DEV</Trace>
<Trace level="1" type="T">Receiver: Header mapped to</Trace>
<Trace level="1" type="T">Party =</Trace>
<Trace level="1" type="T">Agency =</Trace>
<Trace level="1" type="T">Scheme =</Trace>
<Trace level="1" type="T">Service = XIT</Trace>
<Trace level="1" type="T">Party denormalization: sender</Trace>
<Trace level="1" type="T">Sender target scheme =</Trace>
<Trace level="1" type="T">Sender target agency =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Party denormalization: receiver</Trace>
<Trace level="1" type="T">Receiver target scheme =</Trace>
<Trace level="1" type="T">Receiver target agency =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="1" type="System_Error">HTTP-client: error response= <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Error Report</title> <style> td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active

Hi,
The 'Communication Channel' in Integration Builder was not configured right in the 'Service Number' field. There was a J2EE port instead of HTTP port.
J2EE port: 5<instance number>00
HTTP port: 80<instance number>
Good luck to everyone,
Dimitry

HTTP response contains status code 503

Hi All,
Im working on File to JDBC scenario using MsAccess.My file is been picked by XI from the sender folder (im using NFS at the sender side), but it is not inserting the data in the table which i have created on the server.
When i do SXI_MONI , i'm getting a error in call adapter "HTTP response contains status code 503 with the description Service Unavailable Error while sending by HTTP (error code: 503, error text: Service Unavailable)".
Plz do help me to solve it.
Thanks,
Suma

Hi,
503 Service unavailable
this is because of the server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
you can go for the possible solution as mentioned below:
Because of J2EE application com.sap.aii.af.ms.app not active
1. Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine.
2. The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
3. Refer SAP Note 803145,807000,791655
4. In Visual Admin, check if all the required services are running and start them, else restart the Java Stack in the XI server.
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi /people/vinoth.murugaiyan/blog/2007/08/06/how-to-the-change-the-application-stopped-message
http://help.sap.com/saphelp_nw04/helpdata/en/64/351941edd5ef23e10000000a155106/frameset.htm
thanq
krishna

HTTP Status Code from NetConnection

Hey flexers,
I have a flex app that requires a user to be logged in to make service calls. If the user isn't logged in or the session times out and the app makes a call to a backend service via AMF, the server responds with an HTTP status code 401, as expected. The response header looks like this:
HTTP/1.1 401 Authorization Required
Date: Wed, 18 Aug 2010 16:49:01 GMT
Server: Apache/2.2.8 (Ubuntu) PHP/5.2.4-2ubuntu5.6 with Suhosin-Patch mod_ssl/2.2.8 OpenSSL/0.9.8g
X-Powered-By: PHP/5.2.4-2ubuntu5.6
x-ec2-instance-id: i-e52e8b8f
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
Cache-Control: post-check=0, pre-check=0
Content-Length: 185
Content-Type: application/x-amf
Expires: 0
The response content is AMF so it's binary but here's the hex as reported by the Charles Web Debugging Proxy:
00000000 00 00 00 00 00 01 00 0b 2f 31 2f 6f 6e 53 74 61           /1/onSta
00000010 74 75 73 00 00 ff ff ff ff 10 00 1b 66 6c 61 73   tus         flas
00000020 68 2e 65 76 65 6e 74 73 2e 4e 65 74 53 74 61 74   h.events.NetStat
00000030 75 73 45 76 65 6e 74 00 04 69 6e 66 6f 10 00 06   usEvent info
00000040 4f 62 6a 65 63 74 00 07 6d 65 73 73 61 67 65 02   Object message
00000050 00 61 59 6f 75 72 20 73 65 73 73 69 6f 6e 20 69    aYour session i
00000060 73 20 6e 6f 20 6c 6f 6e 67 65 72 20 61 63 74 69   s no longer acti
00000070 76 65 2e 20 20 54 68 69 73 20 69 73 20 6c 69 6b   ve. This is lik
00000080 65 6c 79 20 64 75 65 20 74 6f 20 69 6e 61 63 74   ely due to inact
00000090 69 76 69 74 79 2e 20 50 6c 65 61 73 65 20 72 65   ivity. Please re
000000a0 2d 6c 6f 67 69 6e 20 74 6f 20 63 6f 6e 74 69 6e   -login to contin
000000b0 75 65 2e 00 00 09 00 00 09                        ue.
I'm looking for the proper way, in the Flex app, to figure out it's a 401 status code. Previously, we were watching for the NetStatusEvent coming from NetConnection. If there was a info.errorCode property, we'd use that as the status code. Otherwise, if there was an info.description property, it would normally look like "HTTP: Status 401" in which case we'd pull it out of the string (which makes me cringe just thinking about it). However, at the moment the NetStatusEvent looks like this:
error flash.events.NetStatusEvent (@6a7eee1)
[inherited]
info Object (@7f3ea79)
code "NetConnection.Call.Failed"
description "HTTP: Failed"
details "http://dev.studioj.com"
level "error"
m_info Object (@7f3ea79)
No status code exists in the event anywhere in the event. After all kinds of debugging, rolling back code, etc., I can't figure out why the NetStatusEvent now has description "HTTP: Failed" instead of description "HTTP: Status 401".
Can anyone clarify what's going on? Thanks.

After digging into it more, I've found that it's browser-specific behavior. When simulating an HTTP status code of 401, in Chrome and IE I get a NetStatusEvent that looks like this:
error flash.events.NetStatusEvent (@6c33791)
[inherited]
info Object (@6b14851)
code "NetConnection.Call.Failed"
description "HTTP: Status 401"
details "http://aaronhardy.com/test.php"
level "error"
m_info Object (@6b14851)
Notice the "description" has the status code. In Firefox I get an event that looks like this:
error flash.events.NetStatusEvent (@6c33791)
[inherited]
info Object (@6b14851)
code "NetConnection.Call.Failed"
description "HTTP: Failed"
details "http://aaronhardy.com/test.php"
level "error"
m_info Object (@6b14851)
Notice the status code isn't mentioned anywhere. Is this a known issue in Firefox? Are we really that close to being able to use real HTTP status codes yet so far away?
Aaron

ABAP Proxy HTTP response contains status code 401

We have a client ABAP proxy running in a program successfully in our development system. Today I transported this to our Test system. When I tested, there were no messages in the adapter engine pipeline.
One of my colleagues discovered that when running SXMB_MONI on the Application system (_not_ the XI system), the XML queue there shows the message with an error, the error being:
HTTP response contains status code 401 with the description Unauthorized
I have looked at quite a few posts here with this error; the PIAPPLUSER is not locked, Integration engine is configured the same way in both Development and Test, but I cannot figure out why this is happening.
Any assistance more than welcome!
BR,
Tony.

hi,
Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
If the error is in Adapter Engine
then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
May be wrong password for user XIISUSER
May be wrong password for user XIAFUSER
for this Check the Exchange Profile and transaction SU01, try to reset the password -Restart the J2EE Engine to activate changes in the Exchange Profile After doing this, you can restart the message
Thanks
Swarup

The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code 255

Hello All
We have a server 2008 R2 HyperV server and during the last few months it started to reboot randomly.
Initially we thought its related to the issue fixed by the following hotfix so we applied it but even with the hotfix it still keeps rebooting.
http://support.microsoft.com/kb/2732595
Unlike what's mentioned in the hotfix , the faulting module is not "ntdll.dll" but "msvcrt.dll".Also came up with the following indication the reboots could be related to KB2871997 but that update is not installed
on this system.
Following are the events from system log.
Log Name: System
Source: LsaSrv
Date: 2/9/2015 11:58:12 PM
Event ID: 5000
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: HV2008-Host
Description:
The security package Kerberos generated an exception. The exception information is the data.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
 <Provider Name="LsaSrv" Guid="{199FE037-2B82-40A9-82AC-E1D46C792B99}" />
 <EventID>5000</EventID>
 <Version>0</Version>
 <Level>2</Level>
 <Task>0</Task>
 <Opcode>0</Opcode>
 <Keywords>0x8000000000000000</Keywords>
 <TimeCreated SystemTime="2015-02-10T04:58:12.415529200Z" />
 <EventRecordID>8091130</EventRecordID>
 <Correlation />
 <Execution ProcessID="736" ThreadID="5888" />
 <Channel>System</Channel>
 <Computer>HV2008-Host</Computer>
 <Security UserID="S-1-5-18" />
</System>
<EventData>
 <Data Name="Package">Kerberos</Data>
 <Binary>050000C00000000000000000000000001111F6FEFE070000020000000000000000000000000000008EEB1802000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
Log Name: System
Source: USER32
Date: 2/9/2015 11:58:24 PM
Event ID: 1074
Task Category: None
Level: Information
Keywords: Classic
User: SYSTEM
Computer: HV2008-Host
Description:
The process wininit.exe has initiated the restart of computer HV2008-HOST on behalf of user for the following reason: No title for this reason could be found
Reason Code: 0x50006
Shutdown Type: restart
Comment: The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code 255. The system will now shut down and restart.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
 <Provider Name="USER32" />
 <EventID Qualifiers="32768">1074</EventID>
 <Level>4</Level>
 <Task>0</Task>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2015-02-10T04:58:24.000000000Z" />
 <EventRecordID>8091132</EventRecordID>
 <Channel>System</Channel>
 <Computer>HV2008-Host</Computer>
 <Security UserID="S-1-5-18" />
</System>
<EventData>
 <Data>wininit.exe</Data>
 <Data>HV2008-HOST</Data>
 <Data>No title for this reason could be found</Data>
 <Data>0x50006</Data>
 <Data>restart</Data>
 <Data>The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code 255. The system will now shut down and restart.</Data>
 <Data>
 </Data>
 <Binary>06000500000000000000000000000000000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
Following are the events from Application logs.
Log Name: Application
Source: Application Error
Date: 2/9/2015 11:58:14 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: HV2008-Host
Description:
Faulting application name: lsass.exe, version: 6.1.7601.22653, time stamp: 0x534893ed
Faulting module name: msvcrt.dll, version: 7.0.7601.17744, time stamp: 0x4eeb033f
Exception code: 0xc0000005
Fault offset: 0x0000000000001111
Faulting process id: 0x2e0
Faulting application start time: 0x01d03c91dbe5854f
Faulting application path: C:\Windows\system32\lsass.exe
Faulting module path: C:\Windows\system32\msvcrt.dll
Report Id: 6af0ff3d-b0e1-11e4-83ca-0026b9340d61
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
 <Provider Name="Application Error" />
 <EventID Qualifiers="0">1000</EventID>
 <Level>2</Level>
 <Task>100</Task>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2015-02-10T04:58:14.000000000Z" />
 <EventRecordID>267648</EventRecordID>
 <Channel>Application</Channel>
 <Computer>HV2008-Host</Computer>
 <Security />
</System>
<EventData>
 <Data>lsass.exe</Data>
 <Data>6.1.7601.22653</Data>
 <Data>534893ed</Data>
 <Data>msvcrt.dll</Data>
 <Data>7.0.7601.17744</Data>
 <Data>4eeb033f</Data>
 <Data>c0000005</Data>
 <Data>0000000000001111</Data>
 <Data>2e0</Data>
 <Data>01d03c91dbe5854f</Data>
 <Data>C:\Windows\system32\lsass.exe</Data>
 <Data>C:\Windows\system32\msvcrt.dll</Data>
 <Data>6af0ff3d-b0e1-11e4-83ca-0026b9340d61</Data>
</EventData>
</Event>
Log Name: Application
Source: Windows Error Reporting
Date: 2/9/2015 11:58:23 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: HV2008-Host
Description:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: lsass.exe
P2: 6.1.7601.22653
P3: 534893ed
P4: msvcrt.dll
P5: 7.0.7601.17744
P6: 4eeb033f
P7: c0000005
P8: 0000000000001111
P9:
P10:
Attached files:
C:\Windows\Temp\WER5001.tmp.appcompat.txt
C:\Windows\Temp\WER535C.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WER53DA.tmp.hdmp
C:\Windows\Temp\WER6690.tmp.mdmp
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_lsass.exe_3c1aa5eeba75bf26fcebc4f54e714efe7b5162a2_cab_20a56871
Analysis symbol:
Rechecking for solution: 0
Report Id: 6af0ff3d-b0e1-11e4-83ca-0026b9340d61
Report Status: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
 <Provider Name="Windows Error Reporting" />
 <EventID Qualifiers="0">1001</EventID>
 <Level>4</Level>
 <Task>0</Task>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2015-02-10T04:58:23.000000000Z" />
 <EventRecordID>267650</EventRecordID>
 <Channel>Application</Channel>
 <Computer>HV2008-Host</Computer>
 <Security />
</System>
<EventData>
 <Data>
 </Data>
 <Data>0</Data>
 <Data>APPCRASH</Data>
 <Data>Not available</Data>
 <Data>0</Data>
 <Data>lsass.exe</Data>
 <Data>6.1.7601.22653</Data>
 <Data>534893ed</Data>
 <Data>msvcrt.dll</Data>
 <Data>7.0.7601.17744</Data>
 <Data>4eeb033f</Data>
 <Data>c0000005</Data>
 <Data>0000000000001111</Data>
 <Data>
 </Data>
 <Data>
 </Data>
 <Data>
C:\Windows\Temp\WER5001.tmp.appcompat.txt
C:\Windows\Temp\WER535C.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WER53DA.tmp.hdmp
C:\Windows\Temp\WER6690.tmp.mdmp</Data>
 <Data>C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_lsass.exe_3c1aa5eeba75bf26fcebc4f54e714efe7b5162a2_cab_20a56871</Data>
 <Data>
 </Data>
 <Data>0</Data>
 <Data>6af0ff3d-b0e1-11e4-83ca-0026b9340d61</Data>
 <Data>0</Data>
</EventData>
</Event>
Log Name: Application
Source: Windows Error Reporting
Date: 2/9/2015 11:58:22 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: HV2008-Host
Description:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: lsass.exe
P2: 6.1.7601.22653
P3: 534893ed
P4: msvcrt.dll
P5: 7.0.7601.17744
P6: 4eeb033f
P7: c0000005
P8: 0000000000001111
P9:
P10:
Attached files:
C:\Windows\Temp\WER5001.tmp.appcompat.txt
C:\Windows\Temp\WER535C.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WER53DA.tmp.hdmp
C:\Windows\Temp\WER6690.tmp.mdmp
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_lsass.exe_3c1aa5eeba75bf26fcebc4f54e714efe7b5162a2_cab_20a56871
Analysis symbol:
Rechecking for solution: 0
Report Id: 6af0ff3d-b0e1-11e4-83ca-0026b9340d61
Report Status: 4
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
 <Provider Name="Windows Error Reporting" />
 <EventID Qualifiers="0">1001</EventID>
 <Level>4</Level>
 <Task>0</Task>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2015-02-10T04:58:22.000000000Z" />
 <EventRecordID>267649</EventRecordID>
 <Channel>Application</Channel>
 <Computer>HV2008-Host</Computer>
 <Security />
</System>
<EventData>
 <Data>
 </Data>
 <Data>0</Data>
 <Data>APPCRASH</Data>
 <Data>Not available</Data>
 <Data>0</Data>
 <Data>lsass.exe</Data>
 <Data>6.1.7601.22653</Data>
 <Data>534893ed</Data>
 <Data>msvcrt.dll</Data>
 <Data>7.0.7601.17744</Data>
 <Data>4eeb033f</Data>
 <Data>c0000005</Data>
 <Data>0000000000001111</Data>
 <Data>
 </Data>
 <Data>
 </Data>
 <Data>
C:\Windows\Temp\WER5001.tmp.appcompat.txt
C:\Windows\Temp\WER535C.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WER53DA.tmp.hdmp
C:\Windows\Temp\WER6690.tmp.mdmp</Data>
 <Data>C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_lsass.exe_3c1aa5eeba75bf26fcebc4f54e714efe7b5162a2_cab_20a56871</Data>
 <Data>
 </Data>
 <Data>0</Data>
 <Data>6af0ff3d-b0e1-11e4-83ca-0026b9340d61</Data>
 <Data>4</Data>
</EventData>
</Event>
Would really appreciate if someone can point us to the correct direction on how to get this issue sorted.
Regards,
Dhanushka

Hi Sir,
Please try the following items:
1. if ther is anti-virus installed , please uninstall it temporarily
2. run " sfc /scannow "
3. keep windows up-to-date
4. if you updated some hardware driver please roll it back
5. if the issue persists , please use windows installation media to perform inplace-upgrade for the system
Also please refer to reinstall C++ runtime within the similar thread:
https://social.technet.microsoft.com/Forums/windows/en-US/bf69eeff-24c4-499f-b280-b6a3098f4f9f/problem-with-msvcrtdll-version-70760117744?forum=w7itprogeneral
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Status codes description.

Similar Messages

Maybe you are looking for