We notice that if Shiprush is running in the background and a user closes their instance of QB, the QB process continues to run (the interface is closed, no errors). Sometimes it runs for hours, sometimes just a few seconds before closing. If Shiprush is not running, we do not see this behavior.
I'm wondering if there is a setting in either QB or Shiprush that is causing this. We run both in a client/server environment so shiprush and QB are both clients accessing the database on another server (although this also occurs if we run both clients on the actual DB server as well, its the same server).
Any insight?
I'm wondering if there is a setting in either QB or Shiprush that is causing this. We run both in a client/server environment so shiprush and QB are both clients accessing the database on another server (although this also occurs if we run both clients on the actual DB server as well, its the same server).
Any insight?