Anybody encounterred this issue:DebugBreakPointFailedException

BizTalk Utilities

Xselerator XSLT IDE

Forum main page

Most active member

Search page

Information Online

View our event calendar
Add general event such as an upcoming software release or conference
View all birthdays

Public image gallery
Upload your images in your profile

Profile editing page
Subscription list page
Address book page

Member list page
View the most active member
User groups listing
Private message page

TopXML Discussion Forum

Forums Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

Anybody encounterred this issue:DebugBreakPointFailedException

View related threads: (in this forum | in all forums)

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [BizTalk Utilities] >> BizTalk 2004/2006 Utilities and Adapters >> Anybody encounterred this issue:DebugBreakPointFailedException

Page: [1]

Message

<< Older Topic Newer Topic >>

Anybody encounterred this issue:DebugBreakPointFailedEx... - 23 January 2007

Ryan Lee

Posts: 4
Score: 0
Joined: 23 December 2006
Status: offline

Hello, everyone:

I got a strange issue when invoke a SP by sql adapter in biztalk 2006.

My ochestration firstly receive a message by SSB adapter, and then assign the message to a xmldocument , and parse the message for constructing the parameters which the store procedure requires, finally got a response message from the SP.
Everything is OK when I set a breakpoint in HAT, otherwise I got a strange exception like below:

The XLANG/s runtime failed in breaking instance 0f809f5d-2d58-42e5-b321-b0e83412608b of service type GoodsReceipt_Biz_Project.Main_GoodsReceipt_Orchestration at debug break point.

Exception type: DebugBreakPointFailedException
Additional error information:
        Value was either too large or too small for a UInt16.

Exception type: OverflowException
Source: mscorlib
Target Site: UInt16 Parse(System.String, System.Globalization.NumberStyles, System.Globalization.NumberFormatInfo)
The following is a stack trace that identifies the location where the exception occured
   at System.UInt16.Parse(String s, NumberStyles style, NumberFormatInfo info)
at System.Xml.XmlConvert.ToUInt16(String s)
at Microsoft.XLANGs.RuntimeTypes.XmlHelpers.ParseString(String s, Type targetType, Boolean throwIfNotParsed)
at Microsoft.XLANGs.RuntimeTypes.XmlHelpers.ChangeType(Object val, Type targetType)
at Microsoft.XLANGs.Core.XMessage.GetContentProperties()
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.PrepareMessage(XLANGMessage msg, IList promoteProps, IList toPromote)
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.PersistMessageState(XLANGMessage msg)
at Microsoft.XLANGs.Core.XMessage.PrePersist(Boolean dehydrate, IStateManager state)
at Microsoft.XLANGs.Core.ReferencedMessages.PrePersist(Boolean dehydrate, Context state)
at Microsoft.XLANGs.Core.Context.PrePersist(Boolean dehydrate, Context state)
at Microsoft.XLANGs.Core.Context.PrePersist(Boolean dehydrate, XlangStore store)
at Microsoft.XLANGs.Core.ExecutingSubStates.PrePersist(Boolean dehydrate, Context ctx)
at Microsoft.XLANGs.Core.Context.PrePersist(Boolean dehydrate, Context state)
at Microsoft.XLANGs.Core.ServiceContext.PrePersist(Boolean dehydrate, Context state)
at Microsoft.XLANGs.Core.Service.PrePersist(Boolean dehydrate, Context ctx)
at Microsoft.XLANGs.Core.Service.Persist(Boolean dehydrate, Context ctx, Boolean idleRequired, Boolean finalPersist, Boolean bypassCommit, Boolean terminate)
at Microsoft.XLANGs.Core.BreakpointCmd.OnIdle(Service s)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

   Any help please.

Thanks a lot.
Ryan Lee

Post #: 1

RE: Anybody encounterred this issue:DebugBreakPointFail... - 25 January 2007

Ryan Lee

Posts: 4
Score: 0
Joined: 23 December 2006
Status: offline

I got the reasone by myself, due to there is a exception scope catches the general exception in the orchestration, and somewhere occurred a negligible convert failure error, so wihout debug mode, the negligible exception was catched by the exception scope.

It is OK when I discard the scope for catching general exception.

Or maybe the release version can solve the issue.

(in reply to Ryan Lee)

Post #: 2