Kbase P110442: The prowin32.exe process takes 100% CPU when an r-code is not found
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/2/2005 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge 10.0B
Windows XP
SYMPTOM(s):
prowin32.exe takes 100% CPU when an r-code is not found
The Progress session hangs when an r-code is not found
The problem only happens when Microsoft Office 2003 is installed
The problem only happens when Microsoft Error Reporting Tool is enabled
Sysinternals Filemon shows that the session hangs after dwwin.exe is called (Dr. Watson which is used by the error reporting tool)
CAUSE:
This is not a Progress issue, but a Microsoft issue. The Microsoft Office 2003 installation apparently updates the Microsoft Error Reporting Tool. This new version of the Microsoft Error Reporting Tool causes a hang when it attaches to the prowin32.exe process.
FIX:
Contact Microsoft for further support.
- OR -
Try one of the following workarounds:
- Install the latest Service Pack for Microsoft Office 2003.
- On Windows XP with Office installed, try to disable the Windows Error Reporting *only* for Office.
Please take a look at the following document http://www.personal-computer-tutor.com/abc4/v35/vic35.htm for further details.
- Completely turn off the Error Reporting Tool on the PC which has Office installed.
Please take a look at the following website for the steps: http://www.iamnotageek.com/a/91-p1.php .