This article provides information regarding MaxExchange Synchronization Server 10 Service Release 1 - Series 1833

On this page

Applicability Overview Issues Resolved MaxExchange Remote Issues Upgrading MaxExchange Server when Using HTTP Transport Installing MaxExchange on a Domain Controller Download Install Instructions

Applicability

The following software versions must be installed before installing this service release:

• Maximizer CRM 10 Service Release 1 - Series 1833

and

• MaxExchange Synchronization Server 10 - Series 1743 or
• MaxExchange Synchronization Server 10 Service Pack 1 - Series 1817

All issues fixed in MaxExchange Synchronization Server 10 Service Pack 1 are also fixed in this service release.

For more information, go to www.maximizer.com/support/version_number.html

Overview

This software update contains a number of important corrections and additions. All MaxExchange Synchronization Server 10 users are recommended to apply this update.

top

Issues Resolved

The following issues are resolved when this update is applied

1. Microsoft SQL Server Issues
   • SQL Server transaction log files grow to several times the size of the database.
   • The MaxExchange Server closes unexpectedly if the connection to the SQL Server is broken when the MaxExchange Server begins to process or if the connection breaks while MaxExchange is processing.
   
   
2. MaxExchange Service Issues
   • When MaxExchange Server is running as a service on the same computer as SQL Server, the MaxExchange service fails to start after restarting the computer.
   • The MaxExchange service shuts down when the SQL Server connection times out.
   
   
3. Email Transport Method Issue
   • If the MaxExchange Server sends a packet twice using the email transport method because of a resend request, one of the packets is sent with the incorrect packet number in the .HDR file.
   
   
4. Address Book Entry Issue
   • Changes to Contacts’ addresses on remotes are not always processed correctly by servers.
     

MaxExchange Remote Issues

• In certain circumstances if a remote is set to start up and process after restarting a computer, the process fails with a SQL Server login timeout error.
• The MaxExchange Remote does not build packets when the Outbox contains an existing .MEX file.
• In certain circumstances, the remote’s REM file (MXZREM.BIN) is set to zero kilobytes.
• If an Address Book from the Global List is open in Maximizer, new Address Books created by MaxExchange Remote are created in the Global List causing MaxExchange Remote to close unexpectedly.
• After processing a refresh where a new Address Book is created, the MASTER user must log in to Maximizer before any other users can log in.
• When upgrading a remote database from Pervasive.SQL, an error is generated if the Server database is listed in the Global List and the name of the Address Book is the same in the Local List.
• MaxExchange Remote is unable to upload large packets to the server using the HTTP transport method.

Upgrading MaxExchange Server when Using HTTP Transport

• If you upgrade the MaxExchange Synchronization Server to version 10 without upgrading the remotes, any remotes running the older version of MaxExchange will not be able to connect to the upgraded server using the HTTP transport method. All other transport methods work properly in a mixed-mode environment.
  
  For more information, see the Maximizer knowledge base at www.maximizer.com/knowledgebase.

Installing MaxExchange on a Domain Controller

• Installing MaxExchange on a network domain controller is not supported.