Kbase P179504: _progres via telnet session on Windows server is taking up all cpu
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  15/02/2011 |
|
Status: Unverified
SYMPTOM(s):
_progres via telnet session is taking up all cpu
Telnetting to a Windows server
Task manager shows three executables taking up cpu
Executables utilizing all the cpu are: _progres.exe, conhost.exe, and csrss.exe
FACT(s) (Environment):
Windows Server 2008
Windows 7
OpenEdge 10.2x
Turning off FastCursorMode off does not help
Running telnet without launching _progres does not cause CPU to spike
Running _progres without telnet does not cause the CPU to spike
CAUSE:
Known issue. _progres client receiving invalid handle.
FIX:
Change the owner of the telnet service from "localservice" to Local System Account and reference the following tech web page:http://technet.microsoft.com/en-us/library/cc754102%28WS.10%29.aspx
Follow the steps under section: To use the Local System security account to run Telnet