Critical Error since Update !

To add comments, please log in or register
Skullnick
53
Skullnick  

Hi all,

Since the update pushed yesterday, it is impossible to launch backtests ! I'm currently getting "global initialization failed" and "global initialization critical error".

Help !

Sk

Sergey Golubev
Moderator
106126
Sergey Golubev  
write to the service desk (the link is on your profile).
Skullnick
53
Skullnick  
Done ! Are you getting the same error ?
Sergey Golubev
Moderator
106126
Sergey Golubev  
Skullnick:
Done ! Are you getting the same error ?

Not - no one reported ... it was some issue with something (it was discussed on rus thread) but it was because of the EA which had a bug.

Skullnick
53
Skullnick  
My laptop has the old version (build 18 Jan) and it works fine. :-/
Sergey Golubev
Moderator
106126
Sergey Golubev  
Skullnick:
My laptop has the old version (build 18 Jan) and it works fine. :-/

So, the service desk may help - they may reply with fixing, or they may issue the new build with fix.
But be ready to send log files to them and all the information (Windows version, and more).

Skullnick
53
Skullnick  
Is it possible to revert to an old version meanwhile ? I cannot backtest any strategy because of this.
Anthony Garot
1864
Anthony Garot  
Skullnick:
Is it possible to revert to an old version meanwhile ? I cannot backtest any strategy because of this.

You can simply copy the three files of a previous build over the current ones.

Every time you restart MT5, you must say "no" or "cancel" or whatever it is when they ask you to update.

If you didn't keep a copy around, here's MT5 build 1755 for 64 bit.

https://mega.nz/#F!vhIABIiD!cQfWn-rAKwC8Y9F8k9B-9Q

Anthony Garot
1864
Anthony Garot  
FYI, build 1816 is working for me. It appears they removed the Optimizer Results tab while the optimizer is running, but that's the only oddity I have found thus far.
Skullnick
53
Skullnick  

Hi,

Thank you Anthony ! Yup everything works fine now, except my market watch disappeared with all of my custom symbols, and yet they are in  C:\Users\USERNAME\AppData\Roaming\MetaQuotes\Terminal\XXXXXXXXXXXXXXXXXXXXXXXX\bases\Custom\history folder. Another problem to solve I guess, but in the meantime I can work and debug on the broker symbols.

Regarding the build 1816, just to clarify, my EA havily relies on pointer functions (delegates) and the new build completely messes this up. For instance, I have a StopLossSignal Class that needs a delegate for the desired exit price. I can give examples if you want further explanations.

Regards,

sk

To add comments, please log in or register