- ago
For a few days we have a problem connecting the TWS (IB). The WL/IB connection is already working - but as soon as we go to "Account" or "Quotes Window" Wealth Lab crashes when IB is connected.

If IB is not connected, there is no crash wenn go to Quotes or Account.

But when we want to get streaming quotes from IB, WL crashes again, even though IB hasn't been connected yet.

What is the best way for us to document the error so that you can support us? What can trigger the error?

We have already reinstalled WL with "repair". The problem is still ongoing.

We would now like to uninstall the single extension from IB to fix the error. Does that make sense or how do you do that? Or do you have other suggestions?

Thanks!

0
796
Solved
20 Replies

Reply

Bookmark

Sort
Cone8
 ( 21.52% )
- ago
#1
1. The first thing to consider is, what has changed in the last few days when the problem started?

2. What versions are you running?
a. WealthLab
b. IB Provider
c. IB TWS

Re: .. get streaming quotes... even though IB hasn't been connected yet.
When you request anything from the IB provider, the first thing it does is connect to a running instance of TWS.
0
- ago
#2
I have to correct what I said above. The crash also happens without connecting WL to IB.

I was able to save an error message instead.



0
- ago
#3
1. The first thing to consider is, what has changed in the last few days when the problem started?

The API settings were temporarily changed in the TWS because we want to test access via the server. But that was reset to the original settings.

2. What versions are you running?
a. WealthLab
Build 32
b. IB Provider
c. IB TWS
latest: Build 10.21.1p - March 7th
0
Cone8
 ( 21.52% )
- ago
#4
Okay, this popped up a couple weeks ago. This is an IB problem. It's caused because we're subscribing to BTC.USD for the most coverage to generate a "heartbeat" and the IBApi.EDecoder is having problems with a " " (whitespace) thousands separator.

We're solving it in the next IB Provider by not subscribing to BTC for the heartbeat if the local group separator is a white space. Although now I'm reconsidering that and may just use a forex contract like EUR.USD.

The only way you can get around it now is to change your machine's thousands separator. Unfortunately, this will affect some of your WealthLab settings, so it's best to start with a fresh settings file if you do that.
0
Best Answer
- ago
#5
Ok - Thanks.

That means I can't connect IB to WL at the moment and have to wait for your IB Extension update, right? The workaround you suggested is to complicated...

But that also means that TWS/IB live trading via various APIs is currently not possible, if I understand that correctly.

Is this an issue affecting all customers or is it a problem related to my local settings?

0
Cone8
 ( 21.52% )
- ago
#6
It's an IB API Decoder problem with your local settings that appears when a client subscribes to anything that has a quote above 1000.

Corrected above - it happens when the currency group separator is a whitespace.
0
- ago
#7
Good evening,

I just installed Wealth-Lab, I connected IBKR as the instructions indicate but I have a problem on the graphs. When I click « stream » I have this error displayed and Wealth-Lab closes (as if it does not support) Can anyone help me?

I want to execute orders and strategy from the chart
0
- ago
#8
What a way to take snapshots 😂 Here's how to do it easily:

https://www.howtogeek.com/226280/how-to-take-screenshots-in-windows-10/
0
Cone8
 ( 21.52% )
- ago
#9
Good job finding this discussion, but you can also find the reason for the error in in Posts #4 and #6 above.

Just to make sure, which instrument (symbol and market) caused this?

---
I've reported this error to IB, but it would help if you guys that are actually having the problem report it too. In your IB web account click Help > Secure Message Center > Compose > New Ticket > API > TWS API and use this text:

Subject:
IBApi Decoder Error

Body:
IBApi throws an unhandled exception when parsing streaming data that has trade values over 1000 when the currency group separator is a whitespace (Windows). Fix the IBApi so that this doesn't happen, please.

Account:
Select your account
0
- ago
#10
Sorry for the screenshot, I use my phone especially that the message is displayed for 2 seconds then closes WL. Now I get messages all over the place when I try to stream charts. I specify that I am in paper trading and that I do not subscribe to any data (maybe the reason?). However on my IB account the graphs work well. I tried the delayed data option. Am I the only case ?
if not at the moment, what advice would you give for 1h - 15m - 5m us stock data ?
0
Cone8
 ( 21.52% )
- ago
#11
You need to subscribe to get chart and streaming data through the API. Log in to your account at IB, go to Settings > Market Data Subscriptions . Subscribe to the markets you need data for.

For U.S. Stocks, for example, get the US Securities Snapshot and Futures Value Bundle.

And yes, I think you're the only case!
1
BiBi8
- ago
#12
An error appears after connecting to a Interactive Broker or creating dataset. Then the application closes. Error: Invalid String Format
0
- ago
#13
Not "Invalid String Format" but "Input string was not in a correct format". Merged your duplicate topic with this already existing one. Solution can be found in Cone's posts above.
0
BiBi8
- ago
#14
I must change machine's thousands separator? How can I do it? Please, write step by step instructions
0
- ago
#15
https://www.windowscentral.com/how-adjust-region-settings-windows-11

https://support.microsoft.com/en-us/office/change-the-windows-regional-settings-to-modify-the-appearance-of-some-data-types-edf41006-f6e2-4360-bc1b-30e9e8a54989
0
Cone8
 ( 21.52% )
- ago
#16
It shouldn't be required to do this, but there's an IBApi bug that isn't converting the string properly when the system's number grouping character is a whitespace. In the next set of WealthLab updates (mid July?), we updated to the "Latest" IBApi, which appears to have resolved the problem.
0
- ago
#17
but unfortunately I still get this error:
0
- ago
#18
I moved your post here again, please review Cone's troubleshooting suggestions first.
0
Cone8
 ( 21.52% )
- ago
#19
When I tested it with whitespace grouping after upgrading the IB API, it seemed to work. Maybe the test was flawed and I didn't hit the fail condition.

Nonetheless, the error is actually occurring in System.Decimal.Parse(), used by IB's API. I could try to change that, but it's hard to predict all the side effects. The "cure might be worse than the disease" (a phrase that reminds me of COVID vaccinations).

If this problem persists for you, I'm afraid the only way to avoid this is to start using a character like a comma or decimal point as your Window digit grouping symbol.

1
- ago
#20
The problem was solved after changing the decimal character.
Thank you Cône
1

Reply

Bookmark

Sort