'corrupted history detected' error for EUR/USD and GBP/USD

New comment
 

When first downloading data for EUR/USD and GBP/USD for backtesting the download appeared to start at 49%. It then produced these errors in the log and did not complete the backtest:

2018.12.23 10:33:34.195    Core 1    EURUSD 2018.02.27 03:23:00: corrupted history detected (s:-2100596776, o:121546, h:+0, l:-0, c:0 -- tv:303, rv:0)
2018.12.23 10:33:34.195    Core 1    EURUSD 2018.02.27, bad container found, must be resynchronized
2018.12.23 10:33:34.195    Core 1    stopped on 0% of testing interval with error '20 EURUSD'


How can i resynchronize data for these pairs? I tried deleting the folders in 'History' but that didn't help.

 
 remove and reinstall your terminal
 

Thanks for the response, i reinstalled and now i get a new error:

'2018.12.27 16:36:56.552    Tester    EURUSD: preliminary downloading of M1 history stopped due to timeout'

Still does the same jump to 49% on these two pairs. o.0 Broker is Pepperstone.

Same error with GBP/USD:

"
2018.12.27 16:39:32.195    Core 1    GBPUSD 2018.02.27 03:29:00: corrupted history detected (s:-1822441771, o:2, h:+293724, l:-1, c:1814 -- tv:179, rv:0)
2018.12.27 16:39:32.195    Core 1    GBPUSD 2018.02.27, bad container found, must be resynchronized
2018.12.27 16:39:32.195    Core 1    stopped on 0% of testing interval with error '20 GBPUSD'
"


 

How has this software been around for 7 years and nobody has resolved this error yet? Tried reinstalling Metatrader 5 again:

"
2019.01.07 20:50:01.827    Core 1    EURUSD 2018.02.27 03:23:00: corrupted history detected (s:-2100596776, o:121546, h:+0, l:-0, c:0 -- tv:303, rv:0)
2019.01.07 20:50:01.827    Core 1    EURUSD 2018.02.27, bad container found, must be resynchronized
2019.01.07 20:50:01.827    Core 1    stopped on 0% of testing interval with error '20 EURUSD'

"

Heeeeelp please. :'(
 
Same problem. Have you ever received an answer from Pepperstone? Or were you able to solve the problem?
 
Eamonn OReilly: How has this software been around for 7 years and nobody has resolved this error yet? Tried reinstalling Metatrader 5 again:

Why do you think that bad broker's data has anything to do with the terminal, or that reinstalling the terminal could in any way, fix it?

Do you think that putting a new engine in your car, will fix a flat tire?

New comment
Reason: