Support Board
Date/Time: Sun, 29 Dec 2024 15:54:35 +0000
Error: "Synchronized Internal Position to current Service Position. Current Position qua..
View Count: 14491
| [2016-05-11 16:52:19] |
| |
|
"the Sierra Charts software is interpreting the absence of data as evidence that there are no portfolio changes occurring, and this may be a source of issue."
We do not know what they mean and there is nothing for us at this point to be doing.We have not done anything further on this until you reproduce the issue since our last posting at post #47. 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-05-11 16:54:28
|
| [2016-05-11 20:11:00] |
| User713273 - Posts: 409 |
|
Yes, testing and trying to re-produce without much luck. Will be testing again tomorrow.
|
| [2016-05-12 04:52:37] |
| |
|
It looks like Interactive Brokers identified the problem based upon what was posted in the hidden post: Upon initially launching TWS, it appears that TWS had a problem connecting to the IB server because of a competing session (a simultaneous login with the same username from a different instance of TWS, IB Gateway, WebTrader, or the mobile IB TWS). When there is a competing session, TWS will not be able to connect to the server to perform any task such as retrieving account values, requesting market data etc. It will also not be possible to perform the analogous functions through the API during this time period. Prior to the competing session being disconnected, Sierra Charts appears to make a subscription request to receive account updates. This request is unsuccessful because of the competing session with the same username at this time. Sierra Charts appears to then not check whether the subscription request has been successfull but continues as usual. So we are going to follow up with them about this. But this looks like something they need to resolve within TWS. That is the proper solution. 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-05-12 04:58:19] |
| |
|
We have followed up with Interactive Brokers based upon the most recent information.
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-05-12 14:44:56] |
| User713273 - Posts: 409 |
|
Yes, this is most likely not the issue at hand, I spoke with them about this and this only occurs when I first start up SC and then connect to IB. At no time am I running dual connections or dual sessions. This post was hidden after I got this response; Does this issue occur during the time-frame (11:25:34) that the trade occurs? As you reccomended, I will create a second username when trading specifically. "In the complete TWS log file provided, the issue with a competing session only occurred in the first few seconds after TWS was launched- This was when Sierra Charts attempted to make a subscription to account updates that was unsuccessful." This is normal on startup. Again have had no issues this AM, will ping you if issues comes up. Thx Date Time Of Last Edit: 2016-05-12 14:48:20
|
| [2016-05-12 17:21:37] |
| |
|
With the way that we see the sequence of events we think it can be a problem and we implemented a solution to it where if there is not a response to a request for Position data updates, Sierra Chart will reconnect to TWS. This has been released and tested, it is out in version 1411. When you can update to version 1411. 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-05-12 17:22:52
|
| [2016-05-12 18:21:13] |
| User713273 - Posts: 409 |
|
Updated will monitor, thx for your time. Hopefully this issue is resolved. Also, I've noticed that the times are now synching, great addition. Local computer UTC time and Server UTC time difference: 0 seconds. | 2016-05-12 06:29:16 Date Time Of Last Edit: 2016-05-12 18:25:21
|
| [2016-05-13 18:01:14] |
| |
|
These questions will not be answered within this unrelated thread. You need to start a new Support Request.
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 |
To post a message in this thread, you need to log in with your Sierra Chart account: