• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 829
  • Last Modified:

Quickbooks 2010 slow access

We are running a 5 user version of QuickBooks Enterprise Solutions 2010 and we are experiencing serious slowness issues. We notice the issues the most when we back up the database. It take quite a while to go through the process of backing up. Preparing for backup is the longest process. About 20 minutes from start to finish.

Our data file is 187MB in size.
We are running on a Windows 2003 Server
Workstations are running XP Pro and AVG 2011 (I mention this because I guess this could be part of the problem??)
 As we are doing the backup, the server is idling and the hard drive lights occasionally flash - they aren't on steady

On the server there are two services showing up and both are running
QuickBooksDB19 and QuickBooksDB20

How do we completely remove QuickBooks so that we can do a clean install?

Now to add to this, before I removed QB off of the server, we started one workstation up and it told us that it was going to manage the database. Since we were going to temporarily remove it from the server, I chose that option for now. How will I change it so that I know the server is managing the databases after the dB engine is reinstalled?
0
johnbowden
Asked:
johnbowden
  • 2
1 Solution
 
John HurstBusiness Consultant (Owner)Commented:
Lots here.

1. Unless you have a reason (e.g. BigTime), QuickBooks should not be installed on the server, only the database engine.
2. Go into the server and into Add/Remove Programs. Remove all instances of QuickBooks Server 20xx
3. Make sure QB itself is uninstalled.
4. Consider restarting the server (in an off moment)
5. Install the version of server manager from the CD for QB2010. Start the CD, and at the install point, select just Server Manager. Make certain the server manager is installed on the same physical driver as the ledger is located.
6. At the workstations, set each client so that it does not use Host Multi User Access (File -> Utilities).
7. Make sure each client maps the QB ledger folder in the form NET USE Z: \\server\qbledgerfolder. You can use a script or Windows Explorer.

That size of ledger should perform all right (never speedy). Try what I have suggestd and report back.

... Thinkpads_User
0
 
johnbowdenAuthor Commented:
We run just the QB database engine on the server only
I broke down and called Intuit support. They advised me to run a verify on the data. We did and it failed so then we ran a rebuild that that seems to have fixed the problem
0
 
johnbowdenAuthor Commented:
resolved myself
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now