Skip to main content  

Lotus Notes/Domino V7.0.2 Fix Pack 2 Release Notice
June 4, 2007

IBM announces IBM Lotus Domino V7.0.2 Fix Pack 2. IBM strongly recommends upgrading to the latest Fix Pack because Fix Packs address a small percentage of defects that impact the broadest set of customers. This is a scheduled Fix Pack of a limited number of low-risk/high-impact fixes to help customers safely avoid known problems. Fix Packs are released periodically between Maintenance Releases to provide a greater level of stability for customer environments. Fix Packs go through the same level of fix, regression, and interoperability testing that occurs with our Maintenance Releases. Future V7.0.2 Fix Packs will be cumulative and contain all of the fixes from Lotus Domino V7.0.2 Fix Pack 2 and may be applied on any language version of Lotus Domino V7.0.2.

All fixes in this Fix Pack have already been successfully deployed at customer sites. Fix Pack fixes are included in the next shipping Maintenance Release, so V7.0.2 FP2 fixes will also ship in V7.0.3. Customers unable to upgrade to later Maintenance Releases will want to install Fix Packs to benefit from later fixes made to the product. By providing a small number of fixes, customers can accept fewer code changes with lower risk, allowing them to "patch" an older Maintenance Release until a more extensive upgrade to the current Maintenance Release is possible. Fix Packs can be downloaded from the Web, but are not distributed on CD.

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 Maintenance Release + Fix Pack combination to receive the broadest set of fixes available. You will receive more overall fixes with a later Maintenance Release + Fix Pack than with a set of Fix Packs on top of an earlier Maintenance Release.

The following is a list of the problems fixed in this V7.0.2 Fix Pack.

1. There are seven fixes below with a plus symbol (+) before the SPR number. This symbol indicates fixes for regression bugs. A regression bug is a bug 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 V6.5.5, but did not exist in V6.5.3 is a regression.
2. Technote Numbers are displayed in parentheses following the fix description.

IBM Lotus Domino Web Access
  • +SPR# BRIS5TXQJU - Fixed an HTTP crash during image conversion under certain circumstances. This problem rarely occurs in V6.5x, but code changes make it more likely in V7.0.2 FP1. Due to this, it is flagged as a regression introduced in V7.0.2 FP1. (TN# 1158774)
  • +SPR# COLY6Y2J3Q - Fixed an HTTP page rendering crash. This regression was introduced in V7.0.2 FP1. (TN# 1158774)
  • SPR# JUYA5ZYW56 - Fixed an intermittent HTTP crash using Name Picker. (TN# 1250241)
  • +SPR# PPET6TSS3A - Fixed an HTTP crash when accessing the DWA NamePicker using an iNotes6.ntf-based mail file. There were no error messages displayed during the crash. This regression was introduced in V6.5.6 and V7.0.2. (TN# 1250241)

  • SPR# ADC6TET7N - In a low memory condition, allocvblock will return null which causes a problem for callers of osallocvblock. This problem results in an nserver process crash and "PANIC: OSVBlockAddr: Bad VBlock handle (FFFF\0)" error. Because this problem was fairly deep in the code, symptoms of this problem are fairly transient, other than the Panic error and can occur on a server process. For example, we have customer reports for this in at least the nserver process and nreplica process. (TN# 1249651)
  • SPR# CGAA6SRNAS - Fixed crashes in various areas of Lotus Domino when trying to locate a value in a summary buffer. For this particular SPR, Lotus Domino crashed when updall ran on the Lotus QuickPlace search.nsf and main.nsf databases. (TN# 1252292)
  • SPR# DTEI6FHBW2 - Fixed a server crash in ReturnNameInfoEpilog. (TN# 1260064)
  • SPR# HPES6TYHS5 - Stopped tasks no longer display an obsolete error status in the Admin Client Server Monitoring.
  • SPR# JCHN5CDQE3 - Fixed a crash which occurred after encountering an invalid note in a database. (TN# 1247415)
  • SPR# JJMA6QC8X9 - Domino server crashes on HTTP when accessing an agent that generates an enormous Web page leading to massive memory usage. (TN# 1249051)
  • SPR# JWAE6PXKR6 - This fix prevents a problem which can cause one or more IMAP threads to be stuck in the ResponseProcess. This condition manifests itself as the IMAP server reporting a "Fetch response thread for 'session number'" with a start time of several hours or days previous, when issuing a "show task time" at the server console. (TN# 1243817)
  • SPR# KHON724HGP - Fixed a potential security issue.
  • SPR# KHON72EHWT - Fixed a potential security issue.
  • SPR# KTIS6VZHYR - Fixed an SMTP crash with TNEF conversion enabled (TNEFEnableConversion=1). (TN# 1252932)
  • SPR# MGAN6VCQLT - Fixed a crash on SMTP with TNEF conversion enabled (TNEFEnableConversion=1). (TN# 1252932)
  • SPR# MIAS6VALFX - Fixed a mail router crash when the server was running with constrained memory.
  • +SPR# MKEN6X3NKK - Fixed a potential Denial of Service issue. This regression was introduced in V6.0.
  • SPR# MRSI6TUF6N - This fix prevents a crash that occurred when opening an encrypted calendar entry via Lotus Domino Web Access. (TN# 1254016)
  • SPR# NORK6UFP5W - Fixed a crash that occurred after adding the Anonymous user to the usercache when the anonymous user was disabled at the port level. (TN# 1249109)
  • +SPR# PPET6NQMES - Under certain circumstances, LDAP searches that rely on the FT Index may cause the Domino LDAP server to crash. This regression was introduced in V6.5.4. (TN# 1234657)
  • SPR# SDSS6M8JBM - Fixed an event task crash when Domino Domain Monitor (DDM) probes were enabled. (TN# 1257069)
  • SPR# SKAI6QKHYF - In a low memory condition, allocvblock will return a null value and cause the router to crash when trying to transfer a message. (TN# 1240082)
  • SPR# SVRO6YU2QY - This fix addresses multiple DST 2007 items for non-Windows servers, including outbound iCal off by one hour when MIME conversion is done by the server instead of the client. This fix does not include the HTTP $Preferences component of the fix which requires translation. Please see TN 1256819: "Daylight Saving Time (DST) 2007: Details on issues where Notes/Domino references old DST information if the operating system is not Windows" for more information. (TN# 1256236, TN# 1256819)
  • SPR# SVRO6ZPTRB - Daylight Saving Time will occur three weeks earlier and end one week later in 2007 and forward. Customers should be advised to apply the correct OS patch. For applications that make native Java timezone calls, a Java patch is also needed. An updated JAR file has been included in this release and will be included in V7.0.3. C&S/R&R docs created before the OS patch was applied will have the wrong DST information stored. Please note, the V7.0.2 FP2 fix is applicable for all platforms except z/OS. The fix for the z/OS platform will be included in Lotus Notes/Domino releases 6.5.6 and 7.0.3. (TN# 1193771)
    See Technote # 1247972 for links to additional technotes that describe product areas that can be affected by the DST changes in 2007. Specifically, TN #1232652 which provides an agent to correct documents. (TN#
    1247972, TN# 1232652)
  • SPR# THTO6YVTNJ - Error "PANIC: Invalid pool free chain" displayed during a server crash with DPOOL corruption. The crash occurred while processing a MIME message. (TN# 1256494)
  • SPR# VPRS6XJSXD - Fixed a fixup task crash when it encounters database header corruption. Database is not fixed, but rather marked as corrupt. The database needs to be recovered.
  • +SPR# YSAH6VUASQ - Prior to this fix, expanding category twisties via the Web could hide other entries in the view. This regression was introduced in V7.0.
  • SPR# WSCN6TMNAB - This fix prevents a server crash on the iSeries platform, which occurred when running a LotusScript Agent. (TN# 1245908)

  • SPR# BMSN6TLL9R - Improved the handling of NSD errors. (TN# 1233676)
  • SPR# JROU6UGVQQ - With this fix, NSD now distinguishes between handles and memhandles in Top 10 sections. (TN# 1233676)
  • SPR# JROU6RFTKP - Fixed a problem with the NSD debugger -p option to allow it to collect process specific data. (TN# 1233676)
  • SPR# JROU6UPRA5 - Fixed the NSD service to work under limited user accounts (for example, accounts that are commonly members of the Users group on XP). If the NSD service is run on a limited user account, the NSD would not execute or attempted to run, but it would appear to do nothing. The only workaround to this problem is to run as administrator. (TN# 1233676)
  • SPR# JROU6X6UHG - NSD now makes a separate copy of pid.nbf and reads that; also only reads file once instead of four times. (TN# 1233676)
  • SPR# LQTN6XLCD6 - Added nrecover to the list of processes that we skip when building process lists for Notes instances.
  • SPR# MSAN6RE6BD - NSD annotation enhancements. (TN# 1233676)
  • SPR# MSAN6TERLV - Fixed a Memcheck crash while dumping process static objects. (TN# 1233676)
  • SPR# MSAN6UW3KX - NSD now outputs Server Stats information. The same information that is displayed when a user gives the "show stats" server command is also now captured by NSD. (TN# 1233676)
  • SPR# MSAN6XCTFY - Fixed a problem where NSD -monitor was not detecting Domino processes. (TN# 1233676)
  • SPR# MSAN6XDTHL - Fixed a problem where NSD was not detecting outdated sym files. NSD sometimes fails to detect outdated sym files and incorrectly annotates stack symbols. The reason for this is because NSD relies on the file modification time to determine which sym file to use for a given dll/exe, but it should use the image timestamp generated by the linker. This problem usually happened when customers installed hotfixes, and then upgraded to a newer Lotus Notes/Domino version. (TN# 1233676)
  • SPR# MSAN6Y5M6U - NSD was not detecting/showing the crash stack on AIX when procstack was used. (TN# 1233676)
  • SPR# RGET6E9RSE - Improved NSD diagnostic data collection integrity. (TN# 1233676)
  • SPR# SCOS6QTQWX - Reformatted "TCP Table"; now correctly named "TCP Connection Table" and all data is now aligned in a reasonable way. Added -hostnamelookup option to control whether or not IP addresses are mapped to host names. *NOTE: Specifying -hostnamelookup can negatively impact performance because the network calls to map IP addresses to hostnames can take a significant amount of time, depending upon network responsiveness and the number of addresses needing to be resolved. (TN# 1233676)
  • SPR# SCOS6SAP2T - Added the option to skip processes looking for system handle information. (TN# 1233676)
  • SPR# SCOS6UULZB - Allows NSD debugger to dump a crash stack even if symbol information is not available. (TN# 1233676)
  • SPR# SCOS6UWLLE - This fix makes the NSD service available for the Win32 platform. (TN# 1233676)
  • +SPR# SKAI6RTFHC - Three changes were made in this fix. 1) Changed the NSD section "Last 10 Console Log Messages" to "Last Console Log Messages". 2) Excluded the file "hulsrvc.exe" from the list of examined processes because it causes problems. 3) Fixed a problem which caused the error "Error writing to pid.nbf" by making an exclusive copy for NSD. This regression was introduced in V6.5.5.
  • SPR# SMAI6W8TRB - Allows NSD debugger to run correctly as a service on Windows where paths contain spaces. (TN# 1233676)
  • SPR# SVRO6W8Q3U - Memcheck must suspend Domino processes so that memory does not change while it is being examined. This is an improvement to the suspend method on AIX that is more stable than the previous method. (TN# 1233676)
  • SPR# TBRD6RZLSA - A recent change to run memcheck as a separate process caused the log file to be closed and reopened. The reopen was in binary mode instead of text. This fix was to open in text mode after cleaning messages from the end of memcheck output. (TN# 1233676)

Go back

  Document options
Print view

  Fix list views

 RSS feeds   RSS
Subscribe to the fix list

    About HCL Privacy Contact