Page 1 of 1

1.7.4 + 950 = testing stopped at ... because product is demo

Posted: Thu Feb 11, 2016 7:56 am
by masterpae
I am receiveing this error when I try to test any of the MQL5 payed EAs, no exception.

I have deleted both tickstory and MT4 and freshly reinstalled them and the same error apears

I have tryed fresh installs on another 2 computers running windows 7 and windows 8.1 with no success, the same error apears on all payed EA's that I try to test.

Is anybody able to run test on payed EAs with a 1.7.4 + MT4950 setup?

Here is a log that shows up on MT4:

"2016.02.11 09:54:12.375 EURUSD,M30: 0 tick events (5202 bars, 9922116 bar states) processed in 0:00:00.000 (total time 0:00:00.063)
2016.02.11 09:54:12.375 2015.10.01 00:00 AlgoTradeSoft Innovative EA: testing stopped at 2011.04.07 16:24 because product is demo
2016.02.11 09:54:12.375 2015.10.01 00:00 AlgoTradeSoft Innovative EA inputs: Expert_Id=8888; Spread_MaxAverage=2; Spread_FastBackTest=1; Lot_Type=1; Lot_FixedSize=0.1; Lot_Risk=1; Lot_Max=0; Lot_PersonalPercent=0; StopLoss_FixedSize=1.5; TakeProfit_FixedSize=150; BreakEven_After=3; BreakEven_To=1; TrailingStop_Size=1; TrailingStop_Step=0.8; TrailingStop_CorrectSL=1; TrailingStop_UseRealOPAndSL=1; TrailingStop_TrailingMode=0; TrailingStop_TimeScale=1; TrailingStop_VolatilityScale=3; TrailingStop_VolumeScale=3; TrailingStop_Change
2016.02.11 09:54:12.315 TestGenerator: symbol EURUSD period 30 model 0 from 2015.09.01 to 2016.02.01
2016.02.11 09:54:12.315 TestGenerator: file "C:\Users\\AppData\Roaming\MetaQuotes\Terminal\9E1F6CECD14337B09256BF3B5C3F7923\tester\history\EURUSD30_0.fxt" is read-only
"

Is anything else in the log that seems off?

I would really appreciate any pointers on how to solve this situation, Tickstory is useless for me in this state.

Re: 1.7.4 + 950 = testing stopped at ... because product is

Posted: Thu Feb 11, 2016 11:09 am
by tickstory
Hi Masterpae,

This is not a Tickstory error. The error is being generated by your EA and you will need to contact the author (presumably AlgoTradeSoft, as indicated by the first part of the message) for them to resolve it. If you are using a demo copy of their EA, then this would be the reason for the message.

Regards.

Re: 1.7.4 + 950 = testing stopped at ... because product is

Posted: Thu Feb 11, 2016 3:57 pm
by masterpae
I have tryed about 35 payed EA's from MQL5, none works. Only the free EA's don't give me this error.

Please tell me ONE payed EA that you can test with 1.7.4 + MT4 950?!

Just let me know if with the above set up there is a payed EA that you can test... please name the EA's that you can test...

Re: 1.7.4 + 950 = testing stopped at ... because product is

Posted: Thu Feb 11, 2016 8:54 pm
by tickstory
Hi Masterpae,

Please understand that Tickstory that is not restricting you from testing at all. The authors of these EA applications are preventing you from testing until you have paid for the EA. I believe this is a standard protection mechanism across all the paid EAs in the MQL shop - they only allow you to perform limited tests on the demo version. They are effectively letting you try something but not giving you the full functionality until you pay. Once you have purchased the EA, you will be able to test with no restriction. We have no way of changing this as we do not sell nor write these EAs. Testing with or without Tickstory will give you the same error message.

If you are looking for some EAs to test with freely, the MQL5 website does provide some EAs here:

https://www.mql5.com/en/code/mt4/experts

Hope this helps.

Re: 1.7.4 + 950 = testing stopped at ... because product is

Posted: Thu Feb 11, 2016 9:43 pm
by masterpae
tickstory wrote:The authors of these EAs are preventing you from testing until you have paid for the EA.
Ok so lets take it step by step:

Lets take this EA as a exemple: https://www.mql5.com/en/market/product/4365
In past version of TickStory and MT4 I have tested this EA hundreds of times, I have optimezed this EA for DAYS. With excelent result.

Now the same EA (even the same version of EA), tested on 1.7.4 + 950 gives me this error.

SO the same exact EA, with the same unchanged version(EA version), untouched since I was able to test it with past Tickstory&MT4 versions, NOW ITS UNTESTABLE?!
And under this situation your explanation is that the EA author its blocking me to test this EA? How could he, he didn't updated that EA since long before when I was able to test it.


Now, if I take a fresh MT4 950 and install the demo of the above EA and I test it simply with the MT4, well IT WORKS, no "testing stopped" error, so if the author is blocking me to test this EA, why when I test it in a fresh clean MT4 the testing IS WORKING?!


Now when I point Tickstory to this above mentioned MT4 fresh clean install, and I try to test the EA with Tickstory active I get this amasing error...


So if the author is not blocking me to test the EA as shown above, can you please have a look on your product and try to provide me with a usefull functioning software?!

At least try the above scenario yourself, becouse from your last comment I have a strong feeling you are pretty out of touch with actual useing your software for real MT4 testing.
tickstory wrote:I believe this is a standard protection mechanism across all the paid EAs in the MQL shop - they only allow you to perform limited tests on the demo version.
Where do you have this information from?!
When this change happend? (becouse no more the 2-3 months ago for sure there was no such thing)
And in case its true then your application its completly useless... why would anybody buy Tickstory if you can't test payed EA's before buying them?!

So in the end, please try the above scenario yourself, give it a try to help me find a solution as clearely this error is showing up on Strategy Testing ONLY when Tickstory is active.

Thank you.

Re: 1.7.4 + 950 = testing stopped at ... because product is

Posted: Thu Feb 11, 2016 10:25 pm
by tickstory
Hi Masterpae,

We are well aware of the functionality that we put into our software and know we put in no such restrictions nor introduced any new functionality that would cause this. Tickstory's function is to export tick-quality data and allow you to use it in the Strategy Tester. All messages thereafter are generated by the Strategy Tester and the running EA.

Please note that we do not provide support for EAs or Metatrader, however we have taken the liberty to do a few basic searches:
Dr.Trader:
I have same warning, all demo Expert Advisors can't be tested after 30.nov.2015. I think this warning appeared after updating MT4 to version 920.
It's a new limitation. I think it's something like it will stop testing data that is within a week of current date
https://www.mql5.com/en/forum/67944
All MQL5 programs purchased through the Market are protected from unauthorized use.
https://www.mql5.com/en/articles/385
After the update I can no longer Back test market demo EA. Journal writes, EA: testing stopped at 2016.01.01 23:00 because product is demo
when i test for 2016 only, which shown error on journal "testing stopped at 2016.01.01 23:00 because product is demo"
at the same time from 2015 to 2016 which works for me.
https://www.mql5.com/en/forum/71129

It appears MT4 has introduced various new limitations on how you can back-test a demo product. An option might be to roll-back your MT4 Version, otherwise you will need to work with these new limitations that have been introduced by Metatrader. Either way, we unfortunately cannot change this behaviour on our side.

Thanks.

Re: 1.7.4 + 950 = testing stopped at ... because product is

Posted: Thu Feb 11, 2016 11:07 pm
by masterpae
Fresh MT4 950 + EA demo install = WORKING Strategy Testing... (with broker automaticly downloaded data history)

Fresh MT4 950 + EA demo install + Tickstory = NOT WORKING Strategy Testing...


1. Have you tryed yourself the scenarion I have told you about?
2. Are you able to use Tickstory in any meaningful way?
3. If Strategy Testing works in a fresh MT4 install and stops working when Tickstory is added to the mix how can you say "Either way, there is no way on our side to address this problem"?!?! (I am not asking you to modify MT4 binary, but at least try to investigate whats happening, not just throw "must be a new future" nonsense pressumptions)
tickstory wrote:An option might be to roll-back your MT4 Version
This kind of comment make me think you are not actualy in touch with MT4 Strategy Testing. At this moment if your roll-back MT4 version and try to install ANY kind of EA, demo or not, your will be faced with license error, in case you try to be smart and install the EA, demo or not, while still in 950 before rolling back, you will face an "loading EA blabla" error when you try to start the testing(in the rolled back version). SO there is no way in hell you can roll back from 950 and still be able to test ANYTHING.
tickstory wrote:otherwise you will need to work with these new limitations that have been introduced by Metatrader
Are you serious? This is not a limitation, this is a total and final distruction of any use for your software. You do realize that Tickstory is nothing without the ability to actualy TEST thinks in MT4?!

Re: 1.7.4 + 950 = testing stopped at ... because product is

Posted: Fri Feb 12, 2016 6:19 am
by tickstory
Attached is a copy of the results we have acquired from running the strategy you mentioned on MT4 Build 950 & Tickstory v1.7.4. The EA did not raise any of the "demo" errors and tested an entire year of Tickstory data.
To answer your question "why is it reporting that it's a demo version on my machine?", we have come full circle since we are not privy to how MT4 and the EA author has decided to protect their code. As you mentioned, it was working before and now it's not. In the absence of any changes, we can only assume there is some in-built mechanism to protect the EA from use under certain conditions. There are many ways to implement a restriction without the author having to update their EA. A simple example of time-limiting would be "when EA has been installed > 30 days ago" or "Only allow testing on data between 2010-2012" (as the users in one of the above-mentioned posts seem to be discussing) or "only permit 100k ticks/executions in one run" (meaning you could test a larger range of 1-minute data than tick data) or even a "contact home" protection which can just about implement any type of restriction. **These are examples only** Only the author themselves know what these restrictions are and this is why we advise to contact the author directly. Please do not insist that we continue to speculate on the answer when the author clearly is in the best position to resolve this issue for you. If all is streamlined, this may just be a matter of them hitting the "reset trial" button.

Thanks.