locked
IDOC_INBOUND_ASYNCHRONOUS could not be resolved against SAP system because its metadata could not be obtained. RRS feed

  • Question

  •  

    I'm trying to receive IDOCS from SAP. I'm using the BizTalk Adapter Pack, and have created the Receive Location using the Custom WCF adapter. The RFC connection from SAP successfully connects. However, whenever an IDOC is sent to BizTalk I get the following error.

     

    Event Type: Error
    Event Source: SAP
    Event Category: None
    Event ID: 0
    Date:  7/16/2008
    Time:  9:42:20 AM
    User:  N/A
    Computer: ********

    Description:
    http://schemas.microsoft.com/servicemodel/adapters/Channels/TryReceiveExceptionAn exception was thrown while trying to receive on an IInboundHandlerDefaultDomainMicrosoft.ServiceModel.Channels.Common.Channels.AdapterReplyChannel/41885522Microsoft.ServiceModel.Channels.Common.MetadataException, Microsoft.ServiceModel.Channels, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35RFC IDOC_INBOUND_ASYNCHRONOUSဇ澈၅菐૒ could not be resolved against SAP system because its metadata could not be obtained.   at Microsoft.Adapters.SAP.SapFunctionMetadata.ResolveOperationMetadataUsingSdk(String absoluteName, String displayName, String funcName, String operationNamespace, SAPConnection sapConnection, Boolean isTrfc, MetadataLookup metadataLookup, TimeoutHelper timeoutHelper)
       at Microsoft.Adapters.SAP.SapFunctionMetadata.ResolveOperationMetadata(String absoluteName, String displayName, String funcName, String operationNamespace, SAPConnection sapConnection, Boolean isTrfc, MetadataLookup metadataLookup, TimeoutHelper timeoutHelper)
       at Microsoft.Adapters.SAP.SAPMetadataContract.AdapterResolveOperationMetadata(String operationId, TimeSpan timeout, TypeMetadataCollection& extraTypeMetadataResolved)
       at Microsoft.Adapters.AdapterUtilities.AdapterMetadataContract.ResolveOperationMetadata(String operationId, TimeSpan timeout, TypeMetadataCollection& extraTypeMetadataResolved)
       at Microsoft.ServiceModel.Channels.Common.Design.MetadataCache.GetOperationMetadata(String uniqueId, Guid clientId, TimeSpan timeout)
       at Microsoft.ServiceModel.Channels.Common.MetadataLookup.GetOperationDefinitionFromInputMessageAction(String action, TimeSpan timeout)
       at Microsoft.Adapters.SAP.SAPInboundContract.AdapterTryReceive(TimeSpan timeout, Message& message, IInboundReply& reply)
       at Microsoft.Adapters.AdapterUtilities.AdapterInboundContract.TryReceive(TimeSpan timeout, Message& message, IInboundReply& reply)
       at Microsoft.ServiceModel.Channels.Common.Channels.AdapterReplyChannel.TryReceiveRequest(TimeSpan timeout, RequestContext& IRequestContext)Microsoft.ServiceModel.Channels.Common.MetadataException: RFC IDOC_INBOUND_ASYNCHRONOUSဇ澈၅菐૒ could not be resolved against SAP system because its metadata could not be obtained. ---> Microsoft.Adapters.SAP.RFCException: Details: ErrorCode=RFC_EXCEPTION. ErrorGroup=RFC_ERROR_APPLICATION_EXCEPTION. SapErrorMessage=FU_NOT_FOUND.  AdapterErrorMessage=An error occurred while determining the function interface of the RFC IDOC_INBOUND_ASYNCHRONOUSဇ澈၅菐૒.
       at Microsoft.Adapters.SAP.RFCException.HelperThrow(Int32 retCode, String additionalErrorMessage)
       at Microsoft.Adapters.SAP.RfcClientConnection.GetRfcFunctionInterface(String rfcName)
       at Microsoft.Adapters.SAP.SapFunctionMetadata.ResolveOperationMetadataUsingSdk(String absoluteName, String displayName, String funcName, String operationNamespace, SAPConnection sapConnection, Boolean isTrfc, MetadataLookup metadataLookup, TimeoutHelper timeoutHelper)
       --- End of inner exception stack trace ---
       at Microsoft.Adapters.SAP.SapFunctionMetadata.ResolveOperationMetadataUsingSdk(String absoluteName, String displayName, String funcName, String operationNamespace, SAPConnection sapConnection, Boolean isTrfc, MetadataLookup metadataLookup, TimeoutHelper timeoutHelper)
       at Microsoft.Adapters.SAP.SapFunctionMetadata.ResolveOperationMetadata(String absoluteName, String displayName, String funcName, String operationNamespace, SAPConnection sapConnection, Boolean isTrfc, MetadataLookup metadataLookup, TimeoutHelper timeoutHelper)
       at Microsoft.Adapters.SAP.SAPMetadataContract.AdapterResolveOperationMetadata(String operationId, TimeSpan timeout, TypeMetadataCollection& extraTypeMetadataResolved)
       at Microsoft.Adapters.AdapterUtilities.AdapterMetadataContract.ResolveOperationMetadata(String operationId, TimeSpan timeout, TypeMetadataCollection& extraTypeMetadataResolved)
       at Microsoft.ServiceModel.Channels.Common.Design.MetadataCache.GetOperationMetadata(String uniqueId, Guid clientId, TimeSpan timeout)
       at Microsoft.ServiceModel.Channels.Common.MetadataLookup.GetOperationDefinitionFromInputMessageAction(String action, TimeSpan timeout)
       at Microsoft.Adapters.SAP.SAPInboundContract.AdapterTryReceive(TimeSpan timeout, Message& message, IInboundReply& reply)
       at Microsoft.Adapters.AdapterUtilities.AdapterInboundContract.TryReceive(TimeSpan timeout, Message& message, IInboundReply& reply)
       at Microsoft.ServiceModel.Channels.Common.Channels.AdapterReplyChannel.TryReceiveRequest(TimeSpan timeout, RequestContext& IRequestContext)Microsoft.Adapters.SAP.RFCException, Microsoft.Adapters.SAP.SAPGInvoker, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35Details: ErrorCode=RFC_EXCEPTION. ErrorGroup=RFC_ERROR_APPLICATION_EXCEPTION. SapErrorMessage=FU_NOT_FOUND.  AdapterErrorMessage=An error occurred while determining the function interface of the RFC IDOC_INBOUND_ASYNCHRONOUSဇ澈၅菐૒.   at Microsoft.Adapters.SAP.RFCException.HelperThrow(Int32 retCode, String additionalErrorMessage)
       at Microsoft.Adapters.SAP.RfcClientConnection.GetRfcFunctionInterface(String rfcName)
       at Microsoft.Adapters.SAP.SapFunctionMetadata.ResolveOperationMetadataUsingSdk(String absoluteName, String displayName, String funcName, String operationNamespace, SAPConnection sapConnection, Boolean isTrfc, MetadataLookup metadataLookup, TimeoutHelper timeoutHelper)Microsoft.Adapters.SAP.RFCException: Details: ErrorCode=RFC_EXCEPTION. ErrorGroup=RFC_ERROR_APPLICATION_EXCEPTION. SapErrorMessage=FU_NOT_FOUND.  AdapterErrorMessage=An error occurred while determining the function interface of the RFC IDOC_INBOUND_ASYNCHRONOUSဇ澈၅菐૒.
       at Microsoft.Adapters.SAP.RFCException.HelperThrow(Int32 retCode, String additionalErrorMessage)
       at Microsoft.Adapters.SAP.RfcClientConnection.GetRfcFunctionInterface(String rfcName)
       at Microsoft.Adapters.SAP.SapFunctionMetadata.ResolveOperationMetadataUsingSdk(String absoluteName, String displayName, String funcName, String operationNamespace, SAPConnection sapConnection, Boolean isTrfc, MetadataLookup metadataLookup, TimeoutHelper timeoutHelper)

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

    Wednesday, July 16, 2008 2:06 PM

Answers

  • Is your SAP server a non-unicode server? If so, what's your logon language (the one specified in the uri)?

    Wednesday, July 16, 2008 5:35 PM

All replies

  • Wow, 14 views and no replys?

     

    Can anyone offer suggestions to why an incoming IDOC would fail at the Adapter? I'm open to trying anything here. Thanks!

     

    Wednesday, July 16, 2008 4:03 PM
  • Here's another error that might help.

     

    Event Type: Error
    Event Source: SAP
    Event Category: None
    Event ID: 0
    Date:  7/16/2008
    Time:  12:46:35 PM
    User:  N/A
    Computer: SHR-SV3015
    Description:
    http://Microsoft.Adapters.Sap/OperationMetadata/RFC IDOC_INBOUND_ASYNCHRONOUSဇ澈၅鸸ܷ could not be resolved against SAP system because its metadata could not be obtained.DefaultDomainMicrosoft.Adapters.SAP.RFCException, Microsoft.Adapters.SAP.SAPGInvoker, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35Details: ErrorCode=RFC_EXCEPTION. ErrorGroup=RFC_ERROR_APPLICATION_EXCEPTION. SapErrorMessage=FU_NOT_FOUND.  AdapterErrorMessage=An error occurred while determining the function interface of the RFC IDOC_INBOUND_ASYNCHRONOUSဇ澈၅鸸ܷ.   at Microsoft.Adapters.SAP.RFCException.HelperThrow(Int32 retCode, String additionalErrorMessage)
       at Microsoft.Adapters.SAP.RfcClientConnection.GetRfcFunctionInterface(String rfcName)
       at Microsoft.Adapters.SAP.SapFunctionMetadata.ResolveOperationMetadataUsingSdk(String absoluteName, String displayName, String funcName, String operationNamespace, SAPConnection sapConnection, Boolean isTrfc, MetadataLookup metadataLookup, TimeoutHelper timeoutHelper)Microsoft.Adapters.SAP.RFCException: Details: ErrorCode=RFC_EXCEPTION. ErrorGroup=RFC_ERROR_APPLICATION_EXCEPTION. SapErrorMessage=FU_NOT_FOUND.  AdapterErrorMessage=An error occurred while determining the function interface of the RFC IDOC_INBOUND_ASYNCHRONOUSဇ澈၅鸸ܷ.
       at Microsoft.Adapters.SAP.RFCException.HelperThrow(Int32 retCode, String additionalErrorMessage)
       at Microsoft.Adapters.SAP.RfcClientConnection.GetRfcFunctionInterface(String rfcName)
       at Microsoft.Adapters.SAP.SapFunctionMetadata.ResolveOperationMetadataUsingSdk(String absoluteName, String displayName, String funcName, String operationNamespace, SAPConnection sapConnection, Boolean isTrfc, MetadataLookup metadataLookup, TimeoutHelper timeoutHelper)

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

    Wednesday, July 16, 2008 4:48 PM
  • Is your SAP server a non-unicode server? If so, what's your logon language (the one specified in the uri)?

    Wednesday, July 16, 2008 5:35 PM
  • The logon language is EN, and the schemas generated via Consume Adapter Service are UTF-16. I'm almost positive that the server is unicode, but haven't received a response from our SAP pros. Thanks!

     

    Wednesday, July 16, 2008 5:43 PM
  • Can you try obtaining (and using) the latest 7.0 dlls from SAP MarketPlace (instructions available at http://blogs.msdn.com/adapters/archive/2007/10/07/obtaining-the-rfc-sdk-unicode-libraries-from-sap-service-marketplace.aspx), and see if it helps?
    Wednesday, July 16, 2008 5:47 PM
  • Thanks, it turns out that they are sending IDOCS over in UTF-8, and my schemas are expecting UTF-16. I'm going to modify my schemas to UTF-8, and see if that fixes the problem. I'll also download the new unicode libraries.

     

    Wednesday, July 16, 2008 6:00 PM
  •  

    We think the RFC connection was set to non-unicode, and changing that appears to have fixed the problem. Thanks.
    Wednesday, July 16, 2008 8:17 PM
  • Thank you! Changing the RFC-Connection from non-unicode to unicode solved the problem!!

    Massimo

    Thursday, June 20, 2013 10:40 AM