 |
A new update is now available that includes the fixes outlined
in this article as well as some additional updates. Please apply
MaxExchange Synchronization Server 9 Service Release 2. A link to this new update is found below.
The following information is retained for historical reference.
|
This document describes issues addressed in MaxExchange Synchronization Server 9 Hot Fix 1 for Service Release 1 - Series 1605.
IMPORTANT NOTE:
This hot fix applies only if you were running MaxExchange Synchronization Server version 8 or earlier and have upgraded to MaxExchange Synchronization Server 9 Service Release 1 - Series 1552, but you have not yet upgraded your Address Book. YOU MUST INSTALL THIS HOT FIX BEFORE UPGRADING YOUR MAXIMIZER ADDRESS BOOK TO VERSION 9.
Issue resolved by this hot fix
- Under some circumstances, MaxExchange remotes would send an unusually large packet to the MaxExchange server. This large packet might have contained records that already existed in the Address Book on the server, and processing this packet on the server could create duplicate column setup records on both the server and the remotes.
MODIFIED UPGRADE BEHAVIOR
New upgrade behavior of the server and remote takes place after applying this hot fix as follows:
Immediately after MaxExchange Server is started by launching MaxExchange Server Manager or rebooting the machine where the MaxExchange Service is installed, at least two packets are created for each remote and are saved in a folder called Upgrade (under the Outbox\[HEX Address Book ID] folder). Additional packets may be created as well depending on whether or not the server has additional transactions for the remote. The first packet contains information that
sends a request to the remote for information added on the remote during the upgrade process. The second packet contains any other transactions, if applicable.
In mixed-mode environments (where the server and remotes are running different versions of MaxExchange), only updates and deletions from a remote that has not been upgraded yet are
processed by the server. Additions are discarded until the remote upgrades. After a remote has upgraded, it sends a packet to the server and once that is processed, the packets in the Upgrade folder are sent to the remote and the Upgrade folder is deleted on the server. After the remote has processed the packet from the server, it creates a packet for the server containing information that was added on the remote during the time the mixed-mode environment was running.
| Note: | • | The upgrade behavior described above varies from the information described in the MaxExchange Administrator’s Guide in the second bullet point on page 23 under the Upgrading from Previous Versions of MaxExchange section.
|
| |
• |
When MaxExchange Server starts, the first packet creation
process begins even before logging into MaxExchange Server
Manager as the Master user. |
|