Overview When deploying Workflow 5.0.x on Tomcat 9.0 an "HTTP Status 500 - Internal Server Error" is displayed after every restart of the Tomcat web server. The following exception is displayed in the browser: Searchable Stack Trace: Type Exception Report Message AuthConfigFactory error: java.lang.reflect.InvocationTargetException Description The server encountered an unexpected condition that prevented it from fulfilling the request. java.lang.SecurityException: AuthConfigFactory error: ...
Overview With the release of Tomcat v9.0.19 (April 12, 2019) we have had clients report that our Workflow WAR file deployment has not been successful. This issue has been escalated to our Development team. In the meanwhile, we recommend that our clients use Tomcat v9.0.16 which can be downloaded from the Tomcat repository available here: https://archive.apache.org/dist/tomcat/tomcat-9/v9.0.16/bin/ [https://archive.apache.org/dist/tomcat/tomcat-9/v9.0.16/bin/] Please note this _does not _appl...
OVERVIEW All of our FileCatalyst Products are installed with default memory limits, including both initial reserve and maximum memory. However, these can be configured to fit your specific needs and environment. This article will go through the configuration process for FileCatalyst Workflow or Webmail for Windows, Linux, and MacOSX NOTE: * For all environments: If you are using a 32-bit Operating System or Java 32-bit, the maximum memory you can define for JAVA is limited to 1.5GB of mem...
OVERVIEW When attempting to launch any of our web-based FileCatalyst Applets and are redirected to the Java download page, this is due to a disparity between the type of Java installed on your system and the type of web browser you have installed. If your Java version and your web browser are different bit architecture types, and 32-bit or 64-bit, your system attempts to correct this. ENVIRONMENT FileCatalyst Workflow v4.0 and later. FileCatalyst Webmail v4.0 and later. FileCatalyst ...
OVERVIEW When connecting to a landing page of a Tomcat Web Server directly at http://mycompany.com/ [http://mycompany.com/] you will not be redirected to FileCatalyst Workflow or Webmail automatically. This will hit the landing page of the Tomcat Server. For FileCatalyst Workflow or Webmail to be accessed there must be a /workflow or /fcweb appended to the end of the URL. We can edit the index page in the Root folder of the Tomcat Web Server so that URLs can be redirected to Workflow or Webm...
OVERVIEW When uploading files to FileCatalyst Workflow or Webmail using the HTML Form Upload, there may be many dropped connections or no connectivity for links with high latency (>300ms). During an upload via HTML form (not the Java Applets) the transfer can sometimes be interrupted with timeouts and restarts or the upload progress status window will not update and will show a Page Not Found or Page Can't be displayed error. ENVIRONMENT FileCatalyst Workflow v4.9 and later. FileCatalyst...
OVERVIEW Logs are one of the critical pieces of information requested by FileCatalyst Support. Below is a list of those viewed as most useful from a support perspective and their default locations. If support has requested logs for a given event please remember that they are rotated every 24 hours at the time set in the configuration file and archived with the dates shown in the name. Environment FileCatalyst Workflow v4.9 and later. FileCatalyst Webmail v4.9 and later. Resolution NO...
OVERVIEW Some networks will have IPV6 enabled by default and this may cause an issue with licensing products. This is an issue that has been reported for customers using Unlimi-tech Applets and FileCatalyst Applets. Microsoft has posted a Knowledgebase Article on how to disable IPV6 globally and for a specific NIC. These solutions can be deployed automatically or manually. The guide can be accessed here: https://support.microsoft.com/en-us/kb/929852 [https://support.microsoft.com/en-us/kb/...
OVERVIEW The POODLE attack (which stands for "Padding Oracle On Downgraded Legacy Encryption") is a man-in-the-middle exploit which takes advantage of Internet and security software clients' fallback to SSL 3.0. This can be remedied by specifying the specific SSL Protocol to be used by the Tomcat Web Server Connector. This patch should be done at the same time as Logjam TLS Vulnerability Fix. You can access the Knowledgebase Article here: HTTP://SUPPORT.FILECATALYST.COM/INDEX.PHP?/KNOWLEDG...
OVERVIEW Google has made changes in the default settings of Chrome version 42, released April 14th, 2015, that block Java applets from running in that browser. This is part of Google’s announced strategy (http://blog.chromium.org/2014/11/the-final-countdown-for-npapi.html [http://blog.chromium.org/2014/11/the-final-countdown-for-npapi.html]) of eliminating all NPAPI (or NP-API) applet support by September 2015. For FileCatalyst users, this means that right now you are going to be unable to...
OVERVIEW It's relatively easy for you to change your FileCatalyst Workflow site's default favico image, the icon that appears on browser tabs when people connect to your site. This image is hosted on your local web server, in the case of FileCatalyst Workflow, it is Apache Tomcat.  ENVIRONMENT FileCatalyst Workflow all versions. Apache Tomcat v6.0, v7.0 and v8.0. RESOLUTION To change this from the default FAVICO.ICO file, navigate to the _Tomcat/_webapps_/ROOT_ folder and replace the existi...
__OVERVIEW:   When trying to create a new job in FileCatalyst Workflow after an upgrade or a fresh install an error is generated: _HTTP Status 500 - Unable to compile class for JSP:_ _type Exception report_ _message Unable to compile class for JSP:_ _description The server encountered an internal error that prevented it from fulfilling this request._ _exception_ _org.apache.jasper.JasperException: Unable to compile class for JSP:_ _An error occurred at line: [244] in the generated java fil...
Overview In Tomcat 9, the core engine starts up faster than previous Tomcat versions and the web front end is active. This means that the HTTP Connector is open and listening to requests from your web browser. Our application which is a container in the application is still starting and as a result, the end user is presented with a HTTP 500 error. Sample Stack Trace: org.apache.catalina.core.StandardHostValve.invoke Exception Processing /workflow/ java.lang.SecurityException: AuthConfigFac...
OVERVIEW In this article, we will address the Logjam Vulnerability and simultaneously harden the Tomcat Web Server to prevent a POODLE attack. The deployment of these patches should be done together. A full technical brief is available at https://weakdh.org/. [https://weakdh.org/] This site also contains details on the Logjam Vulnerability and what weaknesses are exploited.   You can access the Knowledgebase Article for the POODLE Fix here: http://support.filecatalyst.com/index.php?/Know...
OVERVIEW Before moving your FileCatalyst Workflow deployment from staging to live status, there are a few optional steps that can be taken to ensure that your Tomcat Web Server has been hardened. The Hardening of a Web Server is a process where the security on the Web Server is enhanced by applying specific changes to the configuration. This results in a reduced risk of malicious attacks on the Web Server. This article will guide you through some of the sections of the Tomcat Server. The path...
OVERVIEW If an existing install of FileCatalyst Workflow and Webmail needs to be moved/migrated/changed to an install on a new machine and the existing settings need to be maintained. This guide will provide instructions on how to backup your settings and export them to a new machine. Please note if after your upgrade your Language File entries do not show, you will need to restart the Tomcat Web Server. Environment FileCatalyst Workflow v4.9 and later. FileCatalyst Webmail v4.9 and late...
OVERVIEW When a connection comes into the Tomcat Web Server it can be directed to use an HTTPS Socket rather than a non-secure HTTP Socket. Tomcat allows a configuration where HTTPS can be enforced only by the Workflow or Webmail deployment or a server wide rule can be enforced. This article will discuss the how to redirect connections to HTTPS using the Tomcat Web Server. It is not necessary to use a server wide rule and an application wide rule.  Environment FileCatalyst Workflow v4.9 a...
OVERVIEW Many clients who have deployed FileCatalyst Workflow in a Linux environment will have other applications that could change the default character set used by the Operating System. This change could be made in the background and may not be visible to the user. When a system does not use the UTF-8 character set, there may be some issues when rendering file names. Some customers have experienced issues with users trying to download files with Chinese, Japanese, Russian, Cyrillic, Italian a...