Scanning Issues: Database Server Manager Not Finding Company Files

August 12, 2026 7 min read

When setting up multi-user access on a host server, administrators use the QuickBooks Database Server Manager (QBDBSM) to scan folders storing company data. A common breakdown occurs during this step: the scan completes, but QBDBSM reports “0 files found”, skips company files, or fails to generate the Network Data (.ND) files required for workstation connections.

This issue typically occurs when folder permissions block the QBDataServiceUser account, when administrators attempt to scan mapped network drive letters instead of local physical paths, or when file extensions are incorrect. Resolving this problem requires scanning direct local paths and granting full folder control to the appropriate service accounts.

Fast-Fix: The 45-Second Solution

Always scan using local physical drive paths (e.g., D:\QuickBooksData), never mapped network drives (such as Z:\). In Windows Explorer, right-click the company file folder, open Properties > Security, and give “Full Control” to both “Everyone” and your server’s specific QBDataServiceUserXX account (e.g., QBDataServiceUser34 for 2024, QBDataServiceUser35 for 2025). Reopen QBDBSM and click Start Scan.

Quick Status & Triage Snapshot

  • Data Risk Tier: Low. Scanning issues affect the utility’s ability to index files and generate network metadata; the underlying .QBW accounting data is not modified or compromised.
  • Multi-User Impact: High. Workstations cannot open company files across the network until QBDBSM detects the files and writes matching .ND files.
  • Common Trigger: Moving company files to a new drive, creating new subfolders without inherited permissions, or running QBDBSM from a non-elevated user account.
  • Estimated Fix Time: 3–5 minutes.

Diagnostic Flowchart: QBDBSM Scan Decision Path

[Start: QBDBSM Scans Folder but Reports "0 Files Found"]
       |
       v
Is the folder path entered as a mapped drive letter (e.g., Z:\Data)?
  |-- YES --> QBDBSM cannot resolve mapped drives across Windows sessions.
  |           Action: Browse to local physical path (e.g., C:\Data or D:\Data).
  |
  \-- NO ---> Path is local (physical drive).
              |
              v
       Are the files named with a true .QBW extension?
         |-- NO ---> Files may be .QBB (Backups) or have hidden double extensions (.qbw.nd).
         |           Action: Fix file extensions in Windows Explorer folder options.
         |
         \-- YES --> Folder access is blocked by Windows NTFS security permissions.
                     Action: Add QBDataServiceUser & grant Full Control.

Technical Anatomy: How QBDBSM Detects and Configures Files

The QuickBooks Database Server Manager performs two critical tasks during a folder scan:

  1. Header Validation: It scans the target directory for files ending in .qbw and reads the internal database header to identify the file format and QuickBooks version.
  2. Network Data Generation: Once validated, the service writes an .ND configuration file in the same directory (e.g., CompanyFile.qbw.nd). This text file stores the server’s current IP address, the assigned TCP port, and the database engine service name.

If QBDBSM cannot read the folder contents, it silently aborts the scan and reports zero files found. This visibility breakdown happens for three main reasons:

  • Session Isolation (Mapped Drives): Mapped network drive letters (like Z:\) exist only within the active user’s interactive Windows login session. Because the database manager runs as an isolated system service, it cannot see mapped drives created by standard user accounts.
  • Missing NTFS Rights for QBDataServiceUser: QuickBooks creates a dedicated Windows service account during installation (e.g., QBDataServiceUser35 for 2025). If the folder permissions do not grant this account read, write, and execute permissions, the service cannot index files in that directory.
  • File Attributes: Files flagged as Hidden or Read-Only (often resulting from copying files directly from external archive media) are ignored by the scanning engine.

Step-by-Step Repair Guide

Step 1: Scan Local Physical Paths Only

Never select a network share or a mapped drive letter inside the Database Server Manager interface.

  1. Log directly onto the server hosting the company files.
  2. Open the QuickBooks Database Server Manager from the Windows Start menu.
  3. Click the Scan Folders tab.
  4. If an existing folder path uses a mapped drive letter (such as Z:\CompanyData or X:\Files):
    • Select the folder path and click Remove Folder.
  5. Click Add Folder.
  6. Browse directly to the local storage drive:
    • Correct: C:\QuickBooksData\CompanyFiles or E:\Data\QuickBooks
    • Incorrect: Z:\CompanyFiles or \\ServerName\CompanyFiles
  7. Click Start Scan.

Step 2: Grant Permissions to the QuickBooks Data Service User

If the utility still finds zero files on a local drive, the service account is being blocked by NTFS permissions.

  1. Open Windows File Explorer and navigate to the directory holding your .QBW files.
  2. Right-click the folder and select Properties.
  3. Select the Security tab and click Edit.
  4. Check the list of user names for your version’s service account:
    • QuickBooks 2024: QBDataServiceUser34
    • QuickBooks 2025: QBDataServiceUser35
    • QuickBooks 2026: QBDataServiceUser36
  5. If the account is missing from the list:
    • Click Add.
    • Under Enter the object names to select, type QBDataServiceUser and click Check Names.
    • Select the account matching your installed version and click OK.
  6. Select the QBDataServiceUserXX account in the list and check the box for Full control under the Allow column.
  7. Also ensure SYSTEM, Administrators, and Users (or Everyone) have Read & execute, List folder contents, and Write permissions.
  8. Click Apply, then OK.

For advanced permission structures and folder sharing rules across enterprise servers, see Data Access: Using QBDBSM to Manage Folder Permissions and Access.

Step 3: Check File Extensions and Windows File Attributes

If files were migrated or restored improperly, their file names or system flags may cause the scanner to skip them.

  1. In Windows File Explorer, click the View tab in the top ribbon (or View > Show in Windows 11).
  2. Ensure the checkbox for File name extensions and Hidden items is enabled.
  3. Check the file name in your company folder:
    • The file must end strictly in .qbw (e.g., MyBusiness.qbw).
    • If it ends in .qbb, it is a backup copy and cannot be scanned; it must first be restored inside QuickBooks.
    • If it ends in .qbm, it is a compressed portable file.
    • Ensure it does not have a double extension such as MyBusiness.qbw.qbw or MyBusiness.qbw.nd.
  4. Right-click the .qbw file and select Properties.
  5. At the bottom of the General tab, under Attributes:
    • Ensure Read-only is unchecked.
    • Ensure Hidden is unchecked.
  6. Click Apply and OK.

Step 4: Run QBDBSM with Administrative Privileges

Insufficient user account permissions running the QBDBSM application can prevent the tool from accessing restricted folders.

  1. Close the QuickBooks Database Server Manager.
  2. Click the Windows Start menu and type QuickBooks Database Server Manager.
  3. Right-click the application icon and select Run as administrator.
  4. Select the target folder and click Start Scan.
  5. Once the scan finishes, confirm that your company files appear in the bottom pane under QuickBooks Company Files Found.

When the Scan Completes but Network Access Fails

If QBDBSM scans the file successfully and creates the .ND file, but workstations still cannot connect:

  • Review Network Diagnostics: Check the third tab in QBDBSM (Database Server). If the network status shows a red warning or failures, refer to Network Diagnostics: Resolving “Network Diagnostics Failed” in QBDBSM.
  • Confirm Version Compatibility: If the company file was created in a newer release of QuickBooks than the database manager version installed on the server, workstations will be rejected. Review the version matching steps in the next guide.

Closing the Books

Scanning issues in the QuickBooks Database Server Manager are almost always caused by environment configuration issues rather than software bugs. Pointing the scanner toward local physical drive paths and ensuring the QBDataServiceUser has full NTFS rights allows QBDBSM to index your company files and write the necessary network connection files.

Version Mismatch: How to Update QBDBSM to Match Your QuickBooks Year

August 12, 2026

Version Mismatch: How to Update QBDBSM to Match Your QuickBooks Year

August 12, 2026

Troubleshooting “QuickBooks Database Server Manager Stopped”

July 2, 2026