Hi everyone
I'm running remote desktop based WYSE thin clients with server-based application access and have been noticing that the winword.exe process on occasion refuses to die and just sits there using around 25% CPU even when the program has ended. If I don't manually kill it other winword.exe processes follow suite over the day and suddenly I have Word using 100% of the CPU.
I've done a fair number of hours research on this issue today and I can tell you the following information:
* I am running Office 2003 Professional with optional 2007 conversion pack.
* I am not running Outlook (it's not even installed)
* The server has twin 1.6GHz Twin Xeon CPUs
* The server has 16GB of RAM
* When the winword.exe service doesn't go rogue on me the 67 thin clients work effortlessly so RAM and CPU are not wanting.
* the version of Word 2003 is (11.5604.5606)
* I run McAfee VirusScan Enterprise 8 in the background and have scanned with SpyBot so I doubt it is anything nasty (except perhaps erroneous code.)
Any help would be appreciated
Cheers
Anthony
- Follow via:
- RSS
- Email Alert
Question
0
Votes
winword.exe process won't die without assisted euthanasia
Updated - 13th Mar 2008
Answers (2)
0
Votes
Have you
read this. Do you have outlook installed on the server. Did you have this problem before installing the conversion pack.
http://support.microsoft.com/kb/211443
http://support.microsoft.com/kb/211443
13th Mar 2008
Replies
Yes I've read that but it doesn't apply to me - different problem, different package version. No outlook. I've been running conversion pack since it came out without any issues. This is related to Remote Desktop I think and Word not shutting down correctly. I cannot replicate the problem outside a Remote Desktop environment.
Anthony Rice
17th Mar 2008
like we have another first. All that I can suggest is to double check your setup.
There is no reference to your particular problem to be found. I also haven't worked with WYSE thin clients. If you are in a school environment I would be checking your users profiles.
http://grox.net/doc/security/nt_system_policies.txt
There is no reference to your particular problem to be found. I also haven't worked with WYSE thin clients. If you are in a school environment I would be checking your users profiles.
http://grox.net/doc/security/nt_system_policies.txt
Jacky Howe
17th Mar 2008
0
Votes
Windows Service to kill long running process
This Windows Services searches for WINWORD.EXE processes that have been idle and kills them, freeing up memory and helping your application get back on track. You can configure the interval that the service will search for processed to kill and the Maximum amount of time the process is allowed to run (Example: Check for WINWORD.EXE processes every 10 mins and kill them if they have been alive longer than 20 mins.)
http://www.spikesolutions.net/ViewSolution.aspx?ID=d288b399-24e0-4942-8ac4-2f78eda45469
http://www.spikesolutions.net/ViewSolution.aspx?ID=d288b399-24e0-4942-8ac4-2f78eda45469
28th Jun 2008
Replies
PsKill v1.12
PsList v1.28
By Mark Russinovich
http://technet.microsoft.com/en-us/sysinternals/bb896683.aspx
PsList v1.28
By Mark Russinovich
http://technet.microsoft.com/en-us/sysinternals/bb896683.aspx
Jacky Howe
28th Jun 2008
