
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
Reinstalled . new log
JP 0 19:54:02.772 Startup MetaTester 5 x64 build 1100 (20 Mar 2015)
QD 0 19:54:02.782 Server MetaTester 5 started on 127.0.0.1:3000
JO 0 19:54:02.783 Startup initialization finished
EM 0 19:54:03.209 127.0.0.1 login (build 1100)
MJ 0 19:54:03.220 Network 38680 bytes of group info loaded
FM 0 19:54:03.220 Network 1490 bytes of tester parameters loaded
GK 0 19:54:03.220 Network 2244 bytes of input parameters loaded
DQ 0 19:54:03.222 Network 947 bytes of symbols list loaded
LG 0 19:54:03.223 Tester expert file added: Experts\Examples\Moving Average\Moving Average.ex5 30450 bytes loaded
NH 0 19:54:03.234 Tester initial deposit 10000.00 RUR, leverage 1:100
LN 0 19:54:03.238 Tester successfully initialized
DG 0 19:54:03.238 Network 52 Kb of total initialization data received
LL 0 19:54:03.238 Tester AMD A8-5557M APU with Radeon HD Graphics , 5581 MB
HF 0 19:54:03.271 Symbols USDJPY: symbol to be synchronized
GR 0 19:54:03.271 Symbols USDJPY: symbol synchronized, 3384 bytes of symbol info received
OD 0 19:54:03.272 History USDJPY: history synchronization started
NI 0 19:54:03.570 History USDJPY: load 1012 Kb of history data to synchronize
NO 0 19:54:03.570 History USDJPY: history synchronized from 2014.01.01 to 2015.04.27
OK 0 19:54:03.744 History USDJPY,M5: contains 34870 bars of beginning data from 2014.01.01 00:00 to 2015.03.31 23:55
CK 0 19:54:03.744 History USDJPY,M5: history cache reserved for estimated 98948 bars
DS 0 19:54:03.751 History USDJPY,M5: history begins from 2014.01.01 00:00
LE 0 19:54:03.752 Tester USDJPY,M5 (BCS5-Real): 1 minutes OHLC ticks generating
ME 0 19:54:03.753 Tester USDJPY,M5: testing of Experts\Examples\Moving Average\Moving Average.ex5 from 2015.04.01 00:00 to 2015.04.27 00:00 started with inputs:
JF 0 19:54:03.753 Tester MaximumRisk=0.02
OM 0 19:54:03.753 Tester DecreaseFactor=3.00
EI 0 19:54:03.753 Tester MovingPeriod=12
DH 0 19:54:03.753 Tester MovingShift=6
ER 0 19:54:03.772 Symbols USDRUR: symbol to be synchronized
NI 0 19:54:03.773 Symbols USDRUR: symbol synchronized, 3384 bytes of symbol info received
CQ 0 19:54:03.774 History USDRUR: history synchronization started
EH 3 19:54:03.777 History no data synchronized, 27 bytes read
GQ 2 19:54:03.777 Symbols symbol USDRUR history synchronization error
DS 2 19:54:03.777 Symbols no prices for symbol USDRUR
FL 2 19:54:03.777 Symbols no prices for symbol USDRUR
PE 2 19:54:03.777 Symbols no prices for symbol USDRUR
RN 2 19:54:03.777 Symbols no prices for symbol USDRUR
PH 0 19:54:03.777 Tester final balance 10000.00
CM 0 19:54:03.777 Tester OnTester result 0
QS 0 19:54:03.783 Tester USDJPY,M5: 115 ticks (7 bars) generated within 217 ms (total bars in history 34877, total time 561 ms)
JS 0 19:54:03.783 Tester 277 Mb memory used
RK 0 19:54:03.783 Tester log file "C:\Users\peace\AppData\Roaming\MetaQuotes\Tester\912C23C26F3BF014083DEC3B1590DC80\Agent-127.0.0.1-3000\logs\20150428.log" written
EQ 0 19:54:09.912 tester tester agent shutdown started
PI 0 19:54:09.913 Tester shutdown tester machine
RK 0 19:54:09.914 Tester tester agent shutdown finished
Server who? What do you mean - brokerage, brokerage quotes?
Open a demo account on the MetaQotes-Demo server
+
Are you testing the standard MoovingEveraging?
I tried all standard ones... MetaQotes-Demo works on that
I use broker quotes.
moneystrategy:
Тогда что-то с котировками у них (у брокера)
they told me to write to mql support and I haven't heard back from them yet)
If you want to test on broker quotes so badly, then open a new demo account there and try it. If it was on 4, then I would advise to download Dukas quotes by tickstory light and import into the terminal with the conditions of the trading account on which the owls will work (using the script). I do not know how to do it for 5ks.
The thing is that even on demo does not open deals with owls)
another log on another EA
Well, then write to the developer of the owl - it means that the problem is in the EA, either glitches or bans
i don't think all EAs are glitched :) I don't think all EAs are glitchy
:) Then write to a broker.
It all comes down to the same thing, you have to write to someone :)