Hi Richard,
Hope you are well. This is probably another outdated tws version support issue but your opinion would be appreciated. I am expecting others to be similarly affected. I have been running 974.4 on a remote server without issues. I lost the connection at 4am this morning and all connections thereafter failed (no messages that this version is not supported were received). When I tested on my local machine I discovered a new prompt requesting connection with an ssl layer which needs to be manually checked.
I run the remote instance with ExistingSessionDetectedAction=primary in the config file. However this setting (perhaps the whole ?configuration file) now seems to be ignored once I select the SSL layer and I now need to close all other sessions, which block, before I can launch using ibc on the remote instance.?
toggle quoted message
Show quoted text
On 24 Aug 2021, at 12:47, Richard L King <rlking@...> wrote:
?
Judging by the OP's screenshot, this is not just API incompatibility. I think IB are saying they will no longer allow you to use 972.
?
I don't really understand why anyone is surprised by this, because it has happened many times before.. It would of course be better if IB gave us a week or two's warning before pulling the plug, but they've never done so before either, and why change the bad habits of a lifetime?...
?
I realise that this is going to cause problems for some people, , but given that this is known behaviour from IB it's perfectly possible to avoid grief by ensuring you test your API clients (at least occasionally) against the current 'latest' (not beta) version. I run the 'latest' version all day every day on my paper-trading account (as well as the 'stable' version on my live account), and run my programs against both. That way, I can be sure that when the 'stable' version is moved up I can switch the live instance to it without problems.
?
Richard
?
?
?
Did your application log files show any error messages?
In case you have logged error code 503 "The TWS is out of date and must be upgraded", it may actually be an incompatibility between your API version and TWS/IBG instead of TWS/IBG and Interactive Brokers. The section says:
Client errors are those occurring purely on the TWS API client code and as such they are never sent by the TWS
And the additional notes for error code 503 say:
Indicates TWS or IBG is too old for use with the current API version. Can also be triggered if the TWS version does not support a specific API function.
We had that a few years back when we tried to use TickByTick data with a TWS that did not support them. The logged "msg" field of the error message was quite specific and pointed us in the right direction. I don't recall, whether TWS also had a popup error, but I believe it did.
´³¨¹°ù²µ±ð²Ô
