FIMS is Running Slowly in an On-Premise Environment

 FIMS runs very slow, especially moving from module to module or posting. How can I improve performance in FIMS if I am on-premises?

Answer:

There are many causes for FIMS running slowly in your environment. Here are some steps to take to improve performance below. 

1. Antivirus and Firewall

• Anti-virus scanning engines can cause FIMS to have performance issues. Your IT team can choose to make an exception in the anti-virus for FIMS.

• Configure any anti-virus software to exclude virus checking on the npo folder (including subfolders) and also exclude run-time checking of programs/applications “_mprosrv.exe” and “prowin32.exe” 
• Create Firewall port exceptions for the FIMS TCP ports (both inbound and outbound) – 2500, 2501 (database ports), 2600 (SQL), 2699 (IGAM), 3000-5000 (database brokers)
• Create Firewall program/application exceptions for “_mprosrv.exe” and “prowin32.exe” (Both are found in n:\dlc\bin, are Progress executables used by FIMS and the databases )
• Check these settings on DB server, RDS\terminal server if used and client machines.

2. System Resources

• Having insufficient RAM can cause FIMS to have performance issues
• If the RAM is not sufficient on your database server, RDS server or workstation, have your IT team check RAM on those machines and potentially upgrade
• Having low available disc space on the database server can cause FIMS to have performance issues
  • If disc space is an issue on the server have your IT team clean up disc space on the drive that has the NPO folder on the database server and also potentially increase drive size. If disc space is an issue, you can also clean up unneeded files as outlined in the article below. 

How to clean up un-needed files on FIMS Server

3. Posting Processes 

• There is a process that you can run to speed up posting processes.
• The process must be run on the database server.

What do I do when running the Edit and Posting reports takes too much time?

4. FIMS Client Memory Allocation Size: 

• Edit the “mmax” value by adding 4096 to the existing value OR add “-mmax 8192” if no value found (add just above the “–T ..\tempfiles” line) in the following file: n:\found\ConfigFiles\wfound.pf 

WARNING: -mmax exceeded. Automatically increasing from xxxx to xxxx. (5490) in FIMS

 5. Running Hypervisor Virtual Server

• If running Hypervisor Virtual Server turn off “Virtual Machine Queues” 

6. Check Database Structure Configuration: 

• Run DB Health 

What is the FIMS Database Health Audit Feature and how do I Use it?