none
The adapter "WCF-BasicHttp" raised an error message. Details "System.NotSupportedException: Specified method is not supported. RRS feed

  • Question

  • I've created sandbox environment: Windows 2003 running BTS 06R2 in a Virtual PC 2007 environment over a Vista native envrionment.  Another inidvidual in my shop built the same set-up and has been stopped cold by this as well:

    Problem:

    When I attempt to send a mesage to my WCF Receive location, i receive the following Event Viewer/enhanced SOAP Fault output:

    The adapter "WCF-BasicHttp" raised an error message. Details "System.NotSupportedException: Specified method is not supported.

       at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkServiceInstance.Microsoft.BizTalk.Adapter.Wcf.Runtime.ITwoWayAsync.BizTalkSubmit(Message message)

       at SyncInvokeBizTalkSubmit(Object , Object[] , Object[] )

       at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)

       at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)

       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc& rpc)

       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc& rpc)

       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc& rpc)

       at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)".

     

    After setting includeExceptionDetailInFaults=”true” in web.config

     

    HTTP/1.1 500 Internal Server Error

    Date: Thu, 31 Dec 2009 22:30:49 GMT

    Server: Microsoft-IIS/6.0

    X-Powered-By: ASP.NET

    X-AspNet-Version: 2.0.50727

    Cache-Control: private

    Content-Type: text/xml; charset=utf-8

    Content-Length: 1724

     

    <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault><faultcode xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:InternalServiceFault</faultcode><faultstring xml:lang="en-US">Specified method is not supported.</faultstring><detail><ExceptionDetail xmlns="http://schemas.datacontract.org/2004/07/System.ServiceModel" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><HelpLink i:nil="true"/><InnerException i:nil="true"/><Message>Specified method is not supported.</Message><StackTrace>   at

    The receive location in question is one of two locations (the other a WCF-Custom Adapter config) which are bound to a single Receive Port.

    Any one seen this/found a solution to this? Any way to enhance the error info.

    Updated 5:05 P.M.

    Sooo... if ITwoWayAsync.BizTalkSubmit Method is "never supposed to be invoked" and I've simply configured a Biztalk receive/port location WITHOUT WRITING ANY CODE, How IS this method getting called.  Is this a configuration issue?

    Thursday, March 4, 2010 5:27 PM

Answers

  • I think the problem started when you deleted the generated port and tried to rewire the location to another port. The wizard actually generates some code that probably refers to the generated receive port. So basically the error you are getting is because it cannot find the generated receive port. I would go through the publishing wizard again and refer to the original (non-generated) receive port so it configures it properly.

    The output from the publishing wizard is not as configurable due to the code/config it generates in the virtual directory. Open up the generated virtual directory files if you want to get a better understanding of what is going on.

    Thanks,
    If this answers your question, please use the "Answer" button to say so | Ben Cline
    Saturday, March 6, 2010 5:58 PM
    Moderator

All replies