Tom'sEa WPFX LIVE (による TomsEaWPFXlive)
そのユーザーはこのシステムを削除しました。
Tom'sEa WPFX LIVE 討論
Mar 26, 2012 at 15:06
craneliu posted:
the TOMs EA Server down again!
please let me know again after the server is recovered
I know!!!! This is rediculous! AGAIN!
Have emailed and chated with Tech support.... all I can get out of them is they are working on it and 'hope' they will have the problem fixed in a few hours.
$1997... I expect better!
Mar 26, 2012 at 15:18
(編集済みのMar 26, 2012 at 15:19)
flopps posted:
craneliu posted:
the TOMs EA Server down again!
please let me know again after the server is recovered
I know!!!! This is rediculous! AGAIN!
Have emailed and chated with Tech support.... all I can get out of them is they are working on it and 'hope' they will have the problem fixed in a few hours.
$1997... I expect better!
To paraphrase Oscar Wilde, 'To lose the service once may be regarded as a misfortune; to lose it twice looks like carelessness...'
You have to ask what's going on over there?! Business-critical systems in mainstream operations are rarely down like this in-flight. Has Dustin et al really invested enough? With the right people/company? Why is there no working failover system (one that's been tested without using us as guinea pigs)?
Over £3k tied up in trades. Pleased I'm not at work today :)
Let's hope they fix this issue properly this time.
Mar 26, 2012 at 15:22
One other thing...
As (I suspect) a great number of us will be running this on a VPS and probably not monitoring it hourly (after all, that was the key selling point!), an early warning system from the TEA mob (e-mail/SMS) to let us know there's an issue wouldn't hurt. Like flopps said, '$1997... I expect better!'
As (I suspect) a great number of us will be running this on a VPS and probably not monitoring it hourly (after all, that was the key selling point!), an early warning system from the TEA mob (e-mail/SMS) to let us know there's an issue wouldn't hurt. Like flopps said, '$1997... I expect better!'
Mar 26, 2012 at 15:26
@PocketGuy
Couldn't have said it better myself. Almost mid-night here in Hong Kong and now I have to say up and manually manage my open trades.
Couldn't have said it better myself. Almost mid-night here in Hong Kong and now I have to say up and manually manage my open trades.
Oct 05, 2011からメンバー
60 投稿
Mar 26, 2012 at 15:46
Here is where we are currently. There are no server issues at this point. We have spent tons of cash on infrastructure and backups. We are currently using Infusionsoft as our customer CRM and data base. This is also one of the best in the business and we pay close to 30k a year for it. The issue we are having is Infusionsoft can only handle so many API calls per day and they are saying that the limit has been reached. We are working with them to get this threshold raised and in the mean time we are going to do a mass authenticate so we can all authenticate again (including myslef). Once we get it back up we will work to find a permanent solution since we have obviously outgrown them. I would appreciate it if when these types of things occur peoples first assumption is we have not or are not willing to spend the money on proper infrastructure because that is not at all the issue. I appreciate your patience as we work to get this resolved.
Mar 26, 2012 at 16:08
Appreciate the focus will always be on handling the crisis, Dustin, but a simple, reactive system to inform everyone of the issues would deal with this (and help us to manage our resultant risk in the process). Leaving Support to indicate directly or via third parties that the 'server is down' (again!) will inevitably lead to these things being bandied about, especially when we're working with live, at-risk funds. I'd respectfully suggest that the way to handle false assumptions is to minimise the probability of them occuring :)
GlobalProfit posted:
Here is where we are currently. There are no server issues at this point. We have spent tons of cash on infrastructure and backups. We are currently using Infusionsoft as our customer CRM and data base. This is also one of the best in the business and we pay close to 30k a year for it. The issue we are having is Infusionsoft can only handle so many API calls per day and they are saying that the limit has been reached. We are working with them to get this threshold raised and in the mean time we are going to do a mass authenticate so we can all authenticate again (including myslef). Once we get it back up we will work to find a permanent solution since we have obviously outgrown them. I would appreciate it if when these types of things occur peoples first assumption is we have not or are not willing to spend the money on proper infrastructure because that is not at all the issue. I appreciate your patience as we work to get this resolved.
As to 'outgrowing' Infusionsoft... If the money's being invested wisely (and I don't doubt a lot of investment has been, and is being made), what happened to the roadmap, with early warning indicators for precisely this scenario? Why does this seem reactive, at least, from the outside?
Speaking purely for myself, I'm onboard for the long haul and simply want to ensure and be assured that TEA works flawlessly and seamlessly for many years to come. So, perhaps you'll understand these observations are designed to help by flushing up obvious questions, not to criticise. As I said earlier, in the absence of pre-emptive information...
For my own part, thanks for dropping by with feedback - it surely helps. Hope you resolve this soon.
Oct 05, 2011からメンバー
60 投稿
Mar 26, 2012 at 16:17
what happened to the roadmap, with early warning indicators for precisely this scenario? Why does this seem reactive, at least, from the outside?
Unfortunately infusionsoft does not have an early warning system and the way they count API calls we are finding was not explained clearly. We were initially told that we get 10k calls a day. We have since found out that we have to earn those calls at a rate of 2 per second that we are not pulling and its capped at 10k a day. So once you drop to zero its a vicious loop and it becomes impossible to catch up.
Mar 26, 2012 at 16:27
GlobalProfit posted:
what happened to the roadmap, with early warning indicators for precisely this scenario? Why does this seem reactive, at least, from the outside?
Unfortunately infusionsoft does not have an early warning system and the way they count API calls we are finding was not explained clearly. We were initially told that we get 10k calls a day. We have since found out that we have to earn those calls at a rate of 2 per second that we are not pulling and its capped at 10k a day. So once you drop to zero its a vicious loop and it becomes impossible to catch up.
Dustin.... thank you for the update. I have just managed to get my copy of the TEA to authenticate and activate. However I look forward to an email from you stating that everything is back to normal and the problem has been fully resolved.
Sep 24, 2009からメンバー
19 投稿
Mar 26, 2012 at 16:28
Hi,
I tend to agree with Pocketguy. We appreciate Dustin and his team action to resolve the issue and we are here for the long haul.
I would have appreciate if subscribers would have received a 'heads up' email from Toms team to alert, explain the situation and highlight action plan instead of seeing the issues appearing in this forum. Keeping us, the customers, of the situation of the situation and any actions that we need to take would be great to see.
Thanks.
I tend to agree with Pocketguy. We appreciate Dustin and his team action to resolve the issue and we are here for the long haul.
I would have appreciate if subscribers would have received a 'heads up' email from Toms team to alert, explain the situation and highlight action plan instead of seeing the issues appearing in this forum. Keeping us, the customers, of the situation of the situation and any actions that we need to take would be great to see.
Thanks.
Oct 05, 2011からメンバー
60 投稿
Mar 26, 2012 at 17:57
craneliu posted:
Dustin, thank you!
please delete this authenticated process which caused problem several times. As the client, I do not want to see same problem happened again and again.
I could not sleep (live in Asia) today until your system recover to normal.
Its not really as easy as deleting it. If we did that then the system would not work at all and you would really be upset with us. We have decided to get another dedicated server that will serve as a backup to the infusionsoft system so that we are not only backing up our systems but also our vendors systems. In the mean time everything should be back to normal at this point regarding the use of the EA. I want to be clear that this only affected the EA users not the users using the Mirror trading platform.
I would have appreciate if subscribers would have received a 'heads up' email from Toms team to alert, explain the situation and highlight action plan instead of seeing the issues appearing in this forum. Keeping us, the customers, of the situation of the situation and any actions that we need to take would be great to see.
The issue was not brought to my attention until mid morning and my first priority is getting the system back online or at a minimum finding out why it went down and then notifying clients. That being said, before sending an email that says ' the system is down' I wanted to find out why it was down and once I had an answer I immediately made a post here and shortly after got an email out.
I truly strive to make this the best EA out there and will do what we can to keep issues like this from coming up however at times, especially when you rely on several systems and some of which being out of our control these types of things will come up. Keep an eye on your inbox for updates as we continue to push forward to improve our delivery systems as well as those that we are working with.
Mar 26, 2012 at 19:46
Metatrader 4 has been updated recently, latest build is 4.18 - this build contains bug that causes malfunction in all EA's and most of the indicators.
If you have build 4.16 or less - do not autoupdate the platform. If you've already updated one, than contact your broker and ask them for older version in order to rollback this update.
Taking into account amount of people affected by this I am sure that metaquotes will fix everything soon, but for us - it's better to stay away from this update for now
If you have build 4.16 or less - do not autoupdate the platform. If you've already updated one, than contact your broker and ask them for older version in order to rollback this update.
Taking into account amount of people affected by this I am sure that metaquotes will fix everything soon, but for us - it's better to stay away from this update for now
forex_trader_53345
Nov 13, 2011からメンバー
53 投稿
Mar 26, 2012 at 22:09
drsong123 posted:
I updated mt4 version 418 without knowing the bug situation several days ago. Now today I got email from my vps company to suspend my vps due to 'port scan' activities. I am wondering whether it is related to the update.
ss
I had this problem yesterday morning, killed my EA's and trade management platform as the DLL calls in 418 are broken. I use several different brokers, and experienced the 'update' on the weekend. Foolishly, I did not backup mt MT4 folders for each of the broker platforms. And many of the brokers have an install file that simply contacts a server to download the latest version 418.
Lesson learnt: never update MT4 without first backing up - it's a 2 second job.
The fix: if you can find a terminal.exe older than 418 (as I did) - rename the terminal.exe in your MT4 folder to terminal_old.exe and replace with the older version. This has fixed the problem (I found a 409 version of terminal.exe) and will wait for the fix from MetaTrader.
This cost me about 3 hours of panic break-fixing yesterday, but as I said, lesson learnt: if it ain't broke, don't fix it!!!
Mar 27, 2012 at 16:31
Basically port scanning means that your PC sends out signals to remote hosts in order to find opened ports, this scheme is usually used by hackers that's willing to get access to someone's private information.. Looks like metaquotes managed to make great hacking tool from standard MT4...
drsong123 posted:
I updated mt4 version 418 without knowing the bug situation several days ago. Now today I got email from my vps company to suspend my vps due to 'port scan' activities. I am wondering whether it is related to the update.
ss
DOWNGRADE INSTRUCTIONS
Downgrade:
#1 Contact your broker and ask them to give you older version of MT4 installer (4.16 or less will be good) in case they don’t have the installer for one or another reason they should at least have “terminal.exe” file.
*******!!!!! IMPORTANT - ASK BROKERS SUPPORT ABOUT INSTALLER TYPE – SOME OF BRAND NEW METAQUOTES INSTALLERS MIGHT WIPE OUT MT4 SETTINGS. BE EXTREMELY CAREFULL! MAKE SURE THAT YOU REMEMBER YOUR LOGIN DETAILS SUCH AS ACC #, SERVER NAME AND PWD!!!!!!. ASK BROKER ABOUT BEST WAY TO DOWNGRADE THE PLATFORM***********
#2 Download installer or single terminal.exe and save it somewhere on your PC
#3 Close all brokers platform
#4 Click on your broker MT4 with right mouse -> Properties. In first window click on “Find target”
This will open up folder of your MT4.
#5 In case you’ve got terminal.exe file simply copy-paste it into this folder. Click “Ok” when it ask whether to replace file or not. After this start MT4 go to Help -> About and checkup the version. It should be downgraded
#6 return to step #4 and look at the top of the folder – up there you should be able to see patch, place where your platform is stored. For example - C:\Program Files (x86)\FXDD - MetaTrader 4
Run the installer, and choose same folder, click “ok” to confirm file overwrite. Once the process is finished – start your MT4 and go to Help -> About to check version. All that’s 4.16 and less is good.
----------------------------------------------------------------------------------------------
Mar 29, 2012 at 11:06
MetaQuotes says that the new update will be ready next week.
Here is on more guide of how to downgrade 418 to 416 build - https://pipburner.com/metatrader-build-418-bug-alarm-how-to-switch-back-to-previous-version/
Regards,
MR
Here is on more guide of how to downgrade 418 to 416 build - https://pipburner.com/metatrader-build-418-bug-alarm-how-to-switch-back-to-previous-version/
Regards,
MR
Apr 02, 2012 at 16:27
craneliu posted:
any similar myfxbook for elemental trader. it'd better to have similar discussion post like TOMs EA here.
For now we do not have one.. we can possibly make some sort of quiz among of the clients and determine whether it's needed or not.. but I guess it's better to address those kind of suggestions to Dustin.
As for the new version - it's ready, it's been tested right now, it will be send out to the people till the end of the day, so far everything seems to be functioning as expected
