We received this message. It was clear it had to do something with the SOAP call and the message type was not set. This can have several reasons: schemas not deployed correctly, target namespace wrong, root name wrong, etc. The SOAP adapter must be able to find the corresponding schema for serializing. In our case we forgot to enter the proxy assembly, type name and the method to use (created a new two-way send port instead of a one-way send port). This proxy assembly holds knowledge on the schema to use.
Error message:
General exception soap Microsoft.XLANGs.Core.XlangSoapException: An error occurred while processing the message, refer to the details section for more information
Message ID: {8E2E044D-EA52-4006-9F1C-32A25DC2A2AC}
Instance ID: {5FCED1F3-8D45-430C-B45F-A77E7D0E46CE}
Error Description: SoapException: Server was unable to process request. —> There was an error generating the XML document. —> The type System.Xml.XmlDocument may not be used in this context.
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.VerifyTransport(Envelope env, Int32 operationId, Context ctx)
at Microsoft.XLANGs.Core.Subscription.Receive(Segment s, Context ctx, Envelope& env, Boolean topOnly)
at Microsoft.XLANGs.Core.PortBase.GetMessageId(Subscription subscription, Segment currentSegment, Context cxt, Envelope& env, CachedObject location)
at DTAOrderMessaging.ProcessOrder.segment2(StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)
Proxy configuration:
Question raised on my site: does BizTalk hold history/information on changed configuration items with a timestamp and user?
Or must we dive in the SQL logs, or must we capture it our self? (didn’t do any investigation on this part)
