OL2000: Integrity Check For Client OAB (232767)

SYMPTOMS

If a Microsoft Message Application Programming Interface (MAPI) client is interrupted while downloading a differential update to its Offline Address Book (OAB), the OAB may be left in a useable but half-updated state. Under such circumstances, usage of the OAB may result in mail being sent to the wrong recipient.

Some common examples of interruptions that may result in this type of scenario are: a client computer is turned off during the download of an OAB, an End Task on the MAPI client process is performed, or a fatal application error (hard crash) occurs during the download.

Additional items that may cause an interruption of the client include the sudden locking of OAB files by another process (such as anti-virus software) and network disturbances (for example, a bad network interface card, cable, or connection), which cause the client to be unable to fully update all the OAB files during the download process.

NOTE: In such cases, the end-user may not receive any error message to indicate a failure. The synchronization log should be reviewed for additional information, but an error log entry is not guaranteed. An error log entry may not be written if the item affecting the OAB sufficiently interferes with the OAB download process but does not prevent it from completing (for example, sporadic network disturbances). These types of cases are rare and can potentially affect multiple applications on an end-user's computer.