MT4 EA Troubleshooting: No Trades, Permissions and Logs
Separate absent signals, missing permissions and rejected orders. Follow this sequence and change one condition at a time.
Thomas · Reviewed: October 8, 2026
Start with these five checks
1. Are quotes updating?
Check the server and connection. Historical candles can remain visible while disconnected.
2. Does the account permit trading?
Investor access is generally read-only. Check login type, account and symbol permissions; never share passwords.
3. Are automation settings consistent?
Check terminal and EA trading permissions. Do not blindly enable DLL imports for unfamiliar programs.
4. Have the strategy conditions occurred?
No order does not necessarily mean failure: time, symbol, timeframe and filters may not meet the rules. Check logs.
5. Was the order rejected?
Record the actual code and time. 130 means invalid stops, 131 invalid volume, and 132 market closed. Investigate each separately; do not remove stops or increase size as a generic fix.
Read the full guides
MT4 Step-by-Step Tutorial: From Download and Installation to Placing Orders, Closing Positions, and EA Troubleshooting
A complete 20-chapter learning path covering account login, gold symbols, order types, stop loss and take profit, mobile app, EA installation, and common errors, with demo practice and operation checklists.
How to Troubleshoot EA Runtime Abnormalities: First Preserve MT4 Logs, Then Change Settings
Distinguish Experts from Journal, preserve the abnormal scene, verify triggers, permissions, and execution results, and avoid restarting or modifying parameters to cover up the real cause.
MT4 Can Show Quotes but Cannot Trade: First Check the Server and Read-Only Permissions
Distinguish between account number, server, master password, and investor password, verify real-time connection and trading conditions, and avoid mistaking read-only access or stale charts for an EA malfunction.
EA backtest curve looks good—first verify these test conditions
Distinguish modeling methods from real tick-by-tick data, record spread assumptions, parameter selection, and independent check intervals, so that EA test conclusions can be reviewed.
What to prepare before asking for help
Provide the terminal version, redacted symbol and timeframe, event time, error code and relevant logs. Hide names, account numbers, passwords and API keys. Use a demo environment for checks and review existing positions separately.