I received an "Unexpected Error" message in the FileHold Desktop Application
If you received the message “An unexpected error occurred in the FileHold Desktop Application. Please try again. If this happens multiple times, please contact FileHold support.“, do the following steps:
- Attempt the operation one more time in the FileHold Desktop Application.
- Repeat the operation in the Web Client, if applicable. If it works in the Web Client, then the issue can be narrowed down to only the FileHold Desktop Application (FDA).
- Click Details to view the error details. Click Copy to Clipboard to send the error to the FileHold support team at .
- If the issue resides only in the FDA, send the trace and error logs to the FileHold support team at . Follow the instructions here to get a copy of the trace and error logs. Once the logs are analyzed by the support team, they will send instructions or set up a meeting to resolve the issue. If the issue also resides in the Web Client, see the following FAQ for instructions.
I received an "Unexpected Error" message in the Web Client
If you received the message “An unexpected error occurred…“, do the following steps:
- Contact your system administrator and report the details of the error such as what you were trying to accomplish in the system, where the error occurred, and so on.
- Click Details to view the error details. Click Copy to Clipboard to send the error to the FileHold support team at .
- A system administrator can run the Health Checker report on the FileHold server and send the results along with the Windows log files to . Once the logs are analyzed by the support team, they will send instructions or set up a meeting to resolve the issue.
I received a "FileHold is not activated" message
If you received the message “The FileHold system is not activated. Please contact your system administrator to enable the license.“, do the following steps:
- Contact your system administrator to let them know the FileHold license has been deactivated. There are a number of reasons why a license could become deactivated.
- A system administrator can use these instructions to obtain and upload a new license file.
I cannot see some documents in FileHold
Depending on permissions, you may or may not have access to particular documents in the FileHold library. If you think that you should have access to documents that you cannot see, do the following steps:
- Contact your library administrator and/or system administrator and let them know what documents you should be able to view in the library.
- The system administrator can check to ensure that you are placed in the proper security groups.
- The library administrator can check to ensure that you have access to the proper cabinets and folders and membership to the schema.
I lost my password
If you have lost your password, and there is no option to reset your password from the login screen, you can ask your system administrator to reset the password for you. If you have exceeded the number of login attempts, you system administrator will also need to enable your account. This typically only occurs for locally managed users.
If you are a system administrator and have lost your password, this can be reset using the FileHold Instrumentation Tool (FHIT) utility on the FileHold server.
Microsoft Office integration is not working
If the FileHold tab is not showing on the ribbon in any of the Microsoft Office applications (Word, Excel, PowerPoint, Visio, Outlook, OneNote), the add-in may need to be enabled. Follow the Microsoft Add-ins troubleshooting article to solve this issue.
I do not know the URL for FileHold
If you do not have the URL for FileHold, contact your system administrator for the link.
The URL format for the FileHold Desktop Application (FDA) should resemble the following example:
http(s)://<servername>/FH/FileHold/For the Web Client URL, the link should resemble the following example:
http(s)://<servername>/FH/FileHold/WebClient/LoginForm.aspx
I cannot add a document or I get an error when adding a document in the Inbox
If you received the message “An error has occurred and the document will be sent back to the Inbox…”, do the following steps:
- Attempt to send the documents into the library one more time.
- Add a document through the Web Client, if applicable. If it works in the Web Client, then the issue can be narrowed down to only the FileHold Desktop Application (FDA).
- If the issue resides only in the FDA, send the trace and error logs to the FileHold support team at . Follow the instructions here to get a copy of the trace and error logs. If the issue also resides in the Web Client, contact your system administrator.
- A system administrator can run the Health Checker report on the FileHold server and send the results along with the Windows log files to . Once the logs are analyzed by the support team, they will send instructions or set up a meeting to resolve the issue.
Knowledge Base
- Access the web client with a short URL
- Active Directory Synchronization tool
- ADAM (ADLDS) objects management in FileHold
- Add documents exported by FileHold
- Add documents using manage imports
- Authentication options comparison
- Change database server instance
- Change port, server name, or protocol of application server
- Change service account to another account
- Custom date, time and currency formats
- Direct access for single sign on with a browser
- Email troubleshooting
- Exporting logs from the FileHold Desktop Application
- FDA installation template file
- FileHold 17.2 upgrade preparation
- FileHold architecture
- FileHold Desktop Application (FDA) antivirus best practices
- FileHold Health Checker tool
- FileHold library setup in FHIT
- FileHold server antivirus settings best practices
- FileHold server backup and recovery guide
- FileHold software version releases
- FileHold Windows event logs
- Installing Microsoft SSRS for integration to FileHold
- Installing Print-to-FileHold virtual printer driver
- Installing the FileHold Desktop Application (FDA)
- Instrumentation utility for the FileHold server (FHIT)
- Label printing
- Managing IIS logs
- Metadata exporter tool
- Microsoft SQL Server configuration for the FileHold databases
- Microsoft SQL Server configuration recommendations
- Microsoft SQL Server maintenance plans
- Migrating FileHold to a new server
- Migration and importing documents into FileHold
- Move FileHold data directories to new storage locations
- Other Microsoft SQL Server database options
- Preparing the FileHold Server for Internet accessibility
- Setting the base URL for generating links to FileHold
- System administrator password change
- The FileHold Desktop Application and TLS 1.2
- Troubleshooting single sign on with Microsoft Active Directory
- Troubleshooting the web client – Internet Explorer
- Uninstall and removal of the FileHold server software
- Upgrading SQL Server when used with FileHold
- Windows server tuning – Port exhaustion
- Windows Server tuning for .NET application pool