Hosted QB Issue (Super hard to troubleshoot)

thecomputerguy

Well-Known Member
Reaction score
1,435
I have a client who uses an inventory program that interfaces with QB. So the hosted environment contains their database for the QB and their inventory system.

Server 2008 R2
Users Remote in through RDP & RDP for Mac

I get intermittent calls from them saying their QB went black. I login and see this. It seems to occur all by itself or when closing.

attachment.php


You can't do anything as the user, you have to login to the server and kill the QBW32.EXE process for that specific remote user. They can then login and use QB normally.

attachment.php


Sometimes this is daily, sometimes they can go a week without having the issue.

I called the Hosted company, they wont take responsibility for it, I dread calling QB, tried googling, but not even sure what to google for.

I've tried at least 5 times to teach someone how to logout of a user and login as the admin on the server to kill the process themselves but they can't remember.

They have 2 users, both have the same problem, I've tried creating a new user and the new user also has the same issue.

Haven't re-installed QB
 

Attachments

  • qb issue.jpg
    qb issue.jpg
    12 KB · Views: 154
  • qb2.jpg
    qb2.jpg
    21.9 KB · Views: 151
Last edited:
Looks like a video issue. Is it similar on the actual server monitor? Has anyone tried f5 to refresh the screen when this happens?

Rick
 
^ This. Also, I'd check to see if they are logging out properly at end of day or leaving hung sessions. Windows gets finicky when sessions are left hung for too long. You also could mess with the session timeouts if you wanted...but usually user education is the better bet if you can manage it.

Properly logging off takes care of removing the processes that are hung...but it sounds like they are all clicking the "x" in order to log off.
 
You could. But the root cause of the issue (if it is that users are not logging off properly) is not fixed. I've seen this cause all sorts of weird issues in TS sessions. All of them resolved by logging the user off and logging them back in again. It's just simple user education...but I have to admit...there are some companies and clients I work with that are like pulling teeth with this. The struggle is REAL.
 
Back
Top