FileHold server diagnostics and recommendations for performance
In order for the FileHold server to run adequately, there are some system checks that can be performed and evaluated.
FileHold system requirements states that it requires a dedicated server to run. FileHold has this requirement to avoid performance conflicts, as well as deeper technical issues that can affect FileHold. FileHold is typically a mission critical application and issues can arise if it is shared with other systems. The server must also meet the minimum recommended hardware configuration. If the server does not meet with the system requirements, issues that arise may not be covered by FileCare.
There are several scheduled tasks that FileHold runs on schedule. These tasks begin with "FH" and run at various times during the day. If the scheduled tasks are not running, run the Health Checker report and send the results to [email protected].
Health Checker report
The Health Checker report check over 250 Windows Server configuration and FileHold Server Application health settings. This tool can be run at any time to check the system health and will be requested by FileHold support if any issues are reported. Be sure to run the tool with the correct administrator permissions or a false error (red) may be given.
If errors are often given for the Temporary ASP.NET folder and sub folders/files, give the FH_Service account full control of this directory: C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files
Manage Microsoft SQL transaction log files
If you have one or more of you databases set to full recovery mode, make sure you have a maintenance plan that runs frequently to reintegrate the log data with the database. Or, if you have no idea why you need full recovery, switch to simple recovery.
TCP/IP port exhaustion
It is recommended that tune the FileHold server for port exhaustion.
Make sure your anti-virus software excludes fileholdadm.exe, the w3wp.exe and the sqlserver.exe processes so they are not being monitored for real-time threat analysis. Make sure it alerts someone in IT to investigate if a document is found to contain a virus and is removed or quarantined. Read this article about antivirus best practices for the FileHold Desktop Client and this article for what to do on the server for antivirus and security considerations.
Microsoft SQL Management Studio maintenance schedule
A nightly maintenance task schedule should be setup in SQL Management Studio to update statistics and indexes on all FileHold databases.
App pool recycling
By default the IIS application pool is set to recycle at an arbitrary time offset from the time the server is started. This generally does not have a detrimental affect on FileHold, but it is a good practice to set the recycle time to a low usage time for FileHold. Recycling clears global variables and will force users to reconnect to FileHold. In versions 14 and higher this reconnection is automatic.