File to Proxy Scenari0, Error in ECC server Messages stucked in Queue

Hi All
we have created a file to proxy scenario in PI & when we are sending the data to Proxy, proxy is not getting executed in SAP ECC & we are getting the following error in out production ECC server & all the messages are getting s
No load could be found for transformation /1SAI/TXSA9475ABE3925030F71D9
could any one of you please help me in resolving this issue.
Thanks
Rinku Gangwani

Hi,
  Are you activate the ICF services in ERP system? This issue must be done for the correct execution of proxy channel.
  What type of program mapping are you using for the content transformation?
  If you use a ABAP mapping program make sure to activate the program correctly.
Best regards
Ivá

Similar Messages

  • Message stuck in queue - Rejected by server

    Okay, so I thought was being smart by trying to set up my companies email on my own. When I entered all of the information (which I made mistakes) I tried to send a test message. Of course it would not go through and was being rejected by my companies server. So I deleted the email account I created on iphone. However, the test email I sent remained in queue and kept trying to resend over and over getting the same error/rejection message from companies email. Since there is no sent box (on .MAC anyway)there was no way to erase the test message stuck in queue.
    Solution: Since I currently have two email accounts .MAC and Yahoo, I just tured off the .MAC and all of a sudden I hear the SHOOOWWWSHHHH. The test message stuck in queue was sent from the yahoo account. (after I confirmed the message was sent, I turned on hte .MAC email account again)
    Now I know this solution is purely dumb luck and playing around with settings, but just incase it happens to you, this was how I solved it.

    Hey, thanks for that! It is very intersting to see how that works. Looks like the outgoing mail queue can change "on demand", like when you left only one account active. This means that the ability to send emails from any of the accounts regardless of where it came in is just a programming step away...

  • File to Proxy Scenario : Error in communication channel monitoring

    Hi,
    I have developed File to Proxy Scenario on PI 7.1 system and it is not working. I see the below error in communication channel monitoring.
    u201CError: com.sap.engine.interfaces.messaging.api.exception.ConfigException: Some of the IS access information is not available. SLDAccess property may be set to true, but SLD is not available.u201D
    File will be picked from the FTP server.
    I have created File system in SLD of type "Third Party", Can this be the issue?
    Please guide me on this.
    Thanks,
    Chandravadan

    Hi!
    Check if the tcode SLDCHECK is ok!
    Check note #764176.
    Also, refer to link below and execute each steps from the links there MANUALLY.
    Wizard-Based Configuration:
    http://help.sap.com/saphelp_nwpi71/helpdata/EN/45/2e4c1b16bb4aa8e10000000a11466f/frameset.htm
    Regards,
    Caio Cagnani

  • File to Proxy Scenario Error

    Hi Experts,
    I am working on File To Proxy Scenario. I am getting the below Error: The Messages in SXMB_MONI are going to AUtomatically Restart Status. I see some Queues with RETRY Status in SMQ2. When i am testing from SPROXY, the Table is Updated with the Corresponding Values. But when i place the file in the ftp folder then i am getting this error.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--
    Call Adapter
    --> 
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand=""> 
    <SAP:Category>XIServer</SAP:Category>  
    <SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>  
    <SAP:P1>500</SAP:P1>  
    <SAP:P2>Internal Server Error</SAP:P2>  
    <SAP:P3>(See attachment HTMLError for details)</SAP:P3>  
    <SAP:P4 />  
    <SAP:AdditionalText />  
    <SAP:Stack>Error while sending by HTTP (error code: 500, error text: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>  
    <SAP:Retry>A</SAP:Retry>  
    </SAP:Error>
    Please check and do the needful .
    Regards,
    GIRIDHAR

    Hi Giridhar,
    The problem is with connection. Please check the below discussion
    HTTP returns status is 500(Internal Server Error)
    Problem in ABAP proxy........ | SCN
    regards,
    Harish

  • Error while sending the messages to JMS Queue

    Hi ,
    I am trying to pick the file from JMS Queue and send the response xml as outbound message to JMS Queue again using XAI Sender
    I Created XAI Sender, Outbound Message Type(DM-RCVRESP) and configured these two with External System.
    I am able to pick the file from JMS Queue but unable to send the message through XAI Sender (Real-time)
    Plz find below the error trace getting.
    [Wed Jun 15 16:12:09 IST 2011] Error while processing sender "UPLOADSTG" : Unable to update response in staging table: Row id not given.
    com.splwg.mpl.sending.SameThreadSendingManager$ProcessException
         at com.splwg.mpl.sending.SameThreadSendingManager.processDestination(SameThreadSendingManager.java:341)
         at com.splwg.mpl.sending.SameThreadSendingManager.sendResponse(SameThreadSendingManager.java:293)
         at com.splwg.mpl.sending.SameThreadSendingManager.doSend(SameThreadSendingManager.java:249)
         at com.splwg.mpl.server.async.ExecSendRequestProcessor.ProcessRequest(ExecSendRequestProcessor.java:61)
         at com.splwg.mpl.server.async.RequestProcessingThreadAdapter.run(RequestProcessingThreadAdapter.java:46)
         at com.splwg.mpl.server.PooledThread.run(PooledThread.java:91)
         at java.lang.Thread.run(Thread.java:662)
    Please guide me in this regard..
    Thanks,
    sukumar

    What have you configured for the response tab for the sender? Are you using the MPL or the MDB?
    Take a look at:
    MPL Best Practices (Doc Id 1308165.1)
    Oracle WebLogic JMS Integration (Doc Id: 1308181.1)

  • Error while enqueue-ing messages in Jms Queue

    While testing the ProcessSalesOrderFulfillmentOSMCFSCommsJMSProducer_1.0 process , in the Order to Bill PIP, we are encountering the following error ,
    09/10/08 15:05:07 Error initializing the Oracle JMS Resource provider for Queues: Io exception: Got minus one from a read call
    <2009-10-08 15:05:07,060> <WARN> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JMSMessageConsumer_init: Retrying connection; attempt #231
    09/10/08 15:05:29 Stop process
    09/10/08 15:05:31 Shutting down...
    09/10/08 15:05:37 Error initializing the Oracle JMS Resource provider for Queues: Io exception: Got minus one from a read call
    <2009-10-08 15:05:37,875> <WARN> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JMSMessageConsumer_init: Retrying connection; attempt #232
    <2009-10-08 15:05:43,484> <INFO> <collaxa> <ServerManager::uninit> Shutting down all domains
    <2009-10-08 15:05:43,487> <INFO> <default.collaxa.cube.engine> <AdapterStats::uninit:Done uninitializing Adapter statistics holder for engine > default
    <2009-10-08 15:05:43,494> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::uninit Shutting down the JCA activation agent, processId='bpel://localhost/default/AIAReadJMSNotificationProcess~1.0/', activation properties={portType=Consume_Message_ptt}
    <2009-10-08 15:05:43,494> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - performing endpointDeactivation for portType=Consume_Message_ptt, operation=Consume_Message
    <2009-10-08 15:05:43,494> <INFO> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JmsResourceAdapter_endpointDeactivation: Deactivating endpoint Endpoint_10
    <2009-10-08 15:05:44,547> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Stopping inbound part of Adapter Framework instance: OraBPEL
    <2009-10-08 15:05:45,549> <INFO> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JmsResourceAdapter_stop: Jms Adapter stopped
    <2009-10-08 15:05:45,550> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::uninit Shutting down the JCA activation agent, processId='bpel://localhost/default/AIADiagnosticsDequeueMessageVerification~1.0/', activation properties={portType=Consume_Message_ptt}
    <2009-10-08 15:05:45,550> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - performing endpointDeactivation for portType=Consume_Message_ptt, operation=Consume_Message
    <2009-10-08 15:05:45,550> <WARN> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JmsResourceAdapter_endpointDeactivation: Cannot deactivate. Endpoint oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec@c50033 has not been activated before.
    <2009-10-08 15:05:45,550> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Stopping inbound part of Adapter Framework instance: OraBPEL
    <2009-10-08 15:05:45,570> <INFO> <default.collaxa.cube.engine> <AdaptorManager::unload> Uninitialized adaptors for platform 'ias_10g', datasource 'oracle'
    <2009-10-08 15:05:45,570> <INFO> <default.collaxa.cube.engine> <CubeEngine::uninit> Uninitialized BPEL domain "default"
    <2009-10-08 15:05:45,577> <INFO> <default.collaxa.cube.engine> <CubeEngine::unload> Unloaded BPEL domain "default"
    <2009-10-08 15:05:45,577> <INFO> <collaxa> <ServerManager::uninit> Done shutting down all domains
    09/10/08 15:06:07 Error initializing the Oracle JMS Resource provider for Queues: Io exception: Got minus one from a read call
    and after restarting OC4J we are able to enqueue messages into the database queue.If anyone has encountered similar problem could you please provide your suggestion to fix this issue .Thanks.
    Regards,
    Keynes.

    What have you configured for the response tab for the sender? Are you using the MPL or the MDB?
    Take a look at:
    MPL Best Practices (Doc Id 1308165.1)
    Oracle WebLogic JMS Integration (Doc Id: 1308181.1)

  • BPM: Message Stucked in Queue on Error even after Cancel Process

    Hi all,
    We have a scenario where we are using BPM to call RFCs in sequence using BPM. In case of exception, we make use of exception branch and canel the process. But even after doing so, failed messages are stucked in queue and if a new message comes in, it goes in pending status due to previous stucked messages.
    Can anybody please suggest how to overcome this.
    Thanks
    -Kulwant

    You need to make sure that:
    1) You have defined a Exception Handler in your Block
    2) You have included this in the Exception Branch properties.
    3) You have included this under the Exceptions section of your Sync Send Step....
    Even I got into the same situation and then figured out that F7 mentioned Exception will never be raised....why??.....the 3rd point was the reason.....check if same applicable to your case also...
    Regards,
    Abhishek.

  • File to Proxy scenario message failed in ECC with staus SYSFAIL

    Hi All,
    We are working on File to proxy scenario,  PI  able to send message successfully to ECC, but  In ECC , message got  stuck in queues with the status 'SYSFAIL',
    when I read the error message it is showing Address Invalid.
    when I run the LUW, it is giving 'Function module does not exist or EXCEPTION 'raised message.
    I'm using PI 7.1 EHP1 , ECC 6.0, can anyone suggest the trouble shooting guidelines for this issue?
    Thanks,
    Venu.

    when I run the LUW, it is giving 'Function module does not exist or EXCEPTION 'raised message.
    in your code, there seems to be an invalid statement.
    check the proxy code.

  • Error on WWI server EHS_GLM_GENSERV: Results file not found on production

    Hi Experts,
    I need some help/advice. We have issues with our new EH&S WWI server. 
    This new setup working OK with Dev and QA (the WWI and GLM part is just fine), We did try to link this server to production then it gives below error.
    Only difference between  existing WWI QA and production server is that
    Existing QA and development WWI server installed at location C:\Program Files (x86)\EHS\WWI 
    And Same path maintain on new server C:\Program Files (x86)\EHS\WWI  
    But existing production WWI server installation path  is  different C:\Program Files\EHS\WWI
    So is there any customizing changes required from SAP side to avoid this error on production
    Can you please advise on this.
    ================================================================================
    Error on WWI server EHS_GLM_GENSERV: Results file not found
    Message no. C$830
    Diagnosis
    The results file of the generation was not found on the WWI server EHS_GLM_GENSERV.
    System Response
    Generation was not carried out.
    Procedure
    Advise your system administrator to check the WWI installation on the WWI server EHS_GLM_GENSERV.
    Check the Windows event log on the WWI generation server. The event log may contain other error messages.
    SAP Note 1058521 provides possible solutions for this error.
    ==================================================================================
    Log shows
    ============================================================================================================================================
    E000 Error: OLE Exception (-2146823114) from Word8_OpenDoc (docs.Open) by Microsoft Word: This file could not be found. (C:\Windows\...\r00000000000001422051.rtf) (HRESULT Code:5174)
    E000 Error opening document (Word8_OpenDoc: Documents.Open failed)
    ================================================================================================================================================

    Hello Gajanan,
    the path of the temporay workfolder can be configured in the IMG. Often this path is setup as the WWI server installed location but it is just a temporay workfolder which must exist on the WWI server. The path can be configured under:
    For ECC 6.0 Ehp 0-2 and lower
    Environment, Health and Safety -> Basic Data and Tools -> Basic Settings -> Specify Environment Parameters
    For ECC 6.0 Ehp 3-6
    Environment, Health and Safety -> Product Safety -> Global Label Management -> Make Settings for Basic Data
    For ECC 6.0 Ehp 7
    Environment, Health and Safety -> Global Label Management -> Set Basic Data and Tools for Global Label Management -> Make Settings for Basic Data

  • File Content Conversion Error in PI 7.1 (file to Proxy)

    Hi
    I am working on File to Proxy Scenario and I gave the File content conversion as below, File is picking up by the PI Server when I look at Communication Channel Monitoring, However when I open the Message ID in the CC monitoring it says as
    404 Not Found
    The requested resource does not exist.
    and I do not see any message SXMB_MONI(Because the content is not converted), Can anyone give an idea how to debug this
    Thanks 
    PR
    Please find the details below which I gave in the content Conversion
    Document Name : MT_TW_AK
    Document NameSpace : http://aiwcd.com/Claims_Management(CM)_Rel2.0
    RecordSet Name : FROISROIAcknowledgement
    RecordSet Structure : Header,1,Record,*,Trailer,1
    Recordset Sequence : Ascending
    KeyField Name :TransactionSetID
    Key Field Type : String (Case Sensitive)
    IgnoreRecordsetName : true
    Header.fieldNames :TransactionSetID,SenderID,ReceiverID,DateTransmissionsent,TimeTransmissionsent,OriginalTransmissionDate,OriginalTransmissionTime,TestProductionCode,InterchangeVersionID
    Header.fieldFixedLengths: 3,25,25,8,6,8,6,1,5
    Header.keyFieldValue     : H
    Record.fieldSeparator :
    Record.fieldNames : TransactionSetID,RecordSequenceNumber,DateProcessed,TimeProcessed,InsurerFEIN,ClaimAdministratorPostalCode,ClaimAdministratorFein,AcknowledgementTransactionSetID,ApplicationAcknowledgmentCode,InsuredReportNumber,ClaimAdministratorClaimNumber,JuridictionClaimNumber,MaintenanceTypeCode,MaintenanceTypeCodeDate,RequestCode,FreeFormText,NumberofErrors,MaintenanceTypeCorrectionCode,MaintenanceTypeCorrectionCodeDate,JurisdictionBranchOfficeCode,ClaimAdministratorAlternatePostalCode,NumOfErrors
    Record.fieldFixedLengths: 3,9,8,6,9,9,9,3,2,25,25,25,2,8,3,60,2,2,8,2,9,19
    Record.keyFieldValue : A
    Trailer.fieldNames:TransactionSetID,DetailRecordCount,TransactionCount
    Trailer.fieldFixedLengths: 3,9,9 
    Trailer.keyFieldValue     : T
    ignoreRecordsetName: true

    PR,
    Can you check the error in sender communication channel?
    Go to RWB ---> Component Monitoring ---> Adapter Engine ---> Communication cahnnel monitoring --> it displays new page. Then give your file sender communication cahnnel name. There you will definitely see some error.
    The error what you are getting is a different to this one. Can you please check the error what I have given above path.
    Regards,
    ---Satish

  • ICM_HTTP_CONNECTION_FAILED error in file to proxy??

    Hi
    In my file to proxy,
    i am maintaining one Http RFC destination..intest Connection i am getting 500 as status.
    two TCP/IP destinations LCRSAPRFC and SAPSLDAPI.
    i am maintaing values in SPROXSET table.
    in SLDAPICUST also.
    and in SXMB_ADM i configuerd Integration engine.
    but i am getting error in sxmb_moni
    SAP:P4></![CDATA[>
      <SAP:AdditionalText><html><head><title>SAP Web Application Server Error</title> <style type="text/css"> body { font-family: arial, sans-serif;} </style> </head> <BODY text="#172972" link="#808080" vlink="#808080" alink="#8e236b" bgcolor=white leftmargin="0" topmargin="0" marginheight="0" marginwidth="0"> <table height="61" width="100%" border="0" cellspacing="0" cellpadding="0"><tr><td background="http://dcexi0605.aaaa.com:8030/sap/public/icman/img/bluebar_tile.gif" height="30"><table> <tr> <td width=5></td> <td width=20% nowrap><font face=arial size="-1" color=white>SAP Web Application Server </font></td><td width=75% align="right" nowrap><font face=arial size="-1" color="white"><a href="http://help.sap.com/">Help </font></td><td width=5% nowrap></font></td> </tr></table> </td><td rowspan=2 width=122 height=61 valign=top><img src= "http://dcexi0605.aaaa.com:8030/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td> </tr><tr><td background="http://dcexi0605.aaaa.com:8030/sap/public/icman/img/graybar_tile.jpg" height="31">  </td></tr> </table> <br><br> <table width=800> <tr><td width=50 nowrap> </td><td> <H2><b>404 Resource not found</b></H2><br><hr><br>Partner not reached<br><br><hr> <table border="0"> <tr><td>Error:</td><td>-20</td></tr> <tr><td>Version:</td><td>6040</td></tr> <tr><td>Component:</td><td>ICM</td></tr> <tr><td>Date/Time:</td><td>Wed Feb 28 12:28:10 2007 </td></tr> <tr><td>Module:</td><td>icxxconn_mt.c</td></tr> <tr><td>Line:</td><td>2121</td></tr> <tr><td>Server:</td><td>ciBGX30_BGX_30</td></tr> <tr><td>Detail:</td><td>Connection request from (42/31087/0) to host: dcesssss08.aaaa.biz, service: 8010 failed (NIECONN_REFUSED) AP-T42, U31087, 100 SOA_AAA, M2B-36-D-1787, 12:28:10, M0, W2, , 1/0</td></tr> </table> <p></p> </td></tr></table> <table><tr><td width=50 nowrap></td> <td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">© 2001-2005, SAP AG</a></FONT></td></tr></table></SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace=""></SAP:ApplicationFaultMessage>
      <SAP:Stack><b>Error when receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)</b></SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    please guide me where i did mistake
    regards
    Ram

    hi friends..
    now i am getting HTTP_RESP_STATUS_CODE_NOT_OK HTTP response contains status code 403 with the description Forbidden Error when sending by HTTP (error code: 403, error text: Forbidden)
    i maintaind in RZ10 the values.intially port is 8100 , now i changed it 8000
    in sxmb_adm..
    corresponding Integarion server:
    http://hostname:8030/sap/xi/engine?type=entry
    the same value is maintained in Sproxset table also
    in SMICM -Services Http services port is 8000
    please suggest me
    regards
    Ram

  • File to proxy ..HTTP_RESP_STATUS_CODE_NOT_OK error in sxmb_moni??

    Hi friends..
    in file to proxy.. i am getting error like this..
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Call Adapter --> <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand=""><SAP:Category>XIServer</SAP:Category><SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code><SAP:P1>500 </SAP:P1><SAP:P2>Internal Server Error</SAP:P2><SAP:P3></SAP:P3><SAP:P4></SAP:P4><SAP:AdditionalText><html><head><title>SAP Web Application Server Error</title>
    <style type="text/css">
    body { font-family: arial, sans-serif;}
    </style>
    </head>
    <BODY text="#172972" link="#808080" vlink="#808080"
    alink="#8e236b" bgcolor=white  leftmargin="0" topmargin="0"
    marginheight="0" marginwidth="0">
    <table height="61" width="100%" border="0" cellspacing="0"
    cellpadding="0"><tr><td background="http://dceazar01:8010/sap/public/icman/img/bluebar_tile.gif"
    height="30"><table> <tr> <td width=5></td> <td width=20% nowrap><font face=arial size="-1" color=white>SAP Web Application Server
    </font></td><td width=75% align="right" nowrap><font face=arial
    size="-1" color="white"><a href="http://help.sap.com/">Help
    </font></td><td width=5% nowrap></font></td> </tr></table>
    </td><td rowspan=2 width=122 height=61 valign=top><img src=
    "http://dceazar01:8010/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td>
    </tr><tr><td background="http://dceazar01:8010/sap/public/icman/img/graybar_tile.jpg" height="31">
     </td></tr>
    </table>
    <br><br>
    <table width=800>
    <tr><td width=50 nowrap>
    </td><td>
    <H2><b>500 Internal Server Error</b></H2><br><hr><br>Internal Server Error(-1)<br><br><hr>
    <table border="0">
    <tr><td>Error:</td><td>-1</td></tr>
    <tr><td>Version:</td><td>6040</td></tr>
    <tr><td>Component:</td><td>HTTP_PLG</td></tr>
    <tr><td>Date/Time:</td><td>Sun Jan  7 12:04:44 2007
    </td></tr>
    <tr><td>Module:</td><td>http_plg_mt.c</td></tr>
    <tr><td>Line:</td><td>3505</td></tr>
    <tr><td>Server:</td><td>dceazar01_SRD_10</td></tr>
    <tr><td>Detail:</td><td>No handler defined for this URL</td></tr>
    </table>
    <p></p>
    </td></tr></table>
    <table><tr><td width=50 nowrap></td>
    <td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">© 2001-2005, SAP AG</a></FONT></td></tr></table></SAP:AdditionalText><SAP:ApplicationFaultMessage namespace=""></SAP:ApplicationFaultMessage><SAP:Stack><b>HTTP response contains status code 500 with the description Internal Server Error
    Error when sending by HTTP (error code: 500, error text: Internal Server Error)</b></SAP:Stack><SAP:Retry>M</SAP:Retry></SAP:Error>
    please guide me..
    regards
    Ram

    hi friends..
    trace is like this...
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Call Adapter --> <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">Party normalization: sender </Trace>
    <Trace level="1" type="T">Sender scheme external = XIParty</Trace>
    <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
    <Trace level="1" type="T">Sender party external = </Trace>
    <Trace level="1" type="T">Sender party normalized = </Trace>
    <Trace level="1" type="T">Party normalization: receiver </Trace>
    <Trace level="1" type="T">Receiver scheme external = </Trace>
    <Trace level="1" type="T">Receiver agency external = </Trace>
    <Trace level="1" type="T">Receiver party external = </Trace>
    <Trace level="1" type="T">Receiver party normalized = </Trace>
    <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
    <Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
    <Trace level="2" type="T">Host = dcexi0602.aaaa.com:8000</Trace>
    <Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
    <Trace level="2" type="T">Remote address = 10.150.113.48</Trace>
    <Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
    <Trace level="3" type="T">Getting type of XMB... </Trace>
    <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
    </Trace>
    <Trace level="2" type="T">XMB kind = CENTRAL</Trace>
    <Trace level="3" type="T">Start pipeline found </Trace>
    <Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
    <Trace level="3" type="T">No triggers found. OK. </Trace>
    </Trace>
    <Trace level="1" type="T">**************************************************** </Trace>
    <Trace level="1" type="T">*                                                  * </Trace>
    <Trace level="1" type="T">*                                                  * </Trace>
    <Trace level="1" type="T">XMB entry processing </Trace>
    <Trace level="3" type="T">system-ID = DGX</Trace>
    <Trace level="3" type="T">client = 100</Trace>
    <Trace level="3" type="T">language = E</Trace>
    <Trace level="3" type="T">user = XIAFUSERDGX</Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:42Z 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><!-- ************************************ -->
    <Trace level="1" type="T">Message-GUID = 6799BA809E4D11DBB72AF6C9E0007003</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><!-- ************************************ -->
    <Trace level="3" type="T">QOS = EO</Trace>
    <Trace level="3" type="T">Message-GUID = 6799BA809E4D11DBB72AF6C9E0007003</Trace>
    <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
    <Trace level="3" type="T">External PLID = CENTRAL</Trace>
    <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
    <Trace level="3" type="T">Generate prefixed queue name </Trace>
    <Trace level="1" type="T">Queue name : XBTI0004</Trace>
    <Trace level="1" type="T">Generated prefixed queue name = XBTI0004</Trace>
    <Trace level="1" type="T">Schedule message in qRFC environment </Trace>
    <Trace level="3" type="T">Setup qRFC Scheduler </Trace>
    <Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>
    <Trace level="3" type="T">Call qRFC .... MsgGuid = 6799BA809E4D11DBB72AF6C9E0007003</Trace>
    <Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
    <Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
    <Trace level="3" type="T">OK. </Trace>
    <Trace level="1" type="T">----------------------------------------------------- </Trace>
    <Trace level="1" type="T">Going to persist message </Trace>
    <Trace level="1" type="T">NOTE: The following trace entries are always lacking </Trace>
    <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST </Trace>
    <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC </Trace>
    <Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
    <Trace level="1" type="T">----------------------------------------------------- </Trace>
    <Trace level="3" type="T">Version number = 000</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">Persisting message Status = 001</Trace>
    <Trace level="3" type="T">Message version 000</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
    <Trace level="3" type="T">Trace object available again now. OK. </Trace>
    <Trace level="3" type="T">Message was read from persist layer. OK. </Trace>
    <Trace level="3" type="T">Message properties in XMB object were setup. OK. </Trace>
    <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read </Trace>
    <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
    </Trace>
    <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
    <Trace level="1" type="B" name="SXMS_ASYNC_EXEC"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
    <Trace level="2" type="T">Increment log sequence to 001</Trace>
    <Trace level="1" type="T">----------------------------------------------------- </Trace>
    <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
    <Trace level="3" type="T">system-ID = DGX</Trace>
    <Trace level="3" type="T">client = 100</Trace>
    <Trace level="3" type="T">language = E</Trace>
    <Trace level="3" type="T">user = XIAFUSERDGX</Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET  </Trace>
    <Trace level="1" type="T">----------------------------------------------------- </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
    <Trace level="3" type="T">External PLID = CENTRAL</Trace>
    <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline attributes </Trace>
    <Trace level="3" type="T">PID        = SAP_CENTRAL</Trace>
    <Trace level="3" type="T">ENABLE     = 1</Trace>
    <Trace level="3" type="T">TRACELEVEL = 0</Trace>
    <Trace level="3" type="T">EXEMODE    = A</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline elements </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0001</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0002</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_INTERFACE_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0003</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0004</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_REQUEST</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0007</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_OUTBOUND_BINDING</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0008</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = =SWITCH=</Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0009</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_RESPONSE</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">ADRESSMOD  = LOCAL</Trace>
    <Trace level="3" type="T">P_CLASS    = CL_RD_PLSRV</Trace>
    <Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG     = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
    <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace>
    <Trace level="1" type="T"> Cache Content is up to date </Trace>
    <Trace level="2" type="T">Start without given receiver </Trace>
    <Trace level="2" type="T">Classic Receiver Determination via Rules. </Trace>
    <Trace level="2" type="T">Check conditions for rule line no. 1  </Trace>
    <Trace level="2" type="T">...valid Receiver w/o Condition:  - SAP_ERP_azar_DEV </Trace>
    <Trace level="2" type="T">No Receiver found behaviour: 0  </Trace>
    <Trace level="2" type="T">Number of Receivers:1  </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="3" type="T">Persisting message after plsrv call </Trace>
    <Trace level="3" type="T">Message-Version = 001</Trace>
    <Trace level="3" type="T">Message version 001</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_INTERFACE_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">ADRESSMOD  = LOCAL</Trace>
    <Trace level="3" type="T">P_CLASS    = CL_ID_PLSRV</Trace>
    <Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG     = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
    <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N </Trace>
    <Trace level="1" type="T"> Cache Content is up to date </Trace>
    <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If)  SAP_ERP_azar_DEV InterfaceCollection </Trace>
    <Trace level="2" type="T">...valid InbIf without Condition: InterfaceCollection </Trace>
    <Trace level="2" type="T">Number of receiving Interfaces:1  </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="3" type="T">Persisting message after plsrv call </Trace>
    <Trace level="3" type="T">Message-Version = 002</Trace>
    <Trace level="3" type="T">Message version 002</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT"></Trace><!-- ************************************ -->
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">ADRESSMOD  = LOCAL</Trace>
    <Trace level="3" type="T">P_CLASS    = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
    <Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG     = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <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><!-- ************************************ -->
    <Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="2" type="T">got property produced by receiver determination </Trace>
    <Trace level="1" type="T">number of receivers: 1 </Trace>
    <Trace level="1" type="T">Single-receiver split case </Trace>
    <Trace level="1" type="T">Post-split internal queue name = XBTOE1__0000</Trace>
    <Trace level="1" type="T">------------------------------------------------ </Trace>
    <Trace level="1" type="T">Persisting single message for post-split handling </Trace>
    <Trace level="1" type="T"> </Trace>
    <Trace level="1" type="T">Going to persist message + call qRFC now... </Trace>
    <Trace level="1" type="T">NOTE: The following trace entries are always lacking </Trace>
    <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST </Trace>
    <Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
    <Trace level="1" type="T">------------------------------------------------ </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">Persisting message Status = 012</Trace>
    <Trace level="3" type="T">Message version 003</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
    <Trace level="3" type="T">Trace object available again now. OK. </Trace>
    <Trace level="3" type="T">Message was read from persist layer. OK. </Trace>
    <Trace level="3" type="T">Message properties in XMB object were setup. OK. </Trace>
    <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read </Trace>
    <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
    </Trace>
    <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
    <Trace level="1" type="B" name="SXMS_ASYNC_EXEC"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
    <Trace level="2" type="T">Increment log sequence to 005</Trace>
    <Trace level="1" type="T">----------------------------------------------------- </Trace>
    <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
    <Trace level="3" type="T">system-ID = DGX</Trace>
    <Trace level="3" type="T">client = 100</Trace>
    <Trace level="3" type="T">language = E</Trace>
    <Trace level="3" type="T">user = XIAFUSERDGX</Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET  </Trace>
    <Trace level="1" type="T">----------------------------------------------------- </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
    <Trace level="3" type="T">External PLID = CENTRAL</Trace>
    <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline attributes </Trace>
    <Trace level="3" type="T">PID        = SAP_CENTRAL</Trace>
    <Trace level="3" type="T">ENABLE     = 1</Trace>
    <Trace level="3" type="T">TRACELEVEL = 0</Trace>
    <Trace level="3" type="T">EXEMODE    = A</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline elements </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0001</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0002</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_INTERFACE_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0003</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0004</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_REQUEST</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0007</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_OUTBOUND_BINDING</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0008</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = =SWITCH=</Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0009</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_RESPONSE</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
    <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_REQUEST</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">ADRESSMOD  = LOCAL</Trace>
    <Trace level="3" type="T">P_CLASS    = CL_MAPPING_XMS_PLSRV3</Trace>
    <Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG     = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
    <Trace level="2" type="T">......attachment XI_Context not found </Trace>
    <Trace level="3" type="T">Mapping is already determined in the interface determination </Trace>
    <Trace level="3" type="T">Object ID of Interface Mapping DA461E413F303668931A977B9D811191 </Trace>
    <Trace level="3" type="T">Version ID of Interface Mapping B2CF8EF067FF11DBA742D7830A967135 </Trace>
    <Trace level="1" type="T">Mapping-Object-Id:DA461E413F303668931A977B9D811191 </Trace>
    <Trace level="1" type="T">Mapping-SWCV:B2CF8EF067FF11DBA742D7830A967135 </Trace>
    <Trace level="1" type="T">Mapping-Step:1  </Trace>
    <Trace level="1" type="T">Mapping-Type:JAVA </Trace>
    <Trace level="1" type="T">Mapping-Program:com/sap/xi/tf/_MM_M_StockMov_To_SAP_ </Trace>
    <Trace level="3" type="T">Dynamic configuration is empty </Trace>
    <Trace level="3" type="T">Multi mapping required. </Trace>
    <Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_M_StockMov_To_SAP_. </Trace>
    <Trace level="3" type="T">Load b2cf8ef0-67ff-11db-a742-d7830a967135, http://aaaa.com/xi/PROCESS/PPE/ERP_MES, -1, com/sap/xi/tf/_MM_M_StockMov_To_SAP_.class. </Trace>
    <Trace level="3" type="T">Search com/sap/xi/tf/_MM_M_StockMov_To_SAP_.class (http://aaaa.com/xi/PROCESS/PPE/ERP_MES, -1) in swcv b2cf8ef0-67ff-11db-a742-d7830a967135. </Trace>
    <Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_M_StockMov_To_SAP_ </Trace>
    <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_M_StockMov_To_SAP_ </Trace>
    <Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_M_StockMov_To_SAP_ completed. (executeStep() of com.sap.xi.tf._MM_M_StockMov_To_SAP_ </Trace>
    <Trace level="3" type="T">Message Type 1  Number of messages 1  </Trace>
    <Trace level="3" type="T">Dynamic configuration is empty </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="3" type="T">Persisting message after plsrv call </Trace>
    <Trace level="3" type="T">Message-Version = 005</Trace>
    <Trace level="3" type="T">Message version 005</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_OUTBOUND_BINDING</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">ADRESSMOD  = LOCAL</Trace>
    <Trace level="3" type="T">P_CLASS    = CL_XMS_PLSRV_OUTBINDING</Trace>
    <Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG     = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
    <Trace level="2" type="T">O U T B O U N D - B I N D I N G </Trace>
    <Trace level="2" type="T"> Cache Content is up to date </Trace>
    <Trace level="2" type="T">determine  OUTBOUND BINDING  for: </Trace>
    <Trace level="2" type="T">-Bs_MES_Stock_proxy </Trace>
    <Trace level="2" type="T">-SAP_ERP_azar_DEV </Trace>
    <Trace level="2" type="T">http://aaaa.com/xi/PROCESS/PPE/ERP_MES.MI_IN_S_StockMov </Trace>
    <Trace level="2" type="T">Channel found:  - SAP_ERP_azar_DEV - CC_IN_XI_Proxy </Trace>
    <Trace level="2" type="T">no header mapping defined </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="3" type="T">Persisting message after plsrv call </Trace>
    <Trace level="3" type="T">Message-Version = 006</Trace>
    <Trace level="3" type="T">Message version 006</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER"></Trace><!-- ************************************ -->
    <Trace level="1" type="Timestamp">2007-01-07T12:48:43Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = =SWITCH=</Trace>
    <Trace level="3" type="T">ADRESSMOD  = SD</Trace>
    <Trace level="3" type="T">P_CLASS    = </Trace>
    <Trace level="3" type="T">P_IFNAME   = </Trace>
    <Trace level="3" type="T">P_METHOD   = </Trace>
    <Trace level="3" type="T">FL_LOG     = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Channel for Integration Engine: XI</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = IENGINE</Trace>
    <Trace level="3" type="T">ADRESSMOD  = SD</Trace>
    <Trace level="3" type="T">P_CLASS    = CL_XMS_PLSRV_IE_ADAPTER</Trace>
    <Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG     = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
    <Trace level="3" type="T">Channel for Integration Engine: XI</Trace>
    <Trace level="1" type="T">Sender: Header mapped to</Trace>
    <Trace level="1" type="T">Party = </Trace>
    <Trace level="1" type="T">Agency = </Trace>
    <Trace level="1" type="T">Scheme = </Trace>
    <Trace level="1" type="T">Service = Bs_MES_Stock_proxy</Trace>
    <Trace level="1" type="T">Receiver: Header mapped to</Trace>
    <Trace level="1" type="T">Party = </Trace>
    <Trace level="1" type="T">Agency = </Trace>
    <Trace level="1" type="T">Scheme = </Trace>
    <Trace level="1" type="T">Service = SAP_ERP_azar_DEV</Trace>
    <Trace level="1" type="T">Party denormalization: sender </Trace>
    <Trace level="1" type="T">Sender target scheme = </Trace>
    <Trace level="1" type="T">Sender target agency = </Trace>
    <Trace level="1" type="T">Sender party normalized = </Trace>
    <Trace level="1" type="T">Sender party external = </Trace>
    <Trace level="1" type="T">Party denormalization: receiver </Trace>
    <Trace level="1" type="T">Receiver target scheme = </Trace>
    <Trace level="1" type="T">Receiver target agency = </Trace>
    <Trace level="1" type="T">Receiver party normalized = </Trace>
    <Trace level="1" type="T">Receiver party external = </Trace>
    <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
    <Trace level="2" type="T">Addressing mode: url</Trace>
    <Trace level="3" type="T">Host = dceazar01</Trace>
    <Trace level="3" type="T">Port = 8010</Trace>
    <Trace level="3" type="T">Transport protocol = HTTP      1.0</Trace>
    <Trace level="3" type="T">Message protocol = </Trace>
    <Trace level="3" type="T">Path = sap/xi/engine?type=receiver</Trace>
    <Trace level="2" type="T">Auth mode: basicSAP</Trace>
    <Trace level="3" type="T">Conversion of language from char2 to char1 EN</Trace>
    <Trace level="3" type="T">User = asar</Trace>
    <Trace level="3" type="T">Client = 400</Trace>
    <Trace level="3" type="T">Language = E</Trace>
    <Trace level="3" type="T">Creating HTTP-client </Trace>
    <Trace level="3" type="T">HTTP-client: creation finished</Trace>
    <Trace level="3" type="T">Security: Basic authentication SAP </Trace>
    <Trace level="3" type="T">Serializing message object... </Trace>
    <Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
    <Trace level="3" type="T">HTTP-client: request sent</Trace>
    <Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
    <Trace level="3" type="T">HTTP-client: response received</Trace>
    <Trace level="3" type="T">HTTP-client: checking status code...</Trace>
    <Trace level="3" type="T">HTTP-client: status code = 500 </Trace>
    <Trace level="3" type="T">Deserializing message object... </Trace>
    <Trace level="3" type="System_Error">HTTP-client: error response= <html><head><title>SAP Web Application Server Error</title>
    <style type="text/css">
    body { font-family: arial, sans-serif;}
    </style>
    </head>
    <BODY text="#172972" link="#808080" vlink="#808080"
    alink="#8e236b" bgcolor=white  leftmargin="0" topmargin="0"
    marginheight="0" marginwidth="0">
    <table height="61" width="100%" border="0" cellspacing="0"
    cellpadding="0"><tr><td background="http://dceazar01:8010/sap/public/icman/img/bluebar_tile.gif"
    height="30"><table> <tr> <td width=5></td> <td width=20% nowrap><font face=arial size="-1" color=white>SAP Web Application Server
    </font></td><td width=75% align="right" nowrap><font face=arial
    size="-1" color="white"><a href="http://help.sap.com/">Help
    </font></td><td width=5% nowrap></font></td> </tr></table>
    </td><td rowspan=2 width=122 height=61 valign=top><img src=
    "http://dceazar01:8010/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td>
    </tr><tr><td background="http://dceazar01:8010/sap/public/icman/img/graybar_tile.jpg" height="31">
     </td></tr>
    </table>
    <br><br>
    <table width=800>
    <tr><td width=50 nowrap>
    </td><td>
    <H2><b>500 Internal Server Error</b></H2><br><hr><br>Internal Server Error(-1)<br><br><hr>
    <table border="0">
    <tr><td>Error:</td><td>-1</td></tr>
    <tr><td>Version:</td><td>6040</td></tr>
    <tr><td>Component:</td><td>HTTP_PLG</td></tr>
    <tr><td>Date/Time:</td><td>Sun Jan  7 13:48:43 2007
    </td></tr>
    <tr><td>Module:</td><td>http_plg_mt.c</td></tr>
    <tr><td>Line:</td><td>3505</td></tr>
    <tr><td>Server:</td><td>dceazar01_SRD_10</td></tr>
    <tr><td>Detail:</td><td>No handler defined for this URL</td></tr>
    </table>
    <p></p>
    </td></tr></table>
    <table><tr><td width=50 nowrap></td>
    <td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">© 2001-2005, SAP AG</a></FONT></td></tr></table></Trace>
    <Trace level="3" type="T">HTTP-client: closing...</Trace>
    </Trace>
    <Trace level="2" type="T">Switch back to normalized party (HTTP response)</Trace>
    <Trace level="1" type="T">Sender scheme external = </Trace>
    <Trace level="1" type="T">Sender agency external = </Trace>
    <Trace level="1" type="T">Sender party external = </Trace>
    <Trace level="1" type="T">Sender party normalized = </Trace>
    <Trace level="1" type="T">Party normalization: receiver </Trace>
    <Trace level="1" type="T">Receiver scheme external = </Trace>
    <Trace level="1" type="T">Receiver agency external = </Trace>
    <Trace level="1" type="T">Receiver party external = </Trace>
    <Trace level="1" type="T">Receiver party normalized = </Trace>
    <Trace level="2" type="T">Undo header mapping (HTTP response) </Trace>
    <Trace level="1" type="T">Sender: Header before undo of mapping</Trace>
    <Trace level="1" type="T">Party = </Trace>
    <Trace level="1" type="T">Agency = </Trace>
    <Trace level="1" type="T">Scheme = </Trace>
    <Trace level="1" type="T">Service = Bs_MES_Stock_proxy</Trace>
    <Trace level="1" type="T">Receiver: Header before undo of mapping</Trace>
    <Trace level="1" type="T">Party = </Trace>
    <Trace level="1" type="T">Agency = </Trace>
    <Trace level="1" type="T">Scheme = </Trace>
    <Trace level="1" type="T">Service = SAP_ERP_azar_DEV</Trace>
    <Trace level="2" type="T">Sender: Header after undo of mapping</Trace>
    <Trace level="2" type="T">Party = </Trace>
    <Trace level="2" type="T">Agency = </Trace>
    <Trace level="2" type="T">Scheme = </Trace>
    <Trace level="2" type="T">Service = Bs_MES_Stock_proxy</Trace>
    <Trace level="2" type="T">Receiver: Header before undo of mapping</Trace>
    <Trace level="2" type="T">Party = </Trace>
    <Trace level="2" type="T">Agency = </Trace>
    <Trace level="2" type="T">Scheme = </Trace>
    <Trace level="2" type="T">Service = SAP_ERP_azar_DEV</Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="3" type="T">Persisting message after plsrv call </Trace>
    <Trace level="3" type="T">Message-Version = 007</Trace>
    <Trace level="3" type="T">Message version 007</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    <Trace level="3" type="System_Error">Error exception return from pipeline processing! </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">Persisting message Status = 014</Trace>
    <Trace level="3" type="T">Message version 008</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </SAP:Trace>
    please guide me ...
    regards
    Ram

  • File To Proxy : Handle the response from ECC to send mail without BPM

    Hi,
    Scenario: FILE To Proxy
    Requirement: We are receiving xml acknowledgement file from bank with IDoc number and status in SAP PI and the file is used to send the status number, message and and IDoc number to ECC. After request is received in ECC BAPI is executed to update the original status of outbound IDOC.
    There would be multiple records in file and PI will send all IDoc acknowledgement to ECC to update the IDoc status.
    Issue: Since PI send all records to ecc, if any single IDoc status update is failing in ECC how would it can be communicated to support.
    ECC can send success or error response in proxy but how we can use the same in PI to send mail to support. Or is there any better error handling we can go for in such scenario.
    Thanks,
    Vertika

    Hi everyone
    thanks for response.
    Interface 1: IDoc (ECC) to File (Bank) --> Done
    Interface 2: Acknowledgment File (Bank) to BAPI (ECC) where BAPI will update the status of IDoc sent in first interface.
    For Interface 2 : PI will receive file from Bank with multiple records i.e multiple IDoc numbers and their status. PI will invoke proxy to send the IDoc number and status number (eg 16) for all the records together. Now if BAPI fails to update status of any single IDoc in that file how support team will know that the particular record is failed. To handle this error ECC is saying they can send Error and Success back to PI. But the problem is how we can use that response in PI in the same interface to send emails to support team. Bank does not want any response back in this case. This is just to ensure proper error handling since this is bank related interface.
    Splitting the interface in two interfaces will definitely help. But is there some way which can be used in same interface and based on error response from ECC mail is triggered.
    If any one has better suggestion for such kind of error handling, please post the same.
    Thanks,
    Vertika

  • [Error] Microsoft SQL Server 2008 Setup. Error reading from file msdbdata.mdf

    Hi all
    I'm trying to install SQL 2008 Express on my Computer: Hp compact DX7300 Slim tower.
    and get this error:
    TITLE: Microsoft SQL Server 2008 Setup
    The following error has occurred:Error reading from file d:\8268cd7b247d294de359c9\x86\setup\sql_engine_core_inst_msi\PFiles\SqlServr\MSSQL.X\MSSQL\Binn\Template\msdbdata.mdf.  Verify that the file exists and that you can access it.
    Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1823.0&EvtType=0xF45F6601%25401201%25401
    Log file
    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Exit code (Decimal):           -2068643839
      Exit facility code:            1203
      Exit error code:               1
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Start time:                    2014-12-09 23:22:03
      End time:                      2014-12-09 23:40:28
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\sql_engine_core_inst_Cpu32_1.log
      Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1823.0
    Machine Properties:
      Machine name:                  VISTA-PC
      Machine processor count:       2
      OS version:                    Windows Vista
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
    Package properties:
      Description:                   SQL Server Database Services 2008
      SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
      ProductName:                   SQL2008
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         d:\8268cd7b247d294de359c9\x86\setup\
      Installation edition:          EXPRESS
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Disabled
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\ConfigurationFile.ini
      ENABLERANU:                    True
      ERRORREPORTING:                False
      FEATURES:                      SQLENGINE,REPLICATION
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    SQLExpress
      INSTANCENAME:                  SQLEXPRESS
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      MEDIASOURCE:                   d:\8268cd7b247d294de359c9\
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      RSINSTALLMODE:                 FilesOnlyMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           VISTA-PC\VISTA
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    0
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\SystemConfigurationCheck_Report.htm
    I will very appriciate if someone can help me solve it. I was trying to set Full control for my account in Properties/Security of root folder and try again but error is still.
    Many thanks

    Hi Foreverduy,
    Before you run SQL Server 2008 express setup, make sure that you have installed Windows installer 4.5 and.NET Framework 3.5 SP1 manually. For more information about the process, please refer to the article:
    http://msdn.microsoft.com/en-us/library/ms143506(v=sql.100).aspx. Moreover, please turn off all the third-party softwares which could prohibit the installation process.
    According to your error message, the issue could be due to that your account has no rights to install SQL Server, or the corruption on the media.
    Firstly, please ensure that your account has admin rights. Also make sure that you right-click the setup.exe and choose “Run as administrator” to complete the installation.
    Secondly, please check if "msdbdata.mdf" file exists at d:\8268cd7b247d294de359c9\x86\setup\sql_engine_core_inst_msi\PFiles\SqlServr\MSSQL.X\MSSQL\Binn\Template. If it exists, please make sure that your account has read permission to the extracted
    folder.
    However, if the file doesn't exist in the extraction, the media could be corrupt. Please download the
    media
    again and check if the issue still occurs.
    Regards,
    Michelle Li

  • Error in FILE 2 Proxy Scenario

    Hi All,
    I am doing File to Proxy Scenario i am getting following error
    Could any one provide the solution for this.
      *<?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>XIProxy</SAP:Category>
      <SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>
      <SAP:P1>ifmmessif</SAP:P1>
      <SAP:P2>MI_Emp_Sender</SAP:P2>
      <SAP:P3>Namespace</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>No implementing class registered for the interface (ABAP interface, request message MI_Emp_Sender, request message, namespace )</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
    Thanks in Advance
    Mahesh
      </SAP:Error>
    Edited by: Mahesh Reddy on Jul 10, 2008 12:47 PM

    Hi Mahesh,
    1) Use SPROXY transaction.
        Menu-> Proxy -> Activate All.
    2) check in the interface determination if u are using correct
    inbound interface.
    3) If this if fine....try deleting all proxy objects of the interface
    and create new.
    Regards,
    Praveen K

Maybe you are looking for

  • Java applet will not install in browser

    My VI will not install a JAva Applet. I jsut keeps saying "Installing Java Applet" and it never prompts for an install or anything. Any ideas? Is there something extra that I need to do that I am not realizing? I attached a screenshot of the window w

  • Solution (or posible) to undetected Ipods!

    Important note: The author of this message doesn't have english as its natal languaje, so there may be some errors especially on verb conjugations. Continue reading: I had the same problems with my brother's new incredible Ipod Video. He almost not k

  • Format, use and rate in easy setup with the JVC gy-hm100u

    Hi. I am about to start using Final Cut studio with my JVC gy-hm100u camcorder. What format, use and rate should I choose in the easy set up?

  • Undetected resolutions doesn't stick !!!

    After following http://mcaf.ee/rqaln (arch-wiki) and doing creating with cvt cvt 1600 900 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz Modeline [b]"1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync[/b] maki

  • Adobe flash CS3 professional

    Hi ! I'm french, so my english isn't totally perfect ! But i absolutely need your help in order to resolve my problem. I call the hot line of adobe to find a solution to my problem but this only one could be resolved asking directly my question in th