QSales / QSalesView Setup and Troubleshooting Guide

Set up QSalesView correctly and troubleshoot slow login, product key, permission, tunnel, service, and database issues.

Guide Summary

AudienceSales managers, implementation team, support staff, AI agents, and developers.
Applies ToQSalesView, QBMWServices, QBM Server, SQL Server, Cloudflare Tunnel, hosted QSales URL.
PurposeExplain what QSalesView is, how it connects to QBM, and how to troubleshoot login or dashboard issues in the correct order.
Last Updated2026-05-18

Overview

QSalesView is a browser-based sales dashboard and manager reporting tool that reads QBM sales, customer, employee, item, location, and permission data through QBMWServices. It does not connect directly to SQL Server from the browser.

QSalesView users normally open a website, enter their QBM login details, and use configured connection values so QBMWServices can reach QBM Server and the selected company database.

Normal Flow

QSalesView browser
-> Service Address, such as https://customername.qbmis.com or an API hostname
-> Cloudflare Tunnel or hosted reverse proxy
-> QBMWServices on local port 8053
-> QBM Server on private port 8051
-> SQL Server and QBM company database

Expected result: Login succeeds, the product key is accepted, user permissions are validated, manager reports load only for allowed users, and dashboard data returns within a reasonable time.

Configuration Values

FieldMeaningCommon Mistake
Service AddressHTTP or HTTPS address used by QSalesView to reach QBMWServices.Entering the SQL Server name or QBM Server name instead of the API address.
Server NameServer value that QBMWServices uses to reach QBM Server.Entering the Cloudflare URL here instead of in Service Address.
PortPrivate QBM Server port used by QBMWServices, commonly 8051.Using 8053 here when the field expects QBM Server.
Instance NameSQL Server instance name used by the customer setup.Typing the Windows server name instead of the SQL instance.
Database NameQBM company database name.Using a test or old database by mistake.
ProductKeyLicense value stored in QBMWServices appsettings.json.Missing, invalid, or replaced during update.

Step-By-Step Setup

  1. Confirm normal QBM Client login works on the server computer.
  2. Confirm QBM Server is installed, running, and reachable on the configured private port.
  3. Confirm QBMWServices is installed, running, and listening on local port 8053.
  4. Confirm ProductKey exists in the QBMWServices appsettings.json file. Do not send the key in public support chats.
  5. Test QBMWServices locally before testing the public URL.
  6. If Cloudflare is used, confirm the tunnel target is http://localhost:8053.
  7. In QSalesView, set Service Address to the public API URL or hosted service URL.
  8. Set Server Name, Port, Instance Name, and Database Name to the real QBM connection values.
  9. Sign in with a valid QBM user that has the required application and report permissions.
# This confirms QBMWServices is installed and running.
Get-Service -Name 'QBMWServices'

# This confirms the API is listening locally.
Get-NetTCPConnection -LocalPort 8053

# This confirms the local TCP path opens.
Test-NetConnection -ComputerName localhost -Port 8053

Login Timeout Case

Message: Login is taking too long. Check the connection and try again.

Most likely causes:

  • QBMWServices is not reachable.
  • Cloudflare Tunnel is not forwarding to the correct local port.
  • QBMWServices is running but cannot reach QBM Server.
  • QBM Server is stopped.
  • SQL Server is stopped or the company database is unavailable.
  • Wrong server name, port, instance name, or database name.
  • Product key is missing or invalid.
  • User permission check is timing out.
  • Firewall is blocking port 8053 or the private QBM Server port.

Troubleshooting Decision Tree

  1. Can normal QBM Client login on the server computer? If no, fix QBM Server, SQL Server, database, or credentials first.
  2. Is QBM Server Windows Service running? If no, start QBM Server and check logs.
  3. Is QBMWServices running? If no, start QBMWServices and check Windows Event Viewer plus the service log folder.
  4. Is port 8053 listening? If no, fix QBMWServices binding, URL reservation, firewall, or service startup.
  5. Does http://localhost:8053 respond locally? If no, check QBMWServices logs and Kestrel configuration.
  6. Does the Cloudflare public URL reach the local service? If no, fix tunnel command, hostname, local target URL, or tunnel service.
  7. Does QSalesView use correct values for Service Address, Server Name, Port, Instance Name, and Database Name? If no, correct them.
  8. If values are correct, check product key, user permissions, manager report permissions, and logs from the same time.

What To Send To Support

  • Screenshot of QSalesView configuration, with secrets masked.
  • Service Address, Server Name, Port, Instance Name, and Database Name.
  • Cloudflare public URL if used.
  • Screenshot showing QBMWServices, QBM Server, and SQL Server service status.
  • Whether normal QBM Client login works on the same computer.
  • Exact error message and approximate time of the error.
  • QSalesView browser console or network error screenshot if available.
  • QBMWServices logs from the same time.

Security Notes

  • Do not send passwords, full product keys, tokens, or full database backups in public chat.
  • Do not expose QBM Server port 8051 directly to the public internet.
  • Cloudflare should reach QBMWServices, not SQL Server and not QBM Server directly.
  • Mask customer data in screenshots before sharing outside the support team.