invalid book transaction - page 4
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
No, restarting the terminal helps :(
And if you run two terminals on the same PC, do they both get this error at the same time?
If I run two terminals on the same PC, do they both get this error at the same time?
I already have 2 terminals on one PC, the errors are NOT occurring at the same time
I already have 2 terminals on the same PC, the errors are NOT "popping up" in sync
That's very strange then, it looks like an external factor... Have you tried another PC, for the sake of the experiment? I can check on my own, so collect statistics on the frequency of these problems, maybe we can understand what affects it.
I also have this problem periodically (Just2Trade broker). It seems to be some kind of failure on the MT5 server, as Transaq's twin server terminals are fine at this time.
I also have this problem periodically (Just2Trade broker). It seems to be some kind of failure on MT5 server, because in the terminals of the paired Transaq server at this time everything is normal.
If it were the server, the error would have occurred on all computers connected to this server at once, which, judging by the messages, does not happen.
Forum on trading, automated trading systems and trading strategies testing
invalid book transaction
prostotrader, 2018.07.19 19:12
I already have 2 terminals on the same PC, the errors are "popping up" NOT in sync
I can repeat the previous message again.
There is no point. The event occurred, but the data transmission error did not cancel it. I am surprised that MQ has not yet fixed the error. It will be fixed very quickly. It will most likely be an event cancellation event :)
By the way, it's missing from the event alphabet.
No, restarting the terminal helps :(
There was a similar thing with ticks too. When after clearing, error 4403 would start popping up for no reason. Developers have fixed it.
Write to them again/remind them that the error persists. Add the minimum required code to playback, make it clear that it is on low-liquid characters that the error occurs and remind, remind, remind about this bug...
There was a similar thing with the ticks. When after clearing, error 4403 would start popping up for no reason. The developers fixed it.
Write to them again/remind them that the error persists. Add the minimum required code to reproduce, specify that it is on the low-liquid characters of the error and remind, remind, remind about this bug...
Everything you wrote is already done.
Opened, Started: 2018.07.19 14:32, #2109819
Added by
NOT just on low liquid, but on all symbols
Everything you wrote has already been done.
Opened, Started: 2018.07.19 14:32, #2109819
Added by
NOT just on low liquid, but on all symbols
Have the developers responded to you? See how it was for me:
As you can see, it took a month before my application was noticed. This, of course, is not normal, but problems can be solved. That is, do not think that you write once and you will get a quick response. There are, unfortunately, a lot of problems in MT.
Did the developers answer you? Look how it was for me:
As you can see, it took a month before my request was noticed. This is certainly not normal, but problems can be solved. That is, don't think that you write once and get a quick response. There are a lot of problems in MT, unfortunately.
I do not think ... :) I do!