Tickstory

I re-installed new mt4, updated TS Lite 1.5, reduced period of data and I got these errors:
2014.05.02 08:11:48.411 TestGenerator: file "C:\Users\A\AppData\Roaming\MetaQuotes\Terminal\2185510BE0A2DC8815CEF56A1AF8B592\tester\history\EURUSD240_0.fxt" cannot open [13, Permission denied]
2014.05.02 08:11:48.411 TestGenerator: file "C:\Users\A\AppData\Roaming\MetaQuotes\Terminal\2185510BE0A2DC8815CEF56A1AF8B592\tester\history\EURUSD240_0.fxt" is read-only.

I unchecked "read-only" checkbox in the properties of the files, but no change.

Hi Sam123,

Did you launch MT4 by using the Tickstory Launcher (i.e. by pressing F8 while in Tickstory)?

Thanks.

Of course I did.

Hi Sam123,

What build of MT4 are using? I assume that there is only 1 instance of the terminal.exe running? Can you try to unmark the files from being read-only and see if this helps?

Thanks.

Build 646(30.4.2014)
It seems it updated 2 days ago from 625.

I unchecked read-only check box.
No cahnge.
Still the same problem.

I see that after a few moments, the account is no longer in "overwrite prevention / fixed spread" mode.
It is in a regular mode like any account.
Is that ok?

Hi Sam,

Build646 appears to have broken the launcher. You should be getting an error from TIckstory reporting this.
Until an updated launcher is available you will need to attempt to revert back to an earlier build.

Regards.
(P.S. This thread will be moved to a new post since it doesn't relate to the original topic).

You're guessing for solutions.
you don't solve the problems.

Hi Sam,

We are trying to work through a solution with the information you have given us. Your original question related to back-test ranges (which I believe has been resolved) and now it relates to another error you are getting in MT4.
In each case, we are following through a set of known issues that our users have experienced. Given that there are numerous variables to identifying a generic "permission denied error" we need to ask questions to rule out possible causes.

Thanks.

FYI - Further tests have been done on the launcher for Build 646 and it appears to still be working. If you require further assistance, please ensure you post comprehensive details about what you are doing and the versions of software you are using. This will help us identify the issue sooner and eliminate iterative posts.

Thanks.