Lotus Notes/Domino 8.0.2 Fix Pack 3 Release Notice & "Top 20" Fix List
November 5, 2009
IBM Lotus announces the release of Notes/Domino 8.0.2 Fix Pack 3, a scheduled Fix Pack of a limited number of low-risk, high-impact fixes to help customers safely avoid known issues. IBM strongly recommends that customers running Notes/Domino 8.0.2 upgrade to this latest Fix Pack since it addresses a small percentage of defects that impact the broadest set of customers. Fix Packs are released periodically between Maintenance Releases to provide a greater level of stability for customer environments. They go through the same level of fix, regression and interoperability testing that occurs with Maintenance Releases. Future Fix Packs are always cumulative and contain all of the fixes from previous ones.
As with 8.0.2 Fix Packs 1 and 2, Notes/Domino 8.0.2 Fix Pack 3 addresses defects in both the Client and Server. As with all Fix Packs, 8.0.2 Fix Pack 3 is language-independent and may be applied on any language version of Notes/Domino 8.0.2. (Note: Multilingual User Interface (MUI) packs for Notes 8.0.2.x should be installed before fixes. See technote #1404436 for more details.)
See technote #4026644 - "Download options for Notes/Domino 8.0.2 Fix Packs." Fix Packs will not be distributed on CD.
- If you have Notes 8.0.2 Basic Configuration or Notes/Admin/Designer (Basic edition) 8.0.2 installed, use the Notes 8.0.2 Fix Pack 3 Basic install.
- If you have Notes 8.0.2 Standard Configuration or Notes/Admin/Designer (Standard edition) 8.0.2 installed, use the Notes 8.0.2 Fix Pack 3 Standard install.
Decision to upgrade
Customers unable to upgrade to later Releases will want to install Fix Packs to benefit from later fixes made to the product. By providing a small number of fixes, customers are able to accept fewer code changes with lower risk, allowing them to "patch" an older Maintenance Release until a more extensive upgrade to the current Release is possible.
However, while Fix Packs provide important fixes and IBM strongly recommends applying the latest Fix Pack available for a Maintenance Release, IBM still recommends that customers upgrade to the latest Release + Fix Pack combination to receive the broadest set of fixes available. You will receive more overall fixes with a later Release + Fix Pack than with a set of Fix Packs on top of an earlier Maintenance Release. For more information, see technote #1368141 - "Differences between Notes/Domino Maintenance Releases, Fix Packs and Cumulative Client Hotfixes."
Fixes contained in this Fix Pack
Notes/Domino 8.0.2 Fix Pack 3 contains fixes for approximately 70 known issues, of which the "top 20" are listed below. This list was compiled to identify the issues that most significantly impact customers. Issues were measured by the SPR severity level, the number of hotfixes given out, the number of customers reporting the issue, and the business impact to customers. For a complete list of SPRs fixed in 8.0.2 Fix Pack 3, see the By Release view of the Notes/Domino Fix List.
Note: A plus symbol (+) before the SPR number indicates a fix for a regression bug. A regression bug is an issue that was introduced in a Maintenance Release that did not exist in previous releases of that code stream. For example, a bug that appears in R8.0.2 but did not exist in R8.0.1 is a regression.
- SPR# PRAD7RSL2H - Security vulnerability with viewing Excel spreadsheets has been resolved (Technote #1396492)
- SPR# RGAU7RDJ9K - IBM Lotus Notes 8.x (Standard Configuration) client includes a built-in RSS feed reader which allows you to receive regular RSS updates from the Web sites. In certain circumstances end users may find themselves vulnerable to a cross-site scripting exploit. (Technote #1403834)
- SPR# - HNAA7H84P2 - DEP (Data Execution Prevention) error message is intermittently generated when Lotus Notes on Vista is terminated
- +SPR # ASHH7MPADL - Disabling "Expand names field contents when printing" option in [File] [Preferences] [Basic Notes Configuration] [Additional Options] does not work with 8.x Mail template (Technote #1397184)
- SPR# SEGN7QBEUG - Fixed client crash when opening a new mail message. (Technote #1397386)
- SPR# WEBB6ZPMDS - "No sitemap found" error is displayed intermittently while accessing Notes Mail application (Technote #1304849)
- SPR# DMAT73QME5 - Images on the document is not correctly printed when printing from a view
- SPR# ADC7CYQLT - Notes 8 crashes intermittently when starting
- SPR# GCHU7BM4LQ - This fix prevents a transaction logging issue where in certain cases "Entry not found in index" errors resulted when trying to get the database's DBIID.(Technote #1306187)
- SPR# JPIU7LZV7C - Crash during Transaction Recovery (panic occurs in RmTransactionPartialRollback due to memory allocation failure) when we run out of memory. (Technote #1375416)
- SPR# HNAA69UNHH - Domino internal function ConvertJustify could possibly crash, in just about any server process, or in Notes. (Technote #1208982)
- SPR# JPMS7F2NQN - Fix Domino crash when clicking on the "Analysis" tab in the Administrator Client if there are multiple Smart Upgrade mail-in databases defined in policies. (Technote #1306193)
- SPR# DCHR7NSUY9 - Fix deleted documents remaining in a view after archiving documents that have been replied to in an ODS 48 mail file. (Technote #1375583)
- SPR# WWHN7HXJJF - Prevent server crash due to excessive memory used by backup application
- +SPR# OIHZ7UVJ7T - After the fix for AJMO7LHMK9 has been applied to stop an infinite loop when folders contained future TimeDates it was possible that we raised the wrong error of "Error 4000: %a's Certification Log". We have fixed this to raise the correct error of "The collection has become invalid". (Technote #1396849)
- SPR# VPRS75WU62 - Check that the maximum size of an element in an internal structure is not exceeded.
- SPR# JCHN77TPZB - The Domino mail server had a crash when converting a specific rich text field to MIME in mail. (Technote #1289400)
- +SPR# VDES7RDENQ - Corrected an issue which caused Administration Process (adminp) to crash if there are errors found in the processing of certain roaming user requests. The errors, and subsequent crashes, where most commonly found during the processing of requests created when attempting to upgrade a user and roaming databases for that user already existed on the roaming server. (Technote #1384440)
- +SPR# BRIS7DPS8D - Access violation in Router with journaling enabled. (Technote #1366981)