We help IT Professionals succeed at work.

Quickbooks PRO 2006 multi-user extremely slow

jiggamoose asked
Medium Priority
Last Modified: 2010-06-27
Would greatly appreciate if someone could help with this.

We use Quickbooks PRO 2006 - multi-user (3 users in office)

Setup - Quickbooks is installed on the 3 users computers
         - The company file resides on a share on a SBS 2003 server

Problem:  Extremely slow performance when using Quickbooks.  It gets even worse when multiple users are on it at the same time.

Attempted solutions:
I have already contacted QB for support (terribly frustrating experience) - our company file was 90mb - basically all they said we could do is reduce the company file by archiving and condensing and stating to me that as long as we are under 60MB we should be fine in terms of performance.  I archived and condensed the file to get it down to 44MB.  The performance is STILL terrible.

I have also adjusted numerous items in the company preferences ie. turning off audit trail, turning off warning about duplicate invoices etc etc.  None of this seems to help much.

Additional info:  Small office environment - server has 2 GB RAM, plenty of CPU power - so I really don't think it's the hardware involved.

This has been extremely frustrating as QB tech support doesn't seem to have any answers for me other than the size of the company file.

1 item to note:  We have 2 MAC users in the office who connect to the server for their mail using IMAP - sometimes it seems as though the performance of QB is better when the MAC users are offline or not in the office.  I am not sure if the MAC users thru their connection to the exchange server via IMAP aren't having some affect on the network performance.

If anyone has experienced similar problems or could point me in the right direction it would be much appreciated!

Watch Question

QB Pro sucks in multi user mode.

What you need is the premier 2006 version.
It uses an SQL data base.

The only thing that I could think of that might help is oppotunistic locking .


Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

From W2K server news:

Windows 2003 Gotcha: Opportunistic File Locking

With the release of a new server OS there is always associated joy and fear. Here is a horror story for y'all to learn and be warned. This was sent in by a subscriber:

"I have been running W2K3 since it was a beta and had no problems with the OS. I then decided it was becoming time to start offering it to my customers so the first step was to get my office running it first. I upgraded the servers all to Windows Server 2003 and as with most engineers I was rushed back into the wild to fix something and let the office jockeys run on it.

I felt that I had a successful migration after a few weeks so I moved on to a contract customer of mine that I have had for six years. I upgraded his Dell PowerEdge 1500SC from Windows 2000 Server to 2003 and immediately the users started complaining of problem accessing there QuickBooks files, then the no access turned into file corruption. This customer also runs a older Paradox database system on the server and files started becoming corrupt with it as well.

I ran through the basic troubleshooting, then the second phase of troubleshooting all with no victory. I called QuickBooks and they said must be hardware, I called Dell and the said must be Windows Server 2003, so I called MS and they said it must be hardware. To shorten this up some I removed Windows 2003 upgrade and reinstalled Windows 2000 Server and the problems immediately went away. The only thing at time my searches on the internet showed had something to do with Opportunistic File locking features in Windows, but nothing conclusive to me.

So I put it on the back burner until yesterday and started searching again, wow what a difference a month makes, now people all over the place are having the same problems with Windows Server 2003 and Database applications, it seems opportunistic file locking is the problem, I found one news group posting where someone stated that Great Plains was experiencing this problem so I took a shot and called our Great Plains contact at MS and he stated that MS had patched it for them but he was not allowed to release it to anyone not running Great Plains. To wrap this up Microsoft has let down an engineer that lives and breathes their product, I make my living off of this software and to be told first that nothing is wrong (must be hardware) and then told that they have a fix but it is only for the big clients is not pretty."


Interesting post PGM554

I will look into the  Opportunistic File Locking - not sure if that applies also to SBS 2003 which we run here.

Unfortunately it does seem as though the multi-user version of PRO does indeed suck.  We are considering upgrading to 2007 Premier edition.

I will let you know how it goes and award points if it's a viable solution.

But I do appreciate your assistance.

Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.