1.877.833.1202

Using the Health Checker to Check the FileHold Server

For troubleshooting or server health verification purposes, you can use the FileHold Health Checker tool to check over 250 server configuration and FileHold Server health settings. The Health Checker tool is the main utility that is used in the diagnosis and repair of the FileHold server. It validates that the FileHold system is running normally. If you should ever experience issues with the server, the Health Checker tool should be run immediately to assess the issue.

The Health Checker checks components such as:

  • Server and IIS properties
  • Configuration files
  • DLL files
  • Databases
  • ADAM
  • Service account
  • Scheduled tasks
  • Full text search index
  • Directories
  • License information

If all server components are running well, the system health for that component appears green. If there are any warnings, the system health for that component appears yellow. If there are issues that need to be remedied, the system health for that component appears red. All components should appear green for optimum system health. If any components appear red, please save the report and send to support@filehold.com for analysis and repair.

Before running this tool, you should make sure that you are logged on as an IT administrator of the server, be a member of the local server administrator group, as well as having administrator access to the SQL server. Otherwise you may see errors because of a lack of access permissions.

To generate a health checker report

  1. On the FileHold Windows server, go to C:\Program Files\FileHold Systems\Application Server\FHInstrumentation.

  2. Right-click on FHInstrumentation.exe and run as an administrator. If this is the first time it has run, then it will update itself and then restart.

  3. Select Health Checker in the FileHold Instrumentation list.

  4. Select one of the following options:

  • Full check — Always use if you have less than 2 million documents in the repository. Checks document repository rights during the system check.

  • Fast check — Recommended for repositories with more than 2 million documents as it will run faster than a Full Check. Does not check document repository rights. Can also be used if you are sure that proper rights have been set up on the document repository.

  1. Click Show to run the Health Checker. The server application and database configuration is tested during this process.This may take some time.

  2. Once complete, the report will display in a color coded format:
  • Green — Good, all conditions normal.

  • Yellow — Warnings / informational messages. This does not mean anything is wrong.

  • Red — A mis-configuration made during server preparation or a change in configuration to the server OS, database server, or you are not running the tool with the correct IT administrator permissions.

FileHold Instrumentation Tools (FHIT) Health Checker Report

  1. Click on individual sections and drill down to learn more about the configuration, what is being checked, or the message or error.
  2. Viewing a yellow notification provides an informational message. In this case, the yellow areas of the product show specific modules when an optional feature has not been purchased.
  3. Click on the Summary section to view a summary of all tests that have passed, generated errors and warnings.
  4. Once the report has been generated and you have reviewed the test results, click Save System Health State and send to support@filehold.com. Select one of the following options:
  • HealthChecker log and event logs — The FileHold support team typically recommends this option if you are experiencing issues with the system.
  • HealthChecker log only — Can be run periodically to ensure that the FileHold system is running normally and save the log file as part of your server maintenance history.
  1. If the currently logged in user does not have access to the Microsoft SQL databases, click Custom Parameters to enter the credentials. Click Check System Health State to run the checker again with the correct credentials.