Contest - moneygrows (Od moneygrows)
| Zisk : | -76.14% |
| Čerpanie | 90.54% |
| Pipy: | 8.9 |
| Obchodníci | 49 |
| Vyhrané: |
|
| Prehrané: |
|
| Typ: | Demo |
| Páka: | 1:500 |
| Obchodovanie: | Neznáme |
Contest - moneygrows Diskusia
Feb 21, 2011 at 12:26
859 Zobrazení
7 Replies
Členom od Jan 14, 2011
35 príspevkov
Mar 03, 2011 at 09:31
great, cant close my NZDCHF! Thanks a lot FxOpen!
Členom od Mar 02, 2011
25 príspevkov
Mar 03, 2011 at 10:10
Hello, please, provide your contest account number and the ticket of the trade you can't close.
What error do you see when you are unable to close?
What error do you see when you are unable to close?
Členom od Jan 14, 2011
35 príspevkov
Mar 03, 2011 at 10:50
Wow, that was fast response, im impressed FXOpen! Sent you the details hannafxopen :)
Členom od Mar 02, 2011
25 príspevkov
Mar 03, 2011 at 10:53
Was it 'trade context busy' by any chance?
The error message “trade context is busy” is displayed when the client is trying to open/close/modify several orders at the same time.
Any operation (opening/closing or modifying an order) is actually a request (command) sent to the trading server via the terminal Meta Trader 4. Meta Trader 4 is programmed in a way, that does not allow to send several requests (commands) at the same time. You have to wait before one request is executed, then make the next request. If you make the second command and the first command has not been completed, you will get the error #146: 'trade context is busy' and the second request will fail.
This often happens when you have several EAs enabled on different charts (or timeframes) and 2 or more EAs are trying to open/close/modify a trade at the same time.
This is an issue with the Meta Trader Terminal, and it is not related to FXOpen trading terms and conditions or any problems with FXOpen trading servers. Please, refer to https://articles.mql4.com/141 for more deatils and possible solutions.
The error message “trade context is busy” is displayed when the client is trying to open/close/modify several orders at the same time.
Any operation (opening/closing or modifying an order) is actually a request (command) sent to the trading server via the terminal Meta Trader 4. Meta Trader 4 is programmed in a way, that does not allow to send several requests (commands) at the same time. You have to wait before one request is executed, then make the next request. If you make the second command and the first command has not been completed, you will get the error #146: 'trade context is busy' and the second request will fail.
This often happens when you have several EAs enabled on different charts (or timeframes) and 2 or more EAs are trying to open/close/modify a trade at the same time.
This is an issue with the Meta Trader Terminal, and it is not related to FXOpen trading terms and conditions or any problems with FXOpen trading servers. Please, refer to https://articles.mql4.com/141 for more deatils and possible solutions.
Členom od May 19, 2010
19 príspevkov
Mar 03, 2011 at 13:45
Hello ,
Unable to delete the pending trade so what to do ,, very bad terminal
Unable to delete the pending trade so what to do ,, very bad terminal
Členom od Mar 02, 2011
25 príspevkov
Mar 03, 2011 at 13:46
hi, do you see any error messages? What is the ticket of the trade?
Členom od Mar 02, 2011
25 príspevkov
Mar 03, 2011 at 13:51
yogeshgr8 posted:Try re-scanning servers (click th connection bars in the right bottom corner of your MT4)
Hello ,
Unable to delete the pending trade so what to do ,, very bad terminal
Členom od Jan 14, 2011
35 príspevkov
Mar 03, 2011 at 14:03
well, i dont use ea, only custom indicators. In fact it happened to me few times again on my EU just now. I noticed it only happens during major move. Oh well, no point in rectifying anything. My account is totally wiped now. Guess im out of the game now. Good luck to everyone else.
*Komerčné použitie a spam nebudú tolerované a môžu viesť k zrušeniu účtu.
Tip: Uverejnením adresy URL obrázku /služby YouTube sa automaticky vloží do vášho príspevku!
Tip: Zadajte znak @, aby ste automaticky vyplnili meno používateľa, ktorý sa zúčastňuje tejto diskusie.
