Error number 6 - page 32

New comment
 
Can these errors affect EA testing? <br / translate="no"> Just for some time now my Expert Advisor during tests (I am optimizing it from time to time, adjusting parameters to changes in the market) has started missing some trades. It has not closed positions and does not pull up stops and instead of a position reversal it simply opens the opposite position without closing the previous one. On the real account TradeDispatcher: trade context is busy.
But the tester has no connection with the server and issues commands and executes them. But some
Positions are not executed by the signal. Why?

Please post the complete code of the Expert Advisor. Surely they will help you to find errors immediately (if there are any).
 
So maybe don't wait for the release, but let those who are eager to try it out?

Yes, we'll try to post a separate build as a beta and let you know.
 
Эти ошибки могут влиять на тестирование советников?
Просто с некоторых пор мой советник на тестах (я его время от времени оптимизирую, подбираю параметры под изменения на рынке) Стал пропускать некоторые сделки. Не закрывает позы, не подтягивает стопы, а вместо переворотов просто открывает противоположную позу, без закрытия предыдущей. На реале тоже постоянно появляется ошибка TradeDispatcher: trade context is busy.
Но в тестере ведь нет соединения с сервером, он сам себе подает команды и их исполняет. Но некоторые
позы по сигналу тоже не исполняет. Почему?

Please post the complete code of the expert. Surely you will be helped to find errors immediately (if there are any).

Posted in the thread
TradeDispatcher: trade context is busy... What is it?
 
Here's another log. It's the latest build. Alas.


24.10.2005 23:18:32, Signal: sell
24.10.2005 23:18:32 Trying to sell, attempt 0

Ask: 1.19840000, StopLoss: 0.00500000, TakeProfit: 0.00000000
failed, error 6

24.10.2005 23:18:32 Trying to sell, attempt 1

Ask: 1.19840000, StopLoss: 0.00500000, TakeProfit: 0.00000000
failed, error 6

24.10.2005 23:18:32 Trying to sell, attempt 2

Ask: 1.19840000, StopLoss: 0.00500000, TakeProfit: 0.00000000
failed, error 6

24.10.2005 23:18:32 Trying to sell, attempt 3

Ask: 1.19840000, StopLoss: 0.00500000, TakeProfit: 0.00000000
failed, error 6

24.10.2005 23:20:22 Trying to sell, attempt 4

Ask: 1.19860000, StopLoss: 0.00500000, TakeProfit: 0.00000000
failed, error 6

24.10.2005 23:20:46 Trying to sell, attempt 5

Ask: 1.19860000, StopLoss: 0.00500000, TakeProfit: 0.00000000
failed, error 6

24.10.2005 23:20:46 Trying to sell, attempt 6

Ask: 1.19860000, StopLoss: 0.00500000, TakeProfit: 0.00000000
failed, error 6

24.10.2005 23:20:46 Trying to sell, attempt 7

Ask: 1.19860000, StopLoss: 0.00500000, TakeProfit: 0.00000000
failed, error 6

24.10.2005 23:20:46 Trying to sell, attempt 8

Ask: 1.19860000, StopLoss: 0.00500000, TakeProfit: 0.00000000
failed, error 6

24.10.2005 23:20:46 Trying to sell, attempt 9

Ask: 1.19860000, StopLoss: 0.00500000, TakeProfit: 0.00000000
failed, error 6
Friday sell error: 4050
1.19830000, 0.00500000, 0.00000000
sold open
 
Looked at Quark's post: no way!!! Looked at my own log: Solid old ticks (i.e. unsynchronisation). Alpari server. The MQ server seems to have passed away.
 
To say I'm fed up with Mistake #6 is just to keep quiet out loud... I have 4 MT4 Expert Advisors in each of 4 charts (actually 8, but half of them are not working, depending on the volatility).
In other words, it turns out that there are 16 active Expert Advisors in 4 programs. Here's just a situation - in each program ONE Expert Advisor at a time was to open positions. ALL 4 programs showed our beloved 6th error.
Eh... And they promised to improve it... And the build is already 184...
 
Is anything being done to resolve error number 6 or is the issue considered closed?
Got the first error number 6 on a new 184 bild.
 
Is anything being done to resolve error number 6 or is the issue considered closed? <br / translate="no"> Got the first error number 6 on the new 184 bild.

it means there was a communication problem. and it didn't depend on the terminal
 
Yes, nowadays 6 comes up exceptionally rarely - it's a sin to reproach the developers.
There may indeed be something wrong with the connection - not with the client, but with the broker and its server ;)
 
Something about bug number 6 gone from the "top 20" in the forum :) That's not right. Here's another observation.

Prehistory. I posted the code, with all checks. We check conditions at a specified time (each EA has its own time window within one hour) and open a position if it is good.

The history - a failure occurs at the moment of requesting an order, as a result we have two orders that were opened by Expert Advisor within a minute.

Here is the log:
2005.11.09 13:01:17 '142605': order is open : #2400577 sell 0.10 EURUSD at 1.1759 sl: 1.1819 tp: 0.0000
2005.11.09 13:01:17 '142605': request in process
2005.11.09 13:01:17 '142605': request was accepted by server
2005.11.09 13:01:16 '142605': instant order sell 0.10 EURUSD at 1.1759 sl: 1.1819 tp: 0.0000
2005.11.09 13:01:16 '142605': login (4.00, #2832F8DDD)
2005.11.09 13:00:50 TradeContext: ping error
2005.11.09 13:00:30 '142605': request was accepted by server
2005.11.09 13:00:23 '142605': instant order sell 0.10 EURUSD at 1.1760 sl: 1.1820 tp: 0.0000
2005.11.09 13:00:23 '142605': login (4.00, #2832F8DD)

Here is the list of positions:
(not shown, because the copy operation is still not there)

Here is the program-generated log (I already cited the code in this thread):
9.11.2005 11:0:15, Signal: sell
9.11.2005 11:0:15 Trying to sell, attempt 0
Ask: 1.17630000, StopLoss: 0.00600000, TakeProfit: 0.00000000 failed, error 6
9.11.2005 11:1:8 Trying to sell, attempt 1
Ask: 1.17620000, StopLoss: 0.00600000, TakeProfit: 0.00000000 successfull
sell opened

I will repeat - one position opened by log and log. In real life :) - two, with an interval of a minute.
1...2526272829303132
New comment