Integration Server Queues Stopping

Hi People,
We are doing a FCC scenario (.CSV to XML), with the content conversion parameters as follows:
Recordset Name: Recordset
Recordset Structure: DataTable1,1
Recordsets per message: 1
As it is clear from the configuration, <b>when the source file will contain multiple line items, XI will create multiple XML files, each containing data for a single line item.</b> My problem is, <b>whenever the source file contains a large number of line items, I see them being picked up (In SXMB_MONI), but the Integration Server inbound queues stop and they show a green flag in MONI with tooltip "Message Scheduled On the Outbound Side". I have to go to SMQ2 and manually activate the queues to release the blocked messages.</b> How to alleviate this problem..because it is really irksome to go and everytime manually activate the queues. Is there any report that can be scheduled so that it caueses the queues to activate automatically when they are blocked?
P.S: We can not change the design. Also, I have seen
<a href="/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically">Naveen Pandarangi's Blog On XI Message re-Scheduling</a>..but the report stated there is not working out for me!
Awaiting your expert views,
Thanks in anticipation,
Regards,
Amitabha

Hi Shabarish,
I followed your instructions, but they did not work out for me...the problem still persists!
Regards,
Amitabha

Similar Messages

  • Integration Server Service 9.3.1 (EIS) entering a stopped state

    Integration Server Service (EIS) is stopping multiple times during the day and sometimes during the nightly processing. There seems to be no reason to when or why it stops. Sometimes users may be running drill through reports, sometimes no one is. We don't have that may users that have access to the system for drill through so volume shouldn't be a problem.
    I have looked in the OLAPISVR log around the time the service stops, but the log has no error or anything in it about why it stops. It has the statement from whatever the last user is logged was doing and then the next statement is where the service is starting back.
    On 7/16/08 the service stopped at 2:56:02. I started the service back at 2:57:09. I had 4 users log on and run drill through reports to make sure it was back up. They ran the reports fine. That was around 3:05. The service went back down again at 3:09:16. This has been going on for about a month. But users have had access to the system for only 2 weeks.
    This is the version we are running 9.3.1.0.0 Build-AIS93100B113.
    Any help would be appreciated.

    The user is requesting too much at one time.
    The query compiles long IN lists and stops the server.
    There is the ability to regulate the depth of the query in the report, but the Excel user can still drag a range and drill thru on too much data.

  • IDOCs  are queued up In Integration Server

    Folks ,
    I am not able to process the iDOCS as they are choked up in Integration server with following trace , can anybody help me out
    <i><b>  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Receiver Grouping
      -->
    - <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>4445B42A-672D-40B8-E100-000064070151</SAP:MessageId>
      <SAP:TimeSent>2006-04-19T18:43:47Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Service>BS_STG_R3_902_NA</SAP:Service>
      <SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">FIDCC2.FIDCCP01</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>BS_DEV_R3_950_CS</SAP:Service>
      <SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">FIDCC2.FIDCCP01</SAP:Interface>
    - <SAP:Mapping notRequired="M">
      <SAP:ObjectId>B4ydE1e/NPq9tEnsDcj7vA==</SAP:ObjectId>
      <SAP:SWCV>U0Q4sKe1Edqe7daFZAcBUQ==</SAP:SWCV>
      <SAP:SP>-1</SAP:SP>
      </SAP:Mapping>
      </SAP:Receiver>
      <SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">FIDCC2.FIDCCP01</SAP:Interface>
      </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SystemAckRequested="false" SystemErrorAckRequested="true" ApplicationAckRequested="true" ApplicationErrorAckRequested="true" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
      </SAP:ReliableMessaging>
    - <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-04-19T18:43:47Z" wasRead="false">
      <SAP:Engine type="IS" />
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">IDoc</SAP:Adapter>
      <SAP:MessageId>44452091-7B42-40B7-E100-000064070151</SAP:MessageId>
      <SAP:Info>FIDCC2.0000000018113400:20060419144347</SAP:Info>
      </SAP:Hop>
    - <SAP:Hop timeStamp="2006-04-19T18:43:47Z" wasRead="false">
      <SAP:Engine type="IS">is.61.sun081</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>4445B42A-672D-40B8-E100-000064070151</SAP:MessageId>
    - <SAP:Branch>
      <SAP:MessageId>4445B42A-672D-40B8-E100-000064070151</SAP:MessageId>
      <SAP:Service>BS_DEV_R3_950_CS</SAP:Service>
      </SAP:Branch>
    - <SAP:Branch>
      <SAP:MessageId>4445B42B-672D-40B8-E100-000064070151</SAP:MessageId>
      <SAP:Service>BS_DEV_R3_R1D_201_IE</SAP:Service>
      </SAP:Branch>
      <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>902</SAP:MANDT>
      <SAP:DOCREL>31I</SAP:DOCREL>
      <SAP:DOCNUM>0000000018113400</SAP:DOCNUM>
      <SAP:DIRECT>1</SAP:DIRECT>
      <SAP:IDOCTYP>FIDCCP01</SAP:IDOCTYP>
      <SAP:CIMTYP />
      <SAP:MESTYP>FIDCC2</SAP:MESTYP>
      <SAP:MESCOD />
      <SAP:MESFCT />
      <SAP:SNDPOR>SAPST4</SAP:SNDPOR>
      <SAP:SNDPRN>ST4-902</SAP:SNDPRN>
      <SAP:SNDPRT>LS</SAP:SNDPRT>
      <SAP:SNDPFC />
      <SAP:RCVPOR>A000000015</SAP:RCVPOR>
      <SAP:RCVPRN>R3DCLNT950</SAP:RCVPRN>
      <SAP:RCVPRT>LS</SAP:RCVPRT>
      <SAP:RCVPFC />
      <SAP:TEST />
      <SAP:SERIAL>20060419144347</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>2006-04-19</SAP:CREDAT>
      <SAP:CRETIM>14:43:47</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>20060419</SAP:Date>
      <SAP:Time>144347</SAP:Time>
      <SAP:Host>sun081</SAP:Host>
      <SAP:SystemId>XID</SAP:SystemId>
      <SAP:SystemNr>61</SAP:SystemNr>
      <SAP:OS>SunOS</SAP:OS>
      <SAP:DB>ORACLE</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>012</SAP:ProcStatus>
      <SAP:AdapterStatus>000</SAP:AdapterStatus>
      <SAP:User>XIAPPL</SAP:User>
      <SAP:TraceLevel>1</SAP:TraceLevel>
      <SAP:LogSeqNbr>000</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
      <SAP:PipelineElementId>5DC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
      <SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
      <SAP:PipelineService>PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:PipelineService>
      <SAP:QIdInternal>XBTOD___0000</SAP:QIdInternal>
      <SAP:CommitActor>A</SAP:CommitActor>
      <SAP:ParentId ChildNo="0" ChildTotal="0">444520917B4240B7E100000064070151</SAP:ParentId>
      <SAP:SplitNumber>0</SAP:SplitNumber>
      <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
      <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
      <SAP:TypeOfEngine client="401">CENTRAL</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID">6407015140B8444684E320CC</SAP:EOReferenceRuntime>
      <SAP:EOReferenceInbound type="TID">6407015E1C50444684E39DF5</SAP:EOReferenceInbound>
      <SAP:EOReferenceOutbound type="TID" />
      <SAP:MessageSizePayload>18029</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>0</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>18029</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>IDOC</SAP:AdapterInbound>
      <SAP:InterfaceAction>DEL</SAP:InterfaceAction>
      <SAP:RandomNumber>24</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="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="sun081">20060419184347.424552</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="sun081">20060419184347.443929</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="sun081">20060419184347.443977</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="sun081">20060419184347.613713</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="sun081">20060419184347.616273</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="sun081">20060419184347.625803</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="sun081">20060419184347.626241</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="sun081">20060419184347.634135</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="begin" host="sun081">20060419184347.634561</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="end" host="sun081">20060419184347.645671</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="sun081">20060419184347.645716</SAP:Timestamp>
      </SAP:RunTimeItem>
      </SAP:PerformanceHeader>
    - <SAP:DynamicConfiguration xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPOR">SAPST4</SAP:Record>
      <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRN">ST4-902</SAP:Record>
      <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="SNDPRT">LS</SAP:Record>
      <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPOR">A000000015</SAP:Record>
      <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRN">R3DCLNT950</SAP:Record>
      <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="RCVPRT">LS</SAP:Record>
      <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="MESTYP">FIDCC2</SAP:Record>
      <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="IDOCTYP">FIDCCP01</SAP:Record>
      <SAP:Record namespace="http://sap.com/xi/XI/System/IDoc" name="CIMTYP" />
      </SAP:DynamicConfiguration>
    - <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:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="B" name="IDX_INBOUND_XMB" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">User: XIAPPL</Trace>
      <Trace level="1" type="T">Language: E</Trace>
      <Trace level="1" type="T">Correct Version from 2 to 3: 3.X-Data to 4.x-Data</Trace>
      <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</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 SAPST4</Trace>
      <Trace level="1" type="T">Convert Segment-Definitions to Types</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 = 401</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = XIAPPL</Trace>
      <Trace level="1" type="Timestamp">2006-04-19T18:43:47Z EST</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 = 444520917B4240B7E100000064070151</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 : XBTI0003</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0003</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 = 401</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = XIAPPL</Trace>
      <Trace level="1" type="Timestamp">2006-04-19T18:43:47Z EST</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: 2</Trace>
      <Trace level="1" type="T">Multi-receiver split case</Trace>
      <Trace level="1" type="T">Persisting initial (pre-split) message</Trace>
      <Trace level="1" type="T">Persisting split messages (split kids)</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Splitting loop start</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTOD___0000</Trace>
      <Trace level="1" type="T">Persisting split kid = 4445B42A672D40B8E100000064070151</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
      </SOAP:Header>
    - <SOAP:Body>
    - <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
    - <SAP:Payload xlink:href="cid:[email protected]">
      <SAP:Name>MainDocument</SAP:Name>
      <SAP:Description />
      <SAP:Type>Application</SAP:Type>
      </SAP:Payload>
      </SAP:Manifest>
      </SOAP:Body>
      </SOAP:Envelope></b></i>

    Hi Manish,
    but you have to register the queues
    go to SXMB_ADM and register queues option
    it's one of the installation/configuration steps
    you have to do it for any kind of message message exchange (if the person who installed XI didn't do it)
    register the queues and restart the messages
    or F6 at the queue entry
    Regards,
    michal

  • Integrated Server stops abruptly.

    Hello,
    I'm using JDevleoper Studio Edition Version 11.1.1.5.0.
    I'm trying to deploy an existing application on a newly created integrated server instance on my PC.
    For this, I created a new Server instance from JDevleoper IDE, Set its port to 7005 & SSL port to 7006.
    For authentication, user id - weblogic and password - weblogic.
    Changed the application properties to point to this new app server instance.
    After deploying the application, it gives following error and stops debugger:
    User: weblogic, failed to be authenticated.
    **** Authentication error while connecting to application server ServerInstance1. Please check settings.
    **** Failed to complete start-up of application server ServerInstance1.
    [Server Instance ServerInstance1 is shutting down.  All applications currently running will be terminated and undeployed.]
    [Forcing termination of ServerInstance1]
    taskkill /F /PID 5244
    [Server Instance ServerInstance1 is shutting down.  All applications currently running will be terminated and undeployed.]
    Debugger connection to debuggee process has been lost.
    [Forcing termination of ServerInstance1]
    taskkill /F /PID 5244
    Process exited.
    Debugger disconnected from local process.
    Please suggest how this can be corrected.
    Regards,
    Nikhil

    Isn't the password weblogic1?

  • Message File Adapter - XI Integration Server not arriving

    We have configured a file adapter to read a file.  According to the audit log the file is successfully read and converted to XML; however, the message is never posted to XI.  We have checked to make sure that no XI* users are locked and we have bounced the server.
    The following error message is listed in the audit log:
    Transmitting the message to endpoint http://kansbwul01:50000/sap/xi/engine/entry?action=execute using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server.
    The following is the application log:
    #1.5#0003BA54D61900190000000C000030E60003EEAAD1138641#1106842349700#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.stop()######3e38f290707e11d996610003ba54d619#SAPEngine_System_Thread[impl:5]_35##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###The running MCF with GUID will be stopped now#1#8fa37160707811d995b00003ba54d619#
    #1.5#0003BA54D619001900000014000030E60003EEAAD16F4730#1106842355713#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.stop()######3e38f290707e11d996610003ba54d619#SAPEngine_System_Thread[impl:5]_35##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###MCF with GUID was stopped successfully.#1#8fa37160707811d995b00003ba54d619#
    #1.5#0003BA54D619006000000009000030E60003EEAAD1A4DD9D#1106842359225#/Applications/ExchangeInfrastructure/AdapterFramework/ResourceAdapter/MessagingSystem/System/Clustering##com.sap.aii.af.ra.ms.runtime.MessagingSystem.reassignMessages(String, String[])#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_11##0#0#Error#1#com.sap.aii.af.ra.ms.runtime.MessagingSystem#Java###Could not redistribute messages due to #1#LockingManager must be initialized before usage.#
    #1.5#0003BA54D6190040000000000000316A0003EEAAD9D40B8C#1106842496535#/Applications/ExchangeInfrastructure/AdapterFramework/Services/SecurityService##com.sap.aii.af.security.MessageSecurityServiceFrame.MessageSecurityServiceFrame.start()#######SAPEngine_System_Thread[impl:5]_24##0#0#Info#1#com.sap.aii.af.security.MessageSecurityServiceFrame#Java###QUEUE_CONNECTION_FACTORY: , ERROR_QUEUE: , QUEUE: , JARM_PREFIX: , JARM_USER: , JARM_ENABLED: .#6#jmsfactory/default/QueueConnectionFactory#jmsqueues/default/MessageSecurityErrorQueue#jmsqueues/default/MessageSecurityQueue#XI:Security:#XISecurityUser#false#
    #1.5#0003BA54D619004A000000060000316A0003EEAADD1ABF82#1106842551500#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###Module Exception 'com.sap.aii.af.mp.module.ModuleException: senderChannel 'c5a6ccb89b113e8c92474a4aa0df5858': Catching exception calling messaging system' found, cause: com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.#
    #1.5#0003BA54D619004A000000080000316A0003EEAADD1AC8F6#1106842551503#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###Delivery Exception for guid'96f35561-707e-11d9-a16c-0003ba54d619' - non recoverable error, retry anyway#
    #1.5#0003BA54D619004A0000000A0000316A0003EEAADD1ACE8D#1106842551504#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###Channel CDWExtFile: Sending file failed with com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available. - continue processing#
    #1.5#0003BA54D6190011000000FD0000316A0003EEAADF49F9C7#1106842588150#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.SpiManagedConnectionFactory()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Plain###This SPIManagedConnectionFactory has the GUID: cc6372c0-707e-11d9-ca96-0003ba54d619#
    #1.5#0003BA54D6190011000001030000316A0003EEAADF4ADA00#1106842588207#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.start()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###MCF with GUID is started now. (,)#3#cc6372c0707e11d9ca960003ba54d619#com.sap.engine.services.deploy.server.ApplicationLoader@5293b95#cc6372c0707e11d9ca960003ba54d619#
    #1.5#0003BA54D6190011000001090000316A0003EEAADF4AEA33#1106842588211#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.start()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###MCF with GUID was started successfully.#1#cc6372c0707e11d9ca960003ba54d619#
    #1.5#0003BA54D6190051000000040000316A0003EEAAE1DFB940#1106842631518#/Applications/ExchangeInfrastructure/Repository#sap.com/com.sap.xi.repository#com.sap.aii.ib.core.applcomp.ApplicationComponent#J2EE_GUEST#0####e63e40d0707e11d9b8020003ba54d619#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.aii.ib.core.applcomp.ApplicationComponent#Plain###Startup of XI Application "REPOSITORY" ok.#
    #1.5#0003BA54D6190054000000170000316A0003EEAAE4BA42E1#1106842679394#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector#J2EE_ADMIN#339####02bf9dd0707f11d9b9830003ba54d619#SAPEngine_Application_Thread[impl:3]_12##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D619004C000000080000316A0003EEAAE692D9D6#1106842710366#/Applications/ExchangeInfrastructure/Directory#sap.com/com.sap.xi.directory#com.sap.aii.ib.core.applcomp.ApplicationComponent#J2EE_GUEST#0##kansbwul01.erc.ge.com_LB1_148575#Guest#d8164a70707e11d9a3490003ba54d619#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap.aii.ib.core.applcomp.ApplicationComponent#Plain###Startup of XI Application "DIRECTORY" ok.#
    #1.5#0003BA54D619004D000000040000316A0003EEAAEB3DF548#1106842788689#/Applications/ExchangeInfrastructure/Directory#sap.com/com.sap.xi.directory#com.sap.aii.ib.server.util.BasicJMSClient#WSHAUN#466#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb6000ffffff90]###43ec08c0707f11d99f8b0003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#com.sap.aii.ib.server.util.BasicJMSClient#Plain###TopicConnectionFactory not found#
    #1.5#0003BA54D619004D000000050000316A0003EEAAEB3E07B0#1106842788693#/Applications/ExchangeInfrastructure/Directory#sap.com/com.sap.xi.directory#com.sap.aii.ib.server.util.BasicJMSClient#WSHAUN#466#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb6000ffffff90]###43ec08c0707f11d99f8b0003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#com.sap.aii.ib.server.util.BasicJMSClient#Plain###Exception during JMS startup for topic "SYNCHRONIZED_CACHE"
    Thrown:
    com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/jms/topic/xi/TopicConnectionFactory.
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:258)
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:621)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
         at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
         at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sap.aii.ib.server.util.BasicJMSClient.initJmsResources(BasicJMSClient.java:77)
         at com.sap.aii.ib.server.util.BasicJMSClient.init(BasicJMSClient.java:54)
         at com.sap.aii.ib.server.util.BasicJMSClient.<init>(BasicJMSClient.java:48)
         at com.sap.aii.ib.server.util.ClusterSyncedCache.<init>(ClusterSyncedCache.java:41)
         at com.sap.aii.ib.server.cpa.AdapterMDCache.<clinit>(AdapterMDCache.java:27)
         at com.sap.aii.ib.sbeans.misc.MiscServicesBean.getAdapterMetadata(MiscServicesBean.java:226)
         at com.sap.aii.ib.sbeans.misc.MiscServicesRemoteObjectImpl10.getAdapterMetadata(MiscServicesRemoteObjectImpl10.java:2028)
         at com.sap.aii.ib.sbeans.misc.MiscServicesRemoteObjectImpl10p4_Skel.dispatch(MiscServicesRemoteObjectImpl10p4_Skel.java:284)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:291)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    #1.5#0003BA54D6190004000000060000316A0003EEAAED036F71#1106842818407#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D6190004000000120000316A0003EEAAED1F56F6#1106842820236#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D61900040000001E0000316A0003EEAAED2014BF#1106842820285#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D61900040000002A0000316A0003EEAAED20EE43#1106842820341#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D6190004000000360000316A0003EEAAED21A105#1106842820386#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D6190004000000420000316A0003EEAAED2268E0#1106842820438#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D61900040000004E0000316A0003EEAAED233205#1106842820489#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D61900040000005A0000316A0003EEAAED23EDCB#1106842820537#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D6190004000000660000316A0003EEAAED249350#1106842820580#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D6190051000000090000316A0003EEAAF39F13CA#1106842929271#/Applications/ExchangeInfrastructure/IntegrationServer#sap.com/com.sap.xi.services#com.sap.aii.ib.core.applcomp.ApplicationComponent#XIDIRUSER#526####97b7c160707f11d9837b0003ba54d619#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.aii.ib.core.applcomp.ApplicationComponent#Plain###Startup of XI Application "RUNTIME" ok.#
    #1.5#0003BA54D619003C0000000C0000316A0003EEAAFD1B729D#1106843088417#/Applications/ExchangeInfrastructure/AdapterFramework/ResourceAdapter/MessagingSystem/System/Queue##com.sap.aii.af.ra.ms.runtime.ListenerFinder.run()#J2EE_GUEST#0####b4a1c0b1707e11d98d600003ba54d619#SAPEngine_Application_Thread[impl:3]_19##0#0#Error#1#com.sap.aii.af.ra.ms.runtime.ListenerFinder#Java###Message listener could not be created for connection after attempts.#3#localejbs/TestListener#test#10#
    #1.5#0003BA54D6190058000000050000316A0003EEAB27D41690#1106843805160#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector#J2EE_ADMIN#635####a1c95a40708111d9887c0003ba54d619#SAPEngine_Application_Thread[impl:3]_28##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    The following is the trace file:
    #1.5#0003BA54D6190000000000140000316A0003EEAAD72107D8#1106842451248#com.sap.engine.core.service630.container.ReferenceResolver##com.sap.engine.core.service630.container.ReferenceResolver#######Thread[Thread-1,5,main]##0#0#Error##Plain###Component com.sap.aii.af.security has a hard reference to service com.sap.aii.af.service.cpa with manual startup mode.#
    #1.5#0003BA54D6190036000000000000316A0003EEAAD94B1302#1106842487558#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
    #1.5#0003BA54D6190036000000010000316A0003EEAAD94C908B#1106842487656#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###**************     CCMS CONNECTOR (System)    **************#
    #1.5#0003BA54D6190036000000020000316A0003EEAAD94C936D#1106842487657#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
    #1.5#0003BA54D6190036000000030000316A0003EEAAD94C9621#1106842487657#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###Tracelevel: 0#
    #1.5#0003BA54D6190036000000040000316A0003EEAAD94E292D#1106842487760#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
    #1.5#0003BA54D6190036000000050000316A0003EEAAD94F65F2#1106842487842#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###*******     Java Monitoring API - Version      ********#1#1.8.8#
    #1.5#0003BA54D6190036000000060000316A0003EEAAD9525DA5#1106842488036#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
    #1.5#0003BA54D6190036000000070000316A0003EEAAD9547512#1106842488173#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Host: , OS: , JDK: .#3#kansbwul01.erc.ge.com#SunOS_sparcv9_5.9#1.4.2_06#
    #1.5#0003BA54D6190036000000080000316A0003EEAAD95490A6#1106842488180#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###Calculated library path: /global/usr/sap/LB1/DVEBMGS00/j2ee/cluster/server0/bin/ext/com.sap.mona.api#
    #1.5#0003BA54D6190036000000090000316A0003EEAAD954A29A#1106842488185#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###System.load [2] /global/usr/sap/LB1/DVEBMGS00/j2ee/os_libs/libjmon.so#
    #1.5#0003BA54D61900360000000A0000316A0003EEAAD95617BA#1106842488280#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Version of JNI library: .#1#3.12 Non-Unicode Version#
    #1.5#0003BA54D61900360000000B0000316A0003EEAAD9562000#1106842488283#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Java tracelevel set to .#1#Error#
    #1.5#0003BA54D61900360000000C0000316A0003EEAAD9577C95#1106842488372#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Connected () to segment (), , .#5#attach#0#read/write#system mode#40000000 bytes#
    #1.5#0003BA54D6190009000000010000316A0003EEAAD97D6C04#1106842490858#com.sap.aii.af.ra.ms.impl.core.queue.Queue##com.sap.aii.af.ra.ms.impl.core.queue.Queue.run()#######SAPEngine_System_Thread[impl:5]_73##0#0#Error##Java###Failed to retrieve message from MessageStore for queue .#2#aef38c80-707d-11d9-a639-0003ba54d619(OUTBOUND)#AFWSend#
    #1.5#0003BA54D6190014000000020000316A0003EEAAD988D5C9#1106842491606#com.sap.aii.af.ra.ms.impl.core.queue.Queue##com.sap.aii.af.ra.ms.impl.core.queue.Queue.run()#######SAPEngine_System_Thread[impl:5]_28##0#0#Error##Java###Failed to retrieve message from MessageStore for queue .#2#ea9f3be0-707c-11d9-834f-0003ba54d619(OUTBOUND)#AFWSend#
    #1.5#0003BA54D619003F000000000000316A0003EEAAD9CFB274#1106842496250#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_65##0#0#Error##Java###CPA Cache not updated with directory data, due to: #1#Couldn't open Directory URL (http://kansbwul01:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.lb1.kansbwul01), due to: HTTP 503: Service Unavailable#
    #1.5#0003BA54D619003F000000010000316A0003EEAAD9D09295#1106842496307#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_65##0#0#Error##Java###Confirmation handling failed, due to: #1#Couldn't send confirmation, due to: Couldn't access Confirmation URL, due to: HTTP 503: Service Unavailable#
    #1.5#0003BA54D6190046000000000000316A0003EEAAD9E5FAD6#1106842497710#com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext##com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext.setCurrentNodeID(int)#######SAPEngine_System_Thread[impl:5]_43##0#0#Info#1#/Version#Plain###Current node set to 1485750#
    #1.5#0003BA54D6190046000000010000316A0003EEAAD9E62B77#1106842497723#com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext##com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext.setEnvironmentState(int)#######SAPEngine_System_Thread[impl:5]_43##0#0#Info#1#/Version#Plain###Environment state set to : ENV_INCOMPLETE#
    #1.5#0003BA54D6190049000000000000316A0003EEAAD9F40CB0#1106842498632#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
    #1.5#0003BA54D6190049000000010000316A0003EEAAD9FB0888#1106842499090#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
    #1.5#0003BA54D6190049000000020000316A0003EEAAD9FB3838#1106842499102#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
    #1.5#0003BA54D6190049000000030000316A0003EEAAD9FB61D0#1106842499113#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
    #1.5#0003BA54D6190009000000020000316A0003EEAADA5386CF#1106842504889#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######9998abd0707e11d9cd270003ba54d619#SAPEngine_System_Thread[impl:5]_73##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server#http://kansbwul01:50000/sap/xi/engine/entry?action=execute#
    #1.5#0003BA54D6190014000000030000316A0003EEAADA542AB7#1106842504931#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######99afb640707e11d9a86c0003ba54d619#SAPEngine_System_Thread[impl:5]_28##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server#http://kansbwul01:50000/sap/xi/engine/entry?action=execute#
    #1.5#0003BA54D619004D000000000000316A0003EEAADAF321D0#1106842515349#com.sap.aii.proxy.xiruntime.web.TransportServlet#sap.com/com.sap.xi.proxyserver#com.sap.aii.proxy.xiruntime.web.TransportServlet.init(...)#J2EE_GUEST#0####a1006c50707e11d99ea30003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Info##Plain###Initialized#
    #1.5#0003BA54D619004D000000010000316A0003EEAADAF32B88#1106842515352#com.sap.aii.proxy.xiruntime.web.TransportServlet#sap.com/com.sap.xi.proxyserver#com.sap.aii.proxy.xiruntime.web.TransportServlet.init(...)#J2EE_GUEST#0####a1006c50707e11d99ea30003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Info##Plain###Registered with Adapter Framework Monitor#
    #1.5#0003BA54D6190055000000010000316A0003EEAADCAC81FD#1106842544275#com.sap.pmi.io.HttpPostThread##com.sap.pmi.io.HttpPostThread######b1f90ee0707e11d9c4300003ba54d619#Thread[Thread-42,5,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/System/Server#Plain###Error sending PMI records to http://kansbwul01:8000/sap/bc/sapi_gate, HTTP response: 404Not found. Please check the HTTP destination "pmistore".#
    #1.5#0003BA54D619004A000000050000316A0003EEAADD1ABD1C#1106842551499#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Module Exception 'com.sap.aii.af.mp.module.ModuleException: senderChannel 'c5a6ccb89b113e8c92474a4aa0df5858': Catching exception calling messaging system' found, cause: com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.#
    #1.5#0003BA54D619004A000000070000316A0003EEAADD1AC765#1106842551502#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Delivery Exception for guid'96f35561-707e-11d9-a16c-0003ba54d619' - non recoverable error, retry anyway#
    #1.5#0003BA54D619004A000000090000316A0003EEAADD1ACD22#1106842551504#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CDWExtFile: Sending file failed with com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available. - continue processing#
    #1.5#0003BA54D619004A0000000C0000316A0003EEAADD1B3AEE#1106842551532#com.sap.engine.services.ts##com.sap.engine.services.ts#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Server#Java#ts_0021##Thread is not associated with any transaction context.##
    #1.5#0003BA54D619004A0000000D0000316A0003EEAADD1B41AE#1106842551533#com.sap.engine.services.ts##com.sap.engine.services.ts#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ts.exceptions.BaseIllegalStateException: Thread is not associated with any transaction context.
         at com.sap.engine.services.ts.jta.impl.TransactionManagerImpl.rollback(TransactionManagerImpl.java:441)
         at com.sap.aii.adapter.file.File2XI.processFileList(File2XI.java:1756)
         at com.sap.aii.adapter.file.File2XI.run(File2XI.java:1007)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    #1.5#0003BA54D6190011000000790000316A0003EEAADDAE5C4B#1106842561174#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.xi.ibresources factory name: jms/topic/xi/TopicConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D61900110000007A0000316A0003EEAADDAFCE2B#1106842561269#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: jms/topic/xi/TopicConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D61900110000007C0000316A0003EEAADDAFE340#1106842561274#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.xi.ibresources factory name: jms/queue/xi/QueueConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D61900110000007D0000316A0003EEAADDB040CB#1106842561298#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: jms/queue/xi/QueueConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000B20000316A0003EEAADE6877ED#1106842573371#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.aii.af.ispeak.app factory name: ISPXAConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000B30000316A0003EEAADE68A1E8#1106842573382#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: ISPXAConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000C10000316A0003EEAADE837B81#1106842575141#com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext##com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext.setEnvironmentState(int)######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#/Version#Plain###Environment state set to : ENV_COMPLETE#
    #1.5#0003BA54D6190011000000C20000316A0003EEAADE83D50E#1106842575164#com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession##com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.initialize()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#/Version#Plain###Looked up factory : com.sap.engine.services.jmsconnector.cci.QueueConnectionFactoryImpl@6cbd9138#
    #1.5#0003BA54D6190011000000C30000316A0003EEAADE83D78C#1106842575165#com.sap.aii.af.protocol.ispeak.j2ee.services.ISPStartupService##com.sap.aii.af.protocol.ispeak.j2ee.services.ISPStartupService.onAllAppStart()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#/Version#Plain###Calling onServerStart on ISPClusterContext...#
    #1.5#0003BA54D6190011000000E60000316A0003EEAADF147D24#1106842584644#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.ip.me.insttool factory name: InstToolTopicFactoryCreateEmptyImage loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000E70000316A0003EEAADF14A82D#1106842584655#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: InstToolTopicFactoryCreateEmptyImage loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000E90000316A0003EEAADF14B7A3#1106842584659#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.ip.me.insttool factory name: InstToolTopicFactoryFinishImage loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000EA0000316A0003EEAADF14DC56#1106842584669#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: InstToolTopicFactoryFinishImage loader does not exist:  . Using default class loader!!!#

    The problem was the Pipeline URL for the integration server.
    http://<server>:50000/sap/xi/engine/entry?action=execute
    is the defective URL. 
    Once we logged into SLD and selected the business system for the integration server we change the pipeline URL to the following
    http://<server>:8000/sap/xi/engine?type=entry
    we then restarted the J2EE server and it worked fine.

  • XI Error ERROR_OBJECT.INTERNAL: Queue stopped

    Hi All,
    In our Integration system there are lot of ques stopped in SMQ2. When we checked the status is SYSFAIL and we are getting message as "XI Error ERROR_OBJECT.INTERNAL: Queue stopped"
    Not sure how to solve this problem and what are the things that i should check.
    "XI Error ERROR_OBJECT.INTERNAL: Queue stopped
    Message no. SR053
    In SM37 i can check that the job named "80144F3A76E71DDFAF9B420D2A9B8456" is created by user   PISUPER and running and active since 86000 secs.
    Can anyone help in this
    Thanks

    hi,
    need to restart Queue..
    ->double click on Quue
    ->it will show you status of the Q....number of messages in the Q...
    -> double-click on the number of entries
    -> you will see a detailed report
    -> double click on the first entry
    -> you will see the message processing due to which the Q got blocked
    -> on the toolbar above (in the same page) you will find the option of Restart...click it....select the tracing level as retain....
    this will cause the message processing to restart and all the messages blocked in the Q will get processed....
    please refer below blog:
    Internal Server Error in PI 7.1
    thanks,

  • "To Be Delivered" status in XI integration server

    Hey Guys!
    I have a question, right now we are trying to load Items into SRM; however, the records are being given the “To Be Delivered” status in the XI Integration Server. The records do not reach SRM. We have tried refreshing the XI Cache, as well as restarting the J2EE engine, all to no avail. Would anyone of you guys know how to address this issue? Thanks in advance!!
    Best Regards,
    Glenn

    Hi,
    Status:  TO_BE_DELIVERED
    Which means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.
    TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.
    Solution:
    This is done via the Messaging System receive servlet:
    http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>
    /<PROTOCOL>
    Only if this was executed successfully the Messaging System returns HTTP 200 to the Integration Server and the Status TO_BE_DELIVERED moves to DELIVERING
    1. Try logging into Sap GUI with two users:  XIAPPLUSER & XIAFUSER
       to see if they are blocked
    2. We can check the messages:
    AdapterFramework
    com.sap.aii.adapterframework.serviceuser.language
    com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
    com.sap.aii.adapterframework.serviceuser.pwd
    ApplicationSystem
    com.sap.aii.applicationsystem.serviceuser.language
    com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
    com.sap.aii.applicationsystem.serviceuser.pwd
    in the exchange profile to make sure the right passwords
    Regards
    Agasthuri Doss

  • SMQ2 queue stops

    Hi,
    I have an integration process that sends a synchronous message (soap adapter) to a receiver system.  After that  the receiver system needs about 5 to 10 minutes to respond to the request. Sometimes this is no problem and the queue of outgoing messages resides in status running.
    However most time the queue stops after some minutes and the only way to go on with processing is to manually unlock the queue in SMQ2.
    Why does this happens? Is there a possibility to restart the queue automatically? Is there a timeout period in queue processing that can be inceased?
    Thank you in advance,
    Daniel

    Dear Daniel,
    In synchronous scenarios running over PI, several communication components are involved where each may lead to a time-out. Such a time-out on one communication component causes the messaging scenario to fail as a whole.
    Various components which may contribut for your queue to fail are:
    Messaging System specific time out, SOAP sender channel time out, and your receiver Adapter time out property.
    There are some pre defined values for them already set in our PI system and these needs to be changed to accomodate the failure case also.
    To give you a lead, In NWA, Go to->Operation Management->Systems-> Start & Stop -> Java Services -> (Under Related Tasks) Java System Properties. Select your adapter type and under properties change the default time.
    For Sender SOAP channel, add u2018Parameter Nameu2019 as: XI.Timeout and in u2018Parameter Valueu2019, give any value in milliseconds.
    Warm Regards,
    Anshul

  • Exchange server 2007 stop receiving emails

    i have a strange issue with our exchange 2007 server, and i hope any one can help me, each day i have one of our exchange servers can't receive emails, and all emails sent to users in this servers are queued in the sending email server, and i have to manually
    restart the Microsoft exchange transport service in this server so that it's able to receive emails, i found an error in the server that always repeated with different parameters
    the error is
    Error ID: 4999
    Error Source: MSExchange Common
    Watson report about to be sent to dw20.exe for process id: 3508, with parameters: E12, c-RTL-AMD64, 08.02.0254.000, edgetransport, M.E.Transport, M.E.P.S.SmtpInServer.HandleConnection, System.NullReferenceException, 69f8, 08.02.0254.000.  ErrorReportingEnabled:
    False
    i receive the same error each time the server stop responds but the parameters is changed each time (Process ID number always changed) like below
    Watson report about to be sent to dw20.exe for process id: 3644, with parameters: E12, c-RTL-AMD64, 08.02.0254.000, edgetransport, M.E.Transport, M.E.P.S.SmtpInServer.HandleConnection, System.NullReferenceException, 69f8, 08.02.0254.000.  ErrorReportingEnabled:
    False
    i hope any one can help me solving this problem
    the server is windows server 2008
    Exchange 2007 SP2 Server Rollup 5
    McAfee Enterprise Antivirus is in the box
    Backup Exec Agent is in the box Also
    a lot of transport rules applied to our exchange organization
    Mahmoud Sabry IT System Engineer

    Hi
    As per the information and details provided by you, Exchange server 2007 stop receiving emails, then please follow these steps: -
    If you do have a 60 GB partition on the C: drive, one of the first signs of trouble is when the free space on C: drops below 2GB. Exchange 2007 stops receiving external
    emails. This is caused by a condition known as Back Pressure.
    Please check the following: -
    Check the nslook up for correct MX record.
    Run the exbpa and llok for any recent changes.
    Check for the device in perimeter network which accepts connections on port 25 FW or any other anti spam device).
    Try to run a telnet session from the firwall and then out side and drop email on the server.
    I hope this information will be helpful for you.
    Thanks and regards
    Shweta@G 

  • Queue stopped in sxmb_moni

    Hi,
    I am getting the problem in sxmb_moni when the XML message goes from one integration process to  SOAP adapter and a mapping is called.The queue status is Queue Stopped. When i click on that queue it shows status as SYSFAIL.When i double click on that queue again it shows Status Text
    as "XI Error CLIENT_SEND_FAIL . INTERNAL :Queue Stoppe ".
    And the trace for that message is
       <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Message Split According to Receiver List
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
      <SAP:P1>35</SAP:P1>
      <SAP:P2>HTTPIO_ERROR_CUSTOM_MYSAPSSO-Fehlermeldung beim Senden der Daten.</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error while sending by HTTP (error code: 35, error text: HTTPIO_ERROR_CUSTOM_MYSAPSSO-Fehlermeldung beim Senden der Daten.)</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    Please help me with this issue...

    Queue Stopped
    For your message processing in sxmb_moni...in the Qstatus column you will be seeing a red circle with stop written in it...
    ->double click it
    ->it will show you status of the Q....number of messages in the Q...
    -> double-click on the number of entries
    -> you will see a detailed report
    -> double click on the first entry
    -> you will see the message processing due to which the Q got blocked
    -> on the toolbar above (in the same page) you will find the option of Restart...click it....select the tracing level as retain....
    this will cause the message processing to restart and all the messages blocked in the Q will get processed....
    Regards,
    Abhishek.

  • How to change connection port between INTEGRATION SERVER and Adapter Engine

    Hi,
    I have scenario that in the productions server we are using SAP web dispatcher to connect to Adapter Engine for example the port is 60000.
    So when we copy this server to DR environment the webdispatcher is not there. is that any way to change the all connection port between IS and Adapter from 60000 back to original port 50000 ?
    Please advise ?
    Thank You and Regards
    Fernand

    HI,
    The waiting status is because of Message Queue is in wiating status. This may be because of overload of the messages, or may be your receiver systems is not ready  etc.
    SO go to SMQ2 and check the status of the queues.
    Also have a look into this blog-
    /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
    <i>
    Why I can see this messages only in the integration server?</i>
    >>>If message reachs the Adapter engine, you can see in the Adapter monitor. In your case, message is still there in the Integration Engine. Once the queues are cleared it will reach the Adapter engine, so you can monitor it in the adapter engine
    Regards,
    Moorthy

  • Apex Mail Queue stopped sending

    Suddenly the APEX mail queue on our production server has stopped sending emails. We have logged into the internal workspace as ADMIN and can see the emails in the queue. There are no errors against them. We've tried both using the "Send all mails" button and also apex_mail.push_queue() from sqlplus but neither has worked - the emails are just backed up. There are no emails in the sent log with errors.
    The configuration is no different from our development server (ie, same SMTP server, same setup within APEX) and that works fine. We haven't made any changes to anything, it just randomly stopped working the other day.
    We have tried using UTL_SMTP on the prod server and that works fine, so it looks like it's something APEX specific.
    Can anyone offer any advice or help before I raise this as an SR?
    Thanks,
    John

    You should run this query as DBA to see ORACLE_APEX_MAIL_QUEUE job run details.
    This job should run for every 5 min or 3 min depending on your apex version. See the latest run date.
    When you run apex_mail.push_queue; then, it should do the same task what above job does. Pushing the queue didn't help you. So I suggest to raise a SR with Oracle Support.
    Regards,
    Hari

  • Queue Stopped, messages not getting processed

    Hello Experts,
    From the pst three days, my XI server is running slowly. All the messages are having the status green. When we check the queues, all the messages are stuck there and the error displayed is SYSFAIL (Queue stopped). If I try to execute the LUW manually it doesn't allow me giving the message "The queus is registered and therefore cannot be activated".
    I have also tried deleting the entry and restarting the message again and then it goes to the same queue and gets stuck again. What should I do further?
    Thanks,
    Merrilly

    Hi,
    To be able to initiate processing of messages stuck in the queue, make sure to set following IS configuration parameter
    MONITOR QRFC_RESTART_ALLOWED to value 1 in SXMB_ADM
    Check this
    /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
    Regards
    Seshagiri
    Edited by: N V Seshagiri on Mar 19, 2008 9:07 AM

  • Insufficient access rights registering Oracle Directory Integration Server

    Hi all!
    following steps I´ve done to use the Oracle Directory Integration Server.(I´ve installed Oracle 10g infrastructure - OID is running - I´m also able to apply successful with ODM and orcladmin account)
    - oidctl connect=mydb1 server=odisrv instance=1 stop
    - odisrvreg -h localhost -p 389 -D cn=orcladmin,cn=Users,dc=localhost;dc=com -w ,pass
    where pass is the password of orcladmin.
    -> now I get the following error:
    registering..
    Error javax.naming.NoPermissionException [LDAP:error code 50: Insufficient Access Rights]; remaining name 'cn=odisrv+orclhostname=maschine,cn=odi,cn=oracle internet directory' !
    Any idea ??
    Thanks for all help & comments.

    I have gone through the documentation for creating the script. But there is one thing which I am not able to understand i.e. Subscription Parameters.
    Can anyone tell me the use of subscription parameters? What is the role of subscription parameters in Oracle Lite and External Authentication.
    Regards
    Kapil

  • IChat server suddenly stopped, now will not restart

    I have a Snow Leopard Server hosting multiple email accounts and websites, file sharing, runing OD, running iCal server, and up until a few days ago running iChat server.  All other functions continue to work normally, but iChat Server simply stopped one day and now won't restart.  Around the same time my external Time Machine hard drive failed (ironic) and I restarted the server in an attempt investigate that failed drive.  About the time of that restart, iChat server stopped working.  Here is the most recent iChat Service Log from attempting to start iChat Server:
    ealm=xserve.server.#####, registration disabled
    Jan 21 08:48:29 xserve jabberd/c2s[63181]: [jupeman.com] configured; realm=#######.com, registration disabled
    Jan 21 08:48:29 xserve jabberd/c2s[63181]: attempting connection to router at 127.0.0.1, port=5347
    Jan 21 08:48:29 xserve jabberd/c2s[63181]: shutting down
    Jan 21 08:48:29 xserve jabberd/resolver[63177]: shutting down
    Jan 21 08:48:29 xserve jabberd/s2s[63184]: attempting connection to router at 127.0.0.1, port=5347
    Jan 21 08:48:29 xserve jabberd/s2s[63184]: shutting down
    Jan 21 08:48:29 xserve jabberd/s2s[63184]: connection to router closed
    Jan 21 08:48:38 xserve org.jabber.jabberd[63176]: ERROR: sm died.  Shutting down server.
    Jan 21 08:48:38 xserve com.apple.launchd[1] (org.jabber.jabberd): Throttling respawn: Will start in 1 seconds
    Jan 21 08:48:39 xserve jabberd/sm[63198]: starting up
    Jan 21 08:48:39 xserve jabberd/sm[63198]: id: xserve.server.#####
    Jan 21 08:48:39 xserve jabberd/sm[63198]: sqlite: can't open database
    Jan 21 08:48:39 xserve jabberd/c2s[63201]: starting up
    Jan 21 08:48:39 xserve jabberd/sm[63198]: initialisation of storage driver 'sqlite' failed
    Jan 21 08:48:39 xserve jabberd/sm[63198]: failed to initialise one or more storage drivers, aborting
    Jan 21 08:48:39 xserve jabberd/c2s[63201]: modules search path: /var/jabberd/modules/jabberd2
    Jan 21 08:48:39 xserve jabberd/c2s[63201]: initialized auth module 'sqlite'
    Jan 21 08:48:39 xserve jabberd/sm[63199]: starting up
    Jan 21 08:48:39 xserve jabberd/router[63200]: starting up
    Jan 21 08:48:39 xserve jabberd/resolver[63197]: starting up
    Jan 21 08:48:39 xserve jabberd/sm[63199]: id: #######.com
    Jan 21 08:48:39 xserve jabberd/s2s[63203]: starting up (interval=60, queue=60, keepalive=0, idle=86400)
    Jan 21 08:48:39 xserve jabberd/router[63200]: loaded user table (1 users)
    Jan 21 08:48:39 xserve jabberd/router[63200]: loaded filters (7 rules)
    Jan 21 08:48:39 xserve jabberd/sm[63199]: sqlite: can't open database
    Jan 21 08:48:39 xserve jabberd/sm[63199]: initialisation of storage driver 'sqlite' failed
    Jan 21 08:48:39 xserve jabberd/sm[63199]: failed to initialise one or more storage drivers, aborting
    Jan 21 08:48:39 xserve jabberd/c2s[63201]: [xserve.server.#####] configured; realm=xserve.server.#####, registration disabled
    Jan 21 08:48:39 xserve jabberd/c2s[63201]: [#######.com] configured; realm=#######.com, registration disabled
    Jan 21 08:48:39 xserve jabberd/resolver[63197]: attempting connection to router at 127.0.0.1, port=5347
    Jan 21 08:48:39 xserve jabberd/router[63200]: [127.0.0.1, port=5347] listening for incoming connections
    Jan 21 08:48:39 xserve jabberd/router[63200]: [127.0.0.1, port=55886] connect
    Jan 21 08:48:39 xserve jabberd/c2s[63201]: attempting connection to router at 127.0.0.1, port=5347
    Jan 21 08:48:39 xserve jabberd/resolver[63197]: shutting down
    Jan 21 08:48:39 xserve jabberd/c2s[63201]: shutting down
    Jan 21 08:48:39 xserve jabberd/router[63200]: [127.0.0.1, port=55887] connect
    Jan 21 08:48:39 xserve jabberd/router[63200]: shutting down
    Jan 21 08:48:39 xserve jabberd/s2s[63203]: attempting connection to router at 127.0.0.1, port=5347
    Jan 21 08:48:39 xserve jabberd/s2s[63203]: shutting down
    Jan 21 08:48:39 xserve jabberd/s2s[63203]: connection to router closed
    Jan 21 08:49:09 xserve org.jabber.jabberd[63196]: ERROR: sm died.  Shutting down server.
    Jan 21 08:49:09 xserve jabberd/sm[63236]: starting up
    Jan 21 08:49:09 xserve jabberd/c2s[63239]: starting up
    Jan 21 08:49:09 xserve jabberd/resolver[63235]: starting up
    Jan 21 08:49:09 xserve jabberd/s2s[63241]: starting up (interval=60, queue=60, keepalive=0, idle=86400)
    Jan 21 08:49:09 xserve jabberd/sm[63237]: starting up
    Jan 21 08:49:09 xserve jabberd/router[63238]: starting up
    Jan 21 08:49:09 xserve jabberd/sm[63236]: id: xserve.server.#####
    Jan 21 08:49:09 xserve jabberd/c2s[63239]: modules search path: /var/jabberd/modules/jabberd2
    Jan 21 08:49:09 xserve jabberd/sm[63236]: sqlite: can't open database
    Jan 21 08:49:09 xserve jabberd/c2s[63239]: initialized auth module 'sqlite'
    Jan 21 08:49:09 xserve jabberd/sm[63236]: initialisation of storage driver 'sqlite' failed
    Jan 21 08:49:09 xserve jabberd/sm[63236]: failed to initialise one or more storage drivers, aborting
    Jan 21 08:49:09 xserve jabberd/router[63238]: loaded user table (1 users)
    Jan 21 08:49:09 xserve jabberd/router[63238]: loaded filters (7 rules)
    Jan 21 08:49:09 xserve jabberd/sm[63237]: id: #######.com
    Jan 21 08:49:09 xserve jabberd/sm[63237]: sqlite: can't open database
    Jan 21 08:49:09 xserve jabberd/sm[63237]: initialisation of storage driver 'sqlite' failed
    Jan 21 08:49:09 xserve jabberd/sm[63237]: failed to initialise one or more storage drivers, aborting
    Jan 21 08:49:09 xserve jabberd/resolver[63235]: attempting connection to router at 127.0.0.1, port=5347
    Jan 21 08:49:09 xserve jabberd/resolver[63235]: [4] [router] write error: Broken pipe (32)
    Jan 21 08:49:09 xserve jabberd/resolver[63235]: connection to router closed
    Jan 21 08:49:09 xserve jabberd/resolver[63235]: attempting reconnect (3 left)
    Jan 21 08:49:09 xserve jabberd/c2s[63239]: [xserve.server.#####] configured; realm=xserve.server.#####, registration disabled
    Jan 21 08:49:09 xserve jabberd/c2s[63239]: [#######.com] configured; realm=#######.com, registration disabled
    Jan 21 08:49:09 xserve jabberd/c2s[63239]: attempting connection to router at 127.0.0.1, port=5347
    Jan 21 08:49:09 xserve jabberd/router[63238]: [127.0.0.1, port=5347] listening for incoming connections
    Jan 21 08:49:09 xserve jabberd/c2s[63239]: shutting down
    Jan 21 08:49:09 xserve jabberd/router[63238]: shutting down
    Jan 21 08:49:09 xserve jabberd/s2s[63241]: attempting connection to router at 127.0.0.1, port=5347
    Jan 21 08:49:09 xserve jabberd/s2s[63241]: shutting down
    Jan 21 08:49:09 xserve jabberd/s2s[63241]: connection to router closed
    Jan 21 08:49:11 xserve jabberd/resolver[63235]: attempting connection to router at 127.0.0.1, port=5347
    Jan 21 08:49:11 xserve jabberd/resolver[63235]: shutting down
    Jan 21 08:49:18 xserve org.jabber.jabberd[63234]: ERROR: sm died.  Shutting down server.
    Jan 21 08:49:18 xserve com.apple.launchd[1] (org.jabber.jabberd): Throttling respawn: Will start in 1 seconds
    Jan 21 08:49:19 xserve jabberd/resolver[63255]: starting up
    Jan 21 08:49:19 xserve jabberd/resolver[63255]: attempting connection to router at 127.0.0.1, port=5347
    Jan 21 08:49:19 xserve jabberd/resolver[63255]: [4] [router] write error: Broken pipe (32)
    Jan 21 08:49:19 xserve jabberd/resolver[63255]: connection to router closed
    Jan 21 08:49:19 xserve jabberd/resolver[63255]: attempting reconnect (3 left)
    Jan 21 08:49:19 xserve jabberd/sm[63256]: starting up
    Jan 21 08:49:19 xserve jabberd/sm[63256]: id: xserve.server.#####
    Jan 21 08:49:19 xserve jabberd/sm[63257]: starting up
    Jan 21 08:49:19 xserve jabberd/sm[63256]: sqlite: can't open database
    Jan 21 08:49:19 xserve jabberd/sm[63256]: initialisation of storage driver 'sqlite' failed
    Jan 21 08:49:19 xserve jabberd/sm[63256]: failed to initialise one or more storage drivers, aborting
    Jan 21 08:49:19 xserve jabberd/sm[63257]: id: jupeman.com
    Jan 21 08:49:19 xserve jabberd/c2s[63259]: starting up
    Jan 21 08:49:19 xserve jabberd/sm[63257]: sqlite: can't open database
    Jan 21 08:49:19 xserve jabberd/sm[63257]: initialisation of storage driver 'sqlite' failed
    Jan 21 08:49:19 xserve jabberd/c2s[63259]: modules search path: /var/jabberd/modules/jabberd2
    Jan 21 08:49:19 xserve jabberd/sm[63257]: failed to initialise one or more storage drivers, aborting
    Jan 21 08:49:19 xserve jabberd/c2s[63259]: initialized auth module 'sqlite'
    Jan 21 08:49:19 xserve jabberd/resolver[63255]: attempting connection to router at 127.0.0.1, port=5347
    Jan 21 08:49:19 xserve jabberd/resolver[63255]: shutting down
    Jan 21 08:49:19 xserve jabberd/c2s[63259]: [xserve.server.#####] configured; realm=xserve.server.boyer, registration disabled
    Jan 21 08:49:19 xserve jabberd/c2s[63259]: [#######.com] configured; realm=jupeman.com, registration disabled
    Jan 21 08:49:19 xserve jabberd/c2s[63259]: attempting connection to router at 127.0.0.1, port=5347
    Jan 21 08:49:19 xserve jabberd/c2s[63259]: shutting down
    Jan 21 08:49:19 xserve jabberd/s2s[63261]: starting up (interval=60, queue=60, keepalive=0, idle=86400)
    Jan 21 08:49:19 xserve jabberd/s2s[63261]: attempting connection to router at 127.0.0.1, port=5347
    Jan 21 08:49:19 xserve jabberd/s2s[63261]: [4] [router] write error: Broken pipe (32)
    Jan 21 08:49:19 xserve jabberd/s2s[63261]: connection to router closed
    Jan 21 08:49:19 xserve jabberd/s2s[63261]: attempting reconnect (3 left)
    Jan 21 08:49:21 xserve jabberd/s2s[63261]: attempting connection to router at 127.0.0.1, port=5347
    Jan 21 08:49:21 xserve jabberd/s2s[63261]: [4] [router] write error: Broken pipe (32)
    Jan 21 08:49:21 xserve jabberd/s2s[63261]: connection to router closed
    Jan 21 08:49:21 xserve jabberd/s2s[63261]: attempting reconnect (2 left)
    Jan 21 08:49:23 xserve jabberd/s2s[63261]: attempting connection to router at 127.0.0.1, port=5347
    Jan 21 08:49:23 xserve jabberd/s2s[63261]: [4] [router] write error: Broken pipe (32)
    Jan 21 08:49:23 xserve jabberd/s2s[63261]: connection to router closed
    Jan 21 08:49:23 xserve jabberd/s2s[63261]: attempting reconnect (1 left)
    Jan 21 08:49:25 xserve jabberd/s2s[63261]: attempting connection to router at 127.0.0.1, port=5347
    Jan 21 08:49:25 xserve jabberd/s2s[63261]: [4] [router] write error: Broken pipe (32)
    Jan 21 08:49:25 xserve jabberd/s2s[63261]: connection to router closed
    Jan 21 08:49:25 xserve jabberd/s2s[63261]: shutting down
    Jan 21 08:49:25 xserve org.jabber.jabberd[63254]: ERROR: sm died.  Shutting down server.
    Jan 21 08:49:25 xserve com.apple.launchd[1] (org.jabber.jabberd): Throttling respawn: Will start in 4 seconds
    Jan 21 08:49:29 xserve servermgrd[70]: servermgr_jabber[E]: Error -- jabberd service failed to start
    Jan 21 08:49:29 xserve servermgrd[70]: servermgr_jabber[W]: some jabberd processes failed to start
    Jan 21 08:49:29 xserve servermgrd[70]: servermgr_jabber[N]: waiting for jabberd to finish shutdown...
    Jan 21 08:49:29 xserve servermgrd[70]: servermgr_jabber[N]: jabberd service shutdown completed.
    Jan 21 08:49:29 xserve servermgrd[70]: servermgr_jabber[E]: Error -- failed to start service: jabberd
    Any help would be appreciated.  (I've hashed out, "#", real names)

    Thanks, Tim!  I noticed that I did not have access permission to the directory /jabberd.  As a result, I set the system admin user's permissions to read & write for that and all sub files in the directory.  I then tried to restart iChat Server and here's the new error log:
    Jan 24 11:15:34 xserve servermgrd[70]: servermgr_jabber[N]: waiting for jabberd to finish startup...
    Jan 24 11:15:34 xserve servermgrd[70]: servermgr_jabber[N]: jabberd service startup completed.
    s/jabberd2
    Jan 24 11:15:36 xserve jabberd/resolver[29370]: starting up
    Jan 24 11:15:36 xserve jabberd/sm[29373]: starting up
    Jan 24 11:15:36 xserve jabberd/sm[29371]: starting up
    Jan 24 11:15:36 xserve jabberd/s2s[29377]: starting up (interval=60, queue=60, keepalive=0, idle=86400)
    Jan 24 11:15:36 xserve jabberd/sm[29373]: id: #######com
    Jan 24 11:15:36 xserve jabberd/sm[29371]: id: xserve.server.#####
    Jan 24 11:15:36 xserve jabberd/c2s[29375]: initialized auth module 'sqlite'
    Jan 24 11:15:36 xserve jabberd/sm[29373]: sqlite: can't open database
    Jan 24 11:15:36 xserve jabberd/sm[29373]: initialisation of storage driver 'sqlite' failed
    Jan 24 11:15:36 xserve jabberd/sm[29373]: failed to initialise one or more storage drivers, aborting
    Jan 24 11:15:36 xserve jabberd/router[29374]: loaded user table (1 users)
    Jan 24 11:15:36 xserve jabberd/router[29374]: couldn't open filter file /etc/jabberd/router-filter.xml: No such file or directory
    Jan 24 11:15:36 xserve jabberd/sm[29371]: sqlite: can't open database
    Jan 24 11:15:36 xserve jabberd/sm[29371]: initialisation of storage driver 'sqlite' failed
    Jan 24 11:15:36 xserve jabberd/sm[29371]: failed to initialise one or more storage drivers, aborting
    Jan 24 11:15:36 xserve jabberd/router[29374]: [127.0.0.1, port=5347] listening for incoming connections
    Jan 24 11:15:36 xserve jabberd/router[29374]: shutting down
    Jan 24 11:15:36 xserve jabberd/s2s[29377]: attempting connection to router at 127.0.0.1, port=5347
    Jan 24 11:15:36 xserve jabberd/s2s[29377]: shutting down
    Jan 24 11:15:36 xserve jabberd/s2s[29377]: connection to router closed
    Jan 24 11:15:36 xserve jabberd/resolver[29370]: attempting connection to router at 127.0.0.1, port=5347
    Jan 24 11:15:36 xserve jabberd/resolver[29370]: shutting down
    Jan 24 11:15:36 xserve jabberd/c2s[29375]: [xserve.server.#####] configured; realm=xserve.server.#####, registration disabled
    Jan 24 11:15:36 xserve jabberd/c2s[29375]: [#######.com] configured; realm=jupeman.com, registration disabled
    Jan 24 11:15:36 xserve jabberd/c2s[29375]: attempting connection to router at 127.0.0.1, port=5347
    Jan 24 11:15:36 xserve jabberd/c2s[29375]: shutting down
    Jan 24 11:15:47 xserve org.jabber.jabberd[29367]: ERROR: sm died.  Shutting down server.
    Jan 24 11:15:47 xserve jabberd/sm[29573]: starting up
    Jan 24 11:15:47 xserve jabberd/sm[29573]: id: xserve.server.#####
    Jan 24 11:15:47 xserve jabberd/resolver[29572]: starting up
    Jan 24 11:15:47 xserve jabberd/sm[29574]: starting up
    Jan 24 11:15:47 xserve jabberd/sm[29574]: id: jupeman.com
    Jan 24 11:15:47 xserve jabberd/sm[29573]: sqlite: can't open database
    Jan 24 11:15:47 xserve jabberd/sm[29573]: initialisation of storage driver 'sqlite' failed
    Jan 24 11:15:47 xserve jabberd/sm[29573]: failed to initialise one or more storage drivers, aborting
    Jan 24 11:15:47 xserve jabberd/sm[29574]: sqlite: can't open database
    Jan 24 11:15:47 xserve jabberd/sm[29574]: initialisation of storage driver 'sqlite' failed
    Jan 24 11:15:47 xserve jabberd/sm[29574]: failed to initialise one or more storage drivers, aborting
    Jan 24 11:15:47 xserve jabberd/c2s[29576]: starting up
    Jan 24 11:15:47 xserve jabberd/c2s[29576]: modules search path: /var/jabberd/modules/jabberd2
    Jan 24 11:15:47 xserve jabberd/c2s[29576]: initialized auth module 'sqlite'
    Jan 24 11:15:47 xserve jabberd/resolver[29572]: attempting connection to router at 127.0.0.1, port=5347
    Jan 24 11:15:47 xserve jabberd/c2s[29576]: [xserve.server.#####] configured; realm=xserve.server.#####, registration disabled
    Jan 24 11:15:47 xserve jabberd/resolver[29572]: shutting down
    Jan 24 11:15:47 xserve jabberd/c2s[29576]: [#######.com] configured; realm=#######.com, registration disabled
    Jan 24 11:15:47 xserve jabberd/c2s[29576]: attempting connection to router at 127.0.0.1, port=5347
    Jan 24 11:15:47 xserve jabberd/c2s[29576]: shutting down
    Jan 24 11:15:56 xserve com.apple.launchd[1] (org.jabber.jabberd): Throttling respawn: Will start in 1 seconds
    Jan 24 11:15:57 xserve jabberd/resolver[29605]: starting up
    Jan 24 11:15:57 xserve jabberd/sm[29607]: starting up
    Jan 24 11:15:57 xserve jabberd/sm[29606]: starting up
    Jan 24 11:15:57 xserve jabberd/sm[29607]: id: #######.com
    Jan 24 11:15:57 xserve jabberd/sm[29606]: id: xserve.server.#####
    Jan 24 11:15:57 xserve jabberd/router[29608]: starting up
    Jan 24 11:15:57 xserve jabberd/c2s[29609]: starting up
    Jan 24 11:15:57 xserve jabberd/c2s[29609]: modules search path: /var/jabberd/modules/jabberd2
    Jan 24 11:15:57 xserve jabberd/s2s[29611]: starting up (interval=60, queue=60, keepalive=0, idle=86400)
    Jan 24 11:15:57 xserve jabberd/sm[29607]: sqlite: can't open database
    Jan 24 11:15:57 xserve jabberd/sm[29607]: initialisation of storage driver 'sqlite' failed
    Jan 24 11:15:57 xserve jabberd/sm[29606]: sqlite: can't open database
    Jan 24 11:15:57 xserve jabberd/sm[29607]: failed to initialise one or more storage drivers, aborting
    Jan 24 11:15:57 xserve jabberd/sm[29606]: initialisation of storage driver 'sqlite' failed
    Jan 24 11:15:57 xserve jabberd/sm[29606]: failed to initialise one or more storage drivers, aborting
    Jan 24 11:15:57 xserve jabberd/router[29608]: loaded user table (1 users)
    Jan 24 11:15:57 xserve jabberd/router[29608]: couldn't open filter file /etc/jabberd/router-filter.xml: No such file or directory
    Jan 24 11:15:57 xserve jabberd/c2s[29609]: initialized auth module 'sqlite'
    Jan 24 11:15:57 xserve jabberd/s2s[29611]: attempting connection to router at 127.0.0.1, port=5347
    Jan 24 11:15:57 xserve jabberd/resolver[29605]: attempting connection to router at 127.0.0.1, port=5347
    Jan 24 11:15:57 xserve jabberd/router[29608]: [127.0.0.1, port=5347] listening for incoming connections
    Jan 24 11:15:57 xserve jabberd/c2s[29609]: [xserve.server.boyer] configured; realm=xserve.server.#####, registration disabled
    Jan 24 11:15:57 xserve jabberd/router[29608]: shutting down
    Jan 24 11:15:57 xserve jabberd/s2s[29611]: shutting down
    Jan 24 11:15:57 xserve jabberd/c2s[29609]: [#######.com] configured; realm=#######.com, registration disabled
    Jan 24 11:15:57 xserve jabberd/s2s[29611]: connection to router closed
    Jan 24 11:15:57 xserve jabberd/resolver[29605]: shutting down
    Jan 24 11:15:57 xserve jabberd/c2s[29609]: attempting connection to router at 127.0.0.1, port=5347
    Jan 24 11:15:57 xserve jabberd/c2s[29609]: shutting down
    I see the errors related to not finding a .xml file and the failed initialization of sqlite storage driver, but I don't know how to fix these.  Any ideas?

Maybe you are looking for