NT8 Crashed and will not start up again

[Grover71]

Not sure what is happening but NT8 crashed this morning after I was changing some values in an indicator setting on a chart. It appeared to freeze up after that then crashed. Now when I start it up it starts restoring the previous windows for that workspace and it crashes and never completely starts back up.

So, I figured there might be a saved chart in that workspace I was using because each time it tried to load that it fail. What I did was to go into the XML _workspaces.xlm and change the active worksheet and drop that back the workspaces directory. It started up after that just fine.

Is this the correct fix? Or do you think I need to do something in addition or different?

[Grover71]

Actually this didn't fix the issue. The platform load up in my black workspace but when I try to launch a chart window it shuts down. Please help!

[Grover71]

Now when I start up in Easy Open workspace it loads initially just fine. I can do the following thing just fine:
1. connect to platforms for accounts / data
2. load the super dom and trade on an account no problem
3. open script editor and edit fine
4. etc..

When I try to load a New Chart (note: no other charts are currently active) then the system hangs and crashes.

I looked at the log and found this one error that might be an issue. Not sure how to fix. -- see the attached screen shot

[backtester831]

When I had something like this, I deleted the db folder inside the NinjaTrader 8 folder and the UI file inside the NinjaTrader 8 folder, then it worked.

[Grover71]

Reading in other places in the forum, I have discovered what probably caused the initial problem.

'On bar close' or 'On each tick'. If you select 'On each price', it will result in the volume only updating the values of the indicator when price changes

So, I was messing around with that selection and selected on each price on an indicator. I'm not sure which one to be sure but maybe it was MFI because that is where I'm getting the error. Or it was with a custom indicator that uses MFI to be more specific.

I think this is the problem but how do I correct the issue is the question now. If I'm loading a new chart that doesn't contain that indicator why would this still error out?



Here is some data from the trace txt file when this first occurred.

2024-02-02 06:03:07:666 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:03:12:666 Cbi.Instrument.RequestBars (to Provider): instrument='MNQ 03-24' from='2/1/2024 12:00:00 AM' to='2/1/2024 12:00:00 AM' period='1 Minute'
2024-02-02 06:03:12:974 Cbi.Instrument.RequestBars (to Provider): instrument='MNQ 03-24' from='2/2/2024 12:00:00 AM' to='2/2/2024 12:00:00 AM' period='1 Minute'
2024-02-02 06:03:13:281 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:04:19:134 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:05:16:374 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:05:25:463 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:05:39:873 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:06:06:060 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:22:45:647 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:22:58:814 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:23:06:871 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:23:35:590 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:23:44:890 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:24:06:628 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:24:19:997 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:24:42:079 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:25:15:213 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:25:34:626 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:25:40:499 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:25:47:342 ERROR: MFI relies on volume updates expecting Calculate 'On each tick' or 'On bar close'
2024-02-02 06:32:13:029 ActiproManager.LoadIntellipromptAssemblies (SharkIndicators.Common): Could not load file or assembly 'System.Json, Version=2.0.6.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

[Grover71]

I tried deleting the UL.xml file as suggested and that didn't do anything to resolve the issue.

Here is what I see when I try to create a new chart. It acts likes its loading and then everything crashes with no errors. Just shuts down.

[NinjaTrader_Erick]

Hello Grover71,

Thank you for reaching out.

Please try testing your platform in Safe Mode to verify if this behavior is being caused by a 3rd-party add-on using the steps below.

Safe Mode will prevent NinjaTrader from:

• Loading workspaces and connecting on start-up.
• Loading custom assemblies (i.e. 3rd-party add-ons and NinjaScripts)
• Getting instrument updates from the server

To enable Safe Mode, you can use the following steps:

• Shut down NinjaTrader.
• Click on the Windows Start Button
• Search for and Launch NinjaTrader (Safe Mode)

Once you have opened the platform in Safe Mode:

• Reconnect to your Data Provider
• Please open a new chart with no custom bar types/indicators/templates and test for issues.

Does the behavior persist on this blank Workspace in Safe Mode?

• If not, please try opening your previous workspace by going to the Control Center > Workspaces drop-down. It may already show as being open. Hit 'close' and do not save and then re-open it again for your windows to re-appear. You will notice that no 3rd-party add-ons are running in Safe Mode.

Does the behavior return on your regular Workspace in Safe Mode?

• If not, restart NinjaTrader, and test for the behavior on your Workspace normally once more with your 3rd-party add-ons available. If this reintroduces issues, I suggest rebuilding your workspace, adding 1 add-on at a time.
• Please keep track of what add-ons you add back in to identify the cause of the behavior if it returns.

If it does not return, it indicates the error was isolated only to your other Workspace. I also suggest making a backup of your workspace so we can restore a working version of it if the issue returns. You will want to keep this backup file on an external hard drive or uploaded to a cloud drive such as Google Drive, Dropbox, or OneDrive.

To create a backup, go to the Control Center > Tools > Export > Backup File. Additional information about backups may be read in our Help Guide linked below.

• NinjaTrader 8 Help Guide — Backup and Restore

Please let me know the results of this test. I look forward to your response.

[Grover71]

I followed your instructions and here is what I know so far...

1. Reloaded in Safe mode, connected to a data feed, loaded the MES chart for futures without issue. This was using my saved "Easy Open" workspace.
2. Reloaded the other worskspace in question and it loaded up fine and chart appears to load fine as well in safemode.
3. Loaded the "easy open" workspace in regular mode, connected to data fine, but when I open a chart it blows up the NT8 platform.
4. Tried same as #3 with original workspace and same thing happens.
5. Tried rebuilding a fresh workspace in regular mode and same thing happens (crash).

What's next?

[NinjaTrader_Erick]

Hello Grover,

Thank you for reaching out.

If the platform does not crash in safe mode, this points to there being issues with custom scripts no longer functioning properly.
Please note that our troubleshooting with 3rd party add-ons is limited and we advise reaching out to the Developer as they will be expert on their piece of software.

When building the workspace from scratch in regular, at point do you notice a crash?

Are you loading each custom component one by one?


If you are able to Open the platform in Safe mode, I would actually recommend you try rebuilding this workspace from new.

While in Safe Mode, please go to Workspaces -> New

Now name this new workspace a name of your choosing.

Please open a new chart with no custom bar types/indicators/templates on this new workspace.

Now Go up to Workspaces again and click "Save"

Now go to the X on the Main Control center and Close the platform.

(It will not ask you to save again before closing, that why we just manually saved)

Now launch the platform in Regular mode once again and this new workspace will open and hopefully, there will be no crashing.

Then please try to start customizing this workspace and test for issues.



You can also try restoring your workspace from an older save using the 'Restore workspace' feature for working version of the workspace from a previous save date:Complete the following steps to use the "Restore workspace" feature:

1. Navigate to Tools -> Database Management
2. Select "Restore workspace"
3. Select Restore to be directed to the location of the recovery workspaces
4. Workspaces will be organized in folders with the same name as the workspace
5. Double click the folder of the workspace you want to recover and then select the recovery file with the date/time that you want to recover. You'll want to select a file larger than 1kb from the available options.

Below I have provided a link to the Restore Workspaces section of our help guide:

• https://ninjatrader.com/support/helpGuides/nt8/en-us/index.html?database_operations.htm#Restoreworkspac e

If this does not work, then I would recommend rebuilding the workspace from scratch.

Please let us know if you have any questions.

[Grover71]

I'm not even loading any indicators or anything. I'm simply trying to open a blank chart when it crashes.

[Grover71]

I created a new workspace in safe mode, loaded a chart... nothing on it... then reloaded in regular NT8... it crashes when loaded the chart... its a blank chart on a clean workspace so its not about the workspace IMO. Something is messed up with loading just a simple chart. Nothing at all on it. I don't have anything other than the main control window and the 1 simple chart for ES futures.

Also noticed Suspended on task in the task manager. This started happening after that initial crash. It can't load a blank chart.

Here is what I'm referring to


.

[NinjaTrader_Erick]

Hello Grover71,

Thank you for your follow up.

To rule out that there are issues with your core files/NinjaTrader Installation, I recommend you try a platform repair first, and if this does not resolve it, then you would want to try installing NT8 "clean".

1. To complete a repair, do the following:

• Shut down NinjaTrader 8
• Go to your computer's Control Panel > Programs & Features (Note: search for 'Control Panel' to find it within the Windows Start Menu. This will be a different window than the Settings page)
• Left-click once on NinjaTrader 8 > select 'Repair' above the list of available programs
• Restart the platform after it finishes repairing, and test for this behavior again. If the issue persists, proceed to step 2.

2. You may follow the steps listed below to completely uninstall and reinstall NinjaTrader clean, and then transfer your custom information to the new installation if you wish.

• Close all running applications.
• Navigate to your Documents folder > Right-click on the 'NinjaTrader 8' folder > Rename > rename the folder to 'NinjaTrader 8 OLD'. DO NOT delete this folder.
• Uninstall NinjaTrader within Windows Control Panel.
• Navigate to C:\ > Program File (x86) > Delete the 'NinjaTrader 8' folder if it exists
• Reboot your PC.

Then reinstall

• Login into the NinjaTrader Account Dashboard
• Click "Download" in the bottom left-hand corner of the sidebar
• Once the installation had downloaded, ensure any previous version of NinjaTrader is closed before running the installation package.

This will now be a "brand new" platform when you launch it.

Please launch, login, and connect. Open a chart to see if it is loading properly.

(If you are asked "How you would like to trade?" Choose "Simulation" and the platform will open. Then go to "Tools" -> "Options" -> enable Multi-Provider" -> then go to "Connections" -> "configure" and add any additional account connections you may need).


If everything works, you may follow these steps to reimport your old, custom information to the new installation if you wish.

First, shut down NinjaTrader, then open the new 'NinjaTrader 8' Documents folder in one window, and the 'NinjaTrader 8 OLD' folder in another (right-click > Open in New Window).

In the new 'NinjaTrader 8' folder, rename the 'workspaces', 'templates', and 'bin' folders to 'workspaces NEW', 'templates NEW', and 'bin NEW'Next, copy/paste the existing 'workspaces', 'templates', and 'bin' folders from the 'NinjaTrader 8 OLD' folder into the new 'NinjaTrader 8' folder.

Please note that if the issue is re-introduced when you copy over your custom files, the issue would point to a possibly "corrupt" workspace or custom scripts affecting platform functionality.

Please let us know if you have any other questions.

[Grover71]

I have discovered after removing some custom scripts that 1 or 2 files are corrupt.
I'm trying to recreate that script from backup to get it resolved.

To get to this point I did uninstall a few old assemblies from Shark Indicators and others that might have had an issue. I also removed my own custom scripts from indicators and strategies.

Relaunched the platform and opened a chart just fine. I added back a few script files at a time until I had an issue. So that allowed me to narrow down what was causing the problem.

Not sure I need any more help or not but if so I'll reply to this thread again.

Thanks for you help Erick.