Error: Unhandled exception

[Asurakun1]

Updated to the new version of nt8 and now this occurs. This happens when i try to edit drawings on the chart and when i attempt to add columns on the market analyzer.

edit: I cleared the cache, db from day, min, and tick, cleared workspace. I even removed the entire folder of nt8 from my documents. Grabbed a new install of nt8 and tried to run it again. The error still pops up.

[NinjaTrader_ShawnB]

Hello Asurakun1,

Thank you for your post.

Could you please send the log and trace from your platform to look further into this inquiry.

To send me your log and trace files from within NinjaTrader. Go to Control Center-->Help-->Email Support in NinjaTrader. Put '2289177 - Att Shawn', in the subject field and enable 'Log and trace files'. Also, give a reference of this thread in the body of the email.

We look forward to assisting you further.

[Asurakun1]

Alright successfully sent. I'll be looking forward to your reply for a way to get this matter fixed.

[NinjaTrader_ShawnB]

Hello Asurakun1,
Thank you for your post.

Unfortunately, we have not yet received your log and trace files.

Please send an email to platformsupport [at] ninjatrader [dot] com with your log and trace files included as an attachment to the email, so I may investigate this matter further.

• Open your NinjaTrader folder under Documents.
• Right click on the 'log' and 'trace' folders and select Send To> Compressed (zipped) Folder.

• Send the 2 compressed folders as attachments to this email.
• Once complete, you can delete these compressed folders.

Put '2289177 - Att Shawn', in the subject field and enable 'Log and trace files'. Also, give a reference of this thread in the body of the email.

Please do not hesitate to contact us for any other NinjaTrader inquiries you may have.

[Asurakun1]

It actually fixed itself once i opened the 32bit client for some reason. Then reopened the 64bit client and things are just fine now.

[juartur]

Hi, actually I had the same error today with the 64bit version, then I did as Asurakun1 and it fixed itself too ... perhaps something to do with the database that gets corrupted for some reason