QBM Error Message Dictionary

Use exact messages to understand meaning, likely causes, first checks, support checks, customer questions, and escalation rules.

Guide Summary

AudienceEnd users, support staff, implementation team, AI agents, and developers.
Applies ToQBM Client, QSalesView, QClock, POS, QBMWServices, SQL Server, printing, integrations.
PurposeConvert exact messages into clear troubleshooting steps and escalation rules.
Last Updated2026-05-18

How To Use This Dictionary

  1. Start with the exact text shown to the user.
  2. Identify the component: QBM Client, QSalesView, QClock, POS, QBMWServices, SQL Server, printing, or integration.
  3. Run the first checks before changing settings.
  4. Collect support evidence if the first checks do not resolve the issue.
  5. Escalate only after the required information is complete.

Expected result: Support and AI agents can move from exact message to first checks, support checks, and escalation without guessing.

Message Dictionary

Error Message Applies To Meaning Most Likely Causes First Checks Escalate When
Invalid TokenQSalesView, QClock, activation, password setupThe token cannot be used for the requested action.Expired token, already used token, broken URL, wrong account, password setup not completed.Request a new activation or password setup link; confirm user account and timestamp.A fresh token fails for the same user and support has the exact link time and account details.
Login is taking too long. Check the connection and try again.QSalesView, QBMWServicesQSalesView did not complete login quickly enough.QBMWServices unreachable, Cloudflare target wrong, QBM Server stopped, SQL Server stopped, bad settings, product key or permission timeout.Check QBM Client login, QBM Server, QBMWServices, port 8053, Cloudflare, settings, logs.All services are healthy but login still times out with current logs.
Access deniedQBM Client, reports, QSalesView, POSThe user is not allowed to perform the action.Security group missing screen/report permission, inactive user, restricted document, manager-only action.Confirm user, security group, screen, report, and action.Permission appears correct but the user is still blocked.
Password is case sensitiveQBM Client, web loginThe typed password may not match the stored password exactly.Caps Lock, wrong keyboard language, saved browser password, outdated password.Retype manually and check Caps Lock; do not ask user to send password.Known correct credentials fail for multiple users.
No connection could be establishedQBM Client, QBM Server, QBMWServicesThe application cannot reach a required service.Service stopped, wrong server, wrong port, firewall, network, VPN, tunnel issue.Check service status, port, server name, network, and firewall.Network path is reachable but application still cannot connect.
Endpoint not foundQBMWServices, QSalesView, integrationsThe requested API route is not available at the target URL.Wrong Service Address, wrong BaseAddress, old version, proxy route mismatch, calling website host instead of API host.Confirm the URL, controller route, deployed version, and browser network request.The endpoint exists in code and deployment but still returns not found.
Client and server versions may not matchQBM Client, QBM ServerThe desktop client and server service are not aligned.Partial update, old workstation, old service files, rollback mismatch.Check QBM Client and QBM Server versions; update both sides.Versions match but compatibility warning continues.
SQL Server instance not foundQBM Client, QBM Server, database toolsThe configured SQL instance cannot be located.Wrong instance name, SQL service stopped, SQL Browser stopped for named instance, firewall, server rename.Check SQL services, instance name, server name, and SQL Browser if required.SQL tools can connect but QBM cannot.
Product key is invalidQBMWServices, QSalesView, activationThe configured license value is missing, invalid, or not accepted.Missing ProductKey, wrong environment, old config overwritten, key copied incorrectly.Confirm ProductKey exists and was not replaced during update; do not expose it.Valid masked configuration still fails after service restart.
Port is not listeningQBM Server, QBMWServicesWindows is not accepting connections on the expected port.Service stopped, binding failed, URL reservation missing, firewall, port conflict.Run service status and Get-NetTCPConnection for the port.Service is running but the port never appears.
Cannot delete because record is in useQBM Client, master data, transactionsQBM is protecting history linked to another record.Record used by transaction, item, account, customer, vendor, report history.Make inactive where available or correct related transaction safely.The user must remove a record and the safe correction path is unclear.
Print preview not openingPrinting, reports, POSQBM or Windows could not open the preview path.Printer driver, template issue, missing viewer, permissions, report data issue.Try another printer, PDF, Windows test print, and a default template.Windows printing works and multiple templates fail in QBM.
PDF not generatingPrinting, reports, emailQBM cannot create the PDF output.Output folder permissions, PDF component, template, file locked, long path.Change output folder, verify permissions, try another template.All output locations and templates fail.
Email sending failedEmail, invoice, statement, reportsQBM could not send through the configured email method.SMTP settings, password or app password, firewall, attachment path, mail server policy.Check email settings, test SMTP, confirm attachment path and size.SMTP test succeeds but QBM email still fails.
Import required field missingImport, Excel, CSVThe import file does not contain a required column or value.Wrong template, blank required column, renamed header, incorrect sheet.Use the correct import template and fill required columns.The file matches the template but import still rejects it.
Duplicate recordMaster data, import, sales, inventoryQBM found an existing record with a unique value.Duplicate name, code, SKU, barcode, account number, reference number.Search existing records and decide whether to use, rename, merge, or correct.The duplicate check appears wrong or blocks a permitted blank optional value.

Troubleshooting Decision Tree

  1. Is the exact message in this guide? If yes, follow its first checks.
  2. If not, identify the component and collect the exact text, screen, timestamp, and steps.
  3. If it is a connection message, start with services, ports, server name, SQL instance, and network.
  4. If it is a permission message, start with user, group, screen/report, and action.
  5. If it is a data message, start with duplicate records, related transactions, required fields, and filters.
  6. If the same issue is reproducible after first checks, escalate with logs and screenshots.

What To Send To Support

  • Exact error message, not a paraphrase.
  • Screen name, document type, customer/vendor/item if relevant, and timestamp.
  • Whether it affects one user, one workstation, one database, or all users.
  • Recent update, restart, network, password, database, or permission change.
  • Relevant logs and safe screenshots.

Security Notes

  • Never ask for passwords.
  • Mask product keys, tokens, customer data, and personal information.
  • Do not request a full database backup in public chat.