SQL Server Support Guide for QBM

Guide Summary

Audience	Support staff, implementation team, database administrators, AI agents, and developers.
Applies To	SQL Server, SQL Browser, QBM Server, QBM company database, backup and restore tools.
Purpose	Diagnose database availability, instance, login, backup, restore, disk, and permission issues safely.
Last Updated	2026-05-18

SQL Server Role

SQL Server stores the QBM company database. QBM users normally do not connect to SQL Server directly. QBM Client reaches QBM Server, and QBM Server reaches SQL Server.

Expected result: SQL Server is running, the correct instance and database are available, and QBM Server can access the company database.

Topic	Support Meaning
Default instance	SQL Server may be reached by server name only.
Named instance	SQL Server may require an instance name and sometimes SQL Browser.
Database name	Must match the selected QBM company database.
SQL Browser	Often needed when named instance discovery is used.
Compressed files	SQL database files should not be stored in NTFS-compressed folders.

Step-By-Step Checks

Confirm SQL Server service is running.
Confirm SQL Browser service if a named instance requires browser discovery.
Confirm the configured SQL instance name exactly matches the installed instance.
Confirm the QBM company database exists and is online.
Confirm disk space is available on data, log, backup, and temp locations.
Confirm database files and folders are not NTFS-compressed.
Confirm the service account or SQL login has the needed access.
After fixes, test normal QBM Client login and one basic report.

Backup And Restore

Take a current backup before updates, repair work, mass imports, or risky troubleshooting.
Restore only to the intended target database; avoid overwriting production by mistake.
Confirm permissions for the backup folder and restore folder.
Check disk space before backup and restore.
After restore, confirm database online status, user access, QBM Server connection, and QBM Client login.

Common SQL Errors

Error	Meaning	First Check
SQL Error 11	General SQL connection problem.	Check service, server name, instance, and network.
SQL Error 17	SQL Server does not exist or access denied.	Check instance name, firewall, and SQL Browser.
Error 40	Could not open a connection to SQL Server.	Check SQL service, network path, and remote connections.
Login failed	SQL login or Windows account is not accepted.	Check account, password policy, permissions, and authentication mode.
Database does not exist	Configured database name is wrong or database is missing.	Check database name and restore status.
Cannot open database requested by login	Login exists but lacks database access.	Check database user mapping and permissions.
Timeout expired	SQL is unreachable, slow, blocked, or overloaded.	Check service health, blocking, network, and disk.
Database files are compressed	SQL files are in an unsupported compressed folder.	Disable NTFS compression on database files and folders.

Troubleshooting Decision Tree

Is SQL Server service stopped? Start it and review Windows Event Viewer if it stops again.
Is the instance name wrong? Correct QBM settings or service configuration.
Is the company database offline or missing? Bring it online or restore the correct backup.
Is login failing? Check SQL account mapping, Windows account, and permissions.
Is the database folder compressed? Remove compression before retrying.
If SQL tools connect but QBM cannot, check QBM Server configuration and logs.

What To Send To Support

Exact SQL error text and timestamp.
SQL Server name, instance name, and database name.
SQL Server and SQL Browser service status.
Whether all users are affected.
Recent backup, restore, update, disk, permission, or server change.
Do not send SQL passwords in chat.

Security Notes

Do not send SQL passwords or administrator credentials.
Do not share full database backups in public chat.
Restrict database backup and restore permissions to authorized staff.