Terminal Server Session performance affected by outlook 2002

  • Thread starter Thread starter N. Okan Guney
  • Start date Start date
N

N. Okan Guney

Hello,

We have been experiencing an interesting problem. From time to time some
users experience a very slow Terminal Server session due to the Outlook
process.

The problem is so severe, that user can not even log off the session. It
looks like the computer has run out of all the memory and running at 100
percent cpu usage where it is not.

Cpu usage for the server at the time of event shows less than 5% and server
has 2GB memory where only 900 Kb used.

Remotely killing the outlook process + the word process if exists for the
specific user solves the problem. So far I can not seem to determine what's
causing the event and how to eliminate it.

Any suggestions?

Config:
RAID 5 36GB hd 24GB Free
Intel P3 1GHZ x 2
2GB Memory
Outlook 2002 Version :10.4608.4219 SP2
Windows 2000 Version: 5.00.2195 SP4
Thanks,
 
I have noticed this too, but i dont think its neccesarily only due to
outlook (i cant recall all the times its happened, probably 100+ in the last
year that i know of), some times i have to log off the user using the ts
manager, or end the explorer process as well as outlook (but i find logging
off the user or reseting the session prolongs the time between relapses).

My machine is a Dell 2650 Dual Xeon 2ghz with 2gb of ram and 4gb of virtual
mem, also uisng Office XP.

Ive just put it down to a day in the life of using TS (we have about 20
full time users and it happens a few times a week)

Im not sure if its related, but we aslo have problem here outlook times out
when trying to talk to the pop3 mail server and times when the PAB file just
refuses to be read, to fix both of them we just have to close and reopen
outlook as well. Do you have any issues like that ?

Tim Hall
 
Nope I do not have those problems since, we have Exchange server set up for
e-mails.

Here is something that might help

I have this vb script placed as an icon on user's quick launch bar, if they
realize slower speeds they just click on it and it kills outlook and word
processes. You can add explorer here to just by extending the or statement.
So far it worked successfully several times and I am thinking that's as my
best option to get around the problem. Feel free to use it.

Okan

'By Okan 8/21/03
strComputer = "."
Set objWMIService = GetObject("winmgmts:" &
"{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
Set colProcessList = objWMIService.ExecQuery ("Select * from Win32_Process
Where Name = 'WinWord.exe'or Name = 'outlook.exe' or Name = 'm2m.exe'")
For Each objProcess in colProcessList
objProcess.Terminate()
Next


'---------------------------------------------------
 
Back
Top