Microsoft Access hangs on PcHelpware Server.

[rgary]

I am running a PcHelpware Viewer on Windows Vista. My customer has the PcHelpware Server running on Windows 2000 sometimes, Windows XP other times.

After we make a PcHelpware connection, if I start Microsoft Access (either MS Access 2000 or MS Access 2003) on the PcHelpware Server computer, MS Access starts/runs normally, but when the MS Access window is closed, Windows Task Manager on the PcHelpware Server computer shows that msaccess.exe is still running in the background. On the PcHelware Server computer, even after closing-down the PcHelpware Server software, the msaccess.exe process on that computer continues to run until manually killed using that computer's Task Manager.

However, once PcHelpware Server is exited on the PcHelpware Server computer, starting/exiting a new Microsoft Access instance on that computer works as expected, with the msaccess.exe process automatically terminating after closing the MS Access window.

Any ideas on what might be causing this behavior when using PcHelpware? This problem does not occur when I use other remote control software to remotely-control these computers. --Thanks!

[YY]

I can't explain why this happen, just want to confirm that I can repeat this problem.

In my test, once the MS Access ghost process is running, even you terminate the PcHelpWare connection and then start & shut down the MS Access again, the ghost process keep on running at background.

[SuperTurtle]

Are you sure that this msaccess.exe running problem is a result of using pchelpware? I use PCHW with remote users of my software (ms access – runtime), and I not seen this problem at all (I using access 2003).

Do note that there are some known bugs that will prevent ms-access from closing. (this bug was from access 97, and is fixed in later versions however). Any chance you talking about access 97? Here is the kb article:

http://support.microsoft.com/kb/164455/en-us

Super Turtle

[YY]

I'm using Access 2003 under Windows XP SP2 with full patches.

I have the same problem as rgary reported, and I don't think my situation is that issue mentioned in the link to MS you provided.
In that article, the issue is Problems Quitting Microsoft Access

In my test result, the Access can close & quit normally in appearance, but actually the process is stilling running in background.

No matter what causes the problem, I found this happened only if starting Access when PcHelpWare is connected.

[SuperTurtle]

Ok, just it was just a thought on my part (I have known about that access 97 bug for a long time). Since you using a2003, then of course that bug does not apply.

I not seen, or heard of this problem, and I spend a lot of time in the ms access newsgroups.

However, I just tried this, and yes…the copy of ms-access stays in memory does not un-load. (and, I just tested this with the runtime of ms-access). And, yes, each time I launch the application, and quit, another copy of ms-access remains in memory. So, if you launch, and then exit 5 times, you will see 5 copies of ms-access.exe in the task manager.

I suspect there are other programs in the office suite that would also suffer from this problem. (perhaps word, or outlook for example).

And, I just tried this on a CLEAN windows xp install (under virtual), and once again without any other parts of office installed except for the ms-access 2003 runtime, the problem again occurs.

Anyway, certainly a strange problem, and it is perplexing that ms-access would suffer from this problem, and not other programs (perahps they do, we just not noted this). Sounds like some resources can't be released by windows once PCHW is running.

Anyway, this behavior is 100% confirmed.

Super Turtle