winword.exe process won’t die without assisted euthanasia

  • This topic is empty.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #1047
    Avatarcybergrunt
    Member
    • Total Post: 7
    • Newbie

    Hi everyone

    I’m running 65 remote desktop based WYSE XPe S90’s 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

    #12228
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hi Anthony,

    I know this is a simple question but can you confirm that Word is running on the server not the thin client and secondly can you confirm its a terminal server back end,

    Cheers,
    -TT

    #12230
    Avatarcybergrunt
    Member
    • Total Post: 7
    • Newbie

    Hi TT, yes Word is running on the server and it is a TS backend running on a Windows Server 2003 Enterprise environment.
    Cheers
    Anthony

    #12232
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    OK, winword.exe gets hung if it can not close all the templates and add-ins correctly. Check where the normal.dot in the user profile is (server or network share). If its on the network try locating it to the server as a test. Also delete/move all the templates in the common templates folder and see if this helps as a test.

    Use a tool to check form open file handles and see if you can find which file word is waiting to close.

    Cheers,
    -TT

    #12276
    Avatarcybergrunt
    Member
    • Total Post: 7
    • Newbie

    Ah yes, I can see that now. Templates are stored on the server @ C:Documents and SettingsUSERApplication DataMicrosoftTemplates as per normal. Going through all the thin client logins I see that some of them have ~$Normal.dot files even though I know Word has closed. I have deleted these but I am unsure whether having them there is causing the issue or they are just the remnants of incorrectly closed Word sessions which I have manually killed as yet. I’m going to have to keep my eyes open to see what’s happening here. I’ll go searching for a open file tool. Thanks for your help so far!

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.