It is currently Fri Oct 24, 2014 10:11 pm



Reply to topic  [ 6 posts ] 
 Office Hours not responding 
Author Message

Joined: Fri Aug 03, 2007 9:34 am
Posts: 40
Post Office Hours not responding
This has been an on-going and intermittant problem with Medisoft and Office Hours for a few years (and a few versions) in our office. There are usually one or two computers on the network that are unable to run office hours. It got so annoying I wrote a small program that is basically a stripped-down clone of Office Hours. The clone program can flawlessly retrieve information from the database under all circumstances... on any machine, at any time, without fail. This always indicated to me that, on misbehaving machines, it is not a network or database issue, but likely either a local machine-specific settings issue that conflicts with Office Hours, or an Office Hours/Medisoft coding problem. If Office Hours is incompatible with certain Windows XP settings, I might again lean towards this actually being a Medisoft coding issue. Sometimes a full uninstall and reinstall will get things working for a while, but the \"gremlined\" machines will usually revert to being disfunctional sometime down the road.

Through a little investigation, I've found a way to get the programs to operate correctly (until the next time they decide to go south). Maybe this would be of some value to the Medisoft development team...

If you start the Office Hours application, it will successfully get beyond the splash screen, then open the main (full-screen) window. The main window will partially paint and then freeze. The usual result is an Office Hours window that displays the window title and the remainder of the window is white. Sometimes the top menu bar, or some of the tan background shading will paint before the application locks up.

Watching the events above as they occur via Windows Task Manager reveals some additional information. Initialy, one \"Office Hours\" task in created and it is hooked to a single \"OHP.exe\" process. Just before Office Hours hangs, a second \"Office Hours\" task starts, this one is linked to the main \"explorer.exe\" process (your desktop!).

I believe, in Task Manager, the mechanism that allows you to \"End task\" from the Applications tab, and the method used to \"End Process\" from the Processes tab, work in a much different manner. \"End Task\" being a fairly civilized shutdown of an application, and \"End Process\" being a crude blow-it-out-of-the-water process kill.

There are two tasks and two processes you could potentially terminate.
If you end either Office Hours task, the one hooked to the OHP.exe process, or the one hooked to the explorer.exe process, Office Hours will eventually terminate, and generate a \"hungapp\" error via Windows Error Reporting. If you kill the OHP.exe process, the same result manifests. So, three of the four possibilities for zapping the hung program behave the same, and all LEAVE OFFICE HOURS INOPERATIVE ON THE PC.

I believe the \"civilized\" nature of \"End Task\", checking dependencies, etc, prevents you from actually killing your desktop when you select to end the task attached to explorer.exe, and instead it kills the actual OHP.exe process and doing that releases the link to explorer.exe.

Here is the interesting part...
If you instead do the fourth option, the odd choice of killing the explorer.exe process (your desktop) while the OHP.exe task is hooked to it and hung up, the following occurs:
Your desktop goes bye-bye, no more icons, no taskbars, no start menu. Your PC is not very useful at this stage, and your only recourse is to do a \"restart\" via the still open Task Manager. Strangely, after the reboot, OFFICE HOURS IS FIXED. It will start normally, repeatedly, and appears to work perfectly. Something is being unregistered, or cleared from the registry, or something reset when forcing the desktop to close while OHP is hooked to it and hung up. Maybe I'll do a before and after comparison of the hives while performing this \"fix\" on one of our bad machines, or see if any cfg or ini files change, or...

Anyway, at this point I do have a crude fix to employ when Office Hours (or Medisoft) decides to stop running on one of our machines.

What do you think???


Fri Jan 08, 2010 11:18 am
Profile

Joined: Fri Aug 03, 2007 9:34 am
Posts: 40
Post 
Grr... the last 2 paragraphs of my prior post were truncated (pretty tight restictions on post size?). I guess the gist of my post got through...

Anyway, at this point, I do have the crude fix posted above to employ when Office Hours (or Medisoft) decides to stop running on one of our machines.

What do you think???

PS - I did find a few links elsewhere on the web that appear to indicate there are others that experience this same problem, such as this recent post:
Medisoft and Office Hours Freezing


Fri Jan 08, 2010 11:26 am
Profile
User avatar

Joined: Wed Apr 04, 2007 9:11 pm
Posts: 2639
Location: Springfield, MO
Post 
Interesting find. I'll have to give that a try the next time I see this.

I have suspected for a long time that an incompatibility with how the .NET Framework is installed causes this. Uninstalling or installing Windows XP SP 3 can fix this.

There are apps that are known to be incompatible with Medisoft. For example McAfee Antivirus and some instant messaging software.

_________________
Gavin Walker
MedTech Medical Management Systems
417-890-6777


Fri Jan 08, 2010 3:00 pm
Profile WWW

Joined: Fri Aug 03, 2007 9:34 am
Posts: 40
Post 
Well, it is a short-lived fix.
A few more reboots and over the weekend, and one of our problem machines reverted.

That method does indeed work though, at least for the next session, and gets Office Hours up and running. So, although it is by no means a permanent fix, I think it may be useful for debugging the issue. I'm going to do a bit more sleuthing and see if I can determine any differences in the environment when comparing a normal PC startup, and one following a forced desktop crash while OH is hung up.


Mon Jan 11, 2010 11:38 am
Profile

Joined: Tue Apr 13, 2010 8:35 am
Posts: 14
Location: Orlando, FL
Post Re: Office Hours not responding
I hate to take over this thread, but is there any permanent solution to this issue yet? It mainly happens on our terminal server (we have about 80 clients that use Medisoft remotely on our TS) and our clients have been extremely annoyed by the OH hanging issue (it even happens with Medisoft sometimes). We upgraded to version 15 from 11 late last year and it has been nothing but trouble for us. Most of our issues can't even be fixed by Medisoft themselves.


Thu Apr 15, 2010 2:19 pm
Profile E-mail WWW
User avatar

Joined: Wed Apr 04, 2007 9:11 pm
Posts: 2639
Location: Springfield, MO
Post Re: Office Hours not responding
Hi Sam, unfortunately Medisoft does not directly support Terminal Server, so your best bet is to work with a Medisoft VAR who does. I am not sure if your issue is related to this thread or not. Can you start a new thread including details of what users were doing when Office Hours hangs? Most Office Hours issues I have seen are related to appointments that do not occur within the appointment window boundaries setup within Program Options.

For example, you have an appointment that starts at 7:59am but the appointment window is from 8am to 5pm.

Or, you have a 159 minute appointment, but your minimum appointment time period is set to 15 minute increments.


Thu Apr 15, 2010 3:48 pm
Profile WWW
Display posts from previous:  Sort by  
Reply to topic   [ 6 posts ] 

Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by STSoftware for PTF.