QBM Update, Upgrade, and Rollback Support Guide

Plan and verify QBM updates across QBM Client, QBM Server, QBMWServices, database changes, and rollback readiness.

Where to find it

Path: Help > Check for Updates, or Help > Help Center > Update and rollback support.

Use this path from the main QBM window. If the command is not visible, confirm that the user has access to the related module and permission for that screen.

Guide Summary

AudienceImplementation team, support staff, AI agents, and developers.
Applies ToQBM Client, QBM Server, QBMWServices, SQL Server database, QSalesView, QClock.
PurposePrevent partial updates, version mismatch, data loss, and configuration loss during QBM upgrades.
Last Updated2026-05-18

Before Update

  1. Schedule a maintenance window and notify users.
  2. Take a verified database backup.
  3. Record current QBM Client, QBM Server, QBMWServices, QSalesView, and QClock versions.
  4. Back up service configuration files such as QBMWServices appsettings.json.
  5. Confirm rollback package and backup location are available.
  6. Stop services only after users are out of active transactions.

Expected result: The update can proceed with a verified backup, preserved configuration, known versions, and a practical rollback path.

Step-By-Step Update

  1. Stop QBM Server and QBMWServices during the approved window.
  2. Update QBM Server files according to the release package.
  3. Update QBM Client workstations to the matching version.
  4. Update QBMWServices files without losing the working production configuration.
  5. Run any required database update only after the database backup is confirmed.
  6. Start QBM Server, then QBMWServices.
  7. Confirm client/server version match.
  8. Do not remove or change Dependent Dlls loading unless development confirms a real bug.

Post-Update Testing

  • Login to QBM Client.
  • Open customer, vendor, item, and account lists.
  • Create or open a safe test transaction if the update affects transactions.
  • Run key reports: sales, purchases, inventory, accounting, VAT, payroll, and POS where applicable.
  • Test printing, PDF, and email.
  • Test QSalesView or QClock if QBMWServices is used.
  • Test backup after update.
  • Confirm support users can access permissions and logs.

Rollback

  1. Stop services before replacing files.
  2. Restore the previous application files from the approved rollback package.
  3. Restore configuration files if they were changed.
  4. Restore the database only if the update changed the database and rollback requires the pre-update state.
  5. Start services and test the same checklist used after the update.
  6. Document why rollback was required and what evidence was collected.

Troubleshooting Decision Tree

  1. Does QBM show client/server mismatch? Align QBM Client and QBM Server versions.
  2. Does QBMWServices fail after update? Restore or fix appsettings.json, ProductKey, and port binding.
  3. Does login fail for all users? Check QBM Server, SQL Server, database update, and permissions.
  4. Do reports fail only in one module? Check module-specific release notes and permissions.
  5. Is data at risk? Stop and restore from verified backup according to the rollback plan.

What To Send To Support

  • Version before and after update.
  • Update package name and time applied.
  • Database backup confirmation.
  • Exact error, screen, and timestamp.
  • Service statuses and logs.
  • What post-update tests passed and failed.

Security Notes

  • Protect database backups and configuration files.
  • Do not send product keys, passwords, or full backups in public chat.
  • Limit update and rollback access to authorized staff.