Home Page › Forums › BizTalk 2004 – BizTalk 2010 › SendFailedException and COMException
- This topic has 0 replies, 1 voice, and was last updated 9 years, 10 months ago by
community-content.
-
AuthorPosts
-
-
December 4, 2007 at 7:38 AM #18568
Hi all!
I am trying to complete an orchestration, in BT
2006 R2, that takes in a XML file and sends it as input to a stored
procedure in SQL Server 2005. I used the Add > Generated Items
method to create the schema for the message sent to SQL, but when it
hits the send shape to send it to SQL, I get an ‘Uncaught Exception’,
along with ‘Inner exception: Failed while attempting to send message
‘Send_MSG” with the following stack trace:Exception type: SendFailedException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void
WriteMessageState(Microsoft.BizTalk.Interop.IBTPEPInfoLookup,
System.Guid, Microsoft.XLANGs.BaseTypes.XLANGMessage,
Microsoft.XLANGs.Core.Segment, System.String, System.String,
System.Collections.IList, Boolean, System.Collections.IList)
The following is a stack trace that identifies the location where the exception occuredat
Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.WriteMessageState(IBTPEPInfoLookup
pepLookup, Guid portId, XLANGMessage msg, Segment seg, String opname,
String url, IList promoteProps, Boolean track, IList toPromote)
at
Microsoft.BizTalk.XLANGs.BTXEngine.BTXLogicalPortBinding.SendMessage(XLANGMessage
msg, XlangStore store, Segment seg, OperationInfo op, IList
additionalProps, IList toPromote, Boolean ignoreRoutingFailure)
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.SendMessage(Int32
iOperation, XLANGMessage msg, Correlation[] initCorrelations,
Correlation[] followCorrelations, Context cxt, Segment seg,
ActivityFlags flags)
at Sample_Send_SQL_Project.Sample_Send_SQL.segment1(StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)
Additional error information:Exception from HRESULT: 0xC0C01672
Exception type: COMException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void PostToSendPort(System.Guid ByRef,
Microsoft.BizTalk.Agent.Interop.IBTMessageBatch,
Microsoft.BizTalk.Agent.Interop.IBTMessage, System.String,
System.String, Microsoft.BizTalk.Interop.IBTMMessageList ByRef)
The following is a stack trace that identifies the location where the exception occuredat
Microsoft.BizTalk.Interop.IBTPEPInfoLookup.PostToSendPort(Guid&
sendPortID, IBTMessageBatch batch, IBTMessage msg, String
operationName, String url, IBTMMessageList& dlMsgList)
at
Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.WriteMessageState(IBTPEPInfoLookup
pepLookup, Guid portId, XLANGMessage msg, Segment seg, String opname,
String url, IList promoteProps, Boolean track, IList toPromote)I’m about to create the schema myself and test it that way, but I’m not
sure why this is happening since all the COM objects are definitely
deployed and registered correctly according to the server and the BT
Administration Console. Unfortunately, I haven’t found many good
examples on such a seemingly simple orchestration.If
anyone has any thoughts or comments, or even some good sources I could
investigate, I’d greatly appreciate it! I’m very new to BT 2006 so any
help would go a long way. Please let me know if any more information
might help.Thanks!
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.