prw.exe has stopped working

Posts related to Medisoft Clinical go here. You should consult with your Medisoft Clinical VAR if you are unsure about any configuration changes suggested here.
Post Reply
Chris_S
Posts: 3
Joined: Wed Oct 05, 2011 3:09 pm

prw.exe has stopped working

Post by Chris_S » Fri Oct 07, 2011 3:06 pm

Clinical 9.5 error where application will not launch. Server 2008 terminal server and 2008 database server.

prw.exe has stopped working
Description:
Stopped working

Problem signature:
Problem Event Name: APPCRASH
Application Name: prw.exe
Application Version: 9.5.1270.0
Application Timestamp: 4d5201ba
Fault Module Name: prw.exe
Fault Module Version: 9.5.1270.0
Fault Module Timestamp: 4d5201ba
Exception Code: c0000005
Exception Offset: 00341f40
OS Version: 6.1.7601.2.1.0.16.7
Locale ID: 1033

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

Re: prw.exe has stopped working

Post by Gavin Walker » Sun Oct 09, 2011 3:28 pm

Makes sure all the PMSI services are running on the server and drive letter P: is still mapped.

User Account Control should be disabled on all computers.

Edit \Program files\McKesson\Practice Partner\PPUser.ini and enter this:
[ENVIRON]
SharedExeDir=Yes

I hope that helps!
Gavin Walker
Walker Tek Solutions, LLC
417-890-6777 x0
fax: 417-763-6386

Chris_S
Posts: 3
Joined: Wed Oct 05, 2011 3:09 pm

Re: prw.exe has stopped working

Post by Chris_S » Mon Oct 10, 2011 11:26 am

Gavin,
PMSI services are running on the db server.
UAC disabled
PPUser.ini already had SharedExeDir=Yes

If I delete the users profile from the terminal server when they get the prw.exe error, they are able to run clinical after their profile rebuilds.
I have tried adjusting the ts session settings with no different outcome.

Chris

Chris_S
Posts: 3
Joined: Wed Oct 05, 2011 3:09 pm

Re: prw.exe has stopped working

Post by Chris_S » Mon Oct 10, 2011 11:28 am

Also, P: is mapped through logon script.

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

Re: prw.exe has stopped working

Post by Gavin Walker » Mon Oct 10, 2011 3:32 pm

Try reinstalling through the Control Panel applet - Add Terminal Server App. Make sure users have Write rights in the application installation folder.

malanois
Posts: 4
Joined: Wed Jun 13, 2012 7:54 am

Re: prw.exe has stopped working

Post by malanois » Wed Jun 13, 2012 8:05 am

I have the same issue. Has anyone found out what causes this and how to resolve it?

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

Re: prw.exe has stopped working

Post by Gavin Walker » Wed Jun 13, 2012 8:28 am

There are many issues that cause this. One possibility is a corrupt database. You can use the CTGUI utility to rebuild the database, but you might also have to do a reindex. Be sure to make a backup before using these utilities.

malanois
Posts: 4
Joined: Wed Jun 13, 2012 7:54 am

Re: prw.exe has stopped working

Post by malanois » Wed Jun 13, 2012 8:32 am

Ok... let me give you some more detail and maybe it will help you to help me.

I only get this error for users that are using terminal services (RDP). The user will run fine for an undetermined amount of time (days, weeks) then this problem crops up. It does not affect all users, only one at a time. If I create a new remote user, the new user works fine while the old user still has the error. If I delete the old user and set it back up, works fine. There seems to be not correlation between user settings and this error. I'm at a loss.

Is it a Microsoft issue or a Medisoft issue? Even knowing this would help.

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

Re: prw.exe has stopped working

Post by Gavin Walker » Thu Jun 14, 2012 11:12 am

Here is a cause that may fit your situation:

If session printers, auto-created or redirected printers are present in a Terminal Services environment, and the total character count in all printer port names in registry key HKCU\Software\Microsoft\WindowsNT\CurrentVersion\PrinterPorts exceeds 5000 characters, prw.exe and textload.exe will terminate on a memory overflow error (or just hang on startup).

Here are the versions of Practice Partner that are affected:
9.5.1 and lower - issue resolved in the 9.5.2 Beta release

Solution:
Resolving this issue involves editing the Windows registry. PROCEED WITH CAUTION - removing the wrong keys from the registry will cause irreparable damage to the operating system. If you are unsure how to safely proceed, contact your McKesson Value Added Reseller for assistance.

1. Open the Windows registry editor - go to Start > Run, then type regedit.exe and click OK.
2. Navigate to HKEY_CURRENT_USER\Software\Microsoft\WindowsNT\CurrentVersion\PrinterPorts
3. If there are hundreds of printer port names for redirected, auto-created or session printers, determine which keys can be safely deleted

4. Change the settings in Terminal Services Configuration so sessions printers are no longer created
A. Server 2003, Server 2003R2:
  • Go to Start > Administrative Tools
    In Terminal Services Configuration, click on 'Connections'
    Right-click on RDP-Tcp, go to Properties
    Select Client Settings
    Select the boxes to disable Windows printer mapping
B. Server 2008, Server 2008R2:
  • Go to Start > Administrative Tools > Terminal Services > Terminal Services Configuration
    Under the Connections section, right-click on RDP-Tcp, select Properties
    Select Client Settings
    Under Redirection, check the boxes to disable Windows Printer and Default to main client printer

malanois
Posts: 4
Joined: Wed Jun 13, 2012 7:54 am

Re: prw.exe has stopped working

Post by malanois » Fri Aug 10, 2012 8:39 pm

I just want to say... this worked!!! Thanks a million!!!

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

Re: prw.exe has stopped working

Post by Gavin Walker » Mon Aug 13, 2012 8:16 am

Just curious, did you load Practice Partner v9.5.2 or edit the registry to correct this?

malanois
Posts: 4
Joined: Wed Jun 13, 2012 7:54 am

Re: prw.exe has stopped working

Post by malanois » Tue Aug 14, 2012 7:38 pm

I edited the registry. The practice I am working with has a different vendor supporting Medisoft so I am trying to get the client to request the update. They refuse to believe this is a Medisoft issue since their Medisoft vendor told them it wasn't. So, they are pushing me to fix the issue. I did have one RDP client start having the PRW.EXE error again today. I checked the registry and deleted a few entries like before (actually deleted a lot just trying to get it to work) but this time it just wouldn't work. The other RDP clients have been working fine since the registry edit. When I launch Clinical it is version 9.5.1 so I assume that is the version which displays this problem.

I think I'll be contacting Medisoft to inquire of their reseller program. :D

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

Re: prw.exe has stopped working

Post by Gavin Walker » Wed Aug 15, 2012 9:04 am

Any version of Practice Partner on v9.5.1 and prior can exhibit this problem in a remote desktop server environment. I think now we know the cause, work around, and solution to your problem!

Post Reply