Error in message processing

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.

Similar Messages

  • Mail on success or error in message processing

    Hi experts
    I need to configure a scenario
    1. Receive idoc from an SAP system
    2. Convert the Idoc into File and Place it in the NFS File directory.
    3. On success of the message, I need to mail to SAP Owner regarding the success of the message.
    4. On error as well , i need the error details to the SAP Owner.
    I had configued all the basic steps in IR. I had struck with the BPM part.
    Please suggest with the steps in the BPM.
    Thnz

    hi Mohamed,
    For sending the mail on success or error in message processing you need to go to the runtime workbench and configure the scenario for mail alerts.
    You need to create the alert rules for the success scenario and the failure scenario.
    While creating the rules you can specify the message id's to which the mail should be sent.
    Please refer to the below link for more clarification.
    http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
    Kindly search SDN also as there are several threads in the forum answering the same question.
    Regards,
    Alpa.

  • 'Job Management' Work Center - Error in Message processing

    Hi,
    I'm trying to create a change request in the 'Job management workcenter, when I try to edit/view the job it throws me an error "Your are not allowed to process the message". How do I resolve this?
    Thanks & Regards,
    Esha Raj

    Hello,
    as the Job Request is a CRM message at the end (usually of transaction type SLFN or rahter SLFJ) you have to configure your assigned business partner properly (in transaction BP). Your business partner has to be configured as employee so that he is allowed to process CRM messages. It is basically the same configuration required as for the SAP Service Desk.
    Best Regards
    Volker

  • Errors in message processing

    if in atypical case 100 files have been sent to the receiver side and later it is found that 10 files had errors, how to identify the names of the files which had errors .

    The error you mean the some busniess error right?
    these are the steps with which you can get the filename alone
    /people/jayakrishnan.nair/blog/2005/06/20/dynamic-file-name-using-xi-30-sp12-part--i - Dynamic File Name Part 1
    /people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii - Dynamic File Name Part 2
    so what you have to do it check the logic in the mapping which detemines the erorr busniess in your strucutre which hold the error mesage add the filed filename and pass the filename to this strucutre....
    i think this should work...

  • AS2 adapter error during inbound processing

    Hello,
    We have upgraded PI to version 7.1 and now we are testing the Seeburger AS2 adapter.
    We have received a testmessage from an AS2 partner and it is shown in the message monitoring of the Seeburger adapter workbench, with status succesfull.
    Only the message is not on the integration server. The message is not shown in sxmb_moni or the message monitor of the RWB.
    In the RWB the communication channel (CC_AS2_Sender) gives the following error:
    "Message inititiation failed: Processing error"
    The message itself gives the following error:
    "Inbound message processing failed! performing rollback
    Can anyone help us with this?
    Thanks in advance.
    Regards,
    Marco

    Hi Marco,
    the message is not forwarded to the intergration egine because there might be an error in your communication channel.
    Are there any other modules in the module chain of this communication channel?
    Can you check "default_trace" and "application_log" for exceptions (/j2ee/cluster/serverXX/log)?
    Did you also restart the Java Stack after the Upgrade?
    regards,
    Daniel
    Edited by: Daniel Rexter on Jun 30, 2010 2:59 PM

  • Message processing failed: Invalid http response: 220

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

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

  • I am trying to order a book, I keep getting the same error message," A network error occurred while processing your order, please check your network connection and try again"

    I am trying to order a book with iphoto, I keep getting the same error message.
    " A network error occurred while processing your order, please check your network connection and try again"
    I get the billing part up, it has even uploaded my jpegs but at the final process, I get the same message.
    I have ordered two books a few months ago without any problems.
    Now I keep getting the same message either half way into
    the order or at the final hurdle after the images have been uploaded.
    Any ideas?
    My shared Network has been fine and that does'nt seem an issue.
    Help.

    Try again in a couple of hours - sometimes it is a temp condition
    LN

  • Getting Err  : An error occurred in the message processing program.

    Hi, Im wrking with Smartforms.
    I have assigned output type LD00 ,with driver prgrm name and Smf name.
    after that executing with VL03N , its giving error .
    Output could not be issued
    Message no. VL086
    Diagnosis
    An error occurred in the message processing program.
    Procedure
    Contact your system administrator.
    ...Actually i have orginal prgrm (zsmf_Orginal) there i had to do some modifications , so after copying that same form into another form(zsmf_Duplicate), i made some changes there, both form are executing in T code SMARTFORMS, but while testing with VL03N , its showing above mentioned err.
    Plz have eye on it.
    <removed by moderator>
    Regards
    vivek.
    Edited by: vivekd358 on Jul 10, 2010 7:35 AM
    Edited by: Thomas Zloch on Jul 12, 2010 11:35 AM

    closed

  • Error in service desk while message processing.

    Dear Basis Guru,
    I have tried to configure the standarad servie desk scenario in solution manager 7.0 EHP1 stack 22.
             The end users are able to raise the message ( both without sap gui and from sap gui )
             Messages are properly getting routed to support teams.
             Message processesor is able to process the mesage ( can reply , can change the status of message ) from sap gui    only .
    But message processor is not able to process the message without sap gui ( thorough web link ).
    Link - http://solprodhml.hmldm.com:8003/sap/bc/webdynpro/sap/ags_workcenter?sap-client=113
    When mssage processor try to change status or propiry through web link following error occurs .
    The URL http://solprodhml.hmldm.com:8003/sap/bc/webdynpro/sap/ags_incident_trans was not called due to an error.
    Note
    The following error text was processed in the system HSP : Could not find attribute ATTR_00000001
    The error occurred on the application server SOLPRODHML_HSP_03 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: IF_WD_CONTEXT_NODE_INFO~GET_ATTRIBUTE of program CL_WDR_CONTEXT_NODE_INFO======CP
    Method: IF_WD_CONTEXT_ELEMENT~GET_ATTRIBUTE of program CL_WDR_CONTEXT_ELEMENT========CP
    Method: UPDATE_BP_EVENT of program /1BCWDY/B33K1JXKX4WX14T8Y3RC==CP
    Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/B33K1JXKX4WX14T8Y3RC==CP
    Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_VIEW========CP
    Method: FIRE_EVENT of program CL_WDR_COMPONENT==============CP
    Method: IFWDR_INTERNAL_API~RAISE_EVENT of program SAPLWDR_RG_PROXY_FACTORY
    Method: IF_COMPONENTCONTROLLER~FIRE_UPDATE_BP_DETAIL_EVT of program /1BCWDY/B33K1JXKX4WX14T8Y3RC==CP
    Method: REFRESH_ONE_ORDER_OBJECT of program /1BCWDY/B33K1JXKX4WX14T8Y3RC==CP
    Method: IF_COMPONENTCONTROLLER~REFRESH_ONE_ORDER_OBJECT of program /1BCWDY/B33K1JXKX4WX14T8Y3RC==CP
    In system st22 shows following dump : -
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_WD_CONTEXT
    Client.............. 113
    User................ "KPIT_PR2"
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "2A02CFE040A5F108B31F18A905457F24"
    Program............. "CL_WDR_CONTEXT_NODE_INFO======CP"
    Screen.............. "SAPMHTTP 0010"
    Screen Line......... 2
    Information on Caller ofr "HTTP" Connection:
    Plug-in Type.......... "HTTP"
    Caller IP............. "192.168.0.145"
    Caller Port........... 8003
    Universal Resource Id. "/sap/bc/webdynpro/sap/ags_incident_trans"
    Please help
    Thanks,
    Rusi123

    Hi
    Please find the reply in Bold :
    What Sol Man release are you workin on?
    SAP Solution Manager 4.0
    What kind of characters get truncated?
    General message characters (English alphabets)... is this because of length constraint?
    Are you working on a unicode system?
    Yes
    Does this happen while creating messages from a satellite system or from within Sol Man?
    When user creates messge in SAP ECC 6.0 , then the sme of the last characters of each row gets truncated.
    Best regards
    Sarang

  • Message processing failed, FTP Receiver Adapter error...

    Hello all,
    We have a Idoc to File(FTP) scenario using PI.
    When PI try to send the file out to the FTP site, we get the following message in the communication channel monitoring and the file never reach the FTP site:
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error when getting an FTP connection from connection pool: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: ConnectException: Connection timed out: connect
    When we look at the detail display, we can see that the connection as been establish with the FTP site but the adapter is unable to deliver the file...
    Any Idea why?
    Thanks in advance.

    Hi ,
    There are two things that you can do
    1- check the connection of FTP from command prompt. If it is acceebile from command prompt then check for authorization that wether you have access to post the file at FTP or not (Full access READ , WRITE and EXCECUTE)
    2- in your adpater change the connection mode from Per file transfer to "Permanent".
    Please feel free to reply on this thread if you are not able to.
    Thanks

  • Error receiving AS2 message from partner: B2B-50037:  B2B inbound message processing error

    B2B/SOA 11.1.1.6.0
    We are setting a new trading partner and when we started document transmissions we are getting errors on the inbound messages: B2B-50037:  B2B inbound message processing error.
    The attachment shows the relevant lines from the soa log and diagnostic log files.  Here is the error detail that shows:
    [URI: /b2b/httpreceiver] Error -:  B2B-50037:  B2B inbound message processing error[[
    Error -:  B2B-50037:  B2B inbound message processing error
            at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:3143)
            at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1650)
            at oracle.tip.b2b.transport.InterfaceListener.onMessageLocal(InterfaceListener.java:403)
            at oracle.tip.b2b.transport.InterfaceListener.onMessage(InterfaceListener.java:214)
            at oracle.tip.b2b.transport.basic.TransportServlet.doPost(TransportServlet.java:754)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
            at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
            at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
            at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
            at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
            at java.security.AccessController.doPrivileged(Native Method)
            at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
            at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
            at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
            at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
            at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
            at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
            at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
            at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
            at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    From the b2b_wire_message we get these Protocol_Transport_BINDINGS:
    ChannelName=TransportServlet
    Reverse-Via=LIN-ISA1
    AS2-To=accobra.....
    Date=Fri, 26 Sep 2014 05:46:17 +0000
    AS2-Version=1.2
    AS2-From=K.......
    Disposition-Notification-Options=signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, sha1
    Disposition-Notification-To=http://<ip&port>/as2in
    Message-ID=<[email protected]>
    MSG_RECEIVED_TIME=Fri Sep 26 00:46:17 CDT 2014
    ECID-Context=1.0050z5j^buc6yGn6wnZf6G0002f60007bt;kXjE1ZDLIPGIj2QCYV8QoKSSmLRO_PQT_IS
    Content-Type=application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m
    Proxy-Client-IP=172.17.25.101
    MIME-Version=1.0
    User-Agent=e-integration AS2 Server V 6.1.8
    X-Forwarded-For=172.17.25.101
    Content-Length=3602
    Host=nalinsoa05.abd.ad.acco.com
    x-weblogic-cluster-hash=QoZzGUzdcjBD5fGIE8Uos5abiHI
    EDIINT-Features=multiple-attachments, CEM
    Connection=Keep-Alive
    X-WebLogic-KeepAliveSecs=30
    X-WebLogic-Request-ClusterInfo=true
    The message creates a wire message, business message, and an application message.
    What doesn't happen is no MDN gets sent back to the partner.  It should be a synchronous MDN.
    We have double checked the certificates on both ends and they are OK.
    The document and Agreement get recognized OK:
    Refer To Message
    Refer To Message
    Sender Type
    AS2 Identifier
    Sender Value
    K. . .
    Receiver Type
    AS2 Identifier
    Receiver Value
    accobr. . .
    Sender
    K. . . l
    Receiver
    ACCO . . .
    Agreement Id
    K. . .l_EDI_X12_4010_856_856Def_Inbound
    Agreement
    K. . .l_EDI_X12_4010_856_856Def_Inbound
    Document Type
    856
    Document Protocol
    EDI_X12
    Document Version
    4010
    Message Type
    REQ
    Direction
    INBOUND
    State
    MSG_ERROR
    Acknowledgement Mode
    SYNC
    Response Mode
    ASYNC
    Send Time Stamp
    09/26/2014 12:46:17 AM
    Receive Time Stamp
    09/26/2014 12:46:17 AM
    The error is vague enough to provide little or no help in locating the root cause of the issue.
    Any assistance in providing information on how to get this working would be greatly appreciated.
    We do have dozens of other AS2 partners working in this instance just foe reference.  We are just having issues with this new partner setup.
    Thank you.
    Regards,
    Ken

    Ken,
    I am observing the Ack Mode is set as "SYNC" . This is selected by default. This option is available in the channel configuration section
    If the usecase is not SYNC, please change as ASYNC and test. It should work.

  • Hello dps team,  A few weeks ago we renewed our dps licence. Now we want to release our newest issue but we can't. Following error message appears "At the attempt to release the folio creates an error. The process could not be started. Please try again la

    Hello dps team,
    A few weeks ago we renewed our dps licence. Now we want to release our newest issue but we can't. Following error message appears "At the attempt to release the folio creates an error. The process could not be started. Please try again later."
    Is there a problem with our dps version or any maintenance work at the servers from Adobe?
    Best,
    Oliver

    Hi Oliver,
    Please login to your DPS dashboard and contact support by clicking "Contact support" at the bottom left
    Thanks
    Lohrii

  • Today is April 10, 2013. I try to login to iTunes connect and I keep getting the message "An error has occurred processing your request. Please try again later or send an email for assistance." It never tells us what email address we need to write to.

    Today is April 10, 2013. I try to login to iTunes connect and I keep getting the message "An error has occurred processing your request. Please try again later or send an email for assistance." It never tells us what email address we need to write to.

    The problem was solved by Apple Technical Help. The process is as flollows:
    1. Open Safari
    2. Menu item Safari-Reset Safari - remove all website data - reset
    3. Now if you try to login on iTunes connect it will work.

  • Error in 'eMail Response - Process Message' --- Error running sub-process 'eMail Response - Create Activity' at step 'Create Activity Process'.(

    Hi,
    When I was simulating the 'eMail Response - Process Message', I had been getting the below error when entering to 'Create activity Process' step.(provided all the inputs per testmode.xml file)
    Error running sub-process 'eMail Response - Create Activity' at step 'Create Activity Process'.(SBL-BPR-00183)
    I increased the log level to 5 and got the below message in log file
    ObjMgrBusServiceLog    InvokeMethod    4    0000000251b51f04:0    2013-06-10 01:30:12    Begin: Business Service 'XML Hierarchy Converter' invoke method: 'DocToHier' at 12cc4240
    ObjMgrBusServiceLog    Error    1    0000000251b51f04:0    2013-06-10 01:30:12    (xmlcnvsv.cpp (548)) SBL-EAI-00246: XML Hierarchy Converter error - empty input message, expecting an XML document in <Value> of input arguments
    I was wondering I could not find 'XML Hierarchy Converter' business service in 'eMail Response - Process Message' and 'eMail Response - Create Activity' sub process.
    Can any body help me out in this regard.
    Thanks in advance..
    Jagadeesh

    Hi Naresh,
    yes, I am using the delete polling strategy. Here is the .jca file:
    <adapter-config name="Pozadavky" adapter="Database Adapter" wsdlLocation="Pozadavky.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
    <connection-factory location="eis/DB/PozadavkyConn" UIConnectionName="PozadavkyConn" adapterRef=""/>
    <endpoint-activation portType="Pozadavky_ptt" operation="receive">
    <activation-spec className="oracle.tip.adapter.db.DBActivationSpec">
    <property name="DescriptorName" value="Pozadavky.Pozadavky"/>
    <property name="QueryName" value="PozadavkySelect"/>
    <property name="MappingsMetaDataURL" value="Pozadavky-or-mappings.xml"/>
    <property name="PollingStrategy" value="DeletePollingStrategy"/>
    <property name="PollingInterval" value="120"/>
    <property name="MaxRaiseSize" value="1"/>
    <property name="MaxTransactionSize" value="10"/>
    <property name="NumberOfThreads" value="1"/>
    <property name="ReturnSingleResultSet" value="false"/>
    </activation-spec>
    </endpoint-activation>
    </adapter-config>

  • Error Occured While Processing Dimension Message:

    Hi
    I got error occured while processing Account dimension message (when pressed save and process)
    Next,what are the steps to be followed;
    rgds
    srinath
    Edited by: srinathgb on Dec 18, 2011 1:20 PM

    Hi Nilanjan
    Its true, we cannot delete master if there are any transactional data. For Eg:System is giving message for such cases and it will revert in such cases & will not allow us to delete.(Atleast give relevant msg in such cases)
    Rgds
    Srinath
    Edited by: srinathgb on Dec 19, 2011 5:58 AM

Maybe you are looking for

  • Error while updating information at My Information page

    Hi, We are facing one exception while updating user information at 'My Infomation' page in section - 'Basic User Information' In UI once we click on 'Apply' button we are getting exception as -  IAM-3050117 : Cannot delete mandatory attribute Role. I

  • JSF 1.2 web.xml configuration parameters

    Actually, I know these JSF 1.2 web.xml configuration parameters: javax.faces.CONFIG_FILES javax.faces.DEFAULT_SUFFIX javax.faces.LIFECYCLE_ID javax.faces.STATE_SAVING_METHOD Are there any more available? (I have to study its performance implications

  • Opening a link in a new window puts its entry in history while browsing in private mode.Does it suppose to work in this way?

    <blockquote>Locking duplicate thread.<br> Please continue here: [/questions/785616]</blockquote><br> I have set Firefox to never remember history.This is equivalent to private browsing but whenever I open a link in a new window I can see an entry in

  • Adobe Photoshop 9 Install Issues

    I upgraded to a new laptop.  I can't install a licensed version of Adobe Photoshop Elements 9.  I receive this message below.  Since its a new laptop, there isn't a previous version installed, and since I'm installing from a CD it can't be corrupt. 

  • Form and the get method

    I am using a simple form with one dropdown menu and one submit button. The form uses the get mothod to send the menu id to another page. The form must also get another value and send it along with the selected menu value. The missing value will come