Input string was not in a correct format

Home Page Forums BizTalk 2004 – BizTalk 2010 Input string was not in a correct format

Viewing 1 reply thread
  • Author
    Posts
    • #26054

      Help,

      I have a strange error occuring in a Orchestration.

      It seems there is a limit to the amount of objects\code\shapes I can add to the orchestration before it suddenly throws the error below. The orchestration isn’t very big and even stranger is the error occurs on a send port with is before the object\shape\code I add which seems to take me over a certain unforseen threshold.

      I have removed all xPath as I’ve found suggestion this could be the issue, had my partner in crime take a good look, whom in 8 years of using Biztalk has never seen the error or experienced this problem.

      Any suggestions or ideas would be greatfully appreciated.

      Thanks in advance

      Rob

       

    • #26055

      Sorry, the error.

      xlang/s engine event log entry: Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'QUASAR.BusinessHiway.Common.PhdInterface.CommonTestTrigger(3bcb26a2-08d7-a4db-8fda-463c4a483850)'.

      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: 7d537472-7283-474e-a690-aafd2876b18e

      Shape name:

      ShapeId: 0194f9a7-adf6-4349-9845-8985ab5c1d43

      Exception thrown from: segment 1, progress 25

      Inner exception: Input string was not in a correct format.

      Exception type: FormatException

      Source: mscorlib

      Target Site: Void StringToNumber(System.String, System.Globalization.NumberStyles, NumberBuffer ByRef, System.Globalization.NumberFormatInfo, Boolean)

      The following is a stack trace that identifies the location where the exception occured

        at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)

        at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

        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.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.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.LongRunningTransaction.PendingCommit(Boolean ignore, XMessage msg)

        at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.SendMessage(Int32 iOperation, XLANGMessage msg, Correlation[] initCorrelations, Correlation[] followCorrelations, SubscriptionWrapper& subscriptionWrapper, Context cxt, Segment seg, ActivityFlags flags)

        at Microsoft.XLANGs.Core.PortBase.SendMessage(Int32 iOperation, XLANGMessage msg, Correlation[] initCorrelations, Correlation[] followCorrelations, SubscriptionWrapper& subscriptionWrapper, Context cxt, Segment seg)

        at QUASAR.BusinessHiway.Common.PhdInterface.PhdInterfaceModify.segment1(StopConditions stopOn)

        at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)

      • #26060

        How many Send ports do you have?

        Is it failing on first send port?

        Is there any helper class?

        • #26063

          Hi ,

          From the error message it is pretty much clear that its your helper class " StringToNumber(System.String, System.Globalization.NumberStyles, NumberBuffer ByRef, System.Globalization.NumberFormatInfo, Boolean)" which has the problem, so can you please have look into the helper class  and also call your helper class in the Atomic scope.

          I hope this helps!!

          //Mahesh

        • #26064

          Hi ,

          From the error message it is pretty much clear that its your helper class " StringToNumber(System.String, System.Globalization.NumberStyles, NumberBuffer ByRef, System.Globalization.NumberFormatInfo, Boolean)" which has the problem, so can you please have look into the helper class  and also call your helper class in the Atomic scope.

          I hope this helps!!

          //Mahesh

Viewing 1 reply thread
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.