QBM Server Windows Service Technical Guide

Where to find it

Path: Help > Help Center > Internal Support, then open service troubleshooting guidance when support asks for it.

This topic is a help or support guide rather than a transaction entry screen. Open it from the Help Center and search by the guide title or the main keyword.

Guide Summary

Audience	Server support, implementation team, AI agents, and developers.
Applies To	QBM Server Windows service, QBM Client, QBMWServices, SQL Server, company database.
Purpose	Explain how QBM Server works and how to verify it without unsafe changes.
Last Updated	2026-05-18

What QBM Server Does

QBM Server is the private Windows service layer used by QBM Client and QBMWServices to access QBM business logic and the SQL Server company database. It should normally run automatically on the server and remain reachable on the configured private network port.

Item	Support Meaning
Windows Service	QBM Server should be registered and running as a Windows service.
Startup Type	Usually Automatic for production servers.
Port	QBM Server normally has two private ports: `8050` for WCF/TCP from the `Port` setting, and `8051` for HTTP from the `HttpPort` setting. Confirm the real customer setting before changing either port.
SQL Connection	QBM Server reaches SQL Server using the configured server, instance, credentials, and database.
Dependent DLLs	If assemblies are loaded from the `Dependent Dlls` folder, this is expected and should not be changed unless development confirms a bug.

Normal Flow

QBM Client
-> QBM Server Windows Service
-> SQL Server
-> QBM Company Database

QSalesView / QClock
-> QBMWServices
-> QBM Server Windows Service
-> SQL Server
-> QBM Company Database

Expected result: QBM Client and QBMWServices can authenticate, validate permissions, read data, save transactions, and run reports through QBM Server.

Step-By-Step Checks

Confirm the QBM Server service exists and is running.
Confirm the configured port is listening on the server.
Confirm the QBM Client version and QBM Server version are compatible.
Confirm SQL Server service is running and the company database is online.
Restart QBM Server only when users are out of critical transactions or support has approved the restart window.
After restart, test QBM Client login and one basic report or list.
If QBMWServices depends on QBM Server, test QSalesView or QClock after QBM Client works.

Common Errors

Symptom	Likely Cause	First Check
Client cannot connect	Service stopped, wrong port, firewall, server name, network.	Check service status and port listener.
Timeout	QBM Server busy, SQL Server slow, blocked network, long query.	Check service logs, SQL service, and affected users.
WCF endpoint error	Wrong binding, port, service not listening, client/server mismatch.	Check endpoint settings and version match.
Version mismatch	Client updated but server not updated, or rollback incomplete.	Update QBM Client and QBM Server to the same release.
DLL loading concern	Dependent DLLs are being loaded from the expected folder.	Do not change this unless development confirms a real issue.

Upgrade And Rollback

Back up the company database before update.
Record the current QBM Client, QBM Server, and QBMWServices versions.
Stop services during the approved update window.
Update QBM Server and dependent files according to the release package.
Update QBM Client workstations to the matching version.
Restart services and test login, lists, reports, transactions, printing, and web apps.
Rollback only with a known good package and database backup plan.

Troubleshooting Decision Tree

Does QBM Client login fail for all users? If yes, check QBM Server and SQL Server first.
Is QBM Server stopped? If yes, start it and review logs if it stops again.
Is the private port not listening? If yes, check binding, firewall, and service startup.
Does SQL Server fail? If yes, repair SQL service, instance, database, or permissions.
Are client and server versions different? If yes, align versions.
If only QSalesView or QClock fails, check QBMWServices after QBM Client works.

What To Send To Support

QBM Server service status and startup type.
Configured server name and port.
QBM Client and QBM Server versions.
Exact connection or WCF error message.
SQL Server service status and database name.
Recent update, restart, firewall, antivirus, VPN, or server change.

Security Notes

Keep QBM Server private. Do not expose its port directly to the public internet.
Do not request passwords or database credentials in support chat.
Do not change Dependent Dlls loading unless development confirms a defect.