PLAINHTTP_ADAPTER.ATTRIBUTE_SERVER error
Hi All,
On a very frequent basis we get the following error in XI.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Internal Server Error</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Http server code 500 reason Internal Server Error explanation Internal Server Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Everytime when this occurs we receive alerts. But when we restart the message processing everything is fine and the message is processed correctly.
Any ideas???
How to obtain more info?
Best Regards
Ron
> The helpdesk is getting a lot of alerts on this
> issue. (every error triggeres an alert). Is is
> possible to suppres alerts on this error?
>
Sure is.
Define a Separate Alert Rule only for this error and then select option Suppress Multiple Alerts of this Rule in the Alert Rule.
Now the Alert will be triggered only once for this error message until the Alert is confirmed int he RWB.
Regards
Bhavesh
Similar Messages
-
PLAIN HTTP ADAPTER -ATTRIBUTE_SERVER ERROR
Hi,
I am facing the following error while using HTTP Receiver adapter,
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Error during parsing of SOAP header</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Http server code 500 reason Internal Server Error explanation Error during parsing of SOAP header</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Help me to solve this problemHi Prabu,
You should be using adapter type XI to connect to the receiver SAP system and not HTTP. Define an RFC connection from XI to that SAP system (SM59 use type HTTP connection to ABAP system) and use that RFC connection name in you XI receiver communication channel. -
HTTP Receiver adapter error ?
HI Guys,
I have configured the IDOC-HTTP. I have defined a bsuiness service on the receiver side as the receiver is not in our landscape and he is our business partner.
I have created a RFC connection of type G and it is working properly but the HTTP reciver adapter gives the error as below
I'm getting an error when I go to "sxmb_moni" which says
Error Category = PLAINHTTP_ADAPTER
Error ID = ATTRIBUTE_SERVER
Kindly help..
Thanks,
Raj
Message was edited by:
raj reddyHi Raj,
<b>Error Category = PLAINHTTP_ADAPTER
Error ID = ATTRIBUTE_SERVER</b>
as far as i know this problem is due to high traffic.When the data comes in bulk some of the message are failing or when they are not able to connect to reciever server.So it gives error.
u can look @ these threads of similer taste
PLAINHTTP_ADAPTER.ATTRIBUTE_SERVER error
PLAIN HTTP ADAPTER -ATTRIBUTE_SERVER ERROR
Plain HTTP adapter error
PLAINHTTP_ADAPTER - ATTRIBUTE_SERVER
and also look @
http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm
Regards
biplab -
Hi Everyone,
I am using a HTTP adapter at the receiver side. I am not sure about what values I should give in the following parameters
Addressing Type,
Target Host,
Service Number,
Path.
I'm getting an error when I go to "sxmb_moni" which says
Error Category = PLAINHTTP_ADAPTER
Error ID = ATTRIBUTE_SERVER
Kindly help..
Regards
Indudhar.this error might be due to bottleneck in the traffic.When the data comes in bulk some of the message is failing or when they are not able to connect to reciever server.
PLAINHTTP_ADAPTER.ATTRIBUTE_SERVER error
PLAIN HTTP ADAPTER -ATTRIBUTE_SERVER ERROR
http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm
Plain HTTP adapter error
PLAINHTTP_ADAPTER - ATTRIBUTE_SERVER
check once again your HTTLP receiver adapter entries......care you getting this in the call adapter step of the Pipiline? -
ATTRIBUTE_MISSING_URL
Hi XI Expert,
please am very neue in XI and I want to send a message to another Xi I have done all Configuration (IR and ID) but i have this error:
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_MISSING_URL</SAP:Code>
Please could do tell me where I can care the URL an logging for the Http adapter for extern Communication.
Thanks in advace
DominiqueHi,
Just test your URL in the browser and check whether there is some error.
The Plain HTTP adapter is not part of the adapter framework, so you cannot see anything in the adapter monitor.
Log on to the server, where the XI is installed. Can you ping the receiver host?
HTTP 500 can be any problem at receiver side.
This problem might be due to bottleneck in the traffic.When the data comes in bulk some of the message is failing or when they are not able to connect to reciever server.
Here are a list of possible reasons for your problem with solutions.
It could be that it cannot find your file adapter.
1. Have you specified your hostname or IP address? Often the server cannot resolve the ip address for the hostname of your PC.
2. Is the path and port in the directory the same as the path and port of your file adapter?
3. Try question 14 (integration engine section)
/people/mark.finnern/blog/2006/01/12/finally-best-of-sdn-2005
4. also question 11 (in the same section)
5. if the avove will not fix it open XI config guide and
have a look at section
"Connecting Business Systems with an Integration Engine to the Central Integration Server"
6. Your error code is 400, so check this link,
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
For http 400 - its a bad request.
'The request could not be understood by the server due to malformed syntax.'
If you have the XI trouble shooting guide see from page 54,and also try:
1.Check that the port really is the ICM HTTP Port (transaction
SMICM) and not the J2EE port
2.If the port is wrong, change the pipeline URL in the SLD in
the business system of the Integration Server
3.Restart the J2EE Engine to reset the SLD buffer of the
Adapter Engine
Source- "XI troubleshooting guide"
Please refer
PLAINHTTP_ADAPTER.ATTRIBUTE_SERVER error
PLAIN HTTP ADAPTER -ATTRIBUTE_SERVER ERROR
http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm
Plain HTTP adapter error
PLAINHTTP_ADAPTER - ATTRIBUTE_SERVER
ICM_HTTP_CONNECTION_FAILED
Thanks
Swarup -
Error while ORDERS05 IDoc transfer from R3 - PI - SNC
Hi Friends,
I am facing error in PI SXMB_MONI for ORDERS05 IDoc transfer from R3 - PI - SNC.
I have done all the configuration setup in Integration Directory for the Scenario, I am able to successfully send the IDOC for PO from R3 to PI but faced the following Error in PI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Message Split According to Receiver List
-->
- <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">PARTY_SERVICE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
*<SAP:Stack>Party and service not defined</SAP:Stack>*
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also I am unable to Configure Sender/Receiver ID in PI > SXMB_ADMIN > Configuration, as while defining Sender/Receiver unable to add the Interface for Sender(ORDERS.ORDERS05)/Reciever(ReplenishmentOrderNotificatio_Out) although I am able to see the same in Integration Repository.
Also In Main message(Part of the message) as shown below, I am able to see Vendor in PARTY Element of xml message for which I have created the PO
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Message Split According to Receiver List
-->
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>0050568F-24A0-1DDD-B9F5-3F6DD541FF93</SAP:MessageId>
<SAP:TimeSent>2009-01-21T10:55:20Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>SAPECC6</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">ORDERS.ORDERS05</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="SAPECC6" scheme="ALE#LI#LF">0000000006</SAP:Party>
<SAP:Service />
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">ORDERS.ORDERS05</SAP:Interface>
<SAP:Mapping notRequired="Y" />
</SAP:Receiver>
Please Suggest the steps needs to be done for resolving the Issue.
Thanks all...
Regards,
Nitin
Edited by: Nitin Patil on Jan 21, 2009 12:18 PMHi Nitin,
I completed the configuraiton but the PO came in PI successfully but stuck in PI with error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Error during parsing of SOAP header</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Error during parsing of SOAP header</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
can you please help what is the problem , I am not able to find out.
Thanks,
Menaga -
HI friends,
Iam facing a problem with a message which is failed at Call Adapter phase of pipeline. The error is as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>00304104-E000-1C91-043C-81C33CF04210</SAP:MessageId>
<SAP:TimeSent>2006-09-01T17:55:04Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>SAPERP_100_X</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">Z_SSC_USER_ROLES</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>C066A_MIIS_D</SAP:Service>
<SAP:Interface namespace="http://mbco.com/humanresources/usermanagement">UsersList_MI</SAP:Interface>
- <SAP:Mapping notRequired="M">
<SAP:ObjectId>0fVlKrKPOra8PalZG0qABQ==</SAP:ObjectId>
<SAP:SWCV>ri/ZsDOqEduXJsPsx74ldQ==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="http://mbco.com/humanresources/usermanagement">UsersList_MI</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>302</SAP:P1>
<SAP:P2>Moved Temporarily</SAP:P2>
<SAP:P3>Redirect</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Http server code 302 reason Moved Temporarily explanation Redirect</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="2006-09-01T17:55:04Z" wasRead="false">
<SAP:Engine type="AE">af.xid.mbsdalxi50</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>00304104-E000-1C91-043C-81C33CF04210</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
- <SAP:Hop timeStamp="2006-09-01T17:55:05Z" wasRead="false">
<SAP:Engine type="IS">is.00.MBSDALXI50</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>00304104-E000-1C91-043C-81C33CF04210</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2006-09-01T17:55:06Z" wasRead="false">
<SAP:Engine type="IS" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
<SAP:MessageId>00304104-E000-1C91-043C-81C33CF04210</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20060901</SAP:Date>
<SAP:Time>125506</SAP:Time>
<SAP:Host>MBSDALXI50</SAP:Host>
<SAP:SystemId>XID</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>014</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>XIAFUSER</SAP:User>
<SAP:TraceLevel>3</SAP:TraceLevel>
<SAP:Logging>1</SAP:Logging>
<SAP:LogSeqNbr>008</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>XBTOI___0000</SAP:QIdInternal>
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="100">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">C7BE2574084844F873FA2EE4</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>89885</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>92145</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>89885</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>85157</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>
<SAP:AdapterOutbound>PLAINHTTP</SAP:AdapterOutbound>
<SAP:InterfaceAction>DEL</SAP:InterfaceAction>
<SAP:RandomNumber>46</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175505.415</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175505.446</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175505.446</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175505.462</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175505.462</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175505.774</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175505.774</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175505.79</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175505.9</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175505.9</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175505.946</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175505.946</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175505.946</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175506.165</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175506.165</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175506.4</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175506.431</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end" host="MBSDALXI50">20060901175506.493</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin" host="MBSDALXI50">20060901175506.54</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>Fatal</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>A87A357B08C7321295F803CCEC380BDC</SAP:OutboundBindingObjectId>
<SAP:FromPartyName />
<SAP:FromServiceName>SAPERP_100_X</SAP:FromServiceName>
<SAP:ToPartyName />
<SAP:ToServiceName>C066A_MIIS_D</SAP:ToServiceName>
<SAP:ToInterfaceName>UsersList_MI</SAP:ToInterfaceName>
<SAP:ToInterfaceNamespace>http://mbco.com/humanresources/usermanagement</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">C066A_MIIS_D</SAP:ServiceName>
<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">HTTP_IB_IAM_USERLIST</SAP:ChannelName>
<SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">HTTP</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">plainHTTP</SAP:MessageProtocol>
<SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">1.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>basicNonSAP</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>contentType</SAP:Name>
<SAP:Value>text/xml</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>copyHTTPDest</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>copyURL</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>dynConfigFailOnMissingProperties</SAP:Name>
<SAP:Value>1</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>enableDynConfigReceiver</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>epilog</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>fifthHeaderFieldRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>fifthURLParamRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>firstHeaderFieldRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>firstURLParamRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>fourthHeaderFieldRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>fourthURLParamRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>headerFieldSelectionRcvr</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>host</SAP:Name>
<SAP:Value>mbsdaliam51.miller.americas.gcn.local</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>httpDestination</SAP:Name>
<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" />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>logonUser</SAP:Name>
<SAP:Value>HS37</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>maskSpecialCharacters</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>messageGuidToQuery</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>path</SAP:Name>
<SAP:Value>/SAP/SAPUserlist.aspx?sapuserlist=</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>port</SAP:Name>
<SAP:Value>80</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>prolog</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>proxyHost</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>proxyPort</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>qosToQuery</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>queueIdToQuery</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>receiverInterfaceToQuery</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>secondHeaderFieldRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>secondURLParamRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>senderPartyToQuery</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>senderServiceToQuery</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>sixthHeaderFieldRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>sixthURLParamRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>thirdHeaderFieldRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>thirdURLParamRcvr</SAP:Name>
<SAP:Value />
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>urlParamSelectionRcvr</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>xmlEncoding</SAP:Name>
<SAP:Value>UTF-8</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="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external = XIParty</Trace>
<Trace level="1" type="T">Receiver agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- <!-- ************************************
-->
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = MBSDALXI50:8000</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 199.190.37.116</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</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="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<Trace level="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="3" type="T">system-ID = XID</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-09-01T17:55:05Z 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 = 00304104E0001C91043C81C33CF04210</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="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = 00304104E0001C91043C81C33CF04210</Trace>
<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="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTI0017</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0017</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = 00304104E0001C91043C81C33CF04210</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">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="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<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="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XID</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-09-01T17:55:05Z 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="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2006-09-01T17:55:05Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2006-09-01T17:55:05Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_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 level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - C066A_MIIS_D</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-09-01T17:55:05Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2006-09-01T17:55:05Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_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 level="2" type="T">Check conditions for (Inb: Party Srvc If) C066A_MIIS_D UsersList_MI</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: UsersList_MI</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-09-01T17:55:05Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- <!-- ************************************
-->
<Trace level="1" type="Timestamp">2006-09-01T17:55:05Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- <!-- ************************************
-->
<Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination</Trace>
<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 = XBTOI___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="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<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="3" type="T">message version successfully read from persist version= 004</Trace>
<Trace level="2" type="T">Increment log sequence to 005</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XID</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-09-01T17:55:06Z 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="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2006-09-01T17:55:06Z CET Begin of pipeline processing PLSRVID = 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="Timestamp">2006-09-01T17:55:06Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping is already determined in the interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping D1F5652AB28F3AB6BC3DA9591B4A8005</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping AE2FD9B033AA11DB9726C3ECC7BE2575</Trace>
<Trace level="1" type="T">Interface Mapping http://mbco.com/humanresources/usermanagement UsersList_IM</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_UsersList_MM_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_UsersList_MM_.</Trace>
<Trace level="3" type="T">Load ae2fd9b0-33aa-11db-9726-c3ecc7be2575, http://mbco.com/humanresources/usermanagement, -1, com/sap/xi/tf/_UsersList_MM_.class.</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_UsersList_MM_.class (http://mbco.com/humanresources/usermanagement, -1) in swcv ae2fd9b0-33aa-11db-9726-c3ecc7be2575.</Trace>
<Trace level="3" type="T">Loaded class com.sap.xi.tf._UsersList_MM_</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._UsersList_MM_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_UsersList_MM_ completed. (executeStep() of com.sap.xi.tf._UsersList_MM_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-09-01T17:55:06Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 005</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2006-09-01T17:55:06Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
<Trace level="2" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
<Trace level="2" type="T">-SAPERP_100_X</Trace>
<Trace level="2" type="T">-C066A_MIIS_D</Trace>
<Trace level="2" type="T">http://mbco.com/humanresources/usermanagement.UsersList_MI</Trace>
<Trace level="2" type="T">Channel found: - C066A_MIIS_D - HTTP_IB_IAM_USERLIST</Trace>
<Trace level="2" type="T">no header mapping defined</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-09-01T17:55:06Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 006</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
- <!-- ************************************
-->
<Trace level="1" type="Timestamp">2006-09-01T17:55:06Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- <!-- ************************************
-->
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS =</Trace>
<Trace level="3" type="T">P_IFNAME =</Trace>
<Trace level="3" type="T">P_METHOD =</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Channel for Plain HTTP adapter: HTTP</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = PLAINHTTP</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_HTTP_PLAIN_OUTBOUND</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type=Hi
According to following link (about HTTP error 302), you have maybe a problem with the user/pwd with your HTTP adapter.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7ccd3e4e-0501-0010-95ae-afa58cb46b75
Else search inside OSS notes with "HTTP error 302" and/or "ATTRIBUTE_SERVER"
Mickael.
No access to service marketplace, for the moment. -
HTTP adapter - 500 Internal server error
Hi Experts,
I have configured a B2B scenarion in which i am using HTTP receiver adapter to send data to vendor.I have checked my configuration every thing is fine but i ended up with the error as below.
SXMB_MONI:
PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER
HTTP server code 500 reason Internal Server Error explanation Internal Server Error
And the queue status is saying red in sxmb_moni also the error in SMQ2 is as follows
XI Error ATTRIBUTE_SERVER.PLAINHTTP_ADAPTER: Queue
I have implemented the notes 804124,807000 but no luck.Also i have restarted the J2EE server and done the soft shutdown but no use.
If i look into th queue scheduler in SMQR its in INACTIVE.
Any hint will be helpful.
Thank YouHi
The Plain HTTP adapter is not part of the adapter framework, so you cannot see anything in the adapter monitor.
Log on to the server, where the XI is installed. Can you ping the receiver host? Can you put the URL of the receiver as browser address, does that work?
HTTP 500 can be any problem at receiver side. Are you sure, that the payload fits to the receiver requirements?
Please refer this thread answered by Stefan Grube
Plain HTTP adapter error
Thanks
Abhishek Mahajan
***Please reward points in case helpful*** -
HTTPS - 500 - Internal Server Error
Hi,
To send XML file over HTTPS, a RFC destination type G is created in SM59 and is used in Plain HTTP receiver Adapter.
Now while testing HTTP destination in SM59, HTTP 200 reponce is OK.
But while sending the XML file, getting an error HTTP 500 - Internal Server Error in SXMB_MONI.
Certificates are installed in STRUST for HTTPS connection.
Any suggetion.
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Internal Server Error</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Internal Server Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
<Trace level="3" type="T">Quality of Service EO</Trace>
<Trace level="1" type="T">Get XML-Dokument from the Message-Objekt</Trace>
<Trace level="2" type="T">HTTP-Destination : EXT_SERVER</Trace>
<Trace level="3" type="T">Server ABCD</Trace>
<Trace level="3" type="T">Service-Nr. 443</Trace>
<Trace level="3" type="T">URL /PATH1/PATH2?Query</Trace>
<Trace level="3" type="T">~request_method POST</Trace>
<Trace level="3" type="T">~server_protocol HTTP/1.0</Trace>
<Trace level="3" type="T">accept: */*</Trace>
<Trace level="3" type="T">quality of service: EO</Trace>
<Trace level="3" type="T">Header-Fields</Trace>
<Trace level="3" type="T">Prolog conversion Codepage: UTF-8</Trace>
<Trace level="3" type="T">Epilog conversion Codepage: UTF-8</Trace>
<Trace level="3" type="T">content-length 2312</Trace>
<Trace level="3" type="T">content-type: text/xml; charset=UTF-8</Trace>
<Trace level="2" type="T">HTTP-Response :</Trace>
<Trace level="1" type="T">Internal Server Error</Trace>
<Trace level="2" type="T">Code : 500</Trace>
<Trace level="2" type="T">Reason: Internal Server Error</Trace>
<Trace level="2" type="T">Code : 500</Trace>
<Trace level="2" type="T">Reason: Internal Server Error</Trace>
Thanks,
MadanHi Madan,
Please have a look at this thread.
Plain HTTP adapter error
Hope this helps to you.
Regards,
P.Rajesh -
HTTP server code 500 reason Internal Server Error explanation Error during
Hi,
I am trying to connect to SAP TM (Tranportation Management) System using HTTP adapter using PI 7.0.The scenario is
ECC ->PI->SAP TM. I have configured HTTP adapter as the receiver with addressing type as HTTP Destination. I have created a RFC destination of type H pointing to SAP TM on PI. I have encountered the following error after executing the scenario.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Error during parsing of SOAP header</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Error during parsing of SOAP header</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
KiranError during parsing of SOAP header
Can you mention what are the settings done in Receiver HTTP channel.....the request that you send to target is not in proper format.
One reason could be incorrect Content Type.....is it text/XML ?
Regards,
Abhishek. -
HTTP server code 500 reason Internal Server Error
HI,
I am getting following error in Call Adapter
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Message canceled
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Internal Server Error</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Internal Server Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have a Business system that is sending the material master data to a different Business System via XI. The message is received by XI correctly. XI correctly performs the transformation and identifies the message interface and selects correct receiver for the message. XI communicates with the receiving business system via the appropriate communication channel.
The message "fails" in the receiving system with the following error:
HTTP server code 500 reason Internal Server Exception explanation Error parsing of SOAP header.
The channel is using HTTP Adapter type, and i cross checked the communication channel details like Addressing type, target host, service number, path, user name, user password.......each and every detail is correct.
Please help me out to find the solution to the problem.
Points will be gladly awarded.
Edited by: Ashish Soni on Sep 24, 2008 9:02 PMtry sending the same XML message picking from moni and check whether you are getting same error or not?
if you get same error then check at web server for logs there you can find exact error. -
Hi all,
I have a scenario in which i am sending an IDoc to a Oracle Table. This sends back an acknowledgement to an HTTP Receiver which is finally sent as an ALEAUD Idoc to the sender system.
The data is getting posted to the table and the acknowledgement is also getting sent.
But the HTTP Server is throwing following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Message ID 071700DC367DAA44A325E05C11D66B14 already exists in called system (pip</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Http server code 500 reason Internal Server Error explanation Message ID 071700DC367DAA44A325E05C11D66B14 already exists in called system (pip</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The path that i have mantioned in the Receiver Communication Channel is:
/sap/xi/adapter_plain?namespace=http://namespace-Idoc2JDBC&interface=ALEAUD_out_asy&service=ITCXI1&QOS=EO
Pls if anybody could guide as to what could be the possible error.
Thanks in advance.
Regards
NeetuHi Neetu,
This SAP Note may help you - 804124
Also make sure that Http server service available. And configuration is correct
Regards,
Moorthy -
Error while connecting to external server through SOAP/HTTP adapter
Hi,
we are trying to connect to the external server through SOAP adapter. The scenario is proxy to SOAP asynchronous scenario.
We are getting following error in Communication channel monitoring:
*Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault*
We also tried HTTP adapter in the receiver side. But it is giving red flag in SXMB_MONI with following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Internal Server Error</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Internal Server Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please help.
Thanks in advance.
Regards,
sriparnaMake sure that the receiver webservice is up and running and in a state to receive the external calls. Confirm if the data you send is as per the requirement of the webservice and they haven't changed anything at their end.
Regards,
Prateek -
Plain HTTP adapter error: Bad Gateway, Proxy Error, please help !
hello all,
i have the following scenario:
filesystem->file adapter->XI->plain http adapter-> receiver system.
the following error occurred while calling plain http adapter:
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_Server</SAP:Code>
<SAP:P1>502</SAP:P1>
<SAP:P2>Bad Gateway</SAP:P2>
<SAP:P3> Proxy Error</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP-Server Code 502 Reason Bad Gateway Explanation Proxy Error</SAP:Stack>
A RFC-Destination with SSL is used in this scenario. Connection test to the destination machine is also succeeded. some files have been transported to the receiver system, yet without payload. data is lost.
anyone has encountered such problem or anybody can tell me please how to solve this problem.
thanks for your help
regardsHi,
I´ve found a SAP-Note concerning this error-message 692057
There is the note 450226 gives an overview over error codes
Probably below solution may help you.........
As an administrator on your portal go to:
System Configuration > Service Configuration >applications
Under: com.sap.portal.ivs.httpservice > Services > Proxy
If any proxy settings are configured you may end up with the problem, so you need to set the "nonProxyHosts" to include the trex host.
After a restart the search was working normally again.
Thanks
Swarup -
HTTP receiver Adapter-- 403-Forbidden-Service Error
Hi ,
Scenario: This is a B2B scenario in which the Sender Party communicates with external partner using HTTPS calls.
I have enabled SSL on ABAP, installed the certificate in STRUST and created an RFC destination of Type G to connect to external system.
<b>Question.</b>
When i do a TEST connection of the RFC destination, the test is successful xith HTTP:1.0 200 OK.
But when i execute my scenario, the message fails in sxmb_moni. with the following error
<SAP:Category>XIAdapter</SAP:Category>
<b> <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>403</SAP:P1>
<SAP:P2>Forbidden</SAP:P2>
<SAP:P3>Service Error</SAP:P3></b>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Http server code 403 reason Forbidden explanation Service Error</SAP:Stack>
Don't know how to proceed about. kindly advice me.
Regards,
Siva MarananiHi,
My problem is solved.
I was getting the following error b'cos the wrong XML document being posted to external serer. When we changed the payload and tested the scenario, its woking fine.
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>403</SAP:P1>
<SAP:P2>Forbidden</SAP:P2>
<SAP:P3>Service Error</SAP:P3>
Regards,
Siva Maranani
Maybe you are looking for
-
How can I stop a program until a button will be clicked
I have a class that create a JTable and in this class I have two columns, the first culumns has the name of the variables an the second column has a checkbox to select the correponding variable.this JTable is created from a vector originating in othe
-
Why is Aperture suddenly asking for serial number?
I have just arrived in the Middle East to shoot some work, opened up Aperture (2) and it's asking for the product serial number. I have been using Aperture for 2 1/2 years and it has never asked me for this. Why is it doing this??? And needless to sa
-
Hi please help me I'm useles with these thing. I've had cydia put on my device didn't like it so deleted ap and now I cant get back into Icloud it's gone very faded in couler the icon in settings. Facebook Twitter and a few others have done the same.
-
The problem about TitleWindow's parent
This problem is confused me. I have main.mxml like this <mx:Application xmlns:mx=" http://www.adobe.com/2006/mxml" layout="absolute" xmlns:v="views.*"> <v:documentsView title="Documents" /> </mx:Application> And from the documentsView component creat
-
Explain Price qty variance account postings...
Hello Could anyone explain the price quantity variance and its account postings. What will happen when: 1. PO for 100 pcs @ 2.0 2. IR for 50 pcs @ 2.2 3. GR For 80 pcs 4. IR again for rest 50 pcs @ 2.2 What will the GR take as a price and what will