TDA Connection

[molite]

I have TDA and just downloaded Ninja the other day.
Right now I am in Sim mode with TDA feed just learning my way around.
This morning for a couple hours I kept getting the error it would not backfill charts. Everything was pretty useless.
Does that happen often? is there a fix?

I have version 6.5.1000.10 do I need to install the special build in the link provided in previous post? I do plan to trade through Ninja soon.
Thanks

one last thing...
With TDA Software I get approx 6 years back data (approx 9 months intra day) is that what i will get accesing TDA with Ninja?

[Edthetrader]

TDA and Ninja Trader have never worked properly for me. It worked fine in sim mode but when I went live it was a nightmare. I lost a lot of money finding this out. Apparently there are "known" issues with TDA & Ninja Trader together. Issues that you won't be told about until you inquire about them. Do yourself a favor and allow me to share my costly error. When you try it with real money, go small and keep your finger on the trigger of your TDA platforms trade ticket. I switched to InteractiveBrokers. Now everything works fine. God luck!

[molite]

Thanks for the heads up. I may switch to IB as my volume goes up.
Maybe I'll stay in sim mode untill the new super version multiproccesor version of Ninja comes out.
Does anyone know how well the automated strategies work with a TDA account?

[nt100]

I too got backfill errors this morning and several of the previous days. The errors eventually go away later in the day which leads me to believe it's an issue on TDA's side.

Can support look into this since it's a serious issue. Here's a link to my original post from 3/16/09:

http://www.ninjatrader-support2.com/vb/showthread.php?t=15184&highlight=nt100

- Thanks

[dtf139]

Unable to log in to Ameritrade this morning. Upgraded to the latest build - 6.5.1000.10 with no change. This is the error that I receive:

ERROR : ORDSTAT we were unable to process your request. please try again later.

[NinjaTrader_Dierk]

Could you please:
- uninstall NT6.5 via control panel
- clear your browser cache
- install latest custom build from here: https://www.ninjatrader-support.com/...er.Install.msi

Please let us know if that would resolve the issue.

[dtf139]

Could you please:
- uninstall NT6.5 via control panel
- clear your browser cache
- install latest custom build from here: www.ninjatrader-support.com/ninjatrader/nt6.5.custom/NinjaTrader.Install.msi

Please let us know if that would resolve the issue.

Okay, that seems to have done the trick. submitted some test orders away from the market and Ameritrade accepted them okay.
Thanks Dierk.

[NinjaTrader_Dierk]

Thanks for your feedback.

[WhoKnows]

POSBAL and OTSSTAT again - which NT version

Working on NT 6.5.10.
Last week I could get connection to TDA, but suddenly the POSBAL and ORDSTAT messages are there again.

I though this was solved with NT6.5.10 but apparently not. What is the latest stable version that is also stable with the latest version of TWA? (I use multiNT with IB).

Or is MultiNT just not stable with both IB and TDA?

I don't really want to go down in versions as I don't know what issues will then appear (old NT versions contain the faulty ParabolicSar and I don't want to edit my strategies again) and I think they require a different TWS.


BTW as asked before (see thread re:CONDEAD) ... PLEASE give us an option to kill the connection manually if it hangs. I now have to exit NT and also loose my connection to IB .... so I also need to restart all the strategies again....and scrutinize and square open positions, etc. etc.
This way MultiNT is just not workable, and a user may be better of with 2 different NTs.

After 2 quarters of leasing NT I was thinking about buying NT (esp. as I like the forum support), but these issues really put me on the brink of looking elsewhere and additionally get the benefit of more advanced optimization and multi-time frame.

I'll hold out until NT7 next month to see what improvements that brings, but please incorporate the option to stop connections.

[NinjaTrader_Dierk]

Can you please post the relevant error messages from your NT logs so I could send them to TDA in order to understand what's going on? Thanks

[WhoKnows]

Mail sent to NT support per your attention.


BTW: TDA is working again.


Too be clear, I accept that servers of brokers (e.g. TDA) may behave problematic resulting in an inability to make contact.
But my gripe with NT is specifically how it deals with TDA errors and the inability to kill unsuccessful connection attempts.
Especially for a Multi broker NT I expect that I don’t have to stop the whole NT and loose all existing/running strategies with other brokers.

[NinjaTrader_Dierk]

Thanks for your suggestion. We'll add it to the list of future considerations.

[WhoKnows]

I am sure you at NT are doing your best to improve your product.

However the implementation of our suggestions would be more inspirational than contributing to a list which must be quite long considering the times I have seen that exact quote.

[WhoKnows]

Damned popups

As asked several times before: Pls adapt NT so that only 1 popup warning of each type is put on the screen.

Again today for 40 minutes every 15 seconds the HTTP call failed popup was dropped on the screen.
I know this message comes from the TDA servers, but it is NT that should handle those error messages.

This NT behavior makes a multibroker NT unusable to trade with IB..


Date Category Message
7/8/2009 14:41 Connection HTTP call failed: LASTORDSTAT 7/8/2009 13:20 Connection Trading Account TD Ameritrade: Primary connection=Connected Price feed=Connected 7/8/2009 13:20 Connection HTTP call failed: LOGIN 7/8/2009 13:19 Connection HTTP call failed: LOGIN 7/8/2009 13:19 Connection HTTP call failed: LOGIN 7/8/2009 13:19 Connection HTTP call failed: LOGIN 7/8/2009 13:19 Connection HTTP call failed: LOGIN 7/8/2009 13:18 Connection HTTP call failed: LOGIN 7/8/2009 13:18 Connection HTTP
.
.
.
.

failed: LOGIN 7/8/2009 13:09 Connection HTTP call failed: LOGIN 7/8/2009 13:09 Connection HTTP call failed: LOGIN 7/8/2009 13:08 Connection HTTP call failed: LOGIN 7/8/2009 13:08 Connection HTTP call failed: LOGIN 7/8/2009 13:08 Connection HTTP call failed: LOGIN 7/8/2009 13:08 Connection HTTP call failed: LOGIN 7/8/2009 13:07 Connection HTTP call failed: LOGIN 7/8/2009 13:07 Connection HTTP call failed: LOGIN 7/8/2009 13:07 Connection HTTP call failed: LOGIN 7/8/2009 13:07 Connection HTTP call failed: LOGIN 7/8/2009 13:06 Connection HTTP call failed: LOGIN 7/8/2009 13:06 Connection HTTP call failed: LOGIN 7/8/2009 13:06 Connection HTTP call failed: LOGIN 7/8/2009 13:06 Connection HTTP call failed: LOGIN 7/8/2009 13:05 Connection HTTP call failed: LOGIN 7/8/2009 13:05 Connection HTTP call failed: LOGIN 7/8/2009 13:05 Connection HTTP call failed: LOGIN 7/8/2009 13:05 Connection HTTP call failed: LOGIN 7/8/2009 13:04 Connection HTTP call failed: LOGIN 7/8/2009 13:04 Connection HTTP call failed: LOGIN 7/8/2009 13:04 Connection HTTP call failed: LOGIN 7/8/2009 13:04 Connection HTTP call failed: LOGIN 7/8/2009 13:03 Connection HTTP call failed: LOGIN 7/8/2009 13:03 Connection HTTP call failed: LOGIN 7/8/2009 13:03 Connection HTTP call failed: LOGIN 7/8/2009 13:03 Connection HTTP call failed: LOGIN 7/8/2009 13:03 Connection HTTP call failed: LOGIN 7/8/2009 13:02 Connection HTTP call failed: LOGIN 7/8/2009 13:02 Connection HTTP call failed: LOGIN 7/8/2009 13:02 Connection HTTP call failed: LOGIN 7/8/2009 13:02 Connection HTTP call failed: LOGIN 7/8/2009 13:01 Connection HTTP call failed: LOGIN 7/8/2009 13:01 Connection HTTP call failed: LOGIN 7/8/2009 13:01 Connection HTTP call failed: LOGIN 7/8/2009 13:01 Connection HTTP call failed: LOGIN 7/8/2009 13:01 Connection HTTP call failed: LOGIN 7/8/2009 13:00 Connection HTTP call failed: LOGIN 7/8/2009 13:00 Connection HTTP call failed: LOGIN 7/8/2009 13:00 Connection HTTP call failed: LOGIN 7/8/2009 13:00 Connection HTTP call failed: LOGIN 7/8/2009 12:59 Connection HTTP call failed: LOGIN 7/8/2009 12:59 Connection HTTP call failed: LOGIN 7/8/2009 12:59 Connection HTTP call failed: LOGIN 7/8/2009 12:59 Connection HTTP call failed: LOGIN 7/8/2009 12:59 Connection HTTP call failed: LOGIN 7/8/2009 12:58 Connection HTTP call failed: LOGIN 7/8/2009 12:58 Connection HTTP call failed: LOGIN 7/8/2009 12:58 Connection HTTP call failed: LOGIN 7/8/2009 12:58 Connection HTTP call failed: LOGIN 7/8/2009 12:57 Connection HTTP call failed: LOGIN 7/8/2009 12:57 Connection HTTP call failed: LOGIN 7/8/2009 12:57 Connection HTTP call failed: LOGIN 7/8/2009 12:57 Connection HTTP call failed: LOGIN 7/8/2009 12:57 Connection HTTP call failed: LOGIN 7/8/2009 12:56 Connection HTTP call failed: LOGIN 7/8/2009 12:56 Connection HTTP call failed: LOGIN 7/8/2009 12:56 Connection HTTP call failed: LOGIN 7/8/2009 12:56 Connection HTTP call failed: LOGIN 7/8/2009 12:55 Connection HTTP call failed: LOGIN 7/8/2009 12:55 Connection HTTP call failed: LOGIN 7/8/2009 12:55 Connection HTTP call failed: LOGIN 7/8/2009 12:55 Connection HTTP call failed: LOGIN 7/8/2009 12:55 Connection HTTP call failed: LOGIN 7/8/2009 12:54 Connection HTTP call failed: LOGIN 7/8/2009 12:54 Connection HTTP call failed: LOGIN 7/8/2009 12:54 Connection HTTP call failed: LOGIN 7/8/2009 12:54 Connection HTTP call failed: LOGIN 7/8/2009 12:53 Connection HTTP call failed: LOGIN 7/8/2009 12:53 Connection HTTP call failed: LOGIN 7/8/2009 12:53 Connection HTTP call failed: LOGIN 7/8/2009 12:53 Connection HTTP call failed: LOGIN 7/8/2009 12:53 Connection HTTP call failed: LOGIN 7/8/2009 12:52 Connection HTTP call failed: LOGIN 7/8/2009 12:52 Connection HTTP call failed: LOGIN 7/8/2009 12:52 Connection HTTP call failed: LOGIN 7/8/2009 12:52 Connection HTTP call failed: LOGIN 7/8/2009 12:51 Connection HTTP call failed: LOGIN 7/8/2009 12:51 Connection HTTP call failed: LOGIN 7/8/2009 12:51 Connection HTTP call failed: LOGIN 7/8/2009 12:51 Connection HTTP call failed: LOGIN 7/8/2009 12:50 Connection HTTP call failed: LOGIN 7/8/2009 12:50 Connection HTTP call failed: LOGIN 7/8/2009 12:50 Connection HTTP call failed: LOGIN 7/8/2009 12:50 Connection HTTP call failed: LOGIN 7/8/2009 12:49 Connection HTTP call failed: LOGIN 7/8/2009 12:49 Connection HTTP call failed: LOGIN 7/8/2009 12:49 Connection HTTP call failed: LOGIN 7/8/2009 12:49 Connection HTTP call failed: LOGIN 7/8/2009 12:49 Connection HTTP call failed: LOGIN 7/8/2009 12:48 Connection HTTP call failed: LOGIN 7/8/2009 12:48 Connection HTTP call failed: LOGIN 7/8/2009 12:48 Connection HTTP call failed: LOGIN 7/8/2009 12:48 Connection HTTP call failed: LOGIN 7/8/2009 12:47 Connection HTTP call failed: LOGIN 7/8/2009 12:47 Connection HTTP call failed: LOGIN 7/8/2009 12:47 Connection HTTP call failed: LOGIN 7/8/2009 12:47 Connection HTTP call failed: LOGIN 7/8/2009 12:46 Connection HTTP call failed: LOGIN 7/8/2009 12:46 Connection HTTP call failed: LOGIN 7/8/2009 12:46 Connection HTTP call failed: LOGIN 7/8/2009 12:46 Connection HTTP call failed: LOGIN 7/8/2009 12:45 Connection HTTP call failed: LOGIN 7/8/2009 12:45 Connection HTTP call failed: LOGIN 7/8/2009 12:45 Connection HTTP call failed: LOGIN 7/8/2009 12:45 Connection HTTP call failed: LOGIN 7/8/2009 12:45 Connection HTTP call failed: LOGIN 7/8/2009 12:44 Connection HTTP call failed: LOGIN 7/8/2009 12:44 Connection HTTP call failed: LOGIN 7/8/2009 12:44 Connection HTTP call failed: LOGIN 7/8/2009 12:44 Connection HTTP call failed: LOGIN 7/8/2009 12:43 Connection HTTP call failed: LOGIN 7/8/2009 12:43 Connection HTTP call failed: LOGIN 7/8/2009 12:43 Connection HTTP call failed: LOGIN 7/8/2009 12:43 Connection HTTP call failed: LOGIN 7/8/2009 12:43 Connection HTTP call failed: LOGIN 7/8/2009 12:42 Connection HTTP call failed: LOGIN 7/8/2009 12:42 Connection HTTP call failed: LOGIN 7/8/2009 12:42 Connection HTTP call failed: LOGIN 7/8/2009 12:42 Connection HTTP call failed: LOGIN 7/8/2009 12:41 Connection HTTP call failed: LOGIN 7/8/2009 12:41 Connection HTTP call failed: LOGIN 7/8/2009 12:41 Connection HTTP call failed: LOGIN 7/8/2009 12:41 Connection HTTP call failed: LOGIN 7/8/2009 12:41 Connection HTTP call failed: LOGIN 7/8/2009 12:40 Connection HTTP call failed: LOGIN 7/8/2009 12:40 Connection HTTP call failed: LOGIN 7/8/2009 12:40 Connection HTTP call failed: LOGIN 7/8/2009 12:39 Connection Trading Account TD Ameritrade: Primary connection=Connected Price feed=ConnectionLost 7/8/2009 12:39 Connection HTTP call failed: LASTORDSTAT 7/8/2009 12:38 Connection HTTP call failed: LASTORDSTAT 7/8/2009 9:57 Connection Time to flatten=12:00:00 AM Flatten all=Disabled 7/8/2009 9:57 Position Instrument='ITRP' Account='779730104' Avg price=9.57 Quantity=140 Market position=Long

[NinjaTrader_Dierk]

- please make sure you are on latest 6.5.1000.11
- please send traces and logs to support AT ninjatrader DOT com and reference this thread so we could take a look. Thanks

Edit: Please make sure you send traces and logs by Help->Mail to support. If that would not work I needed complete (!) directories <my documents>/NinjaTrade6.5/log+trace. Thanks