Slow Opening of Word Documents

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a customer with two servers - one SBS 2000 and one Windows 2003 server
running as an application server TS server. Everything has been going well
until Friday. On Friday, the thin client systems running on the network have
a problem opening Word documents that are stored on the SBS 2003 server. The
PCs running RDP work fine. What happens is that the thin client system tries
to open any Word document that is stored on the SBS system. The file
eventually opens - it may take 25 minutes, but it opens. If the file is
copied to the "My Documents" folder for the thin client session and then
opened from there, it opens immediately. If I do the same thing from a PC
running RDP, everything works correctly. The problem only exists on the thin
client. Any ideas what can be causing the problem? I have checked security
and permissions, but this would prevent the file from opening - not delaying
it. The thin client and the PC are both connected to the same physical
network switch.

Thank you,

Joe Burns, Vice-President
CompuGeek Division
TOMAR Computer Integration, Inc.
 
Hi Joe. I'll take a stab at this. If I understand you correctly, opening up a
Word Doc from the SBS server, which is a domain controller and a file server
and possibly an Exchange server and or SQL server is having a hard time
delivering a file to a thin client's TS session on a Teminal server in the
domain. Perhaps it's a Wyse Terminal or something other kind of thin client?

So the question we could ask is "What does your PC have that the Thin client
does not?
Do I have that right? /:>
 
If the document resides in the company folder on the SBS server, then it
takes about 25 minutes to open. If we move the document to the TS server, it
opens instantly. A PC running RDP apparently has no problem while the Wyse
terminal (or whatever brand it is) has major problems. Since both instances
are really creating virtual computers on the TS server and running everything
from the TS server, there should be no difference.

Joe Burns
 
Soulds like the profile for that session is bloated and needs to be cleaned
out.

Try UPHCLEAN.

UPHClean can run as an application or a service. For your TS servers, it's
convenient to install the service and let it run continuously. The tool will
initially scan for open Registry resources and force them closed. Then it
will continue running and fixing in the background. You can find UPHClean on
the Microsoft Web site. Look for Knowledge Base article 837115.
 
Thanks for the input. I am not sure if this is the problem, but it can't
hurt. I have downloaded the tool and installed it. We'll monitor the
situation to see how things go.

Thanks,

Joe Burns
 
Back
Top