Then, when we try to start it again, QB comes back and says that it sees the database and the computer where the DB lives, and that the database is on a machine set up to share, but the client machine cannot communicate with the database machine. No good reason why. (Oh .. and Yes, we have run the Quickbooks 'tools' - if you can call them that)
What a PAIN in the ASS!
I have pretty much determined that the issue is related the the FACT!!! that Quickbooks does not terminate, gracefully. In fact, it does not terminate at all - even when you exit. After exiting - an image can still be found in TaskManager.
The solution I have found is:
On the Client Machine:
. KILL QBW32.exe in TaskManager
. In Services, stop both QBCFMonitorService and QBIDPService
On the Database Machine:
. KILL QBW32.exe in TaskManager (which is left over from yesterday!)
. In Services, stop both QBCFMonitorService and QBIDPService
. In Services, start both QBCFMonitorService and QBIDPService
On the Client machine:
. In Services, start both QBCFMonitorService and QBIDPService
. Start Quickbooks and then log into the database
On the Databse Machine:
. Start Quickbooks and then log into the database
Amazing. We have to go through this exercise almost every day.