I’ve just published release 3.19.0 of IBC to GitHub. Download the zip for your platform from here:

?

?

The main improvement in this release is the resolution of these issues:

?

#142 Login failed - Server disconnected, please try again

#251 Unknown Username.Password/Duplicate Session?

#253 IBC unable to restart after 2.5 days of running. Happened multiple times.

?

Other enhancements:

?

• there is a revised Task Scheduler template for Windows, to ensure that IBC is automatically restarted if it is closed for any reason
• a Cold Restart mechanism has been introduced. This provides an easy way to ensure compliance with IBKR's requirement that TWS/Gateway be fully logged off at some point on Sundays. See the notes for the new ColdRestartTime setting in config.ini
• the User Guide has been updated to include information about IBC's command server
• sample scripts have been provided to enable easy use of IBC's command server

?

The recommended procedure for installing this release is:

?

1. Rename your existing IBC folder, for example to IBC-old, so you can easily revert to it if need be.
2. Create a new IBC folder.
3. Extract the contents of the zip file as described in the User Guide.
4. Update the config.ini and scripts as required. Note that the top-level start scripts have not changed, so you can copy those back from the renamed IBC folder to the new IBC folder rather than update the new copies. These are:

StartTWS.bat

StartGateway.bat

twsstart.sh

gatewaystart.sh

twsstartmacos.sh

gatewaystartmacos.sh

?

Richard

?

The thread you link to indicates that this was a temporary issue that has now been resolved.

?

Please check to make sure that there really is still an issue for you.

?

If so, it may be that IBKR are enforcing this in the Asia region, but not in Europe or the US (I’m in Europe and have no problem).

?

It may be worth upgrading to the latest TWS which is 1029.1g I think (unless you’re using the stable version, in which case make sure you’ve got the latest version of that).

?

Note that in general, once a ‘latest’ version has been superseded by an even later version, IBKR don’t continue to maintain the previous latest, so bugs in it are not fixed. In other words, if you’re using the ‘latest‘ version, you need to check regularly to make sure you really are still using the latest. Personally I would never consider using the ‘latest’ version for live trading, though I do use it for the paper trading account.

?

I also want to emphasise that I’m reluctant to have IBC override TWS functionality unless it’s really necessary. It may be the case that the Honk Kong authorities have insisted that IBKR enforce this behaviour (if I remember correctly, this is what happened with mandatory 2FA: first Asia, then the rest of the world).

?

So I suggest that someone should complain to IBKR about this issue (if indeed it still is an issue for some users), and find out what their motivation is.

?

Richard

?

?

Unfortunately there is no easy way for something external to the program to tell a Java program where to start. It would be possible (and not difficult) to write a Windows program that would use the Windows API to get a handle to the Gateway window and reposition it. It might even be possible to do it with a VBS script. There is also a utility called cmdow (see ) which should do the job.

?

Another possibility is to use the MinimiseMainWindow setting in IBC’s config.ini so that the Gateway window is actually not visible (and then if you need it you can just click on the taskbar icon).

?

The real answer would be for IB to enhance Gateway to remember the last location it was started in, like TWS. I really can’t imagine why they haven’t already done this.

?

Richard

?

Not that I’m aware of. There is a file called jts.ini which stores settings that are not related to any particular user, and this contains settings for the main window width and height, but not its location.

?

Theoretically IBC should be able to relocate the Gateway main window. However there are issues that can arise, such as when attaching or removing the second monitor, changing the scaling or resolution of the monitors and so on. Nothing insoluble, but it means that it’s not just a simple case of calling a single Java function.

?

So my initial reaction is that it’s probably just not worth my time and effort to pursue this, when it’s only a moment’s effort for the user to drag the window to the other monitor once per session.

?

Feel free to try and convince me that this would be a significant benefit…

?

Richard

?

?

Well, the log file looks perfectly normal. Since you haven’t given any information about what you mean by TWS freezing, or the circumstances when it occurs, there’s really nothing I can do.

?

If the TWS user interface freezes, there is nothing at all that IBC can do about it.

?

And if you restart TWS, then full login with 2FA is mandatory. Every time. That is IBKR policy and again there’s nothing IBC can do about it.

?

You need to find out what’s causing the freezing. I can’t help with that either.

?

Having said all that, I notice something in your logfile that’s almost certainly not correct. You have AcceptIncomingConnectionAction=manual in your config.ini. Is this really what you want? It means that any time something tries to connect to the API, a pop-up window will be displayed and you have to manually accept the connection.. Until you accept it, the API client that is trying to connect will not be able to proceed. Perhaps that’s what is happening? From the API client’s point of view it looks like TWS is not responding, whereas in reality it’s just waiting for you to do something. (However I don’t see any evidence of this in the logfile.) Read the comments in config.ini for this setting for further advice on this.

?

So report your problem to IBKR with as much information about the circumstances as possible.

?

?

Yes. The very first paragraph of the User Guide tells you about it.

?

By the way, I noticed that you said “running start_tws.bat”. But IBC doesn’t have a .bat file of that name. Did you mean StartTWS.bat? Or is this another .bat file from somewhere else?