Skip to content
FMX EPOS
Download
Help Centre home

Database and continuity troubleshooting

In Remote mode, the remote database is where business data is kept permanently. While it is unavailable, FMX EPOS can queue eligible billing writes and send them in order once the database answers again. These checks are for a manager or administrator; cashiers should leave the till as it is and call one.

A till that is already signed in shows the warning banner Database offline (“Sales are kept on this till.”) while the database is away, then Syncing … local writes until its saved work has reached the database. An action may also be refused with a message about the database, a page may show Database Connection Unavailable (“EPOS cannot reach the database right now. Check the network connection, then try again.”), and the sign-in page says so too.

  1. Note the exact message and the time.
  2. Check whether every terminal is affected. If only one is, check that terminal’s network and database settings.
  3. If Back Office is already open on a terminal, check the Database and Continuity cards in Back Office → Diagnostics. A new Back Office sign-in does not work until the database answers.
  4. Use only the offline actions FMX EPOS offers. If an action says it needs the remote database, stop and do not guess.
  5. Do not sign out of the other tills or restart them. While the database is away, the sign-in page says “The database is unavailable or emergency bills are waiting to sync. Only the emergency terminal can sign in offline.” A PIN entered on any other till is refused with “Cannot connect to the database. Check the connection and sign in again.”
  6. Do not change the storage mode or create another database to make the message go away. To find out what is wrong and what fits, use Recover Connection.
  7. If the database is on this PC and FMX EPOS installed it, Recover Connection says so. Otherwise fix the database server or the network connection. A changed database password, or a database that has been renamed or removed, also looks like an outage to FMX EPOS, so check those as well.
  8. Leave the terminal running while the queued writes are sent.
  9. On each terminal that worked offline, watch Pending Writes on the Diagnostics Database card. The Terminals card at the bottom of Diagnostics, and the one on the Database page, show every terminal’s pending writes in one list.

Illustration, not a screenshot. The real screen can differ with the theme or version.

While the database is down, an action that needs it is refused with a message that says so, for example “Coupons cannot be checked while the database is offline. Record the payment without a coupon or wait for the connection.” Kitchen tickets and labels for a queued order wait until the database reconnects, and the order’s full order number shows Pending Sync until the order reaches the database.

Once the database is back, some actions still wait until this terminal’s queued writes have reached it. Most messages name the action and end “Waiting for N queued writes to reach the database.”, for example “Coupons cannot be checked. Waiting for 3 queued writes to reach the database.” This applies to coupons, points and member benefits on any sale, kitchen and label printing for a queued order, a refund of an order whose save or payment is still queued, and a membership fee refund. An order refund says “Waiting for queued writes to reach the database. No refund has been started.”, and a membership fee refund says only “Waiting for 3 queued writes to reach the database.”

X and Z reports need the remote database. A Z report is also refused while this terminal has queued or held writes, while the period has an unknown card result or an unrecorded card refund, or while another online terminal has unconfirmed writes; the message names the terminal. If another terminal is offline, the till shows Run Z Report? with “… is offline. Its unsent data will not be in this Z. Continue?” Select Run Z Report only if you accept that.

  • Pending Writes on the Diagnostics Database card counts every write this terminal still holds, including those held for review. Writes that are not held clear by themselves once the database answers.
  • Review Writes counts the writes that are held.

Held writes are listed under Local Writes Needing Review in Payment Review. A write is held when the database refuses it for a reason other than a lost connection, such as a data error or two tills changing the same record at once; the related writes queued behind it are held too (“Waiting for an earlier update to be reviewed.”). A write marked Review is tried again by itself after waits of 1, 5 and 15 minutes following its failed attempts, while the database is reachable and no earlier held write blocks it; writes waiting for an earlier update carry on once that update is resolved. Some errors need staff or support to act. Check the reason shown before using Reconcile. Other orders keep synchronising. The list appears only on the terminal holding those writes.

To deal with a write needing review:

  1. On the terminal that holds it, open Back Office → Orders → Payment Review. The till’s Cash & Card → Payment Review lists the same writes with the same buttons.
  2. Read the Reason column. The Operation column names an order’s save, payment or refund by the order, for example Order Payment · #12 · £12.50 · Card, and other writes by their type. Expand Recorded Details to see the saved record. If you cannot tell which order, customer or payment it belongs to, send a screenshot to support.
  3. Check in FMX EPOS what the permanent record should be.
  4. Fix the cause, then select Retry Database Write. Retrying never sends another request to Clover. If the write stays in the list, it was not written: read the Reason again.
  5. Use Reconcile only as a last resort (see the warning below).

Illustration, not a screenshot. The real screen can differ with the theme or version.

When a till cannot reach its database, Recover Connection works out why and offers what fits. It is in the desktop app only, while the database does not answer and the terminal is not paused for maintenance. Select it on the till’s sign-in page or on the Database Connection Unavailable page, on each till that cannot connect.

What Is Wrong says where the database is and what FMX EPOS found. What To Do lists the choices, with the likely fix first, marked Recommended. Return to Sign In changes nothing.

The page says Choices
The MySQL service on this PC has stopped Start MySQL, Reinstall MySQL, Use Another Database
MySQL on this PC is running but does not let the till in Reinstall MySQL, Enter New Connection Details, Use Another Database
MySQL on this PC was removed, or only part of it is there Reinstall MySQL, Use Another Database
Its databases are gone Use Another Database
The database is on another computer and does not answer Enter New Connection Details, Use Another Database

Windows asks for permission, then the service starts and the till returns to the sign-in page.

FMX EPOS downloads MySQL 8.4 (about 270 MB, so this PC needs an internet connection) and puts it back onto the databases on this PC. Windows asks for permission first. Sales, menu and settings stay as they were.

Use this when the database server is working but has moved, or its login has changed. You need the username and password of an active Back Office administrator of the store.

  1. Select Enter New Connection Details, then Continue. The New Connection Details page opens.
  2. Enter the Database Server IP Address and Port. If the database login or password has changed, enter the new ones in Database Login and Database Password; leave Database Login blank to keep this till’s login. Then enter a Back Office administrator’s username and password in Administrator Username and Password. These are the Back Office sign-in details, not the database login.
  3. Select Check Database.
  4. FMX EPOS says which shop the database belongs to and asks “Connect this till to it? Its waiting sales and emergency bills then go there.” Select Connect This Till, or Cancel.
  5. The till returns to the sign-in page. Its queued writes are then sent to the database at the new address.

Illustration, not a screenshot. The real screen can differ with the theme or version.

If the till is not registered on the database at that address, the check is refused with “This till is not registered on the database at that address, so it may be another shop’s. Check the address.” If the database was retired by a migration, move the terminal to the new database from Administrator Recovery instead.

This leaves the shop’s database, so use it only when that database has gone or you mean to start again. Select Use Another Database, Continue, then Leave This Database. The data stays in that database, and first-run setup can connect the till to it again. First-run setup then opens, where you can choose a new MySQL database on this PC, Local SQLite, another database server or another till’s database. Back returns here until another database is chosen.

This choice is not available while this till holds sales or emergency bills saved during the outage. They belong to that database, so get them there first.

During a remote database outage, only the Emergency Terminal can keep restaurant table bills. An administrator chooses it in advance in Database → Terminals; see Choose the Emergency Terminal. With none chosen, Diagnostics shows a warning. That terminal must have been online after it was chosen, so that it holds a saved copy of the restaurant set-up. Other terminals can still carry on with the till actions that work offline, but they cannot take table bills: they show “The database is offline. Only the emergency terminal with a saved configuration can do this until it is back.”

While the Emergency Terminal takes these bills, it is in emergency mode. Its order panel shows EMERGENCY · NEW BILLS ONLY, and the table plan says “Emergency Mode: only new bills opened on this terminal are shown. Existing remote bills and table occupancy cannot be checked.” Cash counts and X and Z reports are not available in emergency mode. Coupons and membership benefits cannot be checked while the database is offline.

Bills and orders taken in emergency mode print their kitchen tickets, but they do not appear on the kitchen screen, either during the outage or after they are uploaded. The kitchen works from the paper tickets for them.

A scheduled order taken on the Emergency Terminal during the outage goes to the kitchen by the store’s Kitchen Release rule. The Integration Host cannot see the order yet, so the Emergency Terminal releases it itself. An order set to Manual waits for staff to send it from Orders → Kitchen Release on the Emergency Terminal. An order already released is not sent to the kitchen again after the upload.

Illustration, not a screenshot. The real screen can differ with the theme or version.

When the database comes back, ordinary queued writes are sent first, then the emergency bills are uploaded. The Continuity card in Diagnostics shows Emergency Mode until the upload has finished, and any problem appears next to Attention:

  • “Finish or review the current payment and printing operation before synchronising emergency bills.” or “Record or reverse the approved card payment before synchronising emergency bills.”: finish that payment or print on the Emergency Terminal first. The upload then starts by itself.
  • “Emergency bills are not uploaded until this terminal’s unfinished card requests are checked: …”: FMX EPOS could not finish its automatic check of card requests left by the previous run. Read the reason after the message. The check runs again at the next synchronisation, so leave the terminal running. If the same reason keeps appearing, contact support. A card result marked unknown does not stop the upload. Check that transaction later in Payment Review. Do not repeat a payment or refund until you know whether it went through.
  • “Emergency bills could not be uploaded and need review: …” followed by the reason: nothing was uploaded. The terminal goes back to taking emergency bills until the problem is fixed and an upload succeeds. If the reason says an emergency table is occupied or being cleared remotely, the same table in the restaurant database still has an open bill, is paid and waiting to be released, or is being cleaned. Tables used and released earlier do not count. Free that table on another till, or move the emergency bill to a free table on the Emergency Terminal; neither bill has been overwritten.
  • “Waiting to confirm the remote upload. Do not repeat payment or printing.”: the connection dropped during the upload. The bills stay locked until FMX EPOS can check whether the upload arrived, which happens by itself once the database answers.
  • “Emergency bills were uploaded but could not be cleared from this terminal: …”: the upload arrived. FMX EPOS clears the bills from this terminal at the next synchronisation.

Do not update FMX EPOS on the Emergency Terminal while it still holds emergency bills, because bills recorded by one version must be uploaded by that version. Do not delete local application data or switch databases to force the bills open. If the message does not clear, send it to support.

Data Migration, Import Data, Export Data and the scheduled Automatic Backup on the Database page pause every terminal. A paused terminal shows Terminal Paused: “This terminal is paused for database maintenance. Do not repeat payments or printing. …” with an Administrator Recovery button. An open customer display shows the pause without that button. A terminal that still has queued writes or emergency bills keeps trading while it sends them, then pauses. During an export or automatic backup there is nothing to do: the message says so, and the terminal carries on by itself.

An export or automatic backup releases the terminals when it finishes. If the terminal that started it stops during it, for example in a power cut, it releases them when it starts again. After a successful import or migration, only the terminal that ran it carries on; every other terminal stays paused:

  • After an import, resume each other terminal with Resume This Terminal.
  • After a migration, move each other terminal to the new database with Move to Another Database. The old database is marked as retired, so a terminal cannot resume on it.

If the operation failed before it changed any data, FMX EPOS normally lifts the pause itself. If the new database did not confirm the change, the message says it “may or may not hold the new data” and every terminal stays paused. Check the target database first, then resume the terminal that started the operation, and the other terminals resume by themselves. If an export or automatic backup finished while the database could not be reached, the terminal that made it lifts the pause once the database answers again.

Illustration, not a screenshot. The real screen can differ with the theme or version.

  1. On the terminal that started the operation, read the final migration or import message.
  2. While the result is unknown, do not start the same destructive operation again.
  3. On the paused terminal, select Administrator Recovery.
  4. To carry on with the same database, enter an administrator’s username and password under Resume This Terminal and select Check & Resume This Terminal.
  5. To point this terminal at the new database, fill in Move to Another Database in the desktop app with the new Database Type, Server, Database, Database Username and Database Password, plus an Administrator Username and Administrator Password, then select Move This Terminal. A database with no user accounts starts first-run setup instead.
  6. Do one terminal at a time.

If resuming is refused with “An export or automatic backup started on … has not ended. Resume that terminal first; …”, that terminal’s export or automatic backup is still open. Start that terminal again (for an automatic backup, the Integration Host): it ends the operation itself and the other terminals resume. If it will not come back, tick End an export or automatic backup another terminal started and will not finish under Resume This Terminal and select Check & Resume This Terminal again; that operation changed no data. If resuming is refused with “The configured database is still under maintenance or has been retired. Configure the destination database before resuming this terminal.”, another terminal’s import or migration has not ended, or the database was migrated: resume the terminal that started the operation first, and only after a migration use Move to Another Database.

The terminal that starts maintenance must first send its own queued writes and emergency bills; otherwise it says “Synchronise this terminal’s emergency bills and local writes before maintenance.” It then waits up to 30 seconds for every other registered terminal to pause. If one does not, the message starts “Maintenance did not start. Every registered terminal must confirm that it has stopped and has nothing left to synchronise.” and lists each terminal with its reason, such as “Local writes must be synchronised first”, “Emergency bills must be synchronised first”, “Finish the active operation” or “terminal has not confirmed maintenance”. A terminal that is switched off usually shows “Waiting for maintenance request”.

Then deal with what the refusal names:

  • Another online terminal runs a version of FMX EPOS with a different database structure (“… Update both to the same version before maintenance.”). Update it first.
  • A terminal did not pause, is switched off, or still has unconfirmed writes or emergency bills.
  • “Finish or review these on all terminals before database maintenance: …”: a card operation is in progress, a card result is unknown, or a print job is printing or its result is unknown. The message names the terminal a print job prints on.

Illustration, not a screenshot. The real screen can differ with the theme or version.

Use Diagnostics, Payment Review and the Print Queue on the terminal named, and check the Terminals card on the Database page. Do not remove a terminal only to get past a refusal if it can come back and synchronise.

The scheduled Automatic Backup does not wait for terminals that show Offline on the Terminals card, so a till switched off for the night does not stop it. All other maintenance waits for every registered terminal.

Each FMX EPOS installation has its own terminal identity. If an installation folder is copied to another PC, both PCs carry the same identity. When FMX EPOS finds its identity already running on another computer, it does not start the till. Instead it shows Terminal Identity In Use with “This terminal’s identity is also running on …” and the other PC’s name. It cannot tell which PC is the copy.

Illustration, not a screenshot. The real screen can differ with the theme or version.

  1. Find the PC named in the message and work out which PC is the copy.
  2. If this PC is replacing the other one, switch the other PC off first, wait a few minutes, then start FMX EPOS here again.
  3. If this PC is the copy and both should keep running, select Create a New Terminal Identity in this PC’s till window. The button appears only in the till window. The customer display, kitchen screen and host stand offer Try Again instead.
  4. The desktop app shows “Restarting EPOS…” and starts again as a new terminal, on the sign-in page.
  5. Choose this terminal’s printers again in Local Settings → Printers, and check its terminal name, licence and kitchen station printers.

Never create a new identity on the original till: its printers, routes and unfinished card results belong to its current identity.

FMX EPOS runs only once per PC. If another Windows user on the same PC already has it open, starting it shows “FMX EPOS is already running for another Windows user on this PC.” Close it in that user’s session first.

Wherever possible, reconnect the terminal and let it synchronise first, because removing it cannot check its unsent local writes.

  1. Open Back Office → Database on a working terminal (administrator).
  2. On the Terminals card, find the terminal. Remove is offered only for another terminal that shows Offline.
  3. Read Remove Terminal? and select Remove Terminal.

Removal deletes the terminal’s printer registrations and station routes, and clears the Integration Host and Emergency Terminal choices if they named that terminal. Print jobs still waiting for its printers fail with “The terminal was removed. Choose another printer and retry.” Afterwards, choose the Integration Host, the kitchen station printers and, if it was that terminal, the Emergency Terminal again.

For planned storage changes, follow Manage database storage and maintenance.