Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

Log tab: Input string was not in a correct format

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Log tab: Input string was not in a correct format

    I found out that the following message appears on the log tab every time I run NT8:
    There was an error on initializing instrumentation: Input string was not in a correct format.
    I don't notice that it interferes with my work, but I would like to understand it. What can cause this error?

    #2
    Hello curious,


    Thank you for posting on the NinjaTrader forums.


    There is usually an error message that precedes this - we will usually see something referring to a third party indicator. Are you able to provide a screenshot or let us know what you see around the error message?


    If you provide a screenshot please make sure to omit any relevant account information.


    Thank you!

    Comment


      #3
      Originally posted by NinjaTrader_LuisH View Post
      Hello curious,
      Are you able to provide a screenshot or let us know what you see around the error message?
      Like this, it appears everytime I start NT8
      Attached Files

      Comment


        #4
        Any thoughts on the reasons for this error?

        Comment


          #5
          Hello curious,


          Got some more information on the error from our team.


          It means that during the platform's attempt to load or process data (most likely related to custom instruments, templates, or NinjaScript), it encountered a value that couldn’t be parsed—usually a string that it expected to be a number.


          Common Causes:
          1. Corrupted or incorrectly formatted NinjaScript – A script or indicator is trying to convert a string to a number, but the string is not in a valid numeric format.
          2. Improperly defined instrument or template settings – There may be a malformed or corrupted entry in your instrument settings or data series defaults.
          3. Custom Add-Ons or 3rd Party Scripts – These can sometimes contain formatting bugs, especially when parsing user input or loading data from a file.
          4. Badly formatted strategy or indicator template – If a saved template contains an invalid setting, it could trigger this on startup.

          As a result, we do think it might be best if you reach out to the vendor if you can isolate the error message to a particular NinjaScript add-on.


          Thank you!

          Comment


            #6
            Gee, if only the error message could itself provide more context
            and identify where the heck the error is coming from, then the OP
            might be able to figure who is doing it.

            It's simple Software Engineering 101.

            ... sigh ...

            -=o=-

            Just an idea, I'd also check the relevant trace file, see if any
            additional information is being dropped in there.

            Comment

            Latest Posts

            Collapse

            Topics Statistics Last Post
            Started by argusthome, 03-08-2026, 10:06 AM
            0 responses
            55 views
            0 likes
            Last Post argusthome  
            Started by NabilKhattabi, 03-06-2026, 11:18 AM
            0 responses
            37 views
            0 likes
            Last Post NabilKhattabi  
            Started by Deep42, 03-06-2026, 12:28 AM
            0 responses
            17 views
            0 likes
            Last Post Deep42
            by Deep42
             
            Started by TheRealMorford, 03-05-2026, 06:15 PM
            0 responses
            19 views
            0 likes
            Last Post TheRealMorford  
            Started by Mindset, 02-28-2026, 06:16 AM
            0 responses
            49 views
            0 likes
            Last Post Mindset
            by Mindset
             
            Working...
            X