Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sat, 20 Apr 2024 11:37:50 +0000
[Locked] - Upgrade 1673 - Can't Connect to IB
View Count: 861
| [2017-12-22 00:51:03] |
| gayer2428 - Posts: 75 |
|
I keep getting this set of messages. Cannot connect to IB! Please help. Thanks. Interactive Brokers | Connecting to 127.0.0.1:7496 | 2017-12-21 18:46:33 Socket (76) | Creating socket. | 2017-12-21 18:46:33 Socket (76) | Connecting to IP: 127.0.0.1. | 2017-12-21 18:46:33 Socket connected to TWS. Sending client version: 66. Waiting for acceptance. | 2017-12-21 18:46:33 Interactive Brokers | TWS server version: 76 | 2017-12-21 18:46:33 Interactive Brokers | Connected. Waiting for account information. | 2017-12-21 18:46:33 Socket (76) | Socket gracefully closed by remote side. | 2017-12-21 18:46:33 Socket (76) | Received socket Close event. | 2017-12-21 18:46:33 Socket (76) | Initiating close of socket by core. | 2017-12-21 18:46:33 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2017-12-21 18:46:33 Select 'File >> Disconnect' to prevent further connection attempts. | 2017-12-21 18:46:33 Socket (76) | Performed shutdown. Windows error code 10054: An existing connection was forcibly closed by the remote host. | 2017-12-21 18:46:33 * Socket (76) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2017-12-21 18:46:33 Socket (76) | Closed. | 2017-12-21 18:46:33 Interactive Brokers | Disconnected. | 2017-12-21 18:46:33 Will reconnect to the server in 2.0 minutes. Select 'File >> Disconnect' to prevent further connection attempts. | 2017-12-21 18:46:33 Interactive Brokers | Connecting to 127.0.0.1:7496 | 2017-12-21 18:48:33 Socket (79) | Creating socket. | 2017-12-21 18:48:33 Socket (79) | Connecting to IP: 127.0.0.1. | 2017-12-21 18:48:33 Socket connected to TWS. Sending client version: 66. Waiting for acceptance. | 2017-12-21 18:48:33 Interactive Brokers | TWS server version: 76 | 2017-12-21 18:48:33 Interactive Brokers | Connected. Waiting for account information. | 2017-12-21 18:48:33 Socket (79) | Socket gracefully closed by remote side. | 2017-12-21 18:48:33 Socket (79) | Received socket Close event. | 2017-12-21 18:48:33 Socket (79) | Initiating close of socket by core. | 2017-12-21 18:48:33 Error connecting to Data or Trading service. For help with this issue, press the 'Send For Analysis' button on this window. | 2017-12-21 18:48:33 Select 'File >> Disconnect' to prevent further connection attempts. | 2017-12-21 18:48:33 Socket (79) | Performed shutdown. Windows error code 10054: An existing connection was forcibly closed by the remote host. | 2017-12-21 18:48:33 * Socket (79) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2017-12-21 18:48:33 Socket (79) | Closed. | 2017-12-21 18:48:33 Interactive Brokers | Disconnected. | 2017-12-21 18:48:33 Will reconnect to the server in 2.0 minutes. Select 'File >> Disconnect' to prevent further connection attempts. | 2017-12-21 18:48:33 |
| [2017-12-22 02:00:55] |
| e36mikee - Posts: 3 |
|
i am getting the same thing i believe.. i havent tried logging in in a long time..updated TWS and moved sierra chart to the same harddrive.. double checked all my settings.. cant figure it out.. the lines that stick out to me are .... Socket connected to TWS. Sending client version: 66. Waiting for acceptance. | 2017-12-21 17:58:43 Interactive Brokers | TWS server version: 76 | 2017-12-21 17:58:43 Date Time Of Last Edit: 2017-12-22 02:01:52
|
| [2017-12-22 02:25:52] |
| gayer2428 - Posts: 75 |
|
Update: I can connect my BracketTrader front-end to IB using port 7496. But Sierra Chart connection requests on same port are rejected.
|
| [2017-12-22 02:32:24] |
| |
|
We apologize for this. Just give us a few minutes to resolve. We will update this thread. We have started some updates to the connection to TWS to support option chains, and had updated a version number and did not realize this was happening. 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: 2017-12-22 04:43:01
|
| [2017-12-22 02:40:06] |
| gayer2428 - Posts: 75 |
|
Please post an update once this issue is fixed. Thanks.
|
| [2017-12-22 02:51:37] |
| |
|
Version 1674 has now been released. Follow the instructions here to update: Software Download: Fast Update You will now be able to connect. 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: 2017-12-22 02:51:48
|
| [2017-12-22 02:52:39] |
| gayer2428 - Posts: 75 |
|
So much time wasted troubleshooting this at my end. Also spent a half hour with IB on the phone. When you make mods to your software I think you guys need to take care not to introduce side effects such as this. Thanks for listening. |
| [2017-12-22 02:55:59] |
| |
|
It is best to contact us first when there is a connection problem to Interactive Brokers. It is not difficult for us to look at the Message Log and see what is wrong. The reason for this issue was a very very minor detail involving a protocol version number and it is hard for us to guarantee that these things will not happen. Also, the way that the Interactive Brokers designs their interface, makes this kind of issue more common. Additionally, an issue like this involving Interactive Brokers has not been a problem for many years. That is overall a very good record. What we do is is very very complex, and we always do our best, but inevitably little problems can get through. It is very hard for us to avoid. Sometimes we have to get releases out to fix other small issues, or release critical enhancements. 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: 2017-12-22 03:13:26
|
| [2017-12-22 03:04:57] |
| |
|
We also provide an easy way for you to go back to a previous version if there is any problem after updating. Here are the instructions: Software Download: Software Rollback Procedure 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 |
| [2017-12-22 04:15:24] |
| gayer2428 - Posts: 75 |
|
I did downgrade to Rel 1672, had the same issue with connectivity to IB. Clearly, you guys need to work on your software QA and release process. Develop->Test->QA->Release. Not Develop->Release. |
| [2017-12-22 04:19:49] |
| |
|
In this case you needed to have gone back to 1669 to be sure you could have connected. If you are unsure of the version, just ask, and we will determine that for you. Clearly, you guys need to work on your software QA and release process. Develop->Test->QA->Release. Not Develop->Release. We always do our very best but we cannot always be catching every single detail due to the massive amount of functionality that we offer. That is simply an impossibility. When it comes to trading functionality, that does undergo a special level of care, and undergoes more review and testing. We took care of the problem promptly, and you have the ability to go back to a prior version. We consider this matter resolved and closed. And at this point it is fair for us to blame this on Interactive Brokers due to the poorly designed, substandard and unreliable interface which they provide. That was the core problem. This problem is very insignificant due to the overall problems people have with TWS. The protocol they use has never been well-designed. And now they have started to specify a length for the messages which is a more sensible design and the code had not yet been updated to support that length but the version number was triggering that requirement. What about the quality assurance of Trader Workstation? Do you know that Interactive Brokers cannot even reliably provide Position data and this is been a problem for more than 10 years. Being critical of us totally out of bounds here. You simply are not aware of operational realities. And we did apologize for the issue and we took care of it promptly. Sometimes these things happen and we are here to remedy them quickly. Keep in mind Sierra Chart works across a range of data and trading services. One connectivity issue, is minor and it has to do with the overall architecture of the TWS protocol. 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: 2017-12-22 05:51:30
|
To post a message in this thread, you need to log in with your Sierra Chart account: