Home >> Support Board

Support Board

Date/Time: Fri, 03 May 2024 09:06:13 +0000

How to Post a Message for Support

error message

View Count: 1255

[2016-12-14 15:17:43] #1 [Go To First Post]
User28682 - Posts: 233
Hi, I sent a message log to you. I keep getting an error message and it looks to be related to TD Ameritrade. I am connected to TD Ameritrade just fine the whole time. Thanks TT HTTPS connection to apis.tdameritrade.com:443 (62) \| SSL shutdown indicates not able to send 'close notify'. \| 2016-12-14 06:59:13 HTTPS connection to apis.tdameritrade.com:443 (62) \| SSL has been shut down. \| 2016-12-14 06:59:13 HTTPS connection to apis.tdameritrade.com:443 (62) \| SSL object has been freed. SSL state is now disconnected. \| 2016-12-14 06:59:13 HTTPS connection to apis.tdameritrade.com:443 (62) \| Shutdown and closed. \| 2016-12-14 06:59:13 TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 458. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 459. Request type: Single Order Status Request. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 460. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 461. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 462. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 463. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 464. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 465. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 466. Request type: Single Order Status Request. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 467. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 468. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 469. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 470. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 471. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 472. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 473. Requested script: KeepAlive. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 474. Requested script: KeepAlive. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 475. Request type: Single Order Status Request. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 476. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 477. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 478. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 479. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 480. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 481. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 482. Request type: Single Order Status Request. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 483. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 484. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 485. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 486. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 487. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 488. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * HTTPS connection to apis.tdameritrade.com:443 (0) \| Resolved address apis.tdameritrade.com to IP 216.105.251.201. \| 2016-12-14 07:00:06 HTTPS connection to apis.tdameritrade.com:443 (64) \| Connected. \| 2016-12-14 07:00:06 HTTPS connection to apis.tdameritrade.com:443 (64) \| Starting TLS 1.0 connection. \| 2016-12-14 07:00:06 HTTPS connection to apis.tdameritrade.com:443 (64) \| SSL connection established. \| 2016-12-14 07:00:06 Connection to the external service has been lost. \| 2016-12-14 07:02:35 TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 490. Request type: Single Order Status Request. \| 2016-12-14 07:02:35 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 491. Requested script: BalancesAndPositions. \| 2016-12-14 07:02:35 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 492. Requested script: BalancesAndPositions. \| 2016-12-14 07:02:35 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 493. Requested script: BalancesAndPositions. \| 2016-12-14 07:02:35 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 494. Requested script: BalancesAndPositions. \| 2016-12-14 07:02:35 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 495. Requested script: BalancesAndPositions. \| 2016-12-14 07:02:35 * TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 496. Requested script: BalancesAndPositions. \| 2016-12-14 07:02:35 * HTTPS connection to apis.tdameritrade.com:443 (64) \| SSL shutdown indicates not able to send 'close notify'. \| 2016-12-14 07:02:35 HTTPS connection to apis.tdameritrade.com:443 (64) \| SSL has been shut down. \| 2016-12-14 07:02:35 HTTPS connection to apis.tdameritrade.com:443 (64) \| SSL object has been freed. SSL state is now disconnected. \| 2016-12-14 07:02:35 HTTPS connection to apis.tdameritrade.com:443 (64) \| Shutdown and closed. \| 2016-12-14 07:02:35 TD Ameritrade \| Streamer finished. Request ID: 3. \| 2016-12-14 07:02:35 HTTPS connection to ameritrade02.streamer.com:443 (28) \| SSL shutdown indicates not able to send 'close notify'. \| 2016-12-14 07:02:35 HTTPS connection to ameritrade02.streamer.com:443 (28) \| SSL has been shut down. \| 2016-12-14 07:02:35 HTTPS connection to ameritrade02.streamer.com:443 (28) \| SSL object has been freed. SSL state is now disconnected. \| 2016-12-14 07:02:35 HTTPS connection to ameritrade02.streamer.com:443 (28) \| Shutdown and closed. \| 2016-12-14 07:02:35 TD Ameritrade \| Disconnected. \| 2016-12-14 07:02:35 Disconnected from TD Ameritrade. \| 2016-12-14 07:02:35 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. \| 2016-12-14 07:02:35

[2016-12-14 17:49:36] #2 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
This indicates a communication problem to the TD Ameritrade server: TD Ameritrade \| An HTTP request did not successfully complete. Request ID: 465. Requested script: BalancesAndPositions. \| 2016-12-14 06:59:13 * If it is not causing you a problem, then just ignore the messages and move the Message Log out of the way. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2016-12-14 17:53:18] #3 [Go To First Post]
User28682 - Posts: 233
When it happens, it keeps popping up repeatedly, I dont like having to close it out all the time. Interferes with trading.

[2016-12-14 18:29:25] #4 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
OK, but there is a communication error occurring. We cannot prevent this. We did not say close the Message Log, just move it out of the way and keep it open. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2016-12-14 18:29:59

[2016-12-14 19:22:30] #5 [Go To First Post]
User28682 - Posts: 233
This communication error has been there off/on for many months.

[2016-12-14 19:32:44] #6 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
OK. While we do not really favor Interactive Brokers, that really is going to be a more stable system for stock trading. This is what we recommend: http://www.sierrachart.com/index.php?page=doc/InteractiveBrokers.php For futures trading there are many other choices available other than TD Ameritrade and they are listed here: http://www.sierrachart.com/index.php?page=doc/Data.php TD Ameritrade at this point is considered in our secondary category of supported services. It is not something we would normally recommend any longer. We have no control over the problem. We strongly recommend that you move your futures trading over to another service. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2016-12-14 19:39:24] #7 [Go To First Post]
User28682 - Posts: 233
So even if I just have TD open and not linked to any trading it cant be turned off or corrected?

[2016-12-14 19:47:02] #8 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
The message cannot be turned off. There is nothing we can do to reasonably correct this problem. Any such attempt would be silly. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2016-12-14 19:49:19] #9 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Actually there is a better solution. If you are just using the TD Ameritrade connection so you can get real-time futures data from the Sierra Chart Exchange Data Feed, then what you need to do is just connect once a month to TD Ameritrade as explained here: http://www.sierrachart.com/index.php?page=doc/SierraChartRealTimeFuturesStockDataFeed.php#ConnectingOnlyOnceAMonthToTradingAccount Make sure though that when you are using the SC Data-All Services service directly, that the symbols of the charts match what are in File >> Find Symbol. Refer to help topic 1.3: https://www.sierrachart.com/index.php?page=doc/helpdetails1.php Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2016-12-15 07:07:36

To post a message in this thread, you need to log in with your Sierra Chart account: