We are having an issue with dclerk maxing out the CPU usage and bring the server to a halt when running through Microsoft Terminal Services. <br><br>Here is the relevant parts of the email I received from my Network Admin. <br>
<br> *******<br><br>
<p class="MsoNormal">Ronkonkoma has been having problem with the new remote
application server. When users are in filepro to and are doing the indate
induction process it is causing the CPU utilization on the server to go
to 100%. There is a filepro process called DCLERK.exe that is utilizing
all of the CPU. </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">When this happens <span style="background:yellow">all the users on that server come to a halt/crawl. <br></span></p>
<p class="MsoNormal"><b> </b></p>
<p class="MsoNormal">I was on the phone with Microsoft tech support today for
3hrs to resolve this issue. We tried to limit the cpu utilization of the
DCLERK process but it didn’t work. Microsoft feels the problem is that
filepro is an older 32bit app running on the new 64bit server running terminal
servers. Microsoft is assuming that the version of filepro we are using
was never meant to run in this server environment. They recommend we
contact filepro for a solution.</p><p class="MsoNormal"><br></p><p class="MsoNormal">*******</p><p class="MsoNormal"><br></p><p class="MsoNormal"><br></p>Personally I don't believe it is a filePro issue as the program works using Citrix, but not through Terminal Services. Has anyone coam across the same issue? <br>