开云体育

I'm trying to move from 973.2g to a later version.? I am able to connect and receive several data farm messages, but my requests for account updates and other services are ignored.

Does anyone have an idea of what's going on?

Without any prior warning, TWS terminated on me this morning 40 minutes before the market open with a message that 973.2g is no longer supported.? They used to give me several weeks of warning.? Fortunately 973.2g was working on another computer so I was able to get up & running 5 minutes before the market opened.

I'm using an old c api interface.? There is no activity on the port after submitting the account update request.? It's as if TWS is completely ignoring the request.? If I submit an order on TWS it is not sent to my program.

Any ideas?

Do you have api logging turned on?? Check the api.day.id.log file to see if the request is sent.

IB sometimes sets a new minimum allowable TWS version but I don't remember them doing that with Api versions. I can't seem to find release notes that talk about minimum versions but maybe someone has seen something about recent minimum version changes.

Well, there are a couple error codes that indicate that TWS or the client API are out of date:

• 357??? Your client version is out of date.
• 503??? The TWS is out of date and must be upgraded.

Any chance you get one of those?
There have been a few API changes lately, such as increasing size fields from int (lots or 100) to long (shares) in 985 that may require a more selective version combination between client and TWS.
闯ü谤驳别苍

On Fri, Aug 20, 2021 at 07:04 PM, Frank Bell wrote:

I do have api message logging turned on.? There are no entries when I use 981 or later.? I do get them with 973.2g.

You should at least have up to the error messages like,

In these cases I like to get "a second opinion" (as in use a completely different client) to see whether the problem is on the client or server side. My goto client is Richard King's "Contract Inspector". Just fire it up, connect to your TWS and grab some contract details. It that works, focus on your API. If not, something is out of balance with the TWS or the network between client and TWS.

Log files are encrypted but you can go to Account -> Diagnostics -> ApiLogs in TWS to decrypt them.

Are you sure to retire IBC?
For a reliable ? 24/7-Setup its still necessary. After a shutdown for whatever a reason, you get a clean start.

In ib-container ()? its included in the cron-facility.
This leads to a very robust IB-Gateway-Implementation.

I don't remember the details now, but at some point TWS started sending an additional (unrequested) message upon connection, I think ManagedAccounts. I had to update my library to parse this message since I hadn't needed it previously. This was before the 'V100' protocol so there were no length headers that allowed a client to skip over messages it wasn't interested in.

One of the sneakier aspects of using the TWS APi is that you can't assume anything about the order of messages. Hopefully it won't be too much of an effort to get back going.