It seems that I never made the formal report about it. This is my own text from 6 or so months back, written to PRT :

What I certainly do notice is that PRT has difficulties in initialising the connection with TWS. I mean, by now I have collected quite some combinations of situations which work and which will not work (unless some specific “reset” sequence is applied). I will sent a report about this in a later stage – when I myself see better through what’s happening.
On a side note : I have worked with the API myself a little (programmed with it), so I kind of know a bit how TWS can respond to third party connections.

RubberToe wrote:

And now it connects, after a whole day of fighting with it, grrrrrrrr.  I restarted IBKR for the 5th time and it loaded an update, and a ton of alarms came in to PRT, like they were stored in a que all day.

Yes, I have pictures of those stacked messages too.

From the same sequence of screenshots I made about this, I also find the one you see in the first attachment (also more than one message at the same time). Notice that this is PRT showing the message, while the content of the message seems wrong, but it not really (as it seems). I mean, look at the background in the 2nd attachment. That is TWS which is inactive. As far as I can recall this initiates such a fault situation because you yourself (in my case, that is) caused TWS to disconnect, for example by means of making a connection with the (IBKR) mobile app. THAT now chokes the PRT connection with TWS (quite obviously) but that is the unexpected situation. Do notice that TWS stays live for a minute or so WHILE it is officially not connected to IB indeed (thus, content of the message would be correct).

It will now require that special reset sequence, I really forgot. I definitely recall that either PRT or TWS needed to be restarted TWICE. Something like

1. Start TWS
2. Start PRT
3. Close TWS
4. Start TWS

or

1. Start PRT
2. Stat TWS
3. Close PRT
4. Start PRT

All relates to the (important !) message you see in the 3rd attachment. Thus, you MUST allow TWS to detect the incoming PRT connection. Hence, if PRT already runs prior to starting TWS, this will not happen. This is how the startup sequence becomes crucial.

As a kind of bonus, I added the 4th attachment. I am pretty surely recalling that despite this message, this was NOT the case. All looked OK (connection button is green) but nothing worked for real. So you’d need to keep in touch with that too …

Please remember, you can work directly with PRT and IB. This is probably a matter of asking your PRT support to set it up for you ?

image_2021-05-20_074118.png image_2021-05-20_074245.png image_2021-05-20_074804.png image_2021-05-20_075020.png