0

I've been using MQL4 for a couple of days now, but recently I've been getting the error message: 

(133) trade is disabled

when performing an order.

From reading the different forums, I understand the common belief is that I have to talk to my broker to enable Expert Advisors, but trading DID work for me (on and off) until now!

Has anyone else encountered this error - NOT relating to enable EA from the server?

Stanislav Kralin
  • 11,070
  • 4
  • 35
  • 58
Amir Keren
  • 201
  • 2
  • 7

5 Answers5

0

No need to talk to your Broker

MetaTrader4 Server side has nothing to do with this.

Check your localhost Terminal settings

There might be several reasons, why the EA was working ( "DID work" as you post it ) and still you get an error.

An MT4.Terminal.Profile change can also cause this to happen.

An MT4.Terminal.LogAnotherUser change can also cause this to happen.

An MT4.Terminal.Graph change of { Symbol | Period } can also cause this to happen.

Check Tools > Options > Expert Advisor [TAB] for active values in respective check-boxes for all the above.

Check, if you are correctly logged-on to a correct ( not canceled ) trading account.

Check, if your connection is green / working

Check, if your trading Symbol has active market ( open trading hours )

If still in troubles, send a few OrderSend()-s with PrintScreen-s and copy responses from Log-File & post here.

user3666197
  • 1
  • 6
  • 50
  • 92
  • Thanks! I have been messing around with the graphs (and time periods), that might have something to do with it... I'll look into it :) – Amir Keren Aug 28 '14 at 10:43
  • 2
    @user3666197 - Sometimes you do need to talk to your broker. In my case the symbol I was trying to trade was being expired, so they only allowed closing trades on that symbol - not allowing new ones to be opened. – dalcam Dec 10 '15 at 18:21
0

Maybe it cause of abnormal looping by your Expert Advisor. You may see at journal tab, if it created too many orders or modify orders at a moment of time, server could significantly overloaded and caused lags and malfunctions. Therefore, broker should disable it.

If so, you should fix your EA first, then let your broker know that as consideration for asking them to reenable your account.

Denny Muhammad
  • 1
  • 3
0

Just had this problem using a Broker-configured account, with hedging enabled.

I had been running on DEMO-practice, with no problems, but when I switched to the LIVE-account, error 133 happened.

It was because the trade server that it was linked in was the GMT-5 one, and only the GMT+2 server is allowed for a hedging account.

Server was changed, started working no problem.

user3666197
  • 1
  • 6
  • 50
  • 92
Neil
  • 1
0

Check with your broker that the symbol hasn't been disabled. They do this sometimes when they introduce a new symbols to replace old ones.

A disabled symbol will still show up in MT4 to allow users to close trades in the symbol ( but you get the above mentioned error, if you try to open a new order )

user3666197
  • 1
  • 6
  • 50
  • 92
dalcam
  • 1,027
  • 11
  • 28
0

I encountered that same error code when I tried to modify the Stoploss of an already closed order.

seasick
  • 473
  • 1
  • 4
  • 15