Support Board
Date/Time: Sat, 10 May 2025 19:44:59 +0000
Post From: Has something changes with respect to multiple Sierra Chart connections to IB TWS?
| [2015-01-20 16:14:58] |
| Agent Orange - Posts: 40 |
|
I have an update on this issue. I would say based on the evidence I have now gathered, it's unclear whether this issue arose due to a change at IB or a change at Sierra Chart. What I can say with certainty is that this was not an issue as of last week. I have been connecting 2 instances of Sierra Chart to TWS for years with no problem, but when I tried to do this on the evening of Sunday 1/18/2015, it no longer worked. I would add that regardless of what changes caused this issue, it may require cooperation between Sierra Chart support and IB support to resolve it. I contacted IB support, and they had me enable API logging, and when I attempted to connect a second instance of Sierra Chart to TWS I found the relevant error message to be: "22:02:12:888 -> 4-2--1-2101-Unable subscribe to account as the following clients are subscribed to a different account.{9368395}-" (The first instance of Sierra Chart was already connected to TWS with client ID 9368395, and I was attempting to connect the second instance as 9368396. They also had me connect two instances of their own Java test client using two different client IDs, and, of course, that worked fine, and they interpret that to mean that the problem is with Sierra Chart rather than TWS. I still think it's possible IB changed something on their servers, but I have no way to investigate beyond what I've described below. -------------------- From examining the log files, I now have a guess at what is going on. My account at IB is actually two accounts (call them account #1 and account #2) which are linked (which is to say, I log in to the first account and have access to both accounts). It appears that when the first instance of Sierra Chart connects, it requests account information for each of the two accounts, first by subscribing to account #1 for account data, then unsubscribing, then subscribing to the account data for account #2. My guess is that when the second instance of Sierra Chart attempts to connect, it tries to subscribe to account data for account #1, and this fails because the first instance is still subscribed to the account data for account #2. But as I said, this is only a guess based on what I can see in the log files. As I place my trades through code I wrote myself in Java, the only reason I connect 2 instances of Sierra Chart to TWS is so I can monitor the markets from my laptop from other parts of my home when I am not at my trading machine. So if my guess about what is going on is correct, I could work around the problem if there is a way to tell Sierra Chart not to request my account info when connecting to TWS. Is this possible to accomplish through some settings of Sierra Chart? This would not actually fix the problem for other users, but I suspect this problem may not be affecting very many as it only occurs when attempting to connect multiple Sierra Charts instances to TWS with linked IB accounts. I apologize for the complication of all this and the possibility that this issue was caused by a change at IB; my prior experiences with Sierra Chart support (I've been a VERY happy customer of Sierra Chart for many years) and IB support suggest that you guys are the ones who are most likely to figure it out regardless of who caused it. |