I also tried passing a message of type System.IO.FileStream(“flatfile.txt”) and still getting the following error:
Event Type: Error
Event Source: XLANG/s
Event Category: None
Event ID: 10034
Date: 6/2/2009
Time: 3:22:28 PM
User: N/A
Computer: TOR-12653
Description:
Uncaught exception (see the ‘inner exception’ below) has suspended an instance of service ‘BizTalk_Server_Project1.BizTalk_Orchestration2(12a96338-9656-adeb-4bc0-0e19413b8cee)’.
The service instance will remain suspended until administratively resumed or terminated.
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
InstanceId: 1eebbf9d-be0f-44bf-ae00-fa67bb2c7f5c
Shape name:
ShapeId: 00000000-0000-0000-0000-000000000000
Exception thrown from: segment 2, progress 9
Inner exception: The pipeline manager could not prepare the message(s) for processing pipeline “BizTalk_Server_Project1.ReceivePipeline1”. Error Details: “There was an error generating the XML document.”
Exception type: XLANGPipelineManagerException
Source: Microsoft.XLANGs.Pipeline
Target Site: Microsoft.XLANGs.Pipeline.ReceivePipelineOutputMessages ExecutePipeline(Microsoft.BizTalk.PipelineOM.ReceivePipeline, Microsoft.XLANGs.BaseTypes.XLANGMessage)
The following is a stack trace that identifies the location where the exception occured
at Microsoft.XLANGs.Pipeline.XLANGPipelineManager.ExecutePipeline(ReceivePipeline p, XLANGMessage inMsg)
at Microsoft.XLANGs.Pipeline.XLANGPipelineManager.ExecuteReceivePipeline(Type receivePipelineType, XLANGMessage inMsg)
at BizTalk_Server_Project1.BizTalk_Orchestration2.segment2(StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)
Additional error information:
There was an error generating the XML document.
Exception type: InvalidOperationException
Source: System.Xml
Target Site: Void Serialize(System.Xml.XmlWriter, System.Object, System.Xml.Serialization.XmlSerializerNamespaces, System.String, System.String)
The following is a stack trace that identifies the location where the exception occured
at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)
at System.Xml.Serialization.XmlSerializer.Serialize(Stream stream, Object o)
at Microsoft.XLANGs.RuntimeTypes.XmlHelpers.StreamFromObject(Object o, Type t)
at Microsoft.XLANGs.Core.Value.GetStream(String& encoding, Boolean wantEncoding)
at Microsoft.XLANGs.Core.Value.RetrieveAs(Type t)
at Microsoft.XLANGs.Core.Part.ProtectedRetrieveAs(Type t)
at Microsoft.XLANGs.Core.Part.RetrieveAs(Type t)
at Microsoft.XLANGs.Pipeline.PipelineXPart.ToBaseMessagePart()
at Microsoft.XLANGs.Pipeline.PipelineXMessage.ToBaseMessage()
at Microsoft.XLANGs.Pipeline.XLANGPipelineManager.ExecutePipeline(ReceivePipeline p, XLANGMessage inMsg)
Additional error information:
Timeouts are not supported on this stream.
Exception type: InvalidOperationException
Source: mscorlib
Target Site: Int32 get_ReadTimeout()
The following is a stack trace that identifies the location where the exception occured
at System.IO.Stream.get_ReadTimeout()
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterFileStream.Write4_FileStream(String n, String ns, FileStream o, Boolean isNullable, Boolean needType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterFileStream.Write5_FileStream(Object o)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.