MT5 trade disabled on the account

Causes, most likely first

1. You are logged into an investor password rather than the master password

The investor password grants read-only access — you can see everything and change nothing. This is the most common cause by far, and it is easy to do accidentally when setting up a new terminal. Log out and reconnect with the master password.

2. The account is unverified or restricted

Brokers restrict trading on accounts pending verification, with incomplete documentation, or flagged for review. Only the broker can lift it, and the Journal message will indicate a server-side rather than client-side restriction.

3. The account is read-only or archived

Dormant accounts, expired demos and accounts closed for inactivity all reject orders. Demo accounts frequently expire after a fixed period without warning.

4. Automated trading is blocked for this account type

Some contest and promotional accounts prohibit EAs. The rejection wording distinguishes client-side from server-side — server-side means no local setting will help.

Why this happens

The investor password case deserves special mention because it also appears during bot onboarding. Anyone configuring a bot to run on your behalf needs the master password; the investor password cannot place trades, and handing it over produces a system that appears to work and never trades.

That distinction is also a reasonable security question to ask any provider. A provider who asks for the investor password is asking for read-only access, which is safer but insufficient for trading.

If a manual trade on the same account is also rejected, the problem is definitively the account rather than the EA — which is a fast and conclusive test worth running first.