filePro on terminal Services

[Kenneth Brody]

On 4/9/2012 9:17 AM, Ian Wood wrote:
> 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.
>
> Here is the relevant parts of the email I received from my Network Admin.
>
>   *******
>
> 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.
>
>
>
> When this happens all the users on that server come to a halt/crawl.
>
> * *
[...]
>
> 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?

Well, my first question in a situation like this would be "what happens if 
you run it at the server itself, rather than on the server via terminal 
services?"

In a later e-mail you mention this is a quad-core system.  Is dclerk pegging 
only 1 core, or all 4?

Also, what does "doing the indate induction process" involve?  What is the 
dclerk that's pegging the CPU at 100% doing?  Is it some involved 
CPU-intensive processing, sitting there waiting for user input, or something 
in between?

-- 
Kenneth Brody