We have not experienced any issues on our end, Lou, but then our setup is very different. Let me throw out a few thoughts, some or all of them you may have thought about yourself already:
- Which version of TWS/IBGW are you running? Latest/Stable and Standalone/Autoupdate? Reason why I ask is that IBKR recently switched the stable track from the 981 level to the 10.12 level. There have been a lot of changes introduced in version 10 and I believe there are a couple new settings in the General API screen. Having said that, those TWS/IBGW changes should impact paper and real accounts equally.
- Have you confirmed that the port for your real account in the TWS/IBGW API settings has not changed somehow? In other words, is the TWS/IBGW port really identical to the one you use in your client?
- And finally, have you tried to get a "second opinion", meaning have you tried an API client that is very different from what you normally use? One that comes to mind is
Hope there is something here that gets you a step closer.
闯ü谤驳别苍
On Tue, Jul 5, 2022 at 06:36 PM, Lou Dudka wrote:
Hi All,
I suddenly (over the weekend) cannot connect on:
Call objTWSControl.m_TWSControl.Connect(connectionHost, connectionPort, clientId, False)
connectionHost is blank
connectionPort is correct in TWS API setup
clientId is correct and unique.
ONLY when trying to connect to Production.
I know we've all heard it before, but (to the absolute best of my knowledge) I've changed nothing.? This code is "as is" from IB and has not been changed ever.
If I simply switch (same XLS/VBA code) the connectionPort to the Test API port everything works.
My app (Excel/Win7/ActiveX) just hangs on the call. Old API code, don't know version.
Something changed over the weekend.
Thanks, as always, and Be Well,
Lou Dudka
