write.as

Deviation levels error

Reload ninjascript (hotkey F5, or right-click –> reload ninjascript)

You may have to do this a few times before the error clears, but it usually works. If not, shut down NinjaTrader, clear historical data, restart and try again.

If that doesn't work, just leave the chart up for 30 minutes, then reload ninjascript and that will usually clear the error and display deviation levels.

If it still does not clear after reloading ninjascript at least 5 times, you can try the next options...

Apex Toolkit server error

First, flush your computer's DNS cache:

• (Illustrations here)

• Use the search function in Windows on your computer, type “cmd”, and press enter.

• In the window that appears, type in “ipconfig /flushdns” (without the quotation marks) and press enter.

• Close the command prompt window.

Second, clear your browser DNS cache:

• If you use Google Chrome as your main browser, enter the following address in your browser’s address bar and press the Enter key on your keyboard: chrome://net-internals/#dns

https://www.screencast.com/t/jN3Wl7g2eggz

• Then Reboot your computer and launch NT

• If an error still appears when you load charts, click the “F5” key

If this does not resolve the issue, you might have to continue flushing the DNS and restarting the computer. For some, it has worked after doing this several times.

Apex programmer: “Here's what gets me working, has so far every time. Clear all browser dns, close them. Clear flush computer DNS in command prompt. RESTART the computer. Open whatever, if it doesn't work, flush dns again then it usually works.“

Other things to try:

• Change to a different DNS service. (Options to try are Cloudflare, Quad9, OpenDNS, Google. Other options and instructions listed here and here.)

• Try after changing your IP address.

• Try connecting with a different ISP.

• If you have another computer that has never used the Apex Desktop Assistant before, try the install process there.

• Try in a virtual machine.

• Try these steps:

1. In windows proxy settings, disable 'Automatically detect settings'.
2. In Chrome, clear host cache here: chrome://net-internals/#dns
3. Restart computer
4. Go into windows proxy settings again, and re-enable automatically detect settings
5. Retrieving NT8 toolkit releases should now work

You can keep trying any combination of all the above suggestions until it works. Outside of these things, there are currently no other recommendations aside from waiting for it to be resolved on the backend.