Filr is inaccessible and throws HTTP Status 500 Error after applying the Filr 3.1 Update

  • 7018601
  • 08-Feb-2017
  • 08-Feb-2017


Micro Focus Filr 3.0
Micro Focus Filr 3.1


After applying the Filr 3.1 Update via the Online Update tile in the Appliance Console (port 9443), Filr service is not restarted and accessing the Filr site throws the following HTTP Status 500 error:

HTTP Status 500 - Error creating bean with name 'sPropsUtil' defined in ServletContext resource [/WEB-INF/context/applicationContext.xml]:
    Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException:
    Could not instantiate bean class [org.kablink.teaming.util.SPropsUtil]: Constructor threw exception;
    nested exception is java.lang.IllegalStateException: PropsUtil is a singleton class
    ..... <more>


If you run into this problem immediately following the Filr 3.1 Update, please ensure that you have completed Step 1b below:

1. Applying the Filr 3.1 Update is a 2 step process requiring:
(a) Applying the online update under Filr Console 9443 > Online Update
(b) Re-configuring the Filr appliance under Filr Console 9443 > Configuration

Failure to complete (b) will result in an incomplete update and Filr services will not start.
To complete the update, you will have to complete Step 1b on All Filr appliances in your deployment.

Additional Information

In addition to the above resolution, please be aware of the following known issues related to the Filr 3.1 Update:

2. When completing 1a: In the 'Update Now' pop-up, select 'All Needed Patches' and remember to select the two options:
(a) Automatically agree with all license agreements
(b) Automatically install all interactive patches

Failure to select these two options will cause the progress bar to show the patch is being applied which never completes.
To complete the update, you will have to re-apply the update with the options 2a and 2b selected.

3. If you had previously selected a schedule to apply the updates automatically, it will result in the same situation described in 1.
To complete the update, you will have to complete Step 1b on All Filr appliances in your deployment.

4. If you have a Clustered Filr deployment with more than 1 Filr Appliances, the order in which you complete 1a and 1b is important:
(a) Complete 1a on ALL Filr nodes first
(b) Complete 1b after you have completed 1a on ALL Filr nodes

5. In some instances, you will be required to re-apply your Filr 3.0 License following the 3.1 Update
On the first successful login to Filr 3.1, if you are prompted that your Filr License has expired, please follow these steps to Update your Filr License.