Inbound Queues in XI --System error

HI Friends,
sceanrio : Outbound IDOC
    I have observed some messages struck in inbound queue and first message stoped because of system error.
I know if we delete this message , rest of the message will restart and process it.
BUt i don't know , if i delete , what will happen to this message ? I can't resart bcz restart not possible.
2. If all messages in queue, and restart not possible then what is the solution ? only deletion or  ?????
Deva

HI Deva,
    Before deleting try to unlock the queue and re-execute the first message then remaining messages will process.If you are not able to resend the first message ....analyze the error why it is failing.
Finally if the above two options are not working then you need to Identify the first message and delete the first message informing business to resend that perticular message.
Regards,
Naveen.

Similar Messages

  • Inbound Queues stuck with RFC errors

    Hi Experts,
    Greetings for the Day !
    We have BDOC related issue and we need your expert help ASAP in resolving the same.
    We ahev a few BDOCS lying in intermediate state in transaction SMW01, which we found using BDOC monitoring on daily basis. When we check the same in SMQR - inbound queue, we found that the queues are stuck with an RFC error message.
    We are re-activate these queues to actually resolve the intermediate bdocs. But, my query is
    1> The raeson for getting these BDOCS in intermediate state & stuck queues
    2> A permanent resolution for the same.
    Please help and  let us know if you need more details.
    Regards,
    Kanika

    Hi Kanika,
    RFC error can be due to a bad connection as well. If the server is down, there might be a problem in communication with the connected system and the queues will not be processed further. You need to reactivate or unlock to get the queues processed.
    But if there are any specific errors for which the queues are stuck do state the same, so that we can look into an actual resolution.
    Regards,
    Venkat

  • BADI For Inbound Queue in CRM

    Hi All,
    I am replicating Product Listings (VB02 in ECC)  data from ECC to CRM.
    Now I need to Update a Z table in CRM System with the data coming from ECC when the Inbound Queue in CRM System is processed via SMQ2.
    Can Anybody please tell me what BADI will be useful
    I found one CRM_DATAEXCHG_BADI but not sure how it goes.
    I also tried in Debuging the inbound Queue. It will take Long time to find out BTE or BADI in this way.
    So please help me with the BADI or BTE Name.
    Thanks
    Venkat

    Hi Gautham,
    No good, It did not help me Gautham.
    Can you please suggest me some other way of dong it.
    I have 2 badis to use one is address_update and the other is addres_check.
    I implemented address_check which had a address structure as a changing parameter and I update it there, it works absolutely fine.
    But my requirement is to update the structure based on the condition of BUT000. That is the BUT000-type, which means I need to update the structure only for person and not for organization and group.
    so in the badi address_check i need the BUT000 details, which I am not able to trace even from the local memory as I am getting the error saying "Memory is not yet instantiated"
    and If i use the other badi address_update.
    I have the problem the other way round here. I have all the BUT000 details here I can put the condition to update only for person, but I am not able to update the address structure.
    Please help me. This is required very urgent.
    Maximum points will be rewarded.
    Thanks in advance.
    Arul.

  • Inbound Queue blocked: Parallel and alternative sequences are not supported

    Hi,
    Just now, I checked the Inbound Queue in SCM system through SMQ2 and found which was blocked by error message "Parallel and alternative sequences are not supported". Could you please tell me what does it mean? How to fix it?
    Thanks,
    Quanyin Su

    Hi Quanyin Su,
    Parallel and Alternative sequences are used in routing.
    I believe you are trying to CIF PPM/PDS from ECC to APO and you are getting this queue stuck at inbound of APO.
    Both the alternative and parallel sequences are supported in APO.
    Alternative sequence is used as alternative modes in APO.
    I can think of this as a master data issue.
    At least one of your work center used in either of the sequences is not available in APO or is not APO relevant.
    Could you please check your master data such as all the work centers used and make sure your parallel and alternative sequences are consistent.
    Once you made sure that master is available in ECC, you can CIF it to APO by using CURTO_CREATE transaction in ECC.
    Please see below link for Routing and its usage in APO:
    http://help.sap.com/saphelp_apo/helpdata/en/99/ed3a981d0f11d5b3fc0050dadf0791/content.htm
    You also need to activate a BADI in order to sent alternative sequences to APO.
    Below thread has all the details regarding this.
    Re: /SAPAPO/CURTO 103 : Mode .. is not assigned to an activity
    Regards,
    Abhay Kapase
    Edited by: AbhayKapase on Aug 5, 2011 2:24 PM

  • Messages stuck in QRFC inbound and outbound queues by system error

    Hi Experts,
    We faced a big problem in our PI server which stopped all the traffic in the iDoc to File interface. Both the QRFC queues (inbound - SMQ1 as outbound - SMQ2) where stuck by a system error.
    In IDX5 of PI we saw two inbound iDocs on exact the same date/time of creation. Both iDocs are displayed in SXMB_MONI with the status "Canceled - Since Already Processed". The output files of both iDocs are generetad on the outbound side.
    The output files are genereted with a date/time stamp in filename exactly as: "pi_20101106-221812-437.dat" and "pi_20101106-221812-438.dat". So it seems that both processes where running on exact the same time.
    When looking into the system error we see the following details:
    com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id 00505697-181b-1ddf-babd-68f1ac208528(INBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: [200]: Duplicate key
    This caused that the QRFC queues where both stuck in inbound as outbound with a SYSERROR, so PI stopped and the queues should be reactivated manually.
    Does anybody have some idea of the real cause of this error. We really want to prevent such situation in the future.
    Thanks in advance!
    Best regards,
    Joost

    Hi Joost,
    Are you using an adpater module to avoid the same file name processed by the receiver channel ???
    If this is the case change the filename and retest flow otherwise remove the module (ex: localejbs/AF_Modules/MessageTransformBean - Local Enterprise Bean) from the channel check it whether the file getting processed or not...
    OR...you have an incorrect module configuration in the receiver channel.
    Do not remove the standard SAP module and make sure that you add additional modules before it.
    cheers,
    Ram.

  • Getting an error in CIF Inbound queue:"Only 0 decimal places are permitted for unit of measure PC"

    Hi,
    I am getting an error in CIF Inbound queue (function: CIF_ORDER_INBOUND_30A). The error text says "Only 0 decimal places are permitted for unit of measure PC".
    Can anyone point out the solution to resolve this error? It would be a big help for me as I am new to APO and so getting difficult to find a clue for it.
    Thanks.
    Regards
    Mansi

    Hi Mansi,
    Please check the cif queue you will get the order number from that order number you can find out material code. Then check the material master unit of measure in MM03 you have used some alternative unit of measure and system is unable to convert order to  alternative unit of measure because of decimal setting. If you go to CUNI and check the unit if measure PC it is not permitted for decimal places. If you need decimal than change the UoMof Material and use diff UoM or allow the decimal for PC which is not good practice.
    Regards,
    R.Brahmankar

  • Urgent: Error in Inbound Proxy in SCM system

    Hi All
    Please give your inputs to solve following problem I am facing. I am working on XI first time so please help me out to solve the following problem. Please let me know if you need any more info.
    Thanks a lot for your help guys.
    I am sending ORDERS.ORDER05 from R/3(ECC6.0) to SCM (5.0) through XI. I am using standard message interface ReplenishmentOrderNotification_In to send data to ICH configured on SAP SCM System.
    I am using XI adapter at receiver end. My message successfully going to SCM. SXMB_MONI, its giving error. After clicking on error flag it displays a table with 3 entries, please find them below.
    1. Start of inbound processing: ReplenishmentOrderNotification (ID 0000000000202027) 032(/SCMB/ORDER)
    2. TST 20080429202851 (type MessageCreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
    3. Partner key(s) not found 042(/SCMB/MDL_BASIC)
    Please find the XML message from ERROR node from Inbound Proxy
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Inbound Proxy
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="http://sap.com/xi/SCMBasis/Global">ReplenishmentOrderNotificationFault</SAP:ApplicationFaultMessage>
      <SAP:Stack>Application has thrown an exception</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Please find contents of Trace XML message from Inbound proxy
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Inbound Proxy
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=receiver</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="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 = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T01:31:18Z 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 = 48165647672B03B5E10080000A0C640C</Trace>
      <Trace level="1" type="T">PLNAME = RECEIVER</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 = RECEIVER</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_RECEIVER</Trace>
      <Trace level="1" type="T">Queue name : XBTR0003</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTR0003</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="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface *</Trace>
      <Trace level="1" type="T">select interface namespace</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--start receiver interface action determination</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface ReplenishmentOrderNotification_In*</Trace>
      <Trace level="1" type="T">select interface namespace http://sap.com/xi/SCMBasis/Global</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
      <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 RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T16:19:34Z 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 RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <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="Inbound Framework" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 000</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</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 RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T20:52:28Z 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 RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <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="Inbound Framework" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 002</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</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 RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = RAJARANGA</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T22:34:19Z 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 RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <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="Inbound Framework" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 004</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</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 RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = RAJARANGA</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T22:35:19Z 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 RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <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="Inbound Framework" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 006</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</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 RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = RAJARANGA</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T22:41:24Z 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 RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <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="Inbound Framework" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 008</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</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 RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-05-01T00:07:18Z 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 RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <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="Inbound Framework" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 010</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</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 RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-05-01T00:30:07Z 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 RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 012</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</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 RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-05-01T00:53:39Z 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 RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <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="Inbound Framework" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 014</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</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 RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-05-01T01:04:22Z 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 RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <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="Inbound Framework" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
    Regards
    Amol

    Hi All
    Thanks for your inputs, we are a step ahead now. We applied few notes I will be posting details soon. At the moment we stuck at one poin, its giving a configuration related error.  Please find the process log from SXMB_MONI from SCM system. It is saying Buyer missing in fact we have configured BP01 in SCM system and same we are getting from ECC system.
    Hope to hear from you soon. Thanks a lot for your inputs.
    ReplenishmentOrderNotificationFault
    Proxy Class (Generated)
    Detailed Information
    Start of inbound processing: ReplenishmentOrderNotification (ID 0000000000202043) 032(/SCMB/ORDER)
    The active implementation of BAdI '/SCMB/BIF_I_REPLORD' 'BEFORE_CONVERSION' has been run  080(/SCMB/BIF_COMMON)
    TST 20080508141414 (type MessageCreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
    The active implementation of BAdI '/SCMB/BIF_MI_PARTYID' 'BEFORE_MASTER_DATA_ACCESS' has been run  080(/SCMB/BIF_COMMON)
    Start generic process type determination 000(/SCMB/BIF_CU)
    Process type could not be determined - search for standard process type 002(/SCMB/BIF_CU)
    Standard process type (ICH) determined successfully 013(/SCMB/BIF_CU)
    Start action determination for addresses 070(/SCMB/BIF_CU)
    No Customizing found; standard action is 'map all addresses' 072(/SCMB/BIF_CU)
    End of action determination for addresses 071(/SCMB/BIF_CU)
    Start partner role determination 060(/SCMB/BIF_CU)
    Partner role is 'buyer (sold-to party)' 063(/SCMB/BIF_CU)
    Partner role determination completed successfully 061(/SCMB/BIF_CU)
    TST 20080508000000 (type CreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
    The active implementation of BAdI '/SCMB/BIF_MI_ITMBPRT' 'BEFORE_MASTER_DATA_ACCESS' has been run  080(/SCMB/BIF_COMMON)
    The active implementation of BAdI '/SCMB/BIF_MI_PRODID' 'BEFORE_MASTER_DATA_ACCESS' has been run  080(/SCMB/BIF_COMMON)
    TST 20081027000000 (type DeliveryPeriodStartDateTime, item 00010, sched. line 1) is local, interpret. as UTC 024(/SCMB/BIF_MI)
    Order 4500000105 item 00010: 'DeliveryPeriodEndDateTime' missing in schedule line 1 090(/SCMB/ORDER)
    The active implementation of BAdI '/SCMB/BIF_I_REPLORD' 'AFTER_CONVERSION' has been run  080(/SCMB/BIF_COMMON)
    BOL processing started for object /SCA/CL_SVORDER process name REPLORDER 006(/SCMB/DM_BOL)
    Start: read ODM order 250(/SCMB/ORDER)
    End: read ODM order 251(/SCMB/ORDER)
    Start: validation framework 254(/SCMB/ORDER)
    Validation started for validation profile POC1 (ICH - REPLORDER - HEADER) 606(/SCMB/DM_BOL)
    Business partner 'buyer' is missing in order 4500000105 021(/SCMB/ORDER)
    Validation for val. prof. POC1 (ICH, REPLORDER, HEADER) ended with errors and warnings 608(/SCMB/DM_BOL)
    End: validation framework 255(/SCMB/ORDER)
    Start alert notification for application ALEN - time 08.05.2008 19:15:18 - process mode F 504(/SCMB/ANOT)
    End of alert notification for application ALEN - time 08.05.2008 19:15:18 - process mode F 525(/SCMB/ANOT)
    Start: write ODM order 252(/SCMB/ORDER)
    End: write ODM order 253(/SCMB/ORDER)
    BOL processing ended for object /SCA/CL_SVORDER process name REPLORDER 007(/SCMB/DM_BOL)
    End inb. proc.: ReplenishmentOrderNotification (ReplenishmentOrder ID ) 033(/SCMB/ORDER)

  • SMQ2 (Inbound Queue) : Error occurred during character conversion

    Hi,
    In SMQ2 an Inbound Queue has failed with status text "Error occurred during character conversion". The XML message inside this queue is in waiting status with status text " Scheduled for Outbound Processing" .
    Even after cancelling this message from SXMB_MONI, and reposting the PO, still again the queue and the XML message inside the queue are in same status.
    As this is in XI production system, requesting to provide some suggestion ASAP.
    Thanks,
    Mateen.

    The queue status is still sysfail. There is only 1 message waiting in the queue.
    I think that the queue might be locked for some reason and after unlocking the queue and restarting the message, the message will get processed successfully.
    But before working on this I want to make sure that the queue is locked.
    Do you or anyone else know how and from where can I check whether the queue is locked or unlocked?
    Regards,
    Mateen.

  • XI inbound queues status "RETRY" in a new XI Production system

    Hi
    All the queues (XBT00* AND XBT02*) in XI Production system are not moving. Status is "Retry" all the time. The system is idle. Do you know what is happening here?
    I also see the following error in the queue:
    Command to tRFC/qRFC: Execute LUW again
    Also, lot of errors (below) in the system log (SM21):
    XIRWBUSER - Communication Error CPIC return code 027
    XIAPPLUSER - Perform rollback
    Any ideas?
    Regards
    Chandu

    Hi,
    When any message is sent from any other system to XI, the Inbound queue in XI is processed in the following way,
    1) AI_RUNTIME_JCOSERVER connects to the Java stack to execute the registered program AI_RUNTIME_<SID>.
    2) When this connection is fine, then the queue is processed without any issues.
    Now incase of Production system, which most likely to be a cluster system will fail because you'll find that AI_RUNTIME_JCOSERVER connection test fails, when you turn off one node. The reason being in visual administrator the JCo RFC Provider for the server nodes have not been maintained.
    Solution:
    Login to visual administrator, select the service JCo RFC Provider for both the nodes and set the value accordingly.
    Ex:
    SAP Cluster Virtual Name: XICLSTPROD
    Hostname1: XIPROD1
    Hostname2: XIPROD2
    SID: XIP
    CLIENT: 100
    Instance No: 02
    Values for Node1:
    Program Id: AI_RUNTIME_XIP
    Gateway host: XIPROD1
    Gateway service: sapgw02
    Server count: 20
    Application Server host: XICLSTPROD
    System number: 02
    Client: 100
    Language: EN
    User: PI_JCO_RFC
    Password: ***********
    Values for Node2:
    Program Id: AI_RUNTIME_XIP
    Gateway host: XIPROD2
    Gateway service: sapgw02
    Server count: 20
    Application Server host: XICLSTPROD
    System number: 02
    Client: 100
    Language: EN
    User: PI_JCO_RFC
    Password: ***********
    Change in the similar way for the other Programs registered.
    This should resovle the RETRY issue in Inbound queue.
    Hope this piece of information really helps.
    Regards,
    Kamesh

  • Invalid Flow Context error in Inbound Queues

    I am new to CRM middleware.
    We are getting lot of entries in CRM Inbound Queue (SMQ2) in our production system with error description,
    "Invalid Flow Context".
    The queues are of type, "R3AD_CONNOBJXXXXXXXXXX" and the FM the error was caused in, is "BAPI_CRM_SAVE".
    Can anyone help?
    Thanks in advance!
    Rajiv

    Thanks Rohit,
    When I debugged an entry with this "Invalid Flow Context" error, In method, CRM_GENERIC_CRM_IN, in the call to function, SMOF0_READ_SMOFSUBINT, in read statement,
       read table t_smofsubint binary search
               with key objclass = i_objclass
                        objname  = space.
    I am getting sy-subrc = 4.
    i.e. entries do not exist for SI_POD in table SMOFSUBINT.
    Has this behaviour got anything to do with this error?

  • Error in inbound q in CRM System

    Hello,
    The data sent from R/3 system to BBP CRM 4.0 has errors for the q R3AD_DNL_COND_A512. ie we are having errors for the conditions table and also for R3AI_CUSTOMER_MAIN q in inbound q of CRM system. R/3 is 4.6c.
    Error in R3AD_DNL_COND_A512 : Status of q is sytem fail and error is <b>"No entry in SMOFRSTAT with this REF_ID!"</b>
    Error in R3AI_CUSTOMER_MAIN :Status of q is sytem fail and error is "<b>Error in Mapping (Details: transaction SMW01)"</b>..
    please help.

    Hi,
    - a prerequisite for downloading conditions is a successful download of the condition customizing. You can check that in transaction CND_MAP_LOG_DISPLAY.
    - for analysing the R3AI_CUSTOMER_MAIN error the inbound queue is of no help. Please analyse the error information for the related bdoc in transaction SMW01.
    (by the was: the correct forum for your question would be "Customer Relationship Management (CRM) - General & Framework " )
    Kind regards,

  • Conntrans u2013 initialization error and Client console show no inbound queue

    Hallo,
    I installed Communication station and Client application to two computers. Test from Communication station to CRM is OK, test from client to Communication station is OK too. When I run Conntrans it show: u201CError during Conntrans initalizatin; contact system administratoru201D. In log file is:
    Exception in CGUIDlg::CreateComObjects_AltThread . Was comerror exception (Neplatný ukazatel hr:80004003); technical hint: Create InitPar NamedCollection</SESS_LOG_TEXT>
    </SESSION_ENTRY>
    Client console show me, that I have u201CNo unprocessed messages available in the queueu201D. But in transaction smq1 I have 923 entries to send to Mobile Client.
    I regenerate metadata, reassign siteID and did transaction table again, but still no messages in inbound queue.
    Configuration: CRM 2007, CRM Mobile Client 6.0 SP02.
    Can anyone help me please with these problems.
    Thank you very much.
    Jiri

    Hallo Wolfhard,
    thank you very much for your help and fast reply. I uninstall .NET 1.1 on client side (I had both .NET 1.1 and 2.0). Now I can run Conntrans. When I try synchronizaiton, it wrote "initializing transfer process" and after few second Conntrans fell down. In log is no error - everything have succeeded. I include ending part of log. In Client console inbound queue is the same.
    <SESSION_ENTRY>
      <SESS_LOG_ENTRY_ID>43090EC6134E43479082B5043DD7E18F</SESS_LOG_ENTRY_ID>
      <SESS_LOG_SERVICE_NAME>GUI</SESS_LOG_SERVICE_NAME>
      <SESS_LOG_TYPE>I</SESS_LOG_TYPE>
      <SESS_LOG_DATETIME>8.7.2008 15:04:19</SESS_LOG_DATETIME>
      <SESS_LOG_TEXT>Returning from CGUIDlg::OnInitDialog...</SESS_LOG_TEXT>
      </SESSION_ENTRY>
    - <SESSION_ENTRY>
      <SESS_LOG_ENTRY_ID>A49BAA7D177D463491F635F8A64591E6</SESS_LOG_ENTRY_ID>
      <SESS_LOG_SERVICE_NAME>GUI</SESS_LOG_SERVICE_NAME>
      <SESS_LOG_TYPE>I</SESS_LOG_TYPE>
      <SESS_LOG_DATETIME>8.7.2008 15:04:20</SESS_LOG_DATETIME>
      <SESS_LOG_TEXT>Call to CGUIDlg::OnInitDialog in CTSDialog::OnInitDialog succeeded</SESS_LOG_TEXT>
      </SESSION_ENTRY>
    - <SESSION_ENTRY>
      <SESS_LOG_ENTRY_ID>F5AE51A961664408830DDF07DA60C1F5</SESS_LOG_ENTRY_ID>
      <SESS_LOG_SERVICE_NAME>GUI</SESS_LOG_SERVICE_NAME>
      <SESS_LOG_TYPE>I</SESS_LOG_TYPE>
      <SESS_LOG_DATETIME>8.7.2008 15:04:20</SESS_LOG_DATETIME>
      <SESS_LOG_TEXT>Call to GetConfigurationDetails in CTSDialog::OnInitDialog succeeded</SESS_LOG_TEXT>
      </SESSION_ENTRY>
    - <SESSION_ENTRY>
      <SESS_LOG_ENTRY_ID>1163EBE1ABB249ECAE0D3B230E6CCBB8</SESS_LOG_ENTRY_ID>
      <SESS_LOG_SERVICE_NAME>GUI</SESS_LOG_SERVICE_NAME>
      <SESS_LOG_TYPE>I</SESS_LOG_TYPE>
      <SESS_LOG_DATETIME>8.7.2008 15:04:20</SESS_LOG_DATETIME>
      <SESS_LOG_TEXT>Call to InitConfiguration in CTSDialog::OnInitDialog succeeded</SESS_LOG_TEXT>
      </SESSION_ENTRY>
    - <SESSION_ENTRY>
      <SESS_LOG_ENTRY_ID>BE6FFFFE896D410A80D58C020195B56D</SESS_LOG_ENTRY_ID>
      <SESS_LOG_SERVICE_NAME>GUI</SESS_LOG_SERVICE_NAME>
      <SESS_LOG_TYPE>I</SESS_LOG_TYPE>
      <SESS_LOG_DATETIME>8.7.2008 15:04:20</SESS_LOG_DATETIME>
      <SESS_LOG_TEXT>Call to CreateAndPlaceControls in CTSDialog::OnInitDialog succeeded</SESS_LOG_TEXT>
      </SESSION_ENTRY>
    - <SESSION_ENTRY>
      <SESS_LOG_ENTRY_ID>FD53890701BA40AE8DADB1F9701FDCFC</SESS_LOG_ENTRY_ID>
      <SESS_LOG_SERVICE_NAME>GUI</SESS_LOG_SERVICE_NAME>
      <SESS_LOG_TYPE>I</SESS_LOG_TYPE>
      <SESS_LOG_DATETIME>8.7.2008 15:04:20</SESS_LOG_DATETIME>
      <SESS_LOG_TEXT>Call to TaskBarCreateIcon in CTSDialog::OnInitDialog succeeded</SESS_LOG_TEXT>
      </SESSION_ENTRY>
      </SESSION_ENTRIES>
    After I applied  note 1071267 on Client 6.0 SP02 I could not run Client Console. When I run it, I got "Failed to load control sbtstatus. Your version may be outdated. Make sure you are using the version of the control that was provided with your application". Conntrans after fix I can run, but it is the same as above - it will fell down after few second of synchronization.
    My version of librfc32.dll is newer, so I did not applied note 1074669.
    I will try to uninstall client side and apply note again to clean installation if it helps.
    Thank you very much. With regards
    Jirka

  • Error in Inbound Queue (Tx. SMQ2) / Error "CMW_PIF_PROTOCOL"

    Hello everybody,
    I have got a queue which appears time by time. It is called "ISP_I_000000000000017" in my Inbound Queue.
    Below further information about that.
    Information from Tx. "SE16" about this Error.
    Client             010
    Site-Typ-ID          GWA_01
    ISP Queue-Typ        I
    Log. Queuename       CMW_PIF_PROTOCOL
    Queue-Name           ISP_I_000000000000017
    Destination          ISP_I_000000000000017
    Description        GWA_01/I/CMW_PIF_PROTOCOL
    Has anyone an idea what's behind this? What is the pif-Protocol? How can I avoid this error in the inbound queue.
    Every idea is appreciated.
    Thanks in advance.
    Kind regards Harry

    One option would be to raise an exception for such steps....in the Exception handler you can repeat the same step....in your case it will be the mapping (n:1) .....are you sure that the process failed in Transformation step and that the data was correct....i mean all the 5 IDOCs were sent as an input to the mapping?
    Can you ensure that during this time there was no connection issue between the BPM and the mapping runtime (IE)....may be you can check with your BASIS.
    Regards,
    Abhishek.

  • Inbound queue error"XI Error APPLICATION_ERROR.ABAP: Queue stopped"

    Hi,
    In  SMQ2 ,we have received inbound queue error "XI Error APPLICATION_ERROR.ABAP: Queue stopped".When activate queue error is not going.So please advice.
    Thanks,
    Praveen

    Hello Mr,
    Have a look into SAP Notes: 824554, 906435, 783515, 910649, 706563.
    /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
    To be more helpful, can you post here complete error log?

  • Error in Inbound Queue : Internally required memory not available

    Hi,
         We are trying to send 110MB file from R/3 to Legacy thru XI. It is failing in XI inbound queue with error <b>Internally required memory not available</b>. When i saw memory usage in XI server it is using full 3GB of extended memory and entering in private mode. We dont have any problem upto 50MB files.
    Please any inputs.
    Regards,
    Ranjeeth.

    try to process the data by breaking the message into dependant segments

Maybe you are looking for

  • Inconsistent behavior of "where" filter command in remote powershell session

    I've got a simple powershell script I've written to do a gpo backup (backup-gpo) to a remote file share, and then I launch a remote powershell session with "invoke-command" where I zip up the results of the gpo backup, then delete the gpo backups onc

  • Microsoft Remote Desktop for Mac and Win 2000 Server

    Hello guys, Could you please confirm that the latest version 8.0.15 is compatible with WIN 2000 Server connections? If not, could you please advise which version of Microsoft Remote Desktop for Mac is the match in order to connect to a WIN 2000 serve

  • Kernel Panic on MacBook Pro, brand new.

    HI! I have done a lot of research on the kernel panic. It happens on Safari, and I have done all I think I can do based on what I have read on these forums. (PRAM, reinstall OS, repair permissions, ditch safari prefs, etc) Another odd thing is that i

  • Ias problem in admin tool login.

    Hi, When i try to deploy a 9MB J2EE application on iAS6.0SP2, the process goes fine, but my iAS Admin tool doesnt work. It gives timeout error. But if the same application's size is cut down to 7MB, the admin tool works fine. Can you please suggest m

  • Runtime error 226 at 046A4477

    I have crazy popups with this error message. I need to close them 10 times in a row to proceed to a next web page. I have tried evewerything: reboot, antivirus, etc. IE works well. Only Firefox has this problem.