filePro on terminal Services

[Ian Wood]

I am checking on that right now, and I forgot to mention the version
filePro we are running, it's 5.0.14, obviously on a Windows network.

Windows 2008 R2
   (Server Standard Edition (full installation))



On Mon, Apr 9, 2012 at 9:25 AM, Steve Wiltsie <swiltsie at micro-mui.com>wrote:

> Ian,
>
> I have clients using filePro on a Windows 2008 R2 Terminal Server with
> no problems - actually it is faster than running it from a Windows PC.
> There has to be something else or something in the processing tables
> that is causing this.  Unless, of course, the terminal server is way
> underpowered as far as RAM or CPU is concerned.  I'm assuming this is at
> least a 4 core Xeon system with at least 8GB of RAM.
>
> Steve Wiltsie
> microCONCEPTS
>
> > -----Original Message-----
> > From: filepro-list-bounces+swiltsie=micro-mui.com at lists.celestial.com
> > [mailto:filepro-list-bounces+swiltsie=micro-
> > mui.com at lists.celestial.com] On Behalf Of Ian Wood
> > Sent: Monday, April 09, 2012 8:18 AM
> > To: filepro-list at lists.celestial.com
> > Subject: filePro on terminal Services
> >
> > 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.
> >
> > * *
> >
> > 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.
> >
> >
> > *******
> >
> >
> >
> > 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?
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> > URL: http://mailman.celestial.com/pipermail/filepro-
> > list/attachments/20120409/a9900bad/attachment.html
> > _______________________________________________
> > Filepro-list mailing list
> > Filepro-list at lists.celestial.com
> > Subscribe/Unsubscribe/Subscription Changes
> > http://mailman.celestial.com/mailman/listinfo/filepro-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20120409/fce6385b/attachment.html