Quantower Problems and Fixes
Quantower is built around connections. You can attach several brokers and data vendors at once, and almost every panel is tied to one of them. Most problems come from a connection being down, a panel pointing at the wrong connection, or a workspace that was never saved. Here are the common ones.
A connection fails or will not stay connected
Symptom: A broker or data connection shows as disconnected, or connects and then drops, and the panels using it stop updating.
Cause: Wrong credentials for that specific connection, the wrong environment selected, the provider's maintenance window, or security software blocking the platform.
- Open the connections area and check which connections are active, since Quantower can hold several and only the failing one matters.
- Re-enter the credentials for that connection, remembering they belong to the broker or data vendor and not to Quantower itself.
- Confirm you selected the correct environment for that provider, as live and demo servers are separate and the credentials usually are too.
- Check whether the failure happens at the same time daily, which would point at the provider's scheduled maintenance rather than a fault.
- Allow the platform through your firewall and any third-party security software, then try again.
- If it still fails, contact the provider whose name is on the connection, because they own the login and can see the rejection.
Full walkthrough, how to verify it worked, and how to stop it happening again →A panel is showing the wrong data or trading the wrong account
Symptom: Prices differ between two panels showing the same instrument, or an order goes to an account you did not intend.
Cause: Quantower supports several connections at once, and each panel is bound to one of them. Two panels can show the same instrument from different providers.
- Check which connection each panel is using, since the binding is per panel rather than global.
- Set the panel to the connection you intend, then confirm the instrument reloads from that provider.
- Check the account selector on any order entry panel separately, because the connection and the account are two different choices.
- Expect small price differences between providers on the same instrument, as each has its own feed, and treat a large difference as a sign one is stale.
- Before trading, confirm the order entry panel names the account and connection you expect.
- If you run both a live and a demo connection, keep them on visibly different workspaces so they cannot be confused.
Full walkthrough, how to verify it worked, and how to stop it happening again →A symbol is missing or cannot be found
Symptom: The symbol search returns nothing, or the instrument appears without data.
Cause: Symbols come from the connected provider, so a missing symbol usually means the wrong connection is selected, your account is not entitled to it, or the provider names it differently.
- Check which connection the symbol search is using, as it will only show instruments from that provider.
- Search by the product's root name rather than a full contract code, then pick the contract from the results.
- Confirm your account with that provider is entitled to both the data and the trading permission for the instrument.
- If the instrument is a futures contract, check you are looking at the current contract month rather than an expired one.
- If the symbol appears but has no data, treat it as a data entitlement question for that exchange and take it to your provider.
- Do not copy symbol codes from guides written for other platforms, since the naming belongs to the provider.
Full walkthrough, how to verify it worked, and how to stop it happening again →No live data, or data is delayed
Symptom: A connection is up but prices are blank, frozen or clearly lagging.
Cause: Real-time exchange data is a paid entitlement held with your provider, and it is separate from platform access. Some connections also require a subscription arranged through Quantower or the vendor.
- Confirm with the provider on that connection that you hold a current real-time data subscription for the exchange concerned.
- Check your professional or non-professional classification, since it affects the fee and can suspend access when it changes.
- Check whether depth of market is a separate subscription from top-of-book, because the depth panel will look empty without it.
- Check whether the connection itself requires a paid module or licence, as some integrations are not included by default.
- After any subscription change, disconnect and reconnect so the platform picks up the new entitlement.
- If the provider confirms everything is active, ask them to check the entitlement while you are connected rather than reinstalling.
Full walkthrough, how to verify it worked, and how to stop it happening again →An indicator does not appear on the chart
Symptom: You add an indicator and nothing is drawn, or it disappears when you change something.
Cause: The indicator is drawing outside the visible price range, it is on a hidden or collapsed sub-panel, or its inputs mean it has nothing to plot on the current data.
- Reset the chart's scale, or switch the price axis back to automatic scaling, since an indicator plotting far from price will push everything off screen.
- Check whether the indicator belongs on a separate sub-panel below the chart, and confirm that panel is visible and not collapsed to nothing.
- Open the indicator's settings and confirm the inputs are sensible for the timeframe you are on, as a very long period on a short chart may have too little data to plot.
- Confirm the chart has enough loaded history for the indicator's calculation, because many need a warm-up period before the first value appears.
- Check the indicator's line colours and thickness, as a line the same colour as the background is invisible rather than absent.
- Remove and re-add the indicator once you have corrected the settings.
Full walkthrough, how to verify it worked, and how to stop it happening again →A custom or third-party indicator will not load
Symptom: An indicator you installed does not appear in the list, or reports an error when the platform loads it.
Cause: The file was not placed where the platform looks for it, it was built for a different version, or the platform has not been restarted since it was added.
- Follow the vendor's installation instructions exactly, since the correct location for custom code is specific to the platform and not somewhere you should guess.
- Restart Quantower after adding any custom indicator, because it loads them at startup.
- Check whether the vendor's build matches the version of Quantower you are running, as an indicator built against an older release may not load.
- Look at whatever the platform reports when it fails to load an indicator, and pass that text to the vendor rather than paraphrasing it.
- Remove any older copy of the same indicator before adding a new one, so two versions do not conflict.
- If it is your own code, build it before expecting it to appear, and fix any build errors first.
Full walkthrough, how to verify it worked, and how to stop it happening again →Your workspace or layout is gone
Symptom: The platform opens with a default layout, or your carefully arranged panels are missing after a crash or an update.
Cause: The workspace was not saved, the platform did not shut down cleanly, or you are opening a different workspace from the one you built.
- Check whether the workspace you want still exists in the workspace list, since it is more often unselected than deleted.
- Save the workspace explicitly after arranging it, rather than relying on the platform to capture it on exit.
- Close the platform properly rather than terminating it, because an unclean shutdown can lose changes made since the last save.
- Keep separate named workspaces for different purposes, so an experiment cannot damage your trading layout.
- After a platform update, check your workspace opens correctly before the session rather than during it.
- If a workspace is genuinely gone, rebuild it once and save it immediately, rather than repeatedly hoping it returns.
Full walkthrough, how to verify it worked, and how to stop it happening again →A panel is missing or will not dock where you want
Symptom: You cannot find a panel you had open, or it will not sit where you drag it.
Cause: The panel was closed rather than hidden, it is on a different workspace or a different screen, or the layout has become tangled.
- Open a fresh copy of the panel from the platform's panel list rather than hunting for the old one.
- Check whether the panel is on a second monitor that is currently disconnected, since a window placed off screen will not appear.
- Bind the new panel to the correct connection and instrument, because a fresh panel will not inherit the old one's settings.
- If the layout is badly tangled, load a clean workspace and rebuild rather than fighting the docking.
- Save the workspace once the arrangement is right, so you do not repeat the work.
Full walkthrough, how to verify it worked, and how to stop it happening again →Orders rejected
Symptom: An order is refused, with a message that originates from the broker rather than the platform.
Cause: Insufficient margin, an account limit, an order type the broker does not support, or an instrument your account is not permitted to trade.
- Read the rejection message, since the wording comes from the broker and usually names the actual reason.
- Check the margin required for that contract, and remember futures margin is often much higher outside the intraday session.
- Check the order type you used is supported by that broker through this platform, because integrations do not always support everything the broker offers.
- Check whether your account has a maximum position size or other risk limit, which is common on evaluation and funded accounts.
- Confirm the market is open for that contract and the account is approved for that product.
- If the message is unclear, take it to the broker on that connection, since only they can see why their system refused it.
Full walkthrough, how to verify it worked, and how to stop it happening again →Missing history or gaps in the chart
Symptom: A chart is short of history or has gaps, or history differs between two connections.
Cause: How much history you get is determined by the connected provider, not by the platform, and some connections supply live data only.
- Check how much history the chart is set to load, since a low setting looks identical to missing data.
- Check whether the connection you are using supplies historical data at all, as some order-routing integrations do not.
- If you have more than one connection, compare the same instrument on each, because one may have far deeper history.
- Check whether the gap corresponds to a session break, a holiday or a period the provider does not cover.
- Reload the chart so it requests the range again, and give it time on a long history request.
- For tick-based or volume-based charts, expect much less history than for time-based ones.
Full walkthrough, how to verify it worked, and how to stop it happening again →The platform will not start, or crashes on launch
Symptom: Quantower closes immediately, hangs on the loading screen, or fails to open at all.
Cause: A missing or outdated runtime, an incomplete update, graphics driver problems, or a corrupted workspace being loaded at startup.
- Make sure your operating system and graphics drivers are up to date, as chart rendering depends on both.
- Install any runtime the platform's installer or documentation says it requires, and let the installer complete without interruption.
- Reinstall the platform from a freshly downloaded installer in case the previous download or update was incomplete.
- Temporarily allow the platform through security software, which can block a newly updated executable.
- If it starts but crashes when loading your usual workspace, start with a clean workspace to establish whether the workspace is the problem.
- Keep a copy of any error the platform or the operating system reports, as it is the fastest route to an answer from support.
Full walkthrough, how to verify it worked, and how to stop it happening again →Your trading account does not appear after connecting
Symptom: The connection succeeds but no account is listed, or the balance shown does not match your broker.
Cause: You have connected to the wrong environment, the credentials belong to a different account, or the account is not enabled for platform access by the broker.
- Confirm you connected to the environment the account lives in, since live and demo are separate and an account exists in only one.
- Confirm the credentials belong to the trading account rather than to a client portal or a separate data login.
- Check with the broker that the account is enabled for access through this platform, as some accounts must be explicitly permitted.
- If the account is with a funding firm, check that the firm allows this platform and has provisioned your account for it.
- Compare the balance shown against the broker's own portal, and treat any difference as a sign you are looking at a different account.
- If the account still does not appear, ask the broker to check while you are connected rather than reconnecting repeatedly.
Full walkthrough, how to verify it worked, and how to stop it happening again →Trade with clarity once MetaTrader is running
Market Structure Pro gives one clear TRADE or NO-TRADE verdict on any MT5 chart, with confidence, grade and a plain-English reason. Free 7-day trial, no card.
Start free trialStill stuck? Some issues are specific to your broker or app version, so their support desk can confirm server names, account status and outages. If you use MetaTrader 5, our
install guide and
free tools may also help.
