GL Interface status code of "P"

I noticed that on our GL_INTERFACE table several records which had the status code of "P" instead of "NEW". Since we have no Oracle documentation (especially the Techinical Reference Manuals),does anybody know or can find out what that code means?
Normally, I would though it means pending. When you import the records, if the transactions have a problem or does not balance, these records remain on the interface. I never though that it will set these records as pending. We were trying to import records from two sources at the same time. One set of records from a source had an invalid flexfield combo. After we fixed the problem, all the transaction processed without an problems and the GL_INTERFACE table cleared.
Is this a new function to 11i? I came from a 10.7.4 NCA enviroment and never seen this before. Thanks for your assistance.
David Correia
System Analysis
NECMSC

hi david,
this feature is also there in 10.7. If any one record contains any problem, then all the records in that batch will be stopped. And once the same is corrected the whole batch will be imported. until then the records will be in status 'P', ie pending. This feature is there in 10.7 also.

Similar Messages

Processing status code error

Hi all,
What does processing status code "Error" indicate in rcv_headers_interface.There is no error message in po_interface_errors.There is nothing available in the log of Receiving Transaction Processor.Can someone guide me what exactly this means?
Thanks in advance!!

Hi Sandy;
Please see below notes which could be helpful
Resolving records stuck in the Receiving Transactions Interface [ID 50903.1]
http://docs.oracle.com/cd/E19509-01/820-4390/ggtrm/index.html
Regard
Helios

37 Status code in IDoc to File Scenario

Hi Experts,
I developed Idoc to file scenario, in the PI side all the design time and configuration objects are good .
while I am testing from SAP backend system (All required configuration steps are also good).
I was send the Vendor information details (CREMAS05) by using the Transaction code WE19 , after that I was test with IDoc list by using Transaction code WE05(IDoc list) I am getting status code 37 . what might be the problem.
please help me.
Thanks in advance,
Regards,
Sudeepth.

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

HTTP response contains status code 404 ...

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

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

Receiver XI adapter error :HTTP Status Code 200 during Reponse Parsing

Hi Exeprts,
My Scenario is mail to ABAP proxy , I have got the bellow error in moni while testing my secnario .
Please help me reslove this .
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">OK_BUT_NO_XI_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Regards
Upendra

Hi Mark ,
No error message in attachement . only it daisplay the following information
SAP Library
SAP Library contains the complete documentation for SAP NetWeaver Application Server Java. You can access it by choosing SAP NetWeaver.
      SAP NetWeaver Administrator
A powerful administration, configuration and monitoring tool, which bundles key administrative tasks to keep your SAP NetWeaver system landscape running. SAP NetWeaver Administrator can be used in a central or local scenario. Here you access the local NetWeaver Administrator.
    System Information
System information provides administrators with an overview of the system configuration and its state. It shows all of the system's instances and processes, their current state and important parameters (such as ports) that may be required for support cases, as well as the versions of the components installed.
      Services Registry
The Services Registry is a UDDI based registry that contains definitions of enterprise services and references to their metadata.
   User Management
The user management administration console provides administrators with the functions they need to manage users, groups, roles, and user-related data in the User Management Engine (UME). Users without administrator permissions can use it to change their user profile.
      UDDI Client
The UDDI client provides query and publishing functions for UDDI entities to any UDDI compliant registry.
   Web Services Navigator
Web Services Navigator is a tool that gives you a short overview of a specific Web service based on its WSDL, and enables you to test your Web service by creating and sending a client request to the real end point.
      Web Dynpro
Web Dynpro is a User Interface technology available within the SAP NetWeaver Developer Studio.
Various Web Dynpro tools provide administrators and application developers with performance measurement and application administration capabilities. The Web Dynpro runtime is already deployed.
Regards
Upendra

ADF Mobile: HTTP Status Code 500 Internal Server Error

Hi,
I wrote a SOAP web service and deployed it to my standalone ADF Server. I tested it with the HTTP Analyzer, works great. I used it in a Web Service Data Control in normal ADF Web - works perfect. It returns a table of data as programmed. However, ADF Mobile gives me errors: "Http Status Code 500 Internal Server Error: The server encountered an unexpected condition which prevented it from fulfilling the request".
I developed an ADF Mobile interface with an amx page. I created the same Web Service Data Control and created a List View based on the data control. The error pops up every single time, both on iOS simulator and Android Simulator.
I know the simulators have network access to the web services - because i can open the web service test page and WSDL from both simulator's internet browsers.
I know the web services are running - because my ADF Web application can access it.
Any ideas?
Thank you!
-Gavin

Thanks for the reply. There were no errors in my WLS server. However, I will add some statements to my web service to write to the log file. That way i can see if or at what point is the web service is being accessed by the mobile app.
Thanks,
Gavin

HTTP Status Code 200 Received But Error During Response Parsing

Hi Experts,
We are testing a simple Proxy(ECC) to File scenario in QA. This interface was working fine in Dev but we are getting the following error here in QA:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">OK_BUT_NO_XI_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
We searched other threads but could not get any solution. Please provide suggestions.
Thank You.
Regards,
Anandan

the problem was due to high volume message (247 MB ) ...Java stack was not able to process this huge message ,that is the reason ,it started automatically and as a result , "HTTP Status Code 200 Received But Error During Response Parsing" due to unavailability of AFW during Call adapter step in the pipeline processing...
We have done the following activities in order to solve this problem....
increase the value of icm/HTTP/max_request_size_KB to 512MB
                                    icm/wp_roll_timeout   to maximum
                                    HTTP TIMEOUT to 1800 sec
                                   icm/wp_roll_timeout   to maximum
                                     mpi/total_size_MB to maximum
                                   mpi/buffer_size to maximum
and then increased the maxthreadcount ,maxcontentlength using config tool...
and also increased the java heap size to maximum....
After doing everything ,the file has been successfully processed....
the problem has been resolved...

OSB: Retrieve non XML Payload from a service that returns status code 500

Hello,
I'm using OSB 11g.
I have a Business Service that invokes a REST based service (AnyXML). The service I'm calling may return a 500 status code and some JSON-encoded information in the response body containing the remote service error information.
From a Proxy Service, I invoke the Biz Service using a standard Service Call Out. The Call Out works fine if the service doesn't return any error (status code 200).
The problem starts when the service returns a 500 status error: it seems that there is no way to to get hold of the error information (string) that are in the response body. The $fault variable contains some info, but not the actual payload.
I have also tried to "resume" the flow (using a resume action) but no luck.
Is there a way to retrieve a NON-XML payload of a service even if the service returns a 500 status code?
Thanks
Luciano

Hi,
I have same problem, any idea?
I created several Proxy Services between SOA (BPEL) and JDE. Proxy Service works correct, but if interface response has an error (fault) from JDE side, we get high level error message from OSB and we lost error information from endpoints. I want to get following error information from response body, which containing the remote service error information.
e.g. <SOAP-ENV:Fault>:
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Client</faultcode>
<faultstring>[ISS.0088.9134] Exception occurred while processing the body of the message</faultstring>
<faultactor>http://HOST/soap/default</faultactor>
<detail xmlns:webM="http://www.webMethods.com/2001/10/soap/encoding">
<webM:exception> </webM:exception>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Until now, I solved errorhandling for Proxy Service with single route node, but if I use Proxy Service for “Failover” and OSB connect to Endpoint 2, BPEL-instances with "fault" state get OSB error message and WSG-Response will be lost from $body of messages.--> error-propagation to client is NOT OK.
Regards,
Moh

Cisco Catalyst 6500 version 12.2(33)SXI13 configured as DHCP server for a VLAN responds to Windows 7 client with status code NOA

Can anyone help figure out why the Catalyst 6509 is not able to assign an IPv6 address? Thank you.
Cisco Catalyst 6500 version 12.2(33)SXI13 configured as DHCP server for a VLAN responds to Windows 7 client with status code NOADDRS-AVAIL(2). My configuration on the 6500 for the DHCPv6 server is:
ipv6 dhcp database disk0://DHCPV6-DB
ipv6 dhcp pool VLAN206IPV6
prefix-delegation pool VLAN206IPV6-POOL
dns-server 2620:B700:0:1001::53
domain-name global.bio.com
ipv6 local pool VLAN206IPV6-POOL 2620:B700:0:12C7::/65 65
interface Vlan206
description *** IPv6 Subnet ***
ip address 10.2.104.2 255.255.255.0
ipv6 address 2620:B700:0:12C7::2/64
ipv6 nd prefix 2620:B700:0:12C7::/64 14400 14400 no-autoconfig
ipv6 nd managed-config-flag
ipv6 dhcp server VLAN206IPV6
standby version 2
standby 0 ip 10.2.104.1
standby 0 preempt
standby 6 ipv6 2620:B700:0:12C7::1/64
standby 6 preempt
I'm getting a result from my debug as follows:
Apr 10 16:28:02.873 PDT: %LINK-3-UPDOWN: Interface GigabitEthernet2/2, changed state to up
Apr 10 16:28:02.873 PDT: %LINK-SP-3-UPDOWN: Interface GigabitEthernet2/2, changed state to up
Apr 10 16:28:02.877 PDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2, changed state to up
Apr 10 16:28:03.861 PDT: IPv6 DHCP: Received SOLICIT from FE80::5D5E:7EBD:CDBF:2519 on Vlan206
Apr 10 16:28:03.861 PDT: IPv6 DHCP: detailed packet contents
Apr 10 16:28:03.861 PDT: src FE80::5D5E:7EBD:CDBF:2519 (Vlan206)
Apr 10 16:28:03.861 PDT: dst FF02::1:2
Apr 10 16:28:03.861 PDT: type SOLICIT(1), xid 8277025
Apr 10 16:28:03.861 PDT: option ELAPSED-TIME(8), len 2
Apr 10 16:28:03.861 PDT: elapsed-time 101
Apr 10 16:28:03.861 PDT: option CLIENTID(1), len 14
Apr 10 16:28:03.861 PDT: 00010001195FD895F01FAF10689E
Apr 10 16:28:03.861 PDT: option IA-NA(3), len 12
Apr 10 16:28:03.861 PDT: IAID 0x0FF01FAF, T1 0, T2 0
Apr 10 16:28:03.861 PDT: option UNKNOWN(39), len 32
Apr 10 16:28:03.861 PDT: option VENDOR-CLASS(16), len 14
Apr 10 16:28:03.861 PDT: option ORO(6), len 8
Apr 10 16:28:03.861 PDT: DOMAIN-LIST,DNS-SERVERS,VENDOR-OPTS,UNKNOWN
Apr 10 16:28:03.861 PDT: IPv6 DHCP: Option IA-NA(3) is not supported yet
Apr 10 16:28:03.861 PDT: IPv6 DHCP: Sending ADVERTISE to FE80::5D5E:7EBD:CDBF:2519 on Vlan206
Apr 10 16:28:03.861 PDT: IPv6 DHCP: detailed packet contents
Apr 10 16:28:03.861 PDT: src FE80::21D:E6FF:FEE4:4400
Apr 10 16:28:03.861 PDT: dst FE80::5D5E:7EBD:CDBF:2519 (Vlan206)
Apr 10 16:28:03.861 PDT: type ADVERTISE(2), xid 8277025
Apr 10 16:28:03.861 PDT: option SERVERID(2), len 10
Apr 10 16:28:03.865 PDT: 00030001001DE6E44400
Apr 10 16:28:03.865 PDT: option CLIENTID(1), len 14
Apr 10 16:28:03.865 PDT: 00010001195FD895F01FAF10689E
Apr 10 16:28:03.865 PDT: option STATUS-CODE(13), len 15
Apr 10 16:28:03.865 PDT: status code NOADDRS-AVAIL(2)
Apr 10 16:28:03.865 PDT: status message: NOADDRS-AVAIL

Hello,
maybe hitting the following bug.
Pv6 Address Assignment Support for IPv6 DHCP Server
CSCse81385
Hope this helps

INTERNAL.HTTP_RESP_STATUS_CODE_NOT_OK HTTP response contains status code 50

Hi Gurus,
I am getting error message "INTERNAL.HTTP_RESP_STATUS_CODE_NOT_OK HTTP response contains status code 500 with the description Timeout" when I call a proxy to retrieve data from external database (oracle) through XI (Synchronous Call). This proxy works fine if the data size is limited to 120 MB but terminates with above message if data size is larger may be > 130 MB but some time it works as well with this data size.
Me & our basis team are working hard to fine out the issue but still could not succeeded. we have applied the OSS Note 807000 but still we are getting the error message. To make it more clear I am sending SQL Query to Reciever (Oracle) from SAP through ABAP proxies.
If I check the status of messages in "Monitor for processed XML messages" the message has status icon which says "Log version" I am new in XI Please help me to solve the issue.

hey...try increasing the synchronous timeout parameter. I think the default is 180 secs.
I would suggest you look at redesigning the the interface to pull the data in smaller pieces...120 Mb is really big...Pi gives max throughput at around 5 mb...
Dont worry about the log version....It just persisted in the system when a job is still running... try looking at the same message after a while...it would have changed its stsatus.
Arvind R

Status codes in Purchase Order Response screen

Hello,
I still relatively new to SRM and have a question on how the status codes on the purchase order response screen works.
Specifically what is the logic / selection criteria for "Variance in Purchase order Response"? My initial analysis is that this displays variance against the Original PO values rather than the current PO values if they have been updated to matched the POR.
Thanks
Gary

Thanks Ravi but I belive that we do not use SUS. Suppliers interface with SRM via a web portal.
Any suggestions where I can find detailed user / functional documentation on what each of the search parameters mean ?
Thanks again
Gary

HTTP Error with Status code 403 when using ABAP Server Proxies

Hi All,
I have been working on ABAP Client and Server proxies in my project. The weblogs by Ravikumar, Prateek Shah, Siva Maranani & VijayaKumari were very helpful and thank them all for just helpful and guiding postings.
Interfaces using Client proxies are working fine and have been tested successfully. But I'm facing bit problems with Server Proxies. The scenario is of File to SAP system via XI. Data is coming correct up to Technical routing in pipeline but at call adapter(for Server Proxy to SAP)in XI pipeline I receive Error:
HTTP response contains status code 403 with the description Business Server Page (BSP) Error Error when sending by HTTP (error code: 403, error text: Business Server Page (BSP) Error)
Previously I was receiving authentication and authorization related error of status code 401 and then in communication channel I replaced user profile with a user id having role SAP_XI_APPL_SERV_USER. The basis peron has created new user id with role SAP_XI_APPL_SERV_USER only and that I'm using. I've tried creating a HTTP destination with the created user id and in test connection too receive same error message.
Please help me out with your inputs and understanding on the topic.
Thanks and Best Regards
Prashant Rajani

Hi Prashant,
Please take a look at these threads..They deal with the same problem, and they have been resolved here.
BSP Authorization error
Service cannot be reached . error code 403 the reason forbiddn
403 Error when accessing the server
Hope your issue gets resolved.
cheers,
Prashanth
P.S Please mark helpful answers

"UnexpectedHTTP Response - Status Code:200" error with Yahoo mail.

I am getting constant error "UnexpectedHTTP Response - Status Code:200" error with Yahoo mail. Is it some known error?
I have a snapshot of issue but there is now way I could attach that with this query. This happens more often after I login into yahoo and try to delete my mails or delete my spam mails or go to inbox etc...
Thanks,
Santosh Thankachan

EXACT, but the interface monitor shows that as an error.
And that's what I need, a good monitoring, that should not appear as an error

Sharepoint 2013 webDAV PROPPATCH fails with status code 409 error every time when trying to set custom property.

Sharepoint 2013 webDAV PROPPATCH fails with status code 409 error every time, when trying to set custom property.
anyone have any idea

Hi
Stumbled upon the resolution myself. The Bean Area item needs to be set to Visible=Yes in the property palette for the bean within Forms Builder, and also the implementation class also in the bean's properties must match exactly the package & class name specified in the PJC (my full implementation class string had to be set to oracle.forms.demos.runApplication).
As this bean has no user interface component, and since the Visible property has to be set to Yes, to avoid having a random square shape for the bean sitting on the form's canvas, I also set the Width and Height properties for the bean to 0.001. This does show a very small dot on the form, but that will be acceptable.
So in summary there has been a change for PJC / Bean Areas between 6i and 10g Forms, in 6i you could have the Bean Item to be set Visible=No, and the SET_CUSTOM_ PROPERTY built-in would work, however in 10g Forms the Bean Item must be set to Visible=Yes for the SET_CUSTOM_PROPERTY built-in to work.
Daryl

Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http status code and text is 400, Bad Request.

Hi All,
I am seeing the following error for SMS_AWEBSVC_CONTROL_MANAGER component with Message ID: 8100
Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http status code and text is 400, Bad Request.
awebsctl.log file has below errors:
Call to HttpSendRequestSync failed for port 80 with status code 400, text: Bad Request
SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
13920 (0x3660)
AWEBSVCs http check returned hr=0, bFailed=1
SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
13920 (0x3660)
AWEBSVC's previous status was 1 (0 = Online, 1 = Failed, 4 = Undefined)
SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
13920 (0x3660)
Health check request failed, status code is 400, 'Bad Request'.
SMS_AWEBSVC_CONTROL_MANAGER 12/22/2014 3:37:55 PM
13920 (0x3660)
Management point and Application Catalog Website Point are installed on the same Server where I am seeing the error for Application Catalog Web Service Point role. Management Point and Application Catalog Website Point are functioning properly. Application
Catalog Website is working.
Thanks & Regards, Kedar

Hi Jason,
Application Catalog Web Service Point and Application Catalog Website Point; both are installed as per below configuration on same Server:
IIS Website: Default Web Site
Port Number: 80
with default value for Web Application Name configured.
For SMS_AWEBSVC_CONTROL_MANAGER component, I am getting below error in Component Status:
Application Web Service Control Manager detected AWEBSVC is not responding to HTTP requests. The http status code and text is 400, Bad Request.
Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which AWEBSVC is configured to communicate.
Solution: Verify that the designated Web Site is configured to use the same ports which AWEBSVC is configured to use.
Possible cause: The designated Web Site is disabled in IIS.
Solution: Verify that the designated Web Site is enabled, and functioning properly.
For more information, refer to Microsoft Knowledge Base.
And awebsctl.log has the below error lines:
Call to HttpSendRequestSync failed for port 80 with status code 400, text: Bad Request
SMS_AWEBSVC_CONTROL_MANAGER
12/23/2014 11:04:36 AM 16388 (0x4004)
AWEBSVCs http check returned hr=0, bFailed=1
SMS_AWEBSVC_CONTROL_MANAGER
12/23/2014 11:04:36 AM 16388 (0x4004)
AWEBSVC's previous status was 1 (0 = Online, 1 = Failed, 4 = Undefined)
SMS_AWEBSVC_CONTROL_MANAGER
12/23/2014 11:04:36 AM 16388 (0x4004)
Health check request failed, status code is 400, 'Bad Request'.
SMS_AWEBSVC_CONTROL_MANAGER
12/23/2014 11:04:36 AM 16388 (0x4004)
STATMSG: ID=8100
What should I check from IIS side?
Application Catalog Website is functioning properly.
Thanks & regards,
Kedar
Thanks & Regards, Kedar

GL Interface status code of "P"

Similar Messages

Maybe you are looking for