Diagnoser

Install QBM Diagnoser, locate QBM Client logs per company database, locate QBM Server logs, and collect safe evidence for support review.

Guide Summary

AudienceSupport staff, implementation staff, IT administrators, and approved technical contacts.
Applies ToQBM Client, QBM Server, QBMWServices, workstation connection issues, save-time errors, and server-side service issues.
PurposeShow where logs are saved and how to collect the smallest useful support package without passwords, database backups, or private keys.
Primary Client Logelg.dat
Primary Server Logselg.dat
First step: run QBM Diagnoser before changing services, ports, firewall rules, database settings, or workstation settings unless support already gave a specific instruction.

Install QBM Diagnoser

Install QBM Diagnoser on the affected workstation, and also on the server when server-side checks or server logs are needed.

  1. Download the approved installer: QbmDiagnoser.msi.
  2. Run the installer using a Windows account allowed to install support utilities on that computer.
  3. Open QBM Diagnoser from the desktop shortcut or Start menu.
  4. Select the closest problem type, confirm the detected server details, and run the check.
  5. Save or copy the result only when support asks for it.
Tip: if only one workstation has a problem, run QBM Diagnoser on that workstation first. If all users are affected, run it on the server and one affected workstation.

Client Log Per Database

QBM Client writes a separate log under the current Windows user profile and company database context. The active log file is named elg.dat.

PartMeaningExample
Base folderCurrent user's local QBM settings folder.C:\Users\arahi\AppData\Local\QBM\Local Settings
Company folderThe stored instance or computer name followed by the database name.WORKSTATION01ABCCompany
Database nameThe company database name.ABCCompany
Computer or instance nameThe QBM connection instance value. For simple local setups this is commonly the computer name.WORKSTATION01
Active log fileThe current QBM Client log.elg.dat

Example Client Path

C:\Users\arahi\AppData\Local\QBM\Local Settings\WORKSTATION01ABCCompany\elg.dat

How To Find It

  1. Sign in to Windows as the same user who saw the QBM issue.
  2. Press Windows + R.
  3. Enter %LOCALAPPDATA%\QBM\Local Settings and press Enter.
  4. Open the folder that matches the affected connection and database, for example WORKSTATION01ABCCompany.
  5. Collect elg.dat. If the issue happened earlier, also collect nearby archived files named like elg.dat.20260611-153000.old.
  6. If you are not sure which folder is correct, sort folders by Date modified and open the newest folder that matches the database name.
Named instance note: if the connection instance contains a backslash, QBM stores the folder without that backslash. For example, an instance and database may appear like WORKSTATION01SQLEXPRESSABCCompany.

Server Log

QBM Server writes its application log as selg.dat under the local settings folder for the Windows account running the service. Unlike the client log, this server log is not stored per company database. The default service account in the QBM Server installer is LocalService.

Server ScenarioWhere To LookWhat To Collect
Default QBM Server service accountC:\Windows\ServiceProfiles\LocalService\AppData\Local\QBM\Local Settings\selg.datselg.dat and nearby selg.dat.*.old archives.
Custom service accountC:\Users\<service-user>\AppData\Local\QBM\Local Settings\selg.datThe same active and archived server log files from that account profile.
Service start, stop, and startup errorsWindows Event Viewer > Windows Logs > ApplicationEvents around the failure time for QuickBusinessManagerServer or QBMServer.

How To Confirm The Service Account

  1. On the server, open Services.
  2. Find QuickBusinessManagerServer.
  3. Open Properties, then the Log On tab.
  4. If it shows Local Service, use the default LocalService path above.
  5. If it shows another account, use that account's user profile path or ask the server administrator to open it.
Important: do not change the service logon account just to collect logs. Only read the file path that belongs to the current service account.

Other Useful Evidence

When The Issue MentionsCollect ThisWhere To Look
Browser apps, QSalesView, QClock, or published service addressQBMWServices daily log file and service status.The Logs folder under the QBMWServices installation folder, for example ...\QBMWServices\Logs.
QBM Client cannot connectQBM Diagnoser result, client elg.dat, server selg.dat, service status, and the failure timestamp.Affected workstation and server.
Only one database has the issueClient log from the matching database folder and the database name shown in QBM.%LOCALAPPDATA%\QBM\Local Settings.
All users are affectedQBM Server status, server log, Event Viewer entries, recent restart or update notes, and one affected client log.Server plus one affected workstation.
Printing or export issueScreenshot, exact document/report name, printer/export target, timestamp, and client log.Affected workstation.

Collection Checklist

  1. Record the customer name, company database name, user name, workstation name, and server name.
  2. Record the exact date and time of the failure.
  3. Run QBM Diagnoser on the affected workstation, or on the server when all users are affected.
  4. Collect the matching client elg.dat from the affected Windows user and database folder.
  5. Collect server selg.dat when the issue affects all users, service startup, save-time disconnects, or server connection.
  6. Collect the Windows Event Viewer entries around the same time when the server service stopped, failed to start, or restarted unexpectedly.
  7. Zip only the selected logs, screenshots, and QBM Diagnoser result requested by support.

Quick Commands

These commands are optional. Use them only from an approved support session and avoid changing the customer environment while collecting evidence.

Find Recent Client Log Folders

Get-ChildItem "$env:LOCALAPPDATA\QBM\Local Settings" -Directory |
    Sort-Object LastWriteTime -Descending |
    Select-Object Name, LastWriteTime

Open The Current User Client Log Folder

explorer "$env:LOCALAPPDATA\QBM\Local Settings"

Check QBM Server Service Account

Get-CimInstance Win32_Service -Filter "Name='QuickBusinessManagerServer'" |
    Select-Object Name, State, StartName

Default Server Log Path

explorer "$env:WINDIR\ServiceProfiles\LocalService\AppData\Local\QBM\Local Settings"

Security Notes

  • Do not request or send passwords.
  • Do not send database backups through public chat or unapproved channels.
  • Mask product keys, private connection details, customer-sensitive data, and personal information in screenshots.
  • Do not upload entire QBM folders when support only asked for logs.
  • Do not change services, firewall rules, ports, database settings, or permissions unless support approved the change.
  • Use the approved QBM Diagnoser installer link in this guide instead of files copied from unknown locations.

Rubric Check

CheckPass Condition
Installer linkThe page provides the approved QBM Diagnoser MSI download link.
Client log accuracyThe page identifies the per-database client folder and active elg.dat file.
Server log accuracyThe page identifies the default LocalService path for selg.dat and explains custom service-account paths.
Support usefulnessThe page tells support what to collect for one-workstation, one-database, all-user, browser-app, and server issues.
SecurityThe page avoids asking for passwords, full database backups, product keys, or private connection secrets.
Customer-safe wordingThe page gives operational support steps without exposing development implementation details.
IndexingThe page is linked from the help index and uses searchable log and Diagnoser keywords.