In the rapidly evolving world of enterprise software solutions, staying updated with the latest patches and updates is not just recommended; it’s essential. HCL Technologies underscores this imperative with the release of Fix Pack 1 (FP1) for Notes/Domino 14.0. Rolled out on April 16, 2024, this update is more than just a routine patch. t’s a critical enhancement pack that promises to bolster stability, security, and efficiency for users across the globe. In this blog post, we’ll delve into what makes Fix Pack 1 a must-have for organizations running Notes/Domino 14.0, explore its new features, and discuss the overarching impact of these improvements on your operational resilience. Join us as we unpack the essentials of this significant update and guide you through its strategic benefits.
Notes/Domino FP1, Fix or Feature Pack or maybe both?
Even though we have previously dabbled with Feature Packs at IBM, the current FP1 is actually a Fix Pack. Nevertheless, HCL has ventured to include a few new features in Fix Pack 1, primarily for the Domino Server but also for the Notes Client.
What´s new in 14.0 Fix Pack 1
AutoUpdate integrated with Notes AUT Catalog
You can now use Domino AutoUpdate (autoupdate.nsf) to make it simpler to add Notes software packages for Windows to the Notes Auto Update Catalog (autcat.nsf). For more information, see Pushing Notes installs to the AUT Catalog using Domino AutoUpdate
DAOS resync snapshot documentation
Starting in Domino 12.0, you can enable a snapshot to run during resync to capture data that LocalDomainAdmins can later review. If you need to troubleshoot your environment, you can use this data to understand the server’s DAOS usage. For more information, see Gathering DAOS data using DAOS resync snapshot.
Add functionality for command “tell daosmgr REPAIR <dbname>”
There is a new REPAIR argument to DaosMgr – “tell daosmgr REPAIR <dbname>”. When a user issues this command, an attempt will be made to repair any missing DAOS attachments that the specified database has references to. Reference: SPR # DCKTD2USDR
Note: If you use DAOS Tier 2 storage, do not use this command in FP1. This issue is reported under SPR #PWAGD4ER4Q. See KB0112558 – DAOS Command “Tell daos repair <databasename.nsf>” does not work properly in V14.0 FP1 for Tier 2 Storage
Update dbdirman code to display logical size
The dbdirman code is now updated for displaying the logical size (for DAOS storage tuner). The “show dir” command has a new option “-size” which will display the Logical size of the database in bytes. The Logical size of a database is its physical size plus the size of all of its DAOS attachments.
The points mentioned above primarily relate to the Domino Server. The Notes Client has received an upgrade of the JVM.
Everything fine? Unfortunately not!
I want to emphasize three points which are extremely important for anyone who wants to roll out Fix Pack 1.
When installing Notes 14.0 FP1, a file named “HCL Notes Client Update Installer x64.msi” is generated in the temporary folder without a digital signature. This lack of signature leads to the file being blocked by software whitelisting measures in end-user environments, which require digital signatures for validation. The expected behavior is for the file to be digitally signed to meet these security requirements. The defect status is currently open, and the issue, reported as SPR#ASIAD4FD58, is under investigation by HCL software. Customers can subscribe to the Defect Article for updates.
- Link to KBase article: https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0112516.
Secondly, HCL is propagating the AUT feature as the built-in solution for upgrading Notes Clients.
The issue with HCL Notes versions v14.0 and 64-bit v12.0.2FP1, FP2, and FP3 revolves around a malfunction in the AutoUpdate Tool (AUT) functionality. Users attempting to upgrade to a newer version through AUT encounter a problem where, after being prompted to upgrade and close the Notes client, nothing further happens—the upgrade process fails to initiate, resulting in no actual upgrade taking place.
- Link to KBase article: https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0112413.
A third point is also close to our hearts which is not specifically related to FP1 but important in general. Unless you have already converted all Notes clients to the 64-bit infrastructure (Notes 12.0.2 64-bit / Notes 14), we would advise against using the Notes / Domino Designer in the 64-bit version. I am aware that admins and developers in particular like to use the latest versions and of course also want to test the 64-bit clients. In a mixed client environment (32/64Bit), however, this is not a good idea. It can easily lead to unconscious changes to the applications that result in side effects. Only when all clients have been converted to 64-bit should the Notes Domino Designer also be used in the 64-bit version.
What about fixes in Fix Pack 1
In total we have over 90 fixes in HCL Notes and Domino 14.0 Fix Pack 1. So it is obvious that it is not only a good idea to roll out the current Fix Pack because of the functional enhancement of Notes / Domino 14.
| Category | Summary of Fixes |
|---|---|
| Administration | Fixes related to user rename operations for specific locales and policy assignments. |
| AdminP | Correction of calendar entry issues post user ID rename. |
| API | Resolution of incorrect version display in REST API. |
| AppDev | Enhancement of DQL query handling. |
| Backup & Restore | Improved handling of database backup operations under Windows. |
| Calendar | Multiple fixes addressing calendar crashes, meeting notices, and scheduling issues. |
| Calendaring & Scheduling | Improved integration of DOMI with Zoom using proxy settings. |
| Client Accessibility | Enhancements to JAWS screen reader compatibility and character reading. |
| Client UI | Various UI improvements including crash fixes, memory handling, and display issues. |
| Compact | Resolved crash issues during database compaction. |
| Database | Improvements in database integrity error handling and DAOS operations. |
| Debugger | Fix for a crash in the LotusScript debugger. |
| Design in Client | Resolved issues in Notes client designer regarding XPages properties access. |
| Directory Services | Enhancements in directory synchronization and memory leak prevention. |
| Editor | Fixes for embedded document handling and multi-screen scaling issues. |
| Entitlement Collector | Corrected tracking of entitlements for server access configurations. |
| Errors | Fixed LotusScript issues in Designer related to key parameter handling. |
| Firefox | Resolution of password dialog error in Firefox versions 120 and later. |
| Forms/Subforms/Pages | Optimization of document edit mode switching. |
| Full-text Indexing | Addressed issues in temporary file handling during indexing. |
| Help Facility | Correction of replica ID mismatch in Designer help database. |
| Install/Setup/Config | Fixes for installation issues and auto-update task handling. |
| Java Agents | Stability improvements in Java agent execution. |
| JVM | Resolved Java heap memory handling and application hang issues. |
| LotusScript | Improved LotusScript handling for object creation errors in Excel integration. |
| Enhancements and fixes for mail handling, including crash fixes and forwarding issues. | |
| MIME | Resolved delivery issues for emails with multiple recipients and specific configurations. |
| Miscellaneous | Correction of archive restore command issues introduced in previous versions. |
| REST API | Improved compatibility of REST API with Windows-based LotusScript resources. |
| Restyle | Various fixes to improve database styling and design consistency. |
| Rich Text Editor | Resolved issues with unwanted tag insertion during email editing. |
| Security | Comprehensive security enhancements across client and server components. |
| Source Control | Improved handling of design element synchronization in Designer. |
| Templates | Addressed issues with AutoUpdate functionality in template management. |
| XPages | Numerous fixes enhancing stability and display issues in XPages applications. |
If you want to see a detailed list of all includes fixes and SPR numbers. You can find it here.
Sametime Embedded fixes
SAME-50267 – “Send Transcript as Email” creates a blank email if there is an image in the chat history
SAME-47497 – In the send area, emoticons are overriding by the first emoticon in between the space
SAME-50116 – Preview area is updated as <strike> when user uses strike text property
SAME-50784 – Group List: Participants list is not visible in the group chat
SAME-46974 – Group Invite missing from group chats
SAME-47496 – In the send area, space is showing when selecting emoticons from emoticon palette
SAME-50348 – When selecting more than one emoji to send in a chat message, the first one selected is always used
SAME-50387 – When sending multiple emoticons, only the first one is received.
SAME-50529 – Sometimes “NLS missing message…” is updated in the preview area when smile emojis are sent over.
SAME-50268 – Initial chat IMAGE message MISSING
SAME-50269 – HTML injection through nickname added from contact
SAME-50390 – Heart emoji is updated as camera icon in the preview area on MAC Ventura and a camera icon along with heart symbol on Windows11
Download Resources
You can download HCL Notes and Domino 14.0 Fix Pack 1 with the new HCLSoftware download portal.
Direct Link -> HCL Domino 14.0 Fix Pack 1
Direct Link -> HCL Notes 14.0 Fix Pack 1
Further Information
The JVM was upgraded to Semeru jdk-17.0.10+7 with timezone version 2024a
Starting with 14.0FP1, the AUT files will no longer be attached to Knowledge Base Articles. These AUT files are now on FNO (Filename: AUTRepository_140FP1_StandardAllClientW64.zip)
The dominoblog.ntf, shipped with releases 14.0. and earlier, contains a release of the Dojo Toolkit which is susceptible to Security Bulletin: The Domino Blog template contains version of Dojo susceptible to a Prototype Pollution vulnerability (CVE-2021-23450) (KB0112490). Please see KB0112637 Updates for the dominoblog.ntf template to address Dojo Toolkit vulnerability to obtain the new templates.
In addition, HCL continues to welcome ideas for product improvements. Also, technical articles and documentations can be found in HCL’s well-known Service Portal.
So what should you do?
I usually recommend updating to the latest available version. Here I would differentiate a little. If you have already taken the step towards Notes 14, I would fully recommend using Fix Pack 1. The situation with the unsigned files is more than unpleasant, but if this is not a technical obstacle for you, I would roll out FP1 anyway. However, if you are on an older release, the move to Notes 14 needs to be well thought out. In this case, I would strongly recommend testing Notes 14 first, as the change from 32-bit to 64-bit can lead to side effects, especially with self-programmed applications.
If you are a MarvelClient Upgrade customer, integrating Fix Pack 1 into your Notes 14 client setup is very easy. If you would like assistance, or are interested to learn more about MarvelClient Upgrade, reach out and let’s connect and take a look at the below video.
Music in the video:
Last Time by LiQWYD https://hubs.la/Q02tjSbr0
Creative Commons — Attribution 3.0 Unported — CC BY 3.0
Free Download / Stream: https://hubs.la/Q02tjDJK0
Music promoted by Audio Library: https://hubs.la/Q02tjDKB0
