qbgent locking machine

[jbprincipato]

I am using quickbooks pro 2000 in a windows 2000 environment. We are using windows 2000 server to manage security, DNS, DHCP and other network connections. I have about 8 computers on the network. Applications include microsoft exchange, faxmaker and norton antivirus. Our problem starts when Quickbook pro 2000 starts. Qbagent.exe starts and takes 98% of the CPU resources and results in the program not starting for approximately 30 seconds until qbagent stops. Also when your are exiting Quickbook the problem starts again, qbagent takes 98% cpu resouces and doesn't close quickbooks. If you try and close report windows down or close registers, we get a 'server busy' error until qbagent finishes.

I would like to contact others that are experiencing the same problem and try and identify common factors that contribute to the error. It significantly impacts the productivity of the our staff using the application.

[jbprincipato]

I think I might have found a fix for the problem. I noticed that when I installed antivirus software on anther system in the office the problem with qbagent started. I disabled the antivirus software and the problem seemed to go away. I then applied the windows 2000 service pack 2 on an existing computer that was having the problem and the problem seems to have gone away without disabling the antivirus software. So I think things are corrected.

[Thomas]

I also have the pain of dealing with the Server Busy error message problem. I am running QB Pro 2000, Win98SE, on a 266Mhz PC. Dial up connection to Internet.

The only solution that works is to rename the file Qbdagent.exe to Qbdagent.old. That will work until you need to run payroll. Then you have rename the file back to Qbdagent.exe.

Has anyone seen any sort of permanent fix for this error?

I am beginning to wonder if this problem is related to slower PCs. Does anyone with a faster PC or network say 500 Mhz and above have this problem?

Its very frustrating.

[jasoncpa]

I don't know how helpful this will be to anybody, but I too was extremely frustrated by the server busy problem until........... I got a new computer! Not that I'm letting Intuit off the hook; I still think they have a bug to address. But, going from a Pentium (I), 133 mhz, 48 MB ram to a Pentium III, 1.0 ghz, 512 ram (and reinstalling all software, which could be the fix right there) the problem has not come back. For anybody with an older computer who may need to upgrade anyway, I recommend this course to try to fix the problem.

[Thomas]

After you reinstalled the software, did you then reinstall the maintenance upgrades to the latest release. The Server Busy problem does not appear with the base system, the problem only occurs when you apply the maintenance releases.

If moving up to a faster PC is truly a solution, at least I'll have another reason to upgrade my machine.

Please advise.
Regards,
Tom

[red_hair_swede]

Hello,

I am using QuickBooks Pro 2000.
System is a very speedy PIII 850 with 512 Meg of memory, and very fast hard drives.

Operating system is Windows XP Professional.

I wanted to be up to date, so I recently downloaded from Intuit all the maintenance releases for QB Pro 2000, and boom, delays all over the place: on startup, on exit, and really annoying, whenever I wanted to create some new item or edit something.

First, the speed of the machine is NOT the issue.

The issue is the maintenance releases for QB Pro 2000. If you do not do them, you will not have a problem.

If you do install the maintenance releases, then QBDAgent will hog your CPU cycles to death.

This information was gathered after a Web search, in which I found the following item:


Beitrag aus Forum McAfee ASaPFAQ, Knowledge Base zu den McAfee ASaP Produkten zurück zur Beitrags-Übersicht
Beitrag Datum Autor
Poor performance or system hangs running QuickBooks 2001-12-10 00:00:00 n/e
Summary: After installing VirusScan ASaP on a system running QuickBooks 2000 the system becomes very slow or hangs. The program QBDagent.exe checks the Intuit website constantly for upgrades and this program conflicts with myAgtSvc and the result is high CPU utilization. Solutions: There are 2 possible fixes for this problem. 1. Upgrade to QuickBooks 2001 (while Intuit software that publishes QuickBooks does not admit that they cause the problem, they fixed it in their next version.) On the down side, this is not a free upgrade! 2. Rename the QBDagent.exe file. Before you do this ask if they are having Intuit doing their payroll (if Intuit is doing their payroll they will need to have this program running.) QBDagent.exe is located in the QuickBooks folder in Program Files and to disable it both the file name and extension must be changed. It is now QBDagent.exe you can change it to XXXagent.xxx (or something like this) to disable it.


_____________

I changed the QBDAgent.exe file as described, and magically no delays any more.

But don't try to get payroll updates, QB Pro 2000 will crash.

Hope this helps.

[jasoncpa]

Hmmm. Let me think about the chain of events.

I am not sure when QB 2000 automatically updated, so I am not sure when maintenance releases would have been applied.

AND, I upgraded most of my clients to QB 2001 shortly thereafter.

My apologies, maybe the solution is upgrading to QB 2001???

If that is the case, then Intuit does it again.

[Thomas]

This is the first time I have heard that upgrading to the newer version actually solves this problem. In fact, I was considering upgrading, but thought I read on the message board in the Quickbooks site that the upgrade to QB 2001 did not solve the problem.

I also assume that upgrading to version 2002 skipping 2001 would also solve the problem if the upgrade is a true fix.

I would upgrade immediately, if I could be certain that it would fix this problem. I use the Payroll function and it is a nightmare everytime I run it because of the constant server busy error messages.

Can anyone verify that version 2001 and/or 2002 truly fix this problem?
Regards,
Tom

[jasoncpa]

I think I also read somewhere that upgrading didn't solve the problem.

I have also read (including a comment above) that the speed/ability of the computer didn't make a difference.

But, for me, some combination of a new computer and upgrading to QB 2001 seems to have solved the problem. It is nice to have all new "stuff", but I would hate to see you pay for all new "stuff" and have the problem persist.

I remember how agonizing the problem was. Perhaps getting a new computer out of the deal is worth taking the chance that it will fix the problem???

Good luck.

[derekdcosta]

QB locking machines...

A hot system is not the answer.... QB has made my 1.4Ghz, 256 MB Ram, 40GbHDD 32Mb AGP all singing all dancing machine work like a snail in glue! It's very annoying.

I am running QB 2001 Pro, not running qbagent (disabled in startup options) and despite shutting down ALL TSR programs including Norton Anti Virus the problem persists.

I am convinced this problem is related to QB's integration with the web browser as you will notice the loss of system resources every time you open any of the Centres or reports windows. ( Use windows Resource Meter in System tools to monitor the use of resources)

Eeesh! Somebody convince me otherwise....Pleeease

[Thomas]

I recently did upgrade to version QB Pro 2002 from QB Pro 2000 and I am no longer experiencing the problem. Got an excellent price from Amazon.com and with the $100 rebate, the expense was well worth it!

[SunSoft]

The issue stems from within QB - it apparently hangs in memory long after it is closed, and is tied in with it's looking for an internet connection. In addition to disabling QB Agent, turn off the automatic update feature also. The only thing that I've managed to figure out is don't be connected to the net or have your browser open and close you QB co file before closing QB.

I have Pro 2002, run Windows 2000 Professional, have a pentium III running at 933 and use Netscape not IE that QB seems to love .

[bsndigital]

How do you disable the QB Agent so that it doesn't startup with windows?