News
Abstract
Fix Pack 7.1.0.37 was originally released on October 22, 2025, and refreshed on November 28, 2025, following the discovery of several issues in the initial release.
The additional issues resolved in the refreshed Fix Pack are: DT455374, DT456668, DT455812, and DT456974.
Content
Attention! It is not recommended to install the refreshed Fix Pack 7.1.0.37 on top of the original Fix Pack 7.1.0.37. The refreshed Fix Pack should only be applied to systems that have not yet been upgraded to Fix Pack 7.1.0.37. For NOI 1.6.15 deployments where Impact is on cloud use hot fix CP4AIOPS-22533 For systems with the original Fix Pack 7.1.0.37 already installed
Resolution Options:
Alternatively, you can roll back the Fix Pack and install the refreshed version of Fix Pack 7.1.0.37.
|
Identifying the Installed Fix Pack Version
Included in the output is the version information and build date of the installed package.
If the original Fix Pack 7.1.0.37 is installed, the build date will appear as:
========================================================================
Impact Version Utility: Build date: 7.1.0.37 - 202510162105
========================================================================
Checking a Downloaded Fix Pack Before Installation
Extract the package and open :
# Build date: 7.1.0.37 - 202511261615 #
DT455374: Upgrade Takes Excessive Time Due to Slow Password Migration
Summary:
Upgrading to 7.1.0.37 may take several hours, especially on systems with many data sources (e.g., more than 6 hours for 30 data sources).
Remediation:
If the upgrade was completed, no further action is required.
If you need to upgrade additional systems to 7.1.0.37, replace the upgrade installer with the refreshed version of 7.1.0-TIV-NCI-FP0037.
DT456668: Intermittent decrypt() Password Failures
Summary:
Policies using the decrypt() function may intermittently fail after upgrade, causing incorrect decrypted values and downstream authentication errors (e.g., JS0002 or HTTP 401).
Remediation:
Contact IBM support for a hot fix.
DT455812: JRExec Server Fails to Start
Summary:
After applying Fix Pack 7.1.0.37, the JRExec server may fail to start due to a changes in it's log4j configuration.
On start-up the following error may be observed:
Exception in thread "main" org.apache.logging.log4j.core.config.ConfigurationException: No name attribute provided for Appender rollingerror
Remediation:
- Open
<IMPACT_HOME>/etc/jrexecserver-log4j.propertiesin a text editor. Delete the following line:
appender.rollingerror.layout.pattern=%d{DATE} %-5p [%c{1}] %replace{%m}{(\r|\n)(0[1-9]|[1-2]\d|3[0-1])( |\s)}{}%n- Save the file.
- Restart the JRExec server.
DT456974: User Preferences Not Persisting
Summary:
UI preferences (e.g., editor line numbers) do not persist across sessions.
Remediation:
Contact IBM support for a hot fix or apply the following workaround.
Workaround:
To modify the default preference options, such as always showing line numbers, follow these steps.
1. Locate the following file in the UI server:
$IMPACT_HOME/wlp/usr/servers/ImpactUI/apps/ImpactUI.ear/impactAdmin.war/jsp/PoliciesView.jsp2. Create a backup first. Open the file and locate the following line
showLineNumbers: sessionStorage.getItem(remoteUser+"_showLineNumbers"),3. Replace with:
showLineNumbers: "true",4. You can also modify other preference options (e.g., always enable beta policy editor):
useDojoEditor: "false"5. Save the file.
6. Clear your browser cache and log into the application.
Was this topic helpful?
Document Information
Modified date:
31 August 2026
UID
ibm17253012