Access violation ohp.exe V16

Technical problems with Medisoft.
Post Reply
Marty
Posts: 10
Joined: Tue Jan 25, 2011 2:52 pm

Access violation ohp.exe V16

Post by Marty » Tue Jan 25, 2011 3:03 pm

When I save a copayment using Office Hours Pro V16, I receive the following: Access violation at address 00404D68 in module ohp.exe. Read of address fffffffc.

We have been using Medisoft V16 for 7 months on a windows Vista pc with no issues. This just started today. The payments appear to be saving.

We have received our Medisoft version 17 (from MedTech), but we have not installed it yet.

Thanks in advance for any help.

User avatar
Gavin Walker
Posts: 4626
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: Access violation ohp.exe V16

Post by Gavin Walker » Tue Jan 25, 2011 4:43 pm

Hi Marty, I would download and install Medisoft v16 sp1 with hotfix. Download and install both Medisoft and Office Hours Pro.

If that doesn't clear it up, go into Medisoft -> File -> Program Options and uncheck all the Account Alert settings.
Gavin Walker
Walker Tek Solutions, LLC
417-890-6777 x0
fax: 417-763-6386

Marty
Posts: 10
Joined: Tue Jan 25, 2011 2:52 pm

Re: Access violation ohp.exe V16

Post by Marty » Tue Jan 25, 2011 4:54 pm

Thanks Gavin. I will try that and let you know

Marty
Posts: 10
Joined: Tue Jan 25, 2011 2:52 pm

Re: Access violation ohp.exe V16

Post by Marty » Thu Jan 27, 2011 5:57 pm

I already had the Service packs installed, but the issue seems to have resolved itself. If it comes back I will try changing the account alert settings.

Thanks
Marty

Marty
Posts: 10
Joined: Tue Jan 25, 2011 2:52 pm

Re: Access violation ohp.exe V16

Post by Marty » Mon Nov 28, 2011 10:58 am

The error returned at address 00404D4C. I have unchecked all the Account alert settings. I upgraded to V17 SP2 (which I had on the shelf) but the error continues. I installed V17 SP2 on a windows 7 machine (30 day trial mode) and the error shows on that machine also.
Any advice would be appreciated.

Thanks,
Marty

User avatar
Gavin Walker
Posts: 4626
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: Access violation ohp.exe V16

Post by Gavin Walker » Mon Nov 28, 2011 12:23 pm

Run the Program C:\Medisoft\Bin\MediUtils.exe and run the process "Repair Payment References". This generates a file C:\Medisoft\Bin\FixPax.log. Examine the .log file and see if there are any missing Procedure/Payment/Adjustment codes and add back into your database any that are missing. Re-Run Repair Payment References until there aren't any codes that are reported missing.

Always run a backup before running any MediUtil procedure.

Marty
Posts: 10
Joined: Tue Jan 25, 2011 2:52 pm

Re: Access violation ohp.exe V16

Post by Marty » Tue Dec 06, 2011 12:52 pm

I ran C:\Medisoft\Bin\MediUtils.exe and run the process "Repair Payment References". The following the following is an excerpt from the fixpax report (I m unable to upload a .txt or .log file):
Changed Transaction Type.
Procedure Code: CHECK
Chart Number: 00010134
Case Number: 1
Date From: 8/6/2010
Amount: -35
Units: 1
Old Transaction Type: N
New Transaction Type: K
Date Modified: 8/6/2010 6:22:48 PM

Changed Transaction Type.
Procedure Code: CHECK
Chart Number: 00010133
Case Number: 2
Date From: 8/6/2010
Amount: -35
Units: 1
Old Transaction Type: N
New Transaction Type: K
Date Modified: 8/6/2010 8:34:42 PM

Changed Transaction Type.
Procedure Code: CHECK
Chart Number: 00010132
Case Number: 3
Date From: 8/4/2010
Amount: -25
Units: 1
Old Transaction Type: N
New Transaction Type: K
Date Modified: 8/6/2010 9:02:40 PM

I ran the program a second time and it had noe errors:
Checking Pax table data integrity.

Fix Pax file to show negative guarantor and insurance paid amounts.

Insurance 1 Amount, Insurance 2 Amount, Insurance 3 Amount, Guarantor Amount, Attorney Amount and, Adjustment Amount Recalculated.
Insurance 1 Paid, Insurance 2 Paid, Insurance 3 Paid and, Attorney Paid updated.

Verify PAX entries.

Recalculating Unapplied Amounts.
Recalculating Check Numbers.

I am still receiving the exception errors. Any ideas?

Thanks,

Marty

Post Reply