I can't replicate it either and do get the price wheel as shown in the paste below (v1.12) As for tickets, "we didn't bother" - please understand we get thousands of tickets per day and do our best to reply on a timely basis but it is holiday season and we're also getting hit with the latest variant of Covid like most other firms. So hopefully you can have some patience on the reply. In the meantime, I have noted this thread to some of my colleagues who may look into this.
The issue is that IB is repeatedly sending threatening email messages to its customers, forcing all of them to switch over to the latest version (10.12). The threat is that trading will be disabled on December 29th. It is therefore IB who is creating a deadline for themselves to solve the customers' issues. Which is why customers don't have patience in this instance. Quote from the email (bold letter font used by IB):
Just for the record, rec'd below from IB support. However, I'll stick with prior versions, until they stop working. Meanwhile, I opened yet another account with another broker. Tired of dealing with IB issues. *********************** As we have not received any TWS diagnostic logs or screenshots from you yet we are unable to comment anything on this. However we could advise you to reset you TWS to defaults to eliminate any possible settings error. Please follow the below steps to reset your TWS to defaults. 1. Delete the TWS shortcut icon from your desktop screen and task bar. 2. Find jts folder in File Explorer and rename it to jts.old 2. Open https://www.interactivebrokers.com in the browser. 3. Click on Login>>Download Trader Workstation. 4. Click on TWS Latest>>Download. 5. Follow the onscreen instructions to complete the installation. 6. Open TWS and once you see the login window please click on "More Options" (don't login yet) 7. Uncheck the box next to "Use/store settings on server" 8. Now enter your username and password and proceed to normal login This should load your TWS to default settings and now you could save your new settings. *************************************
I probably shouldn't say anything, but version 9.81 is still letting me run it as of today. The wording of the IB communication seemed a bit different from the usual upgrade deadline - not sure if I'm reading too much into it - "discontinue operation of non-upgraded installs". And it was a one-time bulletin that I haven't seen since. Usually when the deadline is looming I'm seeing it every login. Given the nature of Log4J, I feel like most of the patching was on the server side and related components. I'm certain IB has fixed everything on their end and my hope is they've decided that we really don't need to upgrade. I usually leave the old icon on my desktop for a while whenever I install an upgrade.
Same here. Others told me that IB had solved the Log4Shell vulnerability in version 9.81.3g and therefore that this version is also "safe". I received the same email message twice, a few days apart. Not as a bulletin, but sent to my email inbox.
For the slider (wand) on the normal order lines... If you lost that go to configure -> Display -> and on the lower half of that screen under the Price/Size/Offset Wand Handling make sure the box is ticked for "show wand when field is clicked on immediately"
Once again IB sent e-mail demanding to upgrade to at least 10.12.2G. I did that, but as last time, the BookTrader no longer works properly. I had been using 10.11, without problems, so likely some IB screw-up. Not sure of the work-around yet, but possibly using Sierra Chart equivalent, DOM trader. I had used that for years, but switched back to raw IB. Very disappointing that IB tech can't fix their software.
when I start TWS, I get 10.12.2H and don't seem to have a problem with book trader but I only just tested now with a few orders/modifications/cancellations. Can you tell me the specific issue so I can pass to programming to debug and fix? thx
Would advise not to upgrade. I've had peculiar errors I've never seen before. Gateway and client losing connection while neither the Gateway nor the client were aware of it - client sending requests to void and Gateway showing all clients connected.