Forum Replies Created
-
AuthorPosts
-
June 3, 2009 at 9:26 AM in reply to: SQL Adapter – returning only the first response….not returning all responses #22572
Hi Jerry,
Did you ever find an answer to your SQL adapter issue? I have a simlar problem where I want to use all the message parts returned by SQL Adapter but only first seems to be available even though looking at the message thru Biztalk Admin, it seems like all parts all returned successfully. Database inserts are fine as well.
I don’t want to use a loop in Orchestration. I would love to know how you solved this issue.
Thanks!
Adnan
June 3, 2009 at 9:14 AM in reply to: SQL Adapter – returning only the first response….not returning all responses #22571I have a similar problem. I have a message returned from SQL Adapter Response with three body parts.
When I use a map to pull data from this message I only get first part returned even if I use loop shape. How do I access other two body parts in the message?
Can you explain what you are trying to acheive – certificates in BizTalk can be confusing….
There are a bunch of resources on the web that help you do this, including:
Hope this helps. Rgds, Nick.
ps. You will only need a single Flat-File Disassembler component in your pipeline!
June 3, 2009 at 7:28 AM in reply to: Calling Pipeline Component to disassemble flat file inside orchestration #22568I suppose the first question is: why are you trying to disassemble a flat-file inside of an orchestration? why not create a message containing Xml and disassemble that?
Nick.
You need to set the orchestration in the other project to be public, then add the other project into your current project so that you can call it. Hope that helps.
Hi,
Have anyone seen a solution for that?
June 2, 2009 at 12:26 PM in reply to: Calling Pipeline Component to disassemble flat file inside orchestration #22562I also tried passing a message of type System.IO.FileStream(“flatfile.txt”) and still getting the following error:
Event Type: ErrorEvent Source: XLANG/sEvent Category: NoneEvent ID: 10034Date: 6/2/2009Time: 3:22:28 PMUser: N/AComputer: TOR-12653Description: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-fa67bb2c7f5cShape name:ShapeId: 00000000-0000-0000-0000-000000000000Exception thrown from: segment 2, progress 9Inner 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: XLANGPipelineManagerExceptionSource: Microsoft.XLANGs.PipelineTarget 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 occuredat 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: InvalidOperationExceptionSource: System.XmlTarget 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 occuredat 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: InvalidOperationExceptionSource: mscorlibTarget Site: Int32 get_ReadTimeout()The following is a stack trace that identifies the location where the exception occuredat 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.You can create an Envelop Schema call <ArrayOfItem>, then the receive pipeline will split the ArrayOfItem in into multiple <Item>.
Here is an example of envelop schema:
<?xml version=”1.0″ encoding=”utf-16″?>
<xs:schema xmlns:tns=”http://ArielBPM.Biztalk.RequestManagement.Schemas” xmlns:b=”http://schemas.microsoft.com/BizTalk/2003″ elementFormDefault=”qualified” targetNamespace=”http://ArielBPM.Biztalk.RequestManagement.Schemas” xmlns:xs=”http://www.w3.org/2001/XMLSchema”>
<xs:annotation>
<xs:appinfo>
<schemaInfo is_envelope=”yes” root_reference=”QueueUpAndNotifyRequests” xmlns=”http://schemas.microsoft.com/BizTalk/2003″ />
</xs:appinfo>
</xs:annotation>
<xs:element name=”QueueUpAndNotifyRequests” type=”tns:QueueUpAndNotifyRequests”>
<xs:annotation>
<xs:appinfo>
<recordInfo body_xpath=”/*[local-name()=’QueueUpAndNotifyRequests’ and namespace-uri()=’http://ArielBPM.Biztalk.RequestManagement.Schemas’%5D” xmlns=”http://schemas.microsoft.com/BizTalk/2003″ />
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:complexType name=”QueueUpAndNotifyRequests”>
<xs:sequence>
<xs:any />
</xs:sequence>
</xs:complexType>
</xs:schema>
Add Scope Shape to you orchestration.
Set its Transaction Type property to None.
Right Click on the Scope and add new exception.
You can then handle the exception buy adding expression shape inside the exception shape.
then put
System.Diagnostics.EventLog.WriteEntry(“Web SErvice error”, ExceptionShape.ToString() );
inside the expression shape
You schema is like your contract, meaning that your orchestration will only take the xml that conforms to the schema. In your case, the orchestration expects the message of type Item, not ArrayOfItem
Hi all,
I got the solution of the problem. Source files were transmitted in text format initially. Once I got them in the binary format, the error got disappeared.
Anyways, thanks all
I have am calling a web service via a synchronous operation.
If the calling web service dies or throws an exception on its end than the orchestration just keeps running and remains active forever.
How do I force a timeout on that operation if the response is never received?
June 1, 2009 at 10:39 AM in reply to: Biztalk Server 2006 R2 Compatibility with Developer Edition with Visual studio 2005 and 2008 Professional editions #22547Hi,
Is Biztalk Server 2009 support visual studio 2005?
-
AuthorPosts

