Login Page - Create Account

Support Board


Date/Time: Thu, 28 Mar 2024 21:45:54 +0000



Orders not submitted to IB

View Count: 4244

[2013-08-05 17:52:44]
Sierra Chart Engineering - Posts: 104368
This is now resolved. Please update to version 1005.
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
[2013-08-06 12:59:28]
rc7rader - Posts: 144
I encountered the problem again and I e-mailed you the TWS log. I also described what I was doing when the problem occurred. I hope you could find something in the log or in what I was doing to help resolve this issue.
[2013-08-06 18:18:52]
Sierra Chart Engineering - Posts: 104368
This is what the log says:

SJ 22:41:15:905 JTS-CCPDispatcher-35: Order Canceled - reason:
SJ 22:41:25:905 AWT-EventQueue-0: cached row key []
SJ 22:41:53:480 JTS-Cleaner-31: Cleaning maps
SJ 22:42:29:160 JTS-EServerSocket-951: [9368400:62:68:1:0:0:0:ERR] OrderId {1073} is < 1089

In each copy of Sierra Chart you are running connected to Trader Workstation, go to the Window >> Show/Hide Message Log and let us know what you see for Next Valid Order ID. We need to know this for each copy of Sierra Chart. It will be somewhere near the top of the Message Log.
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: 2013-08-06 18:20:24
[2013-08-07 00:22:56]
rc7rader - Posts: 144
The first instance of Sierrachart has Next Valid Order ID: 1070. I tested submitting an order initially and it was able to submit to IB. It is when I replaced the stock on one chart window that failed when I tested again. When it could not connect, I disconnected and reconnected, I got Next Valid Order ID: 1089.
The second copy of Sierrachart has Next Valid Order ID: 1070, which submitted the order when I tested. I did not replace any stock on the chart windows.

[2013-08-07 00:34:41]
Sierra Chart Engineering - Posts: 104368
Make sure both copies of Sierra Chart have a nonzero and different Instance Client IDs set through Global Settings >> Data/Trade Service Settings.

The problem is they are being given the same range of order IDs. This is going to cause problems. However, there is no reason why the Trader Workstation software should be giving out the same range of IDs. This is clearly an issue on the TWS side.

All of the details about changing the symbols of charts, closing charts, and the number of charts and Chartbooks you are using, has no relevancy at all to this.
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: 2013-08-07 00:35:50
[2013-08-07 02:17:07]
rc7rader - Posts: 144
Yes I have different Instance Client IDS on both copies of Sierrachart. If having the same order ID is causing this, then I should check the message log every time to ensure that I get a different order ID. If not, I should disconnect and reconnect one copy and make sure the two copies have different next valid order IDs.
[2013-08-07 02:42:44]
Sierra Chart Engineering - Posts: 104368
The starting order ID is controlled by Trader Workstation. We have no control over that or know how that is managed. All we can see is that TWS is not doing it correctly. You can try reconnecting.

You do want to make sure that each copy of Sierra Chart has a very significant difference with the Next Order ID.
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
[2013-08-08 07:50:27]
rc7rader - Posts: 144
Yesterday, I had the same starting order ID for both copies of Sierrachart but I was able to submit order to IB on both copies. At first I tried getting a different order ID so I disconnected one copy and reconnected but I still got the same order ID. I then disconnected the second copy and reconnected and it also got the same order ID. I guess disconnecting and reconnecting does not change the next valid order ID that IB gives to Sierrachart. I did not experience any problem yesterday even if both copies of Sierrachart received the same order ID.

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

Login

Login Page - Create Account