In small companies, one thing that I have often run into with client-server accounting systems is that
a machine will lock up while running some process (like posting a batch). Then the user will
go to another machine and try the same process. That machine will lock up and the user will
continue to repeat this process until all licenses for the product are used up. I think
this is the same person that keeps pressing the “print” button in Word when the first
copy does not print.
After a tech support call to Great Plains, I was given the following instructions:
DISCLAIMER: Use this process at your own risk and only when you are sure that all users
are unable to login to the system normally.
This process is not for all situations, but when you get in a bind, it may help you out.
Steve Jones
February 2001
DatabaseJournal.com publishes relevant, up-to-date and pragmatic articles on the use of database hardware and management tools and serves as a forum for professional knowledge about proprietary, open source and cloud-based databases--foundational technology for all IT systems. We publish insightful articles about new products, best practices and trends; readers help each other out on various database questions and problems. Database management systems (DBMS) and database security processes are also key areas of focus at DatabaseJournal.com.
Property of TechnologyAdvice. © 2026 TechnologyAdvice. All Rights Reserved
Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.
