0 votes
Has anyone been able to make this work? I have two customers with ClearOS 6 that have had to switch to using a Windows workstation as the host of the Quickbooks company file, because they received the H202 error when switching to multi-user mode while the ClearOS machine was hosting it. It used to work with QBES 16, and it still works with 17 when the file is in single-user mode.

We are trying to switch back to using the ClearOS machine as a host at one of the clients, because using the workstation to host access for the 7+ simultaneous users is causing lots of other problems that Intuit support doesn't want to help us solve. If I can't make it work I might try installing the Windows version of QB using WINE and host the company file that way, but that seems like a long shot.
Wednesday, August 09 2017, 04:11 PM
Share this post:
Responses (4)
  • Accepted Answer

    Wednesday, September 18 2019, 06:41 PM - #Permalink
    0 votes
    There are several solutions to resolve QuickBooks H202 error. For optimum results, perform the solutions in the following order.

    Solution 1: Test network connectivity

    1. Turn hosting off on all workstations
    2. Ping the server name from your workstation
    3. Enter ping[servername], and press Enter key
    If you detect packet loss or slow reply, it means the network needs to be repaired. In that case, proceed to Solution #2.

    Solution 2: Use the Network Diagnostic Tool
    1. Download and install the tool.
    2. Scan the folder where the data file is placed.
    3. Note down the number of IP addresses and Network Interfaces.
    4. In case the Firewall Status section has an Open Ports button, click the button to enable those ports for QuickBooks.
    5. Test for data file connectivity
    6. Try opening your company data file.

    If the error H202 still persists, try adding the QuickBooks port to the list of exceptions in the Windows Firewall.

    Solution 3: Add your server to Windows Host file
    1. Open the windows hosts file on the computer wherein the error is appearing.
     (C:\Windows\System32\Drivers\Etc\) using Notepad.
     Open Notepad as Admin, if needed.
    2. Place the insertion point after the last IP address and type the server’s IP address.
    3. Press the TAB key once, and type the server name.
    4. From the File menu, choose Save. Then, press Exit.
    5. Try opening the company file.

    Solution 4: Create a new folder for your company file
    1. On the hosting computer create a new folder.
    2. Share the folder and set up folder and Windows access permissions to share company files
    3. Copy the QuickBooks Database (QBW) file to the new folder
    4. Open your company file in multi-user mode again

    Solution 5: Set hosting to local files
    1. Launch QuickBooks and press F2 to open the Product Information screen
    2. In the lower left, below Local Server Information, select Hosting to reflect ‘local files only’
    3. Ensure that no other client system is trying to host the same company file

    Solution 6: Restart QuickBooks Database Server Manager
    1. Launch Windows Run dialog and type services.msc. Click OK
    2. Right-click QuickBooksDB19 (2009), QuickBooksDB18 (2008) or QuickBooksDB17 (2007) and select Stop
    3. Right-click and select Start. Then close the window
    4. Display extensions for known file types
    5. Right-click the Windows Start button and select Explore -> Tools -> Folder Options
    6. Click the View tab and clear ‘Hide extensions’ for the “known file types” box
    7. Again click the View tab and select Show hidden files and folders, clear the ‘Hide protected operating system files’ box
    8. Click ‘Yes’ on the warning and OK
    9. Close Windows Explorer

    Solution 7: Delete and recreate the .ND file
    1. In Windows search, type *.ND and hit Enter
    2. In the Results window, right-click on the .ND file and click on ‘Delete’
    3. Confirm deletion when prompted
    4. Now click the Windows Start button
    5. Select All Programs -> QuickBooks -> QuickBooks Database Server Manager
    6. Click the ‘Scan Folder’ tab
    7. Click the ‘Add Folder’ button and then browse to the company file folder
    8. Select the company file and click the OK button. The path to the company file is in the Folders with QuickBooks company files field
    9. Click ‘Scan’ to start the scanning process
    10. After the scan is complete, click Close

    The reply is currently minimized Show
  • Accepted Answer

    Sunday, May 19 2019, 10:09 AM - #Permalink
    0 votes

    File sharing is such a fiddly technology and SAMBA's attempt to mimic Windows is heroic. I wish people making applications that use networking would use more appropriate technology such as SQL or Streaming or HTML or whatever suits the task rather than simply have the hard drive files moved to a file server. 1980's called and they want their file sharing technology back.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, May 19 2019, 04:43 AM - #Permalink
    0 votes
    In all the times that I have gotten Quickbooks Enterprise to work and all the times that it has failed it was NOT the samba that was the problem but rather the support or lack their of from Intuit.

    The think particular about Quickbooks is that it requires that you run a special service on ClearOS to make it work. This service requires the special 32-bit gliibc and other 32 versions of libraries to function properly. If you are having difficulty getting their service to start, you need these special 32 versions running on 64bit ClearOS.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, May 18 2019, 01:08 PM - #Permalink
    0 votes
    I realise this is old but highlights a common problem with file sharing Windows programs over SAMBA.
    I have a user with a Lotus Approach database which works fine until a 2nd person opens it. They have to wait 3 minutes before it opens and then 1 minute for every action. I tried everything in smb.conf and flexshares.conf to do with oplocks but it would not resolve. I even ran ClearOS 7 as a VM and two Windows VMs on my Linux Mint box and was able to reproduce the problem.

    In this case the solution was to do a database copy on the files. In rebuilding the databases it must have fixed some hidden corruption because after that it worked fine with no special settings in SAMBA.

    I suggest that if there is some way you can rebuild or reindex your Quickbooks then that might resolve the issue.

    In Lotus Approach the other solution would have been to ODBC to a MariaSQL database but the original app would have needed a lot of tidying up due to lack of indexing and sloppy data integrity. I proved the concept though.
    The reply is currently minimized Show
Your Reply