Connection lost with TDA loading multiple strategies - anyone solve ever?

[lmatiukas]

Another update on my side:

I spoke to another tech on TDA side, and they're 100% sure it's the NT8, and I agree with them since NT7 does not drop the connection. On their end, they can see successful logins, but they are not able to see why the disconnect happens. I reckon these techs weren't high enough in the food chain though, as all connections should be monitored to some level for security reasons at the very least.

Their response is simply, however. They provide with an API, similarly how they did in NT6.5 and NT7, so whatever is not working is on NT8 for sure. Hopefully, someone will look into this.

I'm also writing to update, that the latest NT8 update did not fix this, and TDA still does not work.

[NinjaTrader_PatrickG]

The Development Team has spoken with TD Ameritrade directly and has some questions for you. Primarily, they're wondering if you're connected to your TD Ameritrade account in any other way other than one instance of NinjaTrader. For example:

• More than one installation of NinjaTrader
• Think or Swim
• Mobile apps
• etc.

Are any of these the case? Or do you connect only to your TD Ameritrade from one instance of NinjaTrader at a time?

[lmatiukas]

hey there,

I covered these 2 options with TDA tech also

1. Make sure the password is updated/reset to their latest security requirements.
2. Making sure that only one connection is open. I usually restart my computer fully, before starting NT8 just to double check.

I have to say the disconnects are random as heck. TDA will see my latest log in at 12:31:40 pm today, December 18th. Connection dropped 12:35:30 today, December 18th.

Trace file not surprisingly:

"2017-12-18 12:35:36:771 (My TD AMERITRADE) Tda.Adapter.ConnectMessageKeyInfoAsync: url='https://apis.tdameritrade.com/apps/100/MessageKey;jsessionid=A46107AECC35AC8A3B43B450DBE1 8F9B.zScYxaUgIkY5jYmd5GeLyg?source=NT' messageKeyResponse='<?xml version="1.0"?><amtd><result>OK</result><message-key><token>aa77c0b5732f85b28bdc7c3c70f7a0cf17494ef 74e0caf7ff9f13ba055ce7e09c</token><time-stamp>1513618536928</time-stamp></message-key></amtd>'
2017-12-18 12:35:36:771 (My TD AMERITRADE) Tda.Adapter.GetOrderHistoryAsync request='https://apis.tdameritrade.com/apps/100/OrderStatus;jsessionid=A46107AECC35AC8A3B43B450DBE 18F9B.zScYxaUgIkY5jYmd5GeLyg?source=NT&accountid=8 6808****'
2017-12-18 12:35:36:771 (My TD AMERITRADE) Tda.Adapter.GetOrderHistoryAsync request='https://apis.tdameritrade.com/apps/100/OrderStatus;jsessionid=A46107AECC35AC8A3B43B450DBE 18F9B.zScYxaUgIkY5jYmd5GeLyg?source=NT&accountid=8 6808****'
2017-12-18 12:35:36:771 (My TD AMERITRADE) Tda.Adapter.GetOrderHistoryAsync request='https://apis.tdameritrade.com/apps/100/OrderStatus;jsessionid=A46107AECC35AC8A3B43B450DBE 18F9B.zScYxaUgIkY5jYmd5GeLyg?source=NT&accountid=8 6808****'
2017-12-18 12:35:36:771 (My TD AMERITRADE) Tda.Adapter.GetOrderHistoryAsync request='https://apis.tdameritrade.com/apps/100/OrderStatus;jsessionid=A46107AECC35AC8A3B43B450DBE 18F9B.zScYxaUgIkY5jYmd5GeLyg?source=NT&accountid=8 6808****'
2017-12-18 12:35:36:772 (My TD AMERITRADE) Tda.Adapter.Connect.StreamingRequestWorker started
2017-12-18 12:35:36:945 (My TD AMERITRADE Tda.Adapter.GetOrderHistoryAsync0: <?xml version="1.0"?><amtd><result>OK</result><orderstatus-list><account-id>86808****</account-id></orderstatus-list></amtd>
2017-12-18 12:35:37:023 (My TD AMERITRADE Tda.Adapter.GetOrderHistoryAsync0: <?xml version="1.0"?><amtd><result>OK</result><orderstatus-list><account-id>86808****</account-id></orderstatus-list></amtd>
2017-12-18 12:35:37:122 (My TD AMERITRADE Tda.Adapter.GetOrderHistoryAsync0: <?xml version="1.0"?><amtd><result>OK</result><orderstatus-list><account-id>86808****</account-id></orderstatus-list></amtd>
2017-12-18 12:35:37:150 (My TD AMERITRADE Tda.Adapter.GetOrderHistoryAsync0: <?xml version="1.0"?><amtd><result>OK</result><orderstatus-list><account-id>86808****</account-id></orderstatus-list></amtd>
2017-12-18 12:35:38:073 (My TD AMERITRADE) Tda.Adapter.StreamingDataCallback: IOException='System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at System.Net.Sockets.NetworkStream.EndRead(IAsyncRes ult asyncResult)
--- End of inner exception stack trace ---
at System.Net.ConnectStream.EndRead(IAsyncResult asyncResult)
at NinjaTrader.Tda.Adapter.StreamingDataCallback(IAsy ncResult ar)'
2017-12-18 12:35:38:075 (My TD AMERITRADE) Tda.Adapter.StreamingDataCallback: IOException InnerException='System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at System.Net.Sockets.NetworkStream.EndRead(IAsyncRes ult asyncResult)'
2017-12-18 12:35:38:075 ERROR: The connection was forcibly closed by TDA."

[sledge]

I was kicked off 11:00am EST.

[NinjaTrader_PatrickG]

Sledge, please write in with a link to this forum post and 'ATTN Patrick G' in the title. There are some additional diagnostics we can run on your TD Ameritrade connection.

[sledge]

Sledge, please write in with a link to this forum post and 'ATTN Patrick G' in the title. There are some additional diagnostics we can run on your TD Ameritrade connection.

Ok, thanks, I will - but it will be after Christmas probably.

[NinjaTrader_PatrickG]

The Development Team has made some changes to the TD Ameritrade API in the latest release of NinjaTrader (8.0.12.0). Details can be found here:

https://ninjatrader.com/support/helpGuides/nt8/en-us/8_0_12_0.htm

If any users are experiencing the issues mentioned in this post, please ensure you're using 8.0.12.0 or later.

If you still experience the issues mentioned in this thread, please write into PlatformSupport[AT]NinjaTrader[DOT]com so we may work with you individually to find out more about what you're experiencing. Make sure to provide a brief description of the issue and a link to this thread in the body of your message.