none
SAP comunication error RRS feed

  • General discussion

  • Hi 

    i have the nexts warnings:

    Description:

    The adapter "WCF-Custom" raised an error message. Details "System.ServiceModel.CommunicationObjectFaultedException: 

    The communication object, Microsoft.Adapters.Internal.LayeredChannelBindingElement.LayeredInboundChannel`1

    [System.ServiceModel.Channels.IReplyChannel], cannot be used for communication because it is in the Faulted state.

       at System.ServiceModel.Channels.CommunicationObject.Close(TimeSpan timeout)

       at System.ServiceModel.Channels.CommunicationObject.Close()

       at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.Close()".

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    when heappens this warning the architecture can't receive Idoc from SAP systems and the elaboration of others orchestration in BizTalk server is very slow. I have set the receiveTimeout property to 24.20:31:23.6470000. My architecture is BizTalk Server 2006 R2 with Microsoft BizTalk Adapter v2.0 for mySAP Business Suite Service Pack 1.

    How can i for solve this bad situation?
    Thanks in advance


    EZ BizTalk Specialist
    Tuesday, March 30, 2010 10:05 AM

All replies

  • Hi,

    Add a trace during the execution of your port in order to get more details. You can find a guide here : http://msdn.microsoft.com/en-US/library/cc185440(v=BTS.10).aspx



    David GROSPELIER NOVELI dgr@noveli.fr blog.noveli.fr
    Tuesday, March 30, 2010 11:13 AM
  • Hi

    in the trace log appeare the next error message:

    RaiseError: The RequestContext on the IReplyChannel was closed without a reply being sent ...

     

    how can i do for solve this error?

     

    Thanks in advance


    EZ BizTalk Specialist
    Wednesday, March 31, 2010 9:02 AM
  • Is there any additional error messages in the log? And how often this error happens?

    Please add tracing for both "Microsoft.Adapters.SAP" and "Microsoft.ServiceModel.Channels"

    Thanks,

    Jeevitha

    Wednesday, March 31, 2010 9:24 AM
  • Hi Jeevitha

    thank you for your answer. This error appeare just 1-2 times for day. The BT machine receive moreless 100 Idoc from SAP system by SAP Adapter for day and when this error appeare the BT machine is very slow. The log file have many information and this is the just error.

    I have set the property receiveTimeout = 24.20:31:23.6470000 ... it's rights? Is better the value 23:59:59?

    Thanks in advance

    Next is the full trace for just this event

    <E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent"><System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system"><EventID>0</EventID><Type>3</Type><SubType Name="Error">0</SubType><Level>2</Level><TimeCreated SystemTime="2010-03-31T08:54:49.5955229Z" /><Source Name="Microsoft.Adapters.SAP" /><Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" /><Execution ProcessName="BTSNTSvc" ProcessID="672" ThreadID="21" /><Channel /><Computer>MILBIZTALK04</Computer></System><ApplicationData><TraceData><DataItem><TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord"><TraceIdentifier>http://Microsoft.Adapters.Sap/RfcServerConnection/28ea60a2-c303-4cd9-a219-b1e521396320/</TraceIdentifier><Description>RaiseError: The RequestContext on the IReplyChannel was closed without a reply being sent.</Description><AppDomain>DefaultDomain</AppDomain></TraceRecord></DataItem></TraceData><System.Diagnostics xmlns="http://schemas.microsoft.com/2004/08/System.Diagnostics"><LogicalOperationStack></LogicalOperationStack><Timestamp>29813403309426</Timestamp></System.Diagnostics></ApplicationData></E2ETraceEvent>


    EZ BizTalk Specialist
    Wednesday, March 31, 2010 9:38 AM
  • Right. If you have receiveTimeout=24.20:31:23.6470000, you should see this error only if the receive location hasn't received any message for 24+ days.

    And from what you observe, this is not the case. I am interested in getting the details of any other Error/Warning messages in the trace along with the above specified error.

    Thanks,

    Jeevitha

    Friday, April 2, 2010 12:35 PM
  • Hi, Enrico

    We are changing the issue type to "General Discussion" because you have not followed up with the
    necessary information. If you have more time to look at the issue and provide more information,
    please feel free to change the issue type back to Question? If the issue is resolved, we will
    appreciate it if you can share the solution so that the answer can be found and used by other
    community members having similar questions.

    Thank you!


    This posting is provided "AS IS" with no warranties, and confers no rights. Microsoft Online Community Support
    Tuesday, April 6, 2010 4:07 AM
    Moderator