Options

fin.exe cpu usage on Windows Server 2003 Terminal Server

pickseedpickseed Member Posts: 14
edited 2007-03-27 in Navision Financials
We have a terminal server running Windows Server 2003 SP1.

Our version of Nav is 2.6b.

Users have been complaining that the terminal server becomes very slow at times. When I check the CPU usage, I see that there is usually 1 or 2 fin.exe processes for different users using between 30-50% CPU. So when it happens with 2 processes, the cpu is maxed out!

I have gone to see what the users are doing when this happens and most times they have either pulled up an order or generated a report and are simply looking at the screen while the process holds onto cpu time.

I have been searching everywhere for 2 days for information about this.
Is this a known issue, or has anyone at least experienced this before

The terminal server specs are:

Windows Server 2003 SP1 (Updated current to end of Feb)
Intel Xeon 2.8GHz
2GB RAM
RAID1 with 2 x 73GB 15krpm U320SCSI
GB Ethernet
Avg. user count 35

Comments

  • Options
    bbrownbbrown Member Posts: 3,268
    Have not run into this. Any customizations? Consider a technical upgrade to newer clients.

    Also 2 GB seems a bit light for 35 users.
    There are no bugs - only undocumented features.
  • Options
    ara3nara3n Member Posts: 9,256
    The recomendation from convergence is

    50-64 meg of RAM per user
    500 MEG for OS.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • Options
    bbrownbbrown Member Posts: 3,268
    Also don't forget the memory requirements of other applications the users may be running. Plus things like anti-virus. I will usually figure on 1 GB for the O/S.

    Memory is fairly cheap and it can really improve performance if your terminal server sessions are not constantly paging memory to disk.
    There are no bugs - only undocumented features.
  • Options
    pickseedpickseed Member Posts: 14
    OK, I've got 4GB of RAM ordered for the server, it should help overall performance, but I'm still not convinced that it will solve the cpu usage problem.

    I'm looking into adding a 2nd CPU to the Terminal server as well.

    Anyone else have an idea as to what could be causing the cpu spikes?
  • Options
    ara3nara3n Member Posts: 9,256
    look at task manager. In the processes tab check Show processes from all users. Sort if by CPU and you'll see what processes take the most time of cpu.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • Options
    pickseedpickseed Member Posts: 14
    That is what I have been doing.

    In the Task Manager I see usually 1 and sometimes 2 fin.exe processes using about 40-60% cpu each. Once you factor in Outlook, Word and Excel that people are running, the CPU gets maxed out.
  • Options
    ara3nara3n Member Posts: 9,256
    well looks like your single cpu is not powerful enough. You need multi processor server.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • Options
    LangballeLangballe Member Posts: 5
    I have the same problem. Just found this post in a different forum:

    http://groups.google.dk/group/microsoft ... 6d469cdddd

    I have not tested it yet but it is worth a try.
    Wayne Small [SBS-MVP]" <w...@correct.com.au> schrieb im Newsbeitrag > In
    addition, a number of users access Navision from remote offices via a

    > Terminal server - we have seen several instances of the fin.exe file take
    > 100% of the Terminal servers CPU resources simply while a user is paging
    > through stock files. This has the effect of causing all other users on
    the
    > Terminal server to slow to a crawl. Any ideas on why this is the case?


    The problem here are the "tool tips", they take 100% of the Terminal servers
    CPU resources.
    This is even in a local environment reproductible.
    This problem is solved in version 3.60.
    Or you can advise these users on the Terminal server not to use the "tool
    tips".
  • Options
    dick11dick11 Member Posts: 60
    A solution is to delete the CPUMONI.exe file (it is a Navision bug).

    A client of me using Citrix had the same problem.
    Dick van der Sar

    www.dasautomatisering.nl
  • Options
    pickseedpickseed Member Posts: 14
    Langballe: That is exactly what is happening!

    I will try disabling tooltips and see if that helps today.

    Do you know if there is a way to disable tooltips globally, or does it have to be done on each client?
  • Options
    pickseedpickseed Member Posts: 14
    I think the CPUMONI.exe issue has to do with the Navision server processes, as I have already experienced this on our server.

    My issue is on a Terminal Server running approximately 25-30 Navision 2.6b clients.
  • Options
    pickseedpickseed Member Posts: 14
    Well, there have been 16 clients running on the server for over an hour and the cpu usage has not spiked yet.

    So far, disabling ToolTips seems to have worked.

    The real test will come when are western canada office come online in about an hour.

    I will post back with my results.
  • Options
    dick11dick11 Member Posts: 60
    I have seen that the cpu goes to 100% when the mouse is on the tool bar
    Dick van der Sar

    www.dasautomatisering.nl
  • Options
    LangballeLangballe Member Posts: 5
    Pickseed did you find a way to disable tooltips globally?

    Actually I can't even find where to disable it on a client - Can anyone point me in the right direction?
  • Options
    dick11dick11 Member Posts: 60
    did you find a way to disable tooltips globally?

    No.
    Dick van der Sar

    www.dasautomatisering.nl
  • Options
    bbrownbbrown Member Posts: 3,268
    View - Toolbar - Show Tooltips
    There are no bugs - only undocumented features.
  • Options
    themavethemave Member Posts: 1,058
    This can happen with more then just tool tips, we have 4.0 no service pack, but it did the same in 2.01 also, when a user left his curser in the quantity field in the sales order or purchase order.
Sign In or Register to comment.