A
Al Williams
Guest
Server 2003 Standard TS, SP2, all patches.
We had a situation the other day where one TS user was unable to run a
particular (older) application effectively - it was very slow to load and
pretty much unusable. Other TS users had no issues with this same app, just
this particular user and logging out and then back into the TS did not help.
I monitored the program in question with Process Explorer and all I saw was
a long "wait.executive" pauses in various DLL's the program uses -- I
checked another TS user but didn't see those pauses.
In the end I rebooted the terminal server and the one users issue went away.
What I can't figure out is why, it seems to me when the user logs out all of
his session information is destroyed so he should start fresh. I had
checked temporary files but this older application doesn't really use them
AFAIK.
Any ideas on why the reboot fixed it or what I should look for next time?
(this has happened before to another user)
Thanks.
--
Allan Williams
We had a situation the other day where one TS user was unable to run a
particular (older) application effectively - it was very slow to load and
pretty much unusable. Other TS users had no issues with this same app, just
this particular user and logging out and then back into the TS did not help.
I monitored the program in question with Process Explorer and all I saw was
a long "wait.executive" pauses in various DLL's the program uses -- I
checked another TS user but didn't see those pauses.
In the end I rebooted the terminal server and the one users issue went away.
What I can't figure out is why, it seems to me when the user logs out all of
his session information is destroyed so he should start fresh. I had
checked temporary files but this older application doesn't really use them
AFAIK.
Any ideas on why the reboot fixed it or what I should look for next time?
(this has happened before to another user)
Thanks.
--
Allan Williams