File-Proxy (Error while receiving by HTTP )

Hi All,
I have a problem in the scenario file to Proxy....which is that after placing a source file successfuly in the source directory.... it is showing an information message in the XML message monitoring(sxmb_moni) like below
Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)
Could anybody  explain the problem please????where i need to configure to reslove this.
Thanks.
Respond me Imme pls.

First thing to check is that the adapter_plain service is activated in the transaction SICF. (path: default_host-> sap -> xi -> adapter_plain
Then check that the http service is running properly (transaction SMICM).
Also, unless you are connecting to an SAP webAS, you should give a username and password, rather than "Use Logon data fotr SAP System". You could also maintain the URL and authentication data as an sm59 destination and use that in the adapter.
Please look at these...
INTEGRATION_DIRECTORY_HMI: Connection fails
ICM_HTTP_CONNECTION_FAILED
SAF - ICM_HTTP_CONNECTION_FAILED
HTTP adapter setup
Check out this SAP Note- 824554
Also this links
ICM_HTTP_CONNECTION_FAILED
Cache Refresh~
https://websmp201.sap-ag.de/~sapdownload/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
ICM_HTTP_CONNECTION_FAILED ERROR
error code: 400, error text: ICM_HTTP_CONNECTION_FAILED
Error With ABAP Client proxy
Message not reaching Integration server
HTTP content sever - error?
Error in content server configuration
HTTP Client : Code 110 reason
RFC: INTEGRATION_DIRECTORY_HMI
Content server config - error?
Thanks
Swarup

Similar Messages

  • Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED

    Hi experts,
    I have a big issue in production server,
    the Queues are stuking in smq2 " command to tRFC/qRFC: execute LUW again"
    if i am reprocess or press F6 it is going manually.
      <?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="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>400</SAP:P1>
      <SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText><html><head><title>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://xidist:8000/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 NetWeaver 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://xidist:8000/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td> </tr><tr><td background="http://xidist:8000/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>Partner not reached<br><br><hr> <table border="0"> <tr><td>Error:</td><td>-20</td></tr> <tr><td>Version:</td><td>7000</td></tr> <tr><td>Component:</td><td>ICM</td></tr> <tr><td>Date/Time:</td><td>Wed May 14 15:50:24 2014 </td></tr> <tr><td>Module:</td><td>icxxconn.c</td></tr> <tr><td>Line:</td><td>2341</td></tr> <tr><td>Server:</td><td>xidist_GXI_00</td></tr> <tr><td>Error Tag:</td><td>{004654a1}</td></tr> <tr><td>Detail:</td><td>Connection request from (110/28816/0) to host: xidist, service: 50000 failed (NIESERV_USED) EX-T110, U28816, 001 PIAFUSER, 10.1.57.50, 15:50:24, M0, W1, , 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/">&copy; 2001-2009, SAP AG</a></FONT> </td></tr></table> </body></html></SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Regards,
    Kiran polani

    Dear Sriram Ramani,
    in ths case some scenarios are working good. proxy to soap, idoc to soap and jdbc to proxy, proxy to jdbc all are working with out error.
    but my problem is in Soap to RFC case..
    for all RFC communication channels are working but some time it is throwing RFC_COMMUNICATION_ERROR and messages are stucks in smq2 with retry.
    when i check with retry error with in sxmb_moni log showing ICM_HTTP_CONNECTION_FAILED with error code 400.
    not for all signals for few signals for some time..
    Why it is happening i can't understand.
    in repository it is saying Repsitory object hmi failed and address already in use.
    is there any problem with loading IR objects.
    Please suggest me good suggestion for this type of issue what can do for this to resolve.
    Regards,
    Kiran Polani

  • Error CLIENT_RECEIVE_FAILED  Error while receiving by HTTP

    Hi,
    I am working on a XML to flat file scenario where I am using MULTI Mapping to get multiple outputfiles.but in SXMb_MONI I am getting this below  error. and mesages are stuck in SMQ2.
    <?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_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    what might be the cause for the error and do i need to enable any TUNING parameteres in IE specific config ?
    I have gone through different que blogs,but cant find the right one.
    thank you,
    babu

    Babu,
             the error has occured in the last pipeline step - Call adapter... Looks like the message size is too large (happens sometimes with multimapping)...Try increasing the max request size parameter.
    Please go through Micheal's Post - >
    Re: Error-Code: 108 - CLIENT_RECEIVE_FAILED
    Also go through the tuning guide...
    regards,
    Arvind R

  • Error while receiving by HTTP (error code: 110)  ?

    Hi Experts,
    I am working on IDOC to file Scenario.
    I am getting this error in SXMB_MONI. What may be the reason.
    <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_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )</SAP:Stack>
      <SAP:Retry>A</SAP:Retry>
      </SAP:Error>
    Best Regards,
    Anil

    Check these threaads:
    Re: XI Error when upgraded to SP14 (Error Code 110) CLIENT_RECEIVE_FAILED
    Regards,
    ravi

  • Getting the error: Error while receiving by HTTP error code: 110

    Hi,
    I have developed an interface which actually gets data from SCM system and in BPM to gets additional data from R/3. There are five synchronous call to this R/3 to get different sets of data. I am using only one communciation channle from BPM to R/3. The interface works perfectly OK in the development system. When the interface is migrated to the test system I found that the four calls work perfectly fine while the last call error out as below and the J2ee server goes down:
    <?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="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Any input/help will be appreciated. I have tried increasing timeout/connection alive time but still not get resolved.
    Thanks in advance,
    Sushma

    Hi Prateek,
    Thanks. But this note I have checked before and this seems not related. I actually found out the system logs in SM21 and saw the "Operating system call recv failed (error no. 10054)". What I did then is I seach notes related to this error and found a numebr of SAP notes. And I have informed the Basis guys to look into the notes and the system logs. They are working on this and they are deleting the old messages which have errored out. They are suspecting the system memory or too many old messages would have caused this issue.
    If you have any knowledge of why this error would have occurred please let me know.
    Thanks,
    Sushma

  • Timeout error in ECC "INTERNAL.CLIENT_RECEIVE_FAILED Error while receiving by HTTP (error code: 402 , error text: ICM_HTTP_TIMEOUT)"

    Dear Experts,
    I am very critical situation due to this timeout error in ECC, please help me as much as you can. Go-live date is very near, but I am not getting any clue why this error is occurring. our ECC system is EHP 4, and PI is dual stack 7.4
    My scenario is synchronous ABAP proxy to HTTP_AAE. request is triggering from ECC via proxy and reaching to third party (bank) through PI, I am reviving the response back in PI from bank. But from PI to ECC the response is not reaching. So in ECC after the defined Timeout limit its getting timed out.
    I have tried everything by increasing the timeout in ECC more than 15 minutes in HTTP_TIMEOUT under SXMB_adm in ECC, but nothing worked, even if I am increasing for half an hour then also its getting timeout after half an hour.
    response from bank to PI is coming within 30 to 40 seconds, but PI is not sending the response back to ECC.
    This is classical scenario, and I have checked the trace via SXMB_Moni in PI as well as in ECC, in ECC its showing the timeout error, but in PI i did not see any trace for this error.
    I have read many thread on SCN for the same error, and everywhere it has been suggested to increase the timeout, and I have tired that, it didn't help me.
    All ABAP proxy configuration has been done as follows.
    RFC destinations in ECC
    LCRSAPRFC(TCP/IP)
    SAPSLDAPI ((TCP/IP))
    G type destination to path "/sap/xi/engine?type=entry"
    G type destination SAP_PROXY_ESR to path "/rep"
    All the destination connection test is working fine.
    but i have a doubt on G type destination(AAE_XDJ) to path  "/sap/xi/engine?type=entry" which is returns the status code 500 with message "Empty HTTP request received", is it ok with 500 ?
    Configuration in ECC Integration Engine configuration is as follows
    Questions
    How the message gets pushed to ECC from PI, once the message received in PI, I believe by G type RFC destination on path  "/sap/xi/engine?type=entry" , please clarify.
    How to trace this, if message is not getting pushed to ECC, I mean I have checked the trace in PI XSMB_MONI, but didn't get anything for this error. In ECC SXMB_moni only I am able to the timeout error.
    Please expert help me as soon as you can, this error really effecting me badly in front of management
    Thanks,
    Farhan

    Hi Hareesh,
    I configured the scenario based on ICO, and again I received the same timeout error in ECC.
    I am really sick with this error, and I have raised the OSS message to SAP. Meanwhile I just want to double check my entire configuration with you. Please see the below configuration (for classical) for ABAP proxy to HTTP_AAE, and let me know if anything is wrong.
    Request structure (ECC->PI->Bank)
    <?xml version='1.0' ?>
    <PaymentInfoMessage>
    <PaymentInfoRequest>
    <CompanyCode>Partner01</CompanyCode>
    <BankCode>BSFRSARI</BankCode>
    <StartDate>2006-07-09T00:00:00</StartDate>
    <EndDate>2006-07-09T00:00:00</EndDate>
    <TransactionType>940</TransactionType>
    </PaymentInfoRequest>
    </PaymentInfoMessage>
    Response Structure (Bank->PI->ECC)
    <?xml version="1.0"?>
    <PaymentInfoMessageResponse>
    <PaymentInfoResponse>
        <TransactionType>940</TransactionType>
        <SequenceNum>1</SequenceNum>
        <ReceiptTime>2002-01-02T18:01:00</ReceiptTime>
        <ProcessStatus>1</ProcessStatus>
        <Comment>No Comment</Comment>
        <TransactionData>:20:MT940-1007200601
    :25:3210000079901
    :28C:190/0001
    </TransactionData>
        <CompanyCode>PARTNER01</CompanyCode>
    </PaymentInfoResponse>
    <StatusCode>OK</StatusCode>
    <StatusDetail>OK</StatusDetail>
    <ResponseItemCount>2</ResponseItemCount>
    </PaymentInfoMessageResponse>
    ESR Configuration
    Please see the below screenshot for ESR config. I have created 4 data types, 4 message types, 2 Service interface (synchronous), 2 mapping and one operation mapping.
    I just want to clarify about selecting the Request and response message type in inbound and outbound service interface.
    <?xml version='1.0' ?>
    <PaymentInfoMessage>
    <PaymentInfoRequest>
    <CompanyCode>Partner01</CompanyCode>
    <BankCode>BSFRSARI</BankCode>
    <StartDate>2006-07-09T00:00:00</StartDate>
    <EndDate>2006-07-09T00:00:00</EndDate>
    <TransactionType>940</TransactionType>
    </PaymentInfoRequest>
    </PaymentInfoMessage>
    Response Structure (Bank->PI->ECC)
    <?xml version="1.0"?>
    <PaymentInfoMessageResponse>
    <PaymentInfoResponse>
        <TransactionType>940</TransactionType>
        <SequenceNum>1</SequenceNum>
        <ReceiptTime>2002-01-02T18:01:00</ReceiptTime>
        <ProcessStatus>1</ProcessStatus>
        <Comment>No Comment</Comment>
        <TransactionData>:20:MT940-1007200601
    :25:3210000079901
    :28C:190/0001
    </TransactionData>
        <CompanyCode>PARTNER01</CompanyCode>
    </PaymentInfoResponse>
    <StatusCode>OK</StatusCode>
    <StatusDetail>OK</StatusDetail>
    <ResponseItemCount>2</ResponseItemCount>
    </PaymentInfoMessageResponse>
    ESR Configuration
    I have simply created 2 data types for requests(ECC->PI->Bank) and did one to one mapping. Similarly for response(Bank->PI->ECC) 2 data types, one to one mapping for this as well.
    But I just want to clarify about selecting the Request and response message type in inbound and outbound service interface. please explain me this for synchronous interface.
    Please see the below structure from ESR and inbound and Outbound service and let me know if the selection of Request and response message types is correct or not.
    OutBound service interface
    Inbound service interface
    Thanks,
    Farhan

  • Error while creating the HTTP client with destination GB_DPSRetrieve

    Hi All,
    It is an interface R/3 -->XI --> HTTP ( proxy to HTTP ).
    Please find the error log below and throw some light why the HTTP adapter is getting error -
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>SystemError</SAP:MessageClass>
      <SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
      <SAP:MessageId>DC98499F-7E42-74F1-A41F-0017A4107EE6</SAP:MessageId>
      <SAP:RefToMessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:RefToMessageId>
      <SAP:TimeSent>2007-11-21T15:51:30Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">GovernmentGateway</SAP:Party>
      <SAP:Service>GGMailbox</SAP:Service>
      <SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>SAP_DEV_ERP2005</SAP:Service>
      <SAP:Interface namespace="http://sap.com/xi/HR">HR_GB_EFI_DPSretrieve</SAP:Interface>
      </SAP:Receiver>
      <SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
      </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>BestEffort</SAP:QualityOfService>
      </SAP:ReliableMessaging>
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT_DEST</SAP:Code>
      <SAP:P1>GB_DPSRetrieve</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while creating the HTTP client with destination GB_DPSRetrieve</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    - <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    - <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
      <SAP:Engine type="BS">SAP_DEV_ERP2005</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
    - <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
      <SAP:Engine type="IS">is.00.lbsth-tb1ci</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
    - <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
      <SAP:Engine type="IS" />
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
      <SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
      <SAP:Info />
      </SAP:Hop>
      </SAP:HopList>
    - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Date>20071121</SAP:Date>
      <SAP:Time>155130</SAP:Time>
      <SAP:Host>lbsth-tb1ci</SAP:Host>
      <SAP:SystemId>XIS</SAP:SystemId>
      <SAP:SystemNr>00</SAP:SystemNr>
      <SAP:OS>Windows NT</SAP:OS>
      <SAP:DB>ORACLE</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>023</SAP:ProcStatus>
      <SAP:AdapterStatus>000</SAP:AdapterStatus>
      <SAP:User>PISUPER</SAP:User>
      <SAP:TraceLevel>1</SAP:TraceLevel>
      <SAP:LogSeqNbr>000</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
      <SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
      <SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
      <SAP:QIdInternal />
      <SAP:CommitActor>X</SAP:CommitActor>
      <SAP:SplitNumber>0</SAP:SplitNumber>
      <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
      <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
      <SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID" />
      <SAP:EOReferenceInbound type="TID" />
      <SAP:EOReferenceOutbound type="TID" />
      <SAP:MessageSizePayload>0</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>2918</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>0</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>PLAINHTTP</SAP:AdapterInbound>
      <SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
      <SAP:InterfaceAction>INIT</SAP:InterfaceAction>
      <SAP:RandomNumber>15</SAP:RandomNumber>
      <SAP:AckStatus>000</SAP:AckStatus>
      <SAP:SkipReceiverDetermination />
      <SAP:Receiver_Agreement_GUID>24422A5646443F8E9D975D57A3EE8162</SAP:Receiver_Agreement_GUID>
      </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.5</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
      <SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.656</SAP:Timestamp>
      </SAP:RunTimeItem>
      </SAP:PerformanceHeader>
    - <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:TraceLevel>Information</SAP:TraceLevel>
      <SAP:Logging>Off</SAP:Logging>
      </SAP:Diagnostic>
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">SystemError message generated. Guid: DC98499F7E4274F1A41F0017A4107EE6</Trace>
      <Trace level="1" type="T">Error during execution of message : DC98499CA1EABEF1B4DD00110A63BF06</Trace>
      <Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): DC98499CA1EABEF1B4DD00110A63BF06</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
      </SOAP:Header>
    - <SOAP:Body>
      <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />
      </SOAP:Body>
      </SOAP:Envelope>
    Regards,
    Kishore

    Hi,
    In the HTTP Receiver what is the Addressing Type used ? (URL Address or HTTP Destination).
    If its URL Addressing Type, check if right Authentication Type is used with valid values and for HTTP Addressing Type check this HTTP Client Create Error, it could be helpful.
    Also check if the Target system can be reached from the XI server to validate the configuration parameters.
    Regards,
    S.Santhosh Kumar

  • Error while sending by HTTP

    Bom dia
    Gostaria de saber quais são os motivos que levam uma mensagem síncrona, a retornar o erro: Error while sending by HTTP (error code: 500 , error text: Internal Server Error). Tenho em mente que possa ser por o receiver estar down mas não tenho a certeza, alguém me pode ajudar?
    Obrigado,
    Rúben Catrona

    Bom dia Rúben,
    Por ser uma comunicação síncrona acredito que deva ser externo, porém não dá para afirmar visto que o PI também se comunica internamente por HTTP.
    Dê mais detalhes do que está realizando.
    Você consegue fazer o mesmo teste diretamente no servidor destino (sem PI) através de outra ferramenta?
    Outro teste seria aumentar o log na SMICM para 3, fazer a comunicação síncrona, voltar o nível de trace para 1. E analisar o log da SMICM procurando pela resposta 500.
    Atenciosamente, Fernando Da Ró

  • Error while creating the HTTP client with destination

    Hi ,
    I am getting this error while connecting to https location on receiver channel . The below error i am getting in SXMB_moni
    Error while creating the HTTP client with destination
    The receiver party is doing some security setting on there end and for that purpose we have provided the external IP address to them , after that we are getting the above error.
    We have already installed the client certificate on our staging server , and have done the correct setting in SM59 and channel.

    Check few things..
    1) I believe you use specify destination for the addressing type field in the comm channel. If so make sure you entered valid target URL address in the SM59 of type http destination.
    2) Check the validitity of the certificate. You can import the certificate both in java and abap stack.
    3) Make sure certificate is installed as expected.
    4) Send the request and talk to the target system and check what error information they get in their log related to ssl.

  • INTERNAL.CLIENT_RECEIVE_FAILED Error when receiving by HTTP

    Hello my name is Arkaitz.
    I have this error *"INTERNAL.CLIENT_RECEIVE_FAILED Error when receiving by HTTP (error code: 110, error text: )"*
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Integration Server
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>SystemError</SAP:MessageClass>
      <SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
      <SAP:MessageId>DD351E48-7EED-DA5D-E100-0000AC1D4E74</SAP:MessageId>
      <SAP:RefToMessageId>4E111D48-1C55-742C-E100-00000AD2202B</SAP:RefToMessageId>
      <SAP:TimeSent>2008-05-05T15:59:00Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Service>ECYR</SAP:Service>
      <SAP:Interface namespace="" />
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>BSBWC_35</SAP:Service>
      <SAP:Interface namespace="http://www.ecyr.report.bw.sql">MI_1</SAP:Interface>
      <SAP:Mapping />
      </SAP:Receiver>
      <SAP:Interface namespace="http://www.ecyr.report.bw.sql">MI_2</SAP:Interface>
      </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>BestEffort</SAP:QualityOfService>
      </SAP:ReliableMessaging>
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>110</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error when receiving by HTTP (error code: 110, error text: )</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    - <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    - <SAP:Hop timeStamp="2008-05-05T15:59:00Z" wasRead="false">
      <SAP:Engine type="BS">BSBWC_35</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>4E111D48-1C55-742C-E100-00000AD2202B</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
    - <SAP:Hop timeStamp="2008-05-05T16:02:50Z" wasRead="false">
      <SAP:Engine type="IS">is.00.EMSXIL601PRE</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>4E111D48-1C55-742C-E100-00000AD2202B</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
      </SAP:HopList>
    - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Date>20080505</SAP:Date>
      <SAP:Time>175900</SAP:Time>
      <SAP:Host>emmbwl501pre</SAP:Host>
      <SAP:SystemId>BWC</SAP:SystemId>
      <SAP:SystemNr>22</SAP:SystemNr>
      <SAP:OS>Linux</SAP:OS>
      <SAP:DB>ORACLE</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>023</SAP:ProcStatus>
      <SAP:AdapterStatus>000</SAP:AdapterStatus>
      <SAP:User>ES78914719V</SAP:User>
      <SAP:TraceLevel>1</SAP:TraceLevel>
      <SAP:LogSeqNbr>000</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_SENDER</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>SENDER</SAP:PipelineIdExternal>
      <SAP:PipelineElementId>FEC5B93B44BBA66BE10000000A1148F5</SAP:PipelineElementId>
      <SAP:PipelineService>PLSRV_CALL_INTEGRATION_SERVER</SAP:PipelineService>
      <SAP:QIdInternal />
      <SAP:CommitActor>A</SAP:CommitActor>
      <SAP:SplitNumber>0</SAP:SplitNumber>
      <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
      <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
      <SAP:TypeOfEngine client="420">SND_CENTR</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID" />
      <SAP:EOReferenceInbound type="TID" />
      <SAP:EOReferenceOutbound type="TID" />
      <SAP:MessageSizePayload>198</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>0</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>198</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>PROXY</SAP:AdapterInbound>
      <SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
      <SAP:InterfaceAction>INIT</SAP:InterfaceAction>
      <SAP:RandomNumber>52</SAP:RandomNumber>
      <SAP:AckStatus>000</SAP:AckStatus>
      <SAP:SkipReceiverDetermination />
      </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="emmbwl501pre">20080505155900.452389</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="emmbwl501pre">20080505155900.454147</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_INTEGRATION_SERVER</SAP:Name>
      <SAP:Timestamp type="begin" host="emmbwl501pre">20080505155900.454636</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_INTEGRATION_SERVER</SAP:Name>
      <SAP:Timestamp type="end" host="emmbwl501pre">20080505155901.884062</SAP:Timestamp>
      </SAP:RunTimeItem>
      </SAP:PerformanceHeader>
    - <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:TraceLevel>Information</SAP:TraceLevel>
      <SAP:Logging>Off</SAP:Logging>
      </SAP:Diagnostic>
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">COMMIT is expected by application !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = BWC</Trace>
      <Trace level="1" type="T">client = 420</Trace>
      <Trace level="1" type="T">language = S</Trace>
      <Trace level="1" type="T">user = ES78914719V</Trace>
      <Trace level="1" type="Timestamp">2008-05-05T15:59:00Z 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 = 4E111D481C55742CE10000000AD2202B</Trace>
      <Trace level="1" type="T">PLNAME = SENDER</Trace>
      <Trace level="1" type="T">QOS = BE</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline SENDER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_SENDER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
      <Trace level="1" type="T">URL for integration server read from global configuration</Trace>
      <Trace level="1" type="T">URL= Dest://SAPISU_XII</Trace>
      <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP" />
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
      </SOAP:Header>
    - <SOAP:Body>
      <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />
      </SOAP:Body>
      </SOAP:Envelope>
    Can you help me?
    thank

    Hi,
    I think it is the problem with your HTTP connection used by ABAP proxy. so when your PI system tries to connect to ECC using HTTP it fails to connect.
    Regards,
    Indranil
    Award points if applicable

  • Error 8 File permission error while building executable for a RT

    I got error 8 File permission error while building executable for a RT. It happened always after build, I mean new startup.rtexe and startup.alias files have been created. At the build properties, it was set use default .alias file.
    I had the executable built successfully at one time.
    The detail message is:
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    Error 8 occurred at Open/Create/Replace File in RTBEP_Generate_Deploy_Instructions.vi->RTBEP_Invoke_Build_Engine.vi->RTBUIP_Build_Invoke.vi->RTBUIP_Build_Rule_Editor.vi->RTBUIP_Open_Properties.vi->RTBUIP_Item_OnDoProperties.vi->RTBUIP_Item_OnDoProperties.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  File permission error. You do not have the correct permissions for the file.
    =========================
    NI-488:  DMA hardware error detected.
    I checked relevant posts, couldn't find any clue.
    Please give me some ideas.
    Thanks.

    Hi Ya-hoo,
    Error building application in LabView 8.0 seems to describe a similar situation. The .alias file is important, as described in that discussion forum.
    Cheers.
    | Michael K | Project Manager | LabVIEW R&D | National Instruments |

  • No mountable File System error while installing Flash Player

    Hi all,
    i've been having a no mountable file system error while installing Flash Player.  At first i thought it was a problem with the download but i've tried many times and still have the same error when installing the player.  I've attached a screenshot of the error message.
    Hopefully someone can shed some light.  I'm using a 2012 Mac Mini running Mountain Lion on a Fusion Drive.

    elliott777 wrote:
    Thank you for your help! I don't have the capabilities:(
    you don't have what capabilities? to download?

  • Proxy error while running the financial report in workspace.

    Hi,
    We are using the Hyperion financial reporting 9.3.1 with Essbase as a data source.
    While running a report in workspace, we are getting the 'Proxy error' meassage, which is following-
    "<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
    '<html><head>
    <title>502 Proxy Error</title>
    </head><body>
    Proxy Error
    <p>The proxy server received an invalid
    response from an upstream server.<br />
    The proxy server could not handle the request <em><a
    href="/hr/modules/com/hyperion/reporting/web/reportViewer/HRRunJob.jsp">GET /hr/modules/com/hyperion/reporting/web/reportViewer/HRRunJob.jsp</a></em>.<p>
    Reason: <strong>Error reading from remote server</strong></p></p>
    </body></html>"
    Do anybody have any idea on this? Any help will be appriciated on this.
    Thanks & Regards,
    Mohit Jain

    Hi Iain,
    We are using Microsoft Internet explorer 6.0. I am not sure about the 'proxy' (As we don't have any proxy setting in Tool--> Internet options--> connection--> LAN setting). We are accessing the Workspace and FR studio via Citrix application. How can I check the proxy.
    Also, I noticed one more point, Report has prompt for seleting 'Account hierarchy'.If we run the report only for one account hierarchy, report is returning the data but while running for multiple account hierarchy, it is throwing the 'Proxy error' as memtioned above.
    Please help us on this.
    Thank & Regards,
    Mohit

  • File system error while creating a virtual server

    Hi
    I get the following error when I create a virtual server:
    File System Error: Could not create directory /opt/SUNWwbsvr/https-web-content (permission denied)
    The admin server is owned by root but the instance that I want to create should be owned by webservd - like the other instance that is installed.
    this error shows that web server is unable to create a directory under SUNWwbsvr folder. Any hints pls?
    thanks!

    sorry this error is while creating a new server instance - not a new virtual server.
    File System Error: Could not create directory /opt/SUNWwbsvr/https-web-content (permission denied)

  • Windows App developer account and .aetx file, Unknown error while generating AET

    Hi Everyone,
    firstly, sorry for my not perfect english, but I hope that somehow understand what i  want to say.
    So, I am a student (I do not know if it makes a difference but inform you), and I wanted to write a universal windows app for company (This would be the first application WP and Windows this company, previously did app on Android and IOS, and websites).
    I wrote a little bit and I wanted to throw the first version on hockeyapp.net to the head of the company and the customers can test it and i have problem. I upload .appx file bu i have problem with generate .aetx file. When I run this command AETGenerator.exe
    PFXFilepath PFXFilePassword it gives me an error in command prompt
    Unknown error while generating AET
    startIndex cannot be larger than length of string.
    Parameter name: startIndex
    I've read about these certificates but did not find a specific answer (a very specific answer). So what I need to do, What do I need,  what to buy and etc.
    What are my solutions?
    What should I do?
    Is it enough that I register and I buy individual developer account?
    I hope someone answer me, 
    thank you :)

    Try sending it to store anyway… I have the similar issue, the kit hangs when saving result and never complete it.
    Another member has same question.
    https://social.technet.microsoft.com/Forums/en-US/11910167-75e1-47d8-a0fb-fb8046c57f89/windows-app-certification-kit-31-reports-failure-due-to-crash-or-hang?forum=projectsiena.
    If you want to test your app, you can also send to beta store and you can get response from the testers.

Maybe you are looking for