EA Errors

Start with the full message, not only its number. Read the Experts and Journal entries around the failed MT5 request. If you use MetaTrader 4, open its separate error reference below; numbers can mean different things on the two platforms.

If TradingView fires but no corresponding message reaches PineConnector, start with Missing signals. This page covers terminal and trade-request errors after that stage.

Find your error

Platform	Error
MT5	4752 — EA trading disabled · 4756 — request failed
MT4 or MT5	Zero divide

On Edge: select the affected instance in Portal → Edge → Experts / Journal using the hosted log walkthrough. Match its account and event time before applying a fix. On self-hosting: see Experts, Journal, or saved log files.

MetaTrader 5

4752

MetaTrader 5

EA trading is disabled

ERR_TRADE_DISABLED: Expert Advisors are not permitted to trade.

Start here

Read the full error in the affected terminal’s logs. Choose the Edge or self-hosted check below.

1. On Edge

   Select the affected instance in Portal → Edge → Experts / Journal. Inspect Edge → instance → EA Settings and Connections → account → Terminal info, then contact Support with the error and event time. Changing Algo Trading in a local terminal does not change Edge.

2. On a self-hosted terminal

   Confirm that Algo Trading is enabled in MetaTrader and allowed in the PineConnector EA’s properties. Both the terminal toolbar setting and the EA’s own permission must allow the action.

3. Confirm the result before retrying

   Check the broker account for any existing order or position first. After the cause is corrected, use a controlled demo test and compare Experts, Journal and the resulting order.

Use Edge logs and Support for hosted permission issues. The hosted settings procedure covers editable EA inputs, not local MT5 permission controls. Editing those inputs does not establish that hosted trading permissions are enabled.

4756

MetaTrader 5

Trade request could not be sent

ERR_TRADE_SEND_FAILED is a general request failure. The accompanying message identifies the next check.

Start here

Read the full Experts and Journal message at the same timestamp. Match its wording to a case below.

Match the message beside 4756

Message	Check first	Next action
Message: Unsupported filling mode	Check first: The symbol’s permitted order-filling policy	Next action: Check the broker/symbol specification. Self-hosted older EAs: use Broker Set B only if it exists in your version and matches the supported configuration. Edge: send the hosted log detail to Support. Change the hosted Broker Set only when Support asks you to; changing a local Broker Set does not change Edge.
Message: No prices	Check first: Symbol selection, connection and incoming quotes	Next action: Self-hosting: show the exact symbol in Market Watch and confirm a current quote during its trading session. Edge: check the same account’s symbol and session through your broker’s supported MT5 mobile, web or desktop terminal; inspect hosted Experts/Journal and contact Support if hosted quotes remain unavailable. Do not keep resending against an unavailable quote.
Message: Invalid request	Check first: Exact symbol and the full request parameters	Next action: Compare the message with the broker’s symbol and supported order type. A matching symbol alone does not prove the rest of the request is valid.
Message: Trade disabled	Check first: Whether the account and symbol permit this trade	Next action: Confirm the symbol, session and broker restrictions. For terminal/EA permissions, use the Edge or self-hosted 4752 branch above.
Message: Invalid expiration	Check first: The pending order’s expiration policy	Next action: Check the broker’s supported expiration settings. Self-hosted older EAs: confirm version support before using Broker Set C. Edge: share the pending request and hosted logs with Support. Change the hosted Broker Set only when Support asks you to.
Message: Invalid volume	Check first: Minimum, maximum and volume step	Next action: Check requested lots against the symbol’s contract specification. Explicit volume fields name their units; legacy risk= depends on Volume Type. On Edge, inspect Edge → instance → EA Settings; use the review and apply procedure for changes, which restart the terminal and interrupt signal execution. Ask Support if the setting or its applied state is unclear.
Message: Invalid stops	Check first: Target units, correct side and minimum distance	Next action: Follow the stops checklist.
Message: Requote	Check first: The current quote and execution mode	Next action: Check the broker’s returned detail. Confirm whether any order was placed before retrying, then investigate repeated requotes with your broker/support on demo.
Message: Invalid price	Check first: Price validity for that symbol and order	Next action: Check the allowed price increment, direction and distance of the pending entry, stop loss and take profit.

These cases correspond to separate MetaTrader trade-server return details. 4756 alone does not select one fix.

Check stops and prices

Use this checklist for MT5 Invalid stops/Invalid price or MT4 130:

1. Confirm units. A legacy sl= or tp= value follows the EA’s Target Type. A price such as 1.08000 must not be interpreted as a pip distance. Review the exact parameter in Syntax.
2. Check the correct side. For an open buy position, SL must be below your broker’s current Bid and TP above it; for an open sell, SL must be above the current Ask and TP below it. When modifying a stop, the original entry price alone is not the side check. For a pending order, SL and TP must fit the pending entry price and direction.
3. Check minimum distances. On self-hosting, open the symbol specification and inspect its Stops level, shown in points. On Edge, obtain the same account’s MT5 specification from your broker or Support if it is not exposed in your broker app. Use the point size and the documented PineConnector pip convention for that instrument; do not treat a displayed point count as the same number of pips.
4. Check price increments. The broker must accept the requested price step and decimal precision.
5. Check pending entries separately. The entry price and expiration can be invalid even when SL and TP are acceptable.

See MetaTrader’s MT5 stop and freeze-level rules and MT4 trade limits for the broker-level constraints.

TradingView and your broker can quote different prices

A price level copied from TradingView may be too close to, or on the wrong side of, your broker’s current quote. Distance-based targets can avoid that specific mismatch when they suit your strategy; they still must satisfy the broker’s minimum distances.

MetaTrader 4 errorsOpen this reference only if your terminal is MT4.

These checks apply to MetaTrader 4. Choose the matching error below; the shared stops checklist and Zero divide guidance remain available outside this section.

MT4 error	MT4 error
130 — invalid stops	4017 — DLL calls disabled
131 — invalid volume	4051 — invalid parameter
132 — market closed	4106 — unknown symbol
133 — trade disabled	4109 — trading not allowed
134 — insufficient margin	4202 — object missing

130

MetaTrader 4

Invalid stops

ERR_INVALID_STOPS: a stop or pending-entry level is invalid for the request.

Start here

Compare the message’s target units with the EA’s Target Type and pending-entry setting.

1. Inspect the symbol specification

   Check minimum stop distance, price increments and the current broker quote.

2. Review the actual levels

   Use the stops-and-prices checklist above. Correct the parameter or level, then repeat a controlled demo test.

131

MetaTrader 4

Invalid trade volume

ERR_INVALID_TRADE_VOLUME: the requested lot size does not meet the broker’s rules.

Start here

Open the symbol specification and compare minimum volume, maximum volume and volume step with the requested lots.

1. Check how the EA calculated the size

   Confirm your Volume Type and the value supplied in the message. Decimal places alone do not establish a valid volume step.

132

MetaTrader 4

Market closed

ERR_MARKET_CLOSED: the symbol is outside its trading session.

Start here

Check that symbol’s trading hours on your broker’s server, including holidays and session breaks.

1. Wait for a valid session

   Send a new test only when the symbol is open and quotes are available.

133

MetaTrader 4

Trading disabled

ERR_TRADE_DISABLED: trading is not available for this account or symbol.

Start here

Confirm the exact symbol and whether your broker permits trading it on this account.

1. Check the local setup

   Show the symbol in the Symbols list and confirm the EA’s live-trading permission is enabled.

2. Separate a broker restriction from an EA issue

   On a demo account, check whether an equivalent manual trade is permitted. Ask the broker about a restriction if manual trading is blocked too.

134

MetaTrader 4

Not enough margin

ERR_NOT_ENOUGH_MONEY: the account does not have enough available margin for the request.

Start here

Read the required and available margin in the Experts output.

1. Review the requested size

   Confirm Volume Type before reducing a risk/volume value. Existing positions and broker margin rules affect what is available.

2. Escalate an apparent mismatch

   If the log shows sufficient available margin but the broker rejects the trade, send the full request and broker response to support.

4017

MetaTrader 4

DLL calls are not allowed

ERR_DLL_CALL_NOT_ALLOWED: the required DLL permission is disabled.

Start here

Review Allow DLL imports in both MetaTrader Options and the PineConnector EA’s properties.

1. Check your environment

   Your self-hosted computer or VPS must support the PineConnector EA’s required DLL usage. Follow the MT4 setup guide for its current files and permissions.

4051

MetaTrader 4

Invalid function parameter

ERR_INVALID_FUNCTION_PARAMETER_VALUE: a function received an invalid value.

Start here

Read the full error and compare your message with the required fields for that command.

1. Check entry sizing fields

   A missing risk= is one case identified by the older entry-message guide. Follow the syntax supported by your EA version; this error number does not prove that a missing risk field is the cause.

2. Keep the failing example

   If the message matches the reference, send the exact request and log to support instead of adding guessed parameters.

4106

MetaTrader 4

Unknown symbol

ERR_UNKNOWN_SYMBOL: MetaTrader does not recognise the requested symbol.

Start here

Copy the name exactly from your broker’s Symbols list, including capitalisation and any suffix.

1. Check any mapping

   Confirm that TradingView placeholders or Symbol Mapping resolve to that exact name. EURUSD and eurusd are not interchangeable in the documented syntax.

4109

MetaTrader 4

Trading is not allowed

ERR_TRADE_NOT_ALLOWED: automated trading permission is disabled.

Start here

Enable automated trading in Tools → Options → Expert Advisors, then check Allow live trading in the EA’s Common tab.

1. Confirm the EA is ready

   Check the AutoTrading toolbar state and the EA’s chart status. Use a demo request to verify the permission change.

4202

MetaTrader 4

Chart object does not exist

ERR_OBJECT_DOES_NOT_EXIST: a chart object expected by the program was not found.

Start here

Save the full error and the surrounding Experts output.

1. Send the context to support

   Include the EA version, event time, Signal ID where available, and what you were doing when the error appeared. Do not assume changing trade size will fix a chart-object error.

For another MT4 code, use the official MQL4 error list. Confirm the terminal platform before applying its checks.

Zero divide

Zero divide

MetaTrader 4 or MetaTrader 5

A calculation attempted division by zero

The program could not complete a calculation. The location and surrounding log are needed to investigate the cause.

Start here

Record the complete message, including any line/column numbers shown in brackets, and your PineConnector EA version.

1. Preserve the request and environment

   Keep the Signal ID, symbol, relevant EA settings and Experts/Journal lines around the event.

2. Report the issue

   Send that evidence to PineConnector Support. Do not repeatedly resend a live request while its outcome is uncertain.

Still stuck, or using Edge?

For a self-hosted setup, collect the local Experts and Journal logs. For an Edge connection, select the affected instance in Portal → Edge → Experts / Journal and compare its connection and signal details. Contact support if the required detail is missing or the hosted issue remains unresolved. Desktop permission steps apply to a terminal you manage yourself.

Send PineConnector Support the platform/EA version, event time, relevant Signal ID, exact error and expected outcome. Share account details privately only when needed, and omit passwords and signal secrets from screenshots.

For an MT5 code not listed here, use the official MQL5 runtime error list.