Interactive-Brokers-B57-Connection-closed-Resolved

Thanks for the details, but I just tried it on 3 systems and can't make it "not" work.

After it disconnected, did you try just hitting Order Manager > IBKR > "Connect" again?

I'll keep looking, but if you have the time to try again (this weekend), a screenshot of the Order Manager and messages could help.

Yes, I hit connect again. It connects and drops the connection after a few seconds.

I also downloaded the newest offline TWS (10.32.1j) and re-installed. Same issue. I won't have time to dig deeper into it tonight, however I will in the morning and will provide whatever else I can find.

Thanks,
Matthias

Hi Cone,

I removed all of my Wealth-Lab data on my development PC, reinstalled just B102 of Wealth-Lab and B57 of Interactive Brokers.

The Order Manager shows this after 4 slowly repeated clicks on connect:



When installing build 56, it works without an issue.

I have also the TWS API Logfiles for b56 and b57 (detailed), which I can provide via email if needed.

Thanks,
Matthias

Here is the screenshot for b56:

Is TWS/IBG running on the same machine as WealthLab?
That's something I didn't consider with the changes in build 57 and would be a problem if it weren't running on the same machine.

TWS was not running on the same machine for these tests (it’s running on a VPS connected via Tailscale).

However, when I first reported the issue, I did also try with a local install connected via 127.0.0.1 and had the same issue.

I will re-validate again however and report back here later today.

Here's some more debugging:

Wealth-Lab and TWS on same machine (Win 11) - Wealth Lab 102 and IBKR build 57:



TWS 10.31 - does NOT work:





TWS 10.32 - DOES work:





Now when trying to connect to TWS on my VPS via Tailscale:



It does NOT work:



Now, when going directly to my VPS (Win 2022 Server) and having 10.32 installed there, it does work when b56 is used using 127.0.0.1 and also via my Tailscale 100.xx.xx.xx address for the same machine.

When installing b57, it does NOT work when using my Tailscale 100.xx.xx.xx address nor does it work with the 127.0.0.1 address.

An observation is that I have to change the client ID in the settings to get it to try to reconnect after a "Connext to Interactive Brokers failed". Only then I get the new try to connect and the "shut down or restarting" error. This might point me to believe that to the connection is being dropped by Wealth Lab and TWS still believes the client is connected?



I do not know why it does work on Win 11 with WL 102 and B57.

Any other ideas what I should try to help?

Build 57 won't work across networks. To fix that we'll add an option in the config for "TWS/IBG not local". You'll be able to connect across a network again, but it disables the "reconnect after TWS restart" feature.

The TWS version is not important as long as it's 10.23 or higher. I don't what was going on with your 10.31 test. The Client ID can't matter either as long as another client isn't connecting with the same ID.

I don't know anything about Tailscale, but it sounds like Windows processes run a bit differently on it.
In that case Build 58's "TWS/IBG not local" will work for that too.

Thanks! I'll wait for the new release then. Thank you for the continued work you put into your great products!

Thank you so much! It works with the new flag.
Have a good rest of your week!

I have a similar problem. This problem occurs in Build 57 and 58. Build 56 works normally. When I connect to the TWS, the connection is immediately disconnected and a new connection attempt is started. I get the following error messages:



@Cone: Do you have an idea?

Strange. It doesn't seem to be due to the error messages. When I use build 56, the error messages are also present, but the connection to the TWS is stable.
Here is the message from Build 56 (as I said, the connection is stable here):

Now I have installed build 58 for the third time and suddenly the connection to TWS is stable. I'll let you know if there are any more interruptions. I hope I haven't confused anyone...

Your errors are caused by MSFT's ML.net library, not IBKR.

Is there any way to fix this?

You'd have to remove those DLLs from the WL8 installation folder manually. I'm not sure how they arrived there, do you have any idea?

It may be related to an older finantic extension. However, I am not sure. Then I will remove these files manually. Many thanks for the hint.

Unfortunately, the problem has now reappeared. The connection to TWS is constantly interrupted.
The following error message appears:



It concerns Build 58.
Everything works with Build 56.

Regressing to build 56 is a good option for anyone having trouble with build 57 or 58. If you do it, make sure to change "UTC format" to the "operator timezone".

Before that, you can simply try the TWS/IBG non-local configuration option in build 58. It disables the new restart detection logic which periodically checks for TWS or IBG running on the same machine.



Personally, I run build 58 on two computers all day without any problem with that option unchecked.

Thank you very much Cone. Unfortunately, it doesn't work with these settings either. The following error messages still appear:

Did you restart WealthLab after making that change?

I`m not sure :-)
I will try it again.

..... I have now tried it again. Installed build 58 and restarted WealthLab. Unfortunately, the problem still persists.

Where's the first connect message? This can't be the full log. Use the Log Viewer instead, click "Uncheck All", and then check only "Interactive Brokers".

It's really very strange... I just installed build 58 and suddenly it works again. If the error occurs again, I'll take a screenshot of the complete log. Thanks for the quick support!

The problem has unfortunately reappeared. Here is the complete log:

This cannot be the full log after WL restart, and, Timestamps are cutoff. (Tip: You don't have to go through the trouble of posting an image. After doing the IB filter like you did, just right click and Copy Messages to Clipboard, paste.)

Anyway, it's Saturday. Disconnects from IB are expected because they do maintenance every Saturday morning.

Unfortunately, the problem still exists:

Timestamp Source Message Exception
"11.11.2024 10:15:10:560" "Interactive Brokers" "10:15:10.56 516: Request Open Order Sending Error -"
"11.11.2024 10:15:10:561" "Interactive Brokers" "10:15:10.561 IB Connection closed."
"11.11.2024 10:15:10:561" "Interactive Brokers" "10:15:10.56 TWS/IBG disconnected from IB Servers. _internetConnected is True"
"11.11.2024 10:15:10:562" "Interactive Brokers" "10:15:10.562 IB Connection closed."
"11.11.2024 10:15:30:598" "Interactive Brokers" "10:15:30.59 531: Request Current Time Sending Error - "
"11.11.2024 10:15:30:598" "Interactive Brokers" "10:15:30.598 IB Connection closed."
"11.11.2024 10:15:30:599" "Interactive Brokers" "10:15:30.59 TWS/IBG disconnected from IB Servers. _internetConnected is True"

It does not work with version 57 either. Version 56, on the other hand, works perfectly.

We keep going in circles on this, but the first connection message after restarting WealthLab cannot be "Request Open Order Sending Error".

Start TWS.
Restart WealthLab.
Show me the log.

I understand that a few of you are having trouble with Build 58, but it works perfectly for most of us. I've got it on 3 machines and don't have any trouble, so getting a complete log after restart is important to get a clear picture of what's happening for you.

Unfortunately, there is nothing more in my log. I have now closed everything again. Restarted the TWS and then WL. I confirmed the connection attempt to the TWS with “yes”.

Here is my log again as a screenshot:



Or have I overlooked something?

I guess you haven't, but thanks for humouring me. I just don't yet see how it's possible to get that result. :(

By the message (Request Open Order Sending Error), can we assume you have active orders?

Yes, there are active orders in the TWS. I definitely don't want to humor you.

😂 Don't take it the wrong way. Humouring (or humoring) means to go along with or accommodate someone. So it's a good thing. You gave me what I asked for 3 times, but I didn't really understand it until the last time. 😉

Ok, now I have understood it :-)

Although the information in the log is not exactly the same, I found that the problem I'm having is very similar to the one described in the post.

I would like to ask where I can download the ibkr extension version 56 so I can try to see if using the previous version solves my problem.

If it's different, it could be helpful to see your log too.
Just filter the Log for Interactive Brokers, right click and Copy Messages to Clipboard, paste.

I'll working on getting a download build 56...

We put a link to download Build 56 at the bottom of the IB Provider page.

Don't forget to select "operator timezone" in the TWS/IBG API configuration. "UTC format" won't work properly for Build 56.

My situation is like this: First I open tws and then open wealthlab. At this point I get these 2 logs:

1. TWS connected
2. Market data connections OK：usfarm.nj, hfarm, cashfarm, usopt, usfarm, apachmds，ushmds, secdefhk

I found that when the third log about time difference appears, it means that everything is normal. But now most of the time there are only the above two logs.

Next I will open order manager and click “connect. ”After waiting for a while, a red box about connect failure will appear, and there will be an updated log, similar to the screenshot in the above post:

TWS/IBG disconnected from IB Servers.
internetConnected is True

But I can't copy and paste the log now because when I click“connect” now, the software will freeze and don't respond until I quit the program.

If I can reproduce the logs thatI just described, I'll update them as soon as I can.

Update: Version 56 works for me！
It can connect automatically and normally after installation.
Thank you Cone for sharing this version.

Adding my $0.02, fwiw.

Both IB B57 & B58 had caused WL8 to freeze on hitting the Stream button, causing me to force-close the app.
Downgrading to B56 after each IB update restored normal functionality, and that's the build I'm currently using.