Error:

There was a failure executing the receive pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ Source: “XML disassembler” Receive Port: “Receive_ExtractEFSR_Delta_FMA” URI: “mssql://.//QTAviation?InboundId=ExtractEFSR&ExtractTypeCode=Delta_FMA_Daily” Reason: Finding the document specification by message type “http://schemas.microsoft.com/Sql/2008/05/Polling/#Polling” failed. Verify the schema deployed properly.

 

Solution: Needed to change from Polling to TypedPolling  (on Binding tab, inboundOperationType

Error:  Failed to update binding information. (mscorlib)

Object reference not set to an instance of object (Microsoft.BizTalk.ExplorerOM)

This happened when I created a new empty application.  It took a binding file, i.e. “a feed” from another app, exported it, changed the environment names, and re-imported it.

The problem was that the binding used maps and pipelines from another app.  There was nothing wrong with the binding file.  The way to get around the error was to add a reference in the new app to the old app that contains the maps and pipelines.

There was a failure executing the response(receive) pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ Source: “XML disassembler” Send Port: “FlightStatsAPITest_1.0.0.0_FlightStatsAPITest.DemoFlightStats_FlightStats_271205145d00a26b” URI: “https://api.flightstats.com/flex/connections/docs/v1/lts/soap/schedulesConnectionsService.wsdl” Reason: Finding the document specification by message type “http://schemas.xmlsoap.org/wsdl/#definitions” failed. Verify the schema deployed properly. 

Solution: make sure don’t have the .wsdl on the URL of the URL that you type in SEND port.
This was a “dumb mistake” I made.  I pasted the .wsdl URL instead of the service URL into the website to be called by the send port.  To the response message was coming back to my orchestration, but didn’t have a matching schema.