Home > Support > Version > Maximizer Exchange 5

Maximizer Exchange 5

MaxExchange 5.5 HotFix No. 1 - Series 1129
Released on July 30th, 2001
 
Type of Release: Hot Fix Release
PSN Prefix: N/A
Files Modified: Not Available
 
Changes:
The following issues are fixed:
  • Error Code 22 - Under specific conditions, packets containing "Related Entry", "Document", and "Client" transactions would result in an error code 22 during synchronization.

  • Memory Leaks - During processing and connection via FTP, memory could leak causing the application to hang after a while. This was particularly noticeable on NT 4.0, and Windows 2000 platforms.
MaxExchange 5.5 HotFix No. 1 - Series 1129
Released on July 30th, 2001
 
Type of Release: Hot Fix Release
PSN Prefix: N/A
Files Modified: Not Available
 
Changes:
The following issues are fixed:
  • Error Code 22 - Under specific conditions, packets containing "Related Entry", "Document", and "Client" transactions would result in an error code 22 during synchronization.

  • Memory Leaks - During processing and connection via FTP, memory could leak causing the application to hang after a while. This was particularly noticeable on NT 4.0, and Windows 2000 platforms.
 
MaxExchange 5.6 - Series 1104
Released on January 26th, 2001
 
Type of Release: Full Release
PSN Prefix: N/A
Files Modified:  
 
Changes:
  • N-tier support - Now MaxExchange allows for multi-level synching of data, allowing for an easier way to structure your synchronization. Remotes can now synchronize directly to their office, while the office can stay synchronized to the main office

  • Import List Initial Distribution - A feature good for companies who import a lot of records into Maximizer. This feature allows the imported records to be distributed to their respective sites more rapidly than normal

  • Support for Enterprise 5.1 SQL and Enterprise 2000 - 5.6 supports both these platforms making it easier to manage for BP's

  • Speed increase for SQL db

  • Error code 22 when processing on the Server - This was caused by a change in the distribution of an Address Book entry that had at least one large document, and any UDF's or Related Entries. In other words, anytime a distribution group was added or taken away from an Address Book entry under these circumstances. This error no longer occurs

  • Import Packet on initial distribution. - The first packet if sent to a remote site by disk would not import and thus not process. The remote can now successfully fulfill this task.

  • E-mail document corruption - Now sending an E-mail document from the SQL Server MaxExchange Server to a btrieve remote works properly, and the remote gets the correct copy of the document.

  • User Password not synchronizing - If a Users password was changed, it would erroneously not be synchronized throughout the system. Now it is.
 
MaxExchange 5.2 Patch - Series 1104
Released on January 26th, 2001
 
Type of Release: Patch Release
PSN Prefix: N/A
Files Modified:  
 
Changes:
  • E-mail document corruption - ported code from 5.6 - see 5.6

  • Error code 22 when processing on the Server- ported code from 5.6 - see 5.6

  • User Password not synchronizing- ported code from 5.6 - see 5.6

  • Resolving not getting all udf items after refresh problem
 
MaxExchange 5.2 SQL- Series 1025
Released on August 4th, 2000
 
Type of Release: Full Release
PSN Prefix: N/A
Files Modified:  

Part Number  
CD0105 MaxExchange 5.2 SQL CD
 
Changes:
  • Process Refreshes Only - The ability to tell the Server to suspend all regular processing activity to allow Refreshes to be performed first.

  • Resolving some memory leak problems

  • Speed enhancement
 
MaxExchange 5.5 Service Release 1- Series 949
Released on November 26th, 1999
 
Type of Release: Service Release
PSN Prefix: N/A
Files Modified: SPDM.EXE and Install of the MaxExchange Server

Part Number  
CD0069 MaxExchange 5.5 CD series 949
 
Changes:
  • The problem being addressed involved Documents being corrupted due to an invalid buffer length at the Server, resulting in documents received at the Remote being corrupted. The buffer length has been corrected in SPDM.EXE, so by sending a Refresh from Remotes, the documents can be fixed at the Remote.
 
MaxExchange 5.5- Series 936
Released on September 17th, 1999
 
Type of Release: Full Release
PSN Prefix: N/A
Files Modified:  

Part Number  
CD0048 MaxExchange 5.5 CD
 
Changes:
  • Created a File Integrity Checker that verifies the DRB file. It would stop people from having to delete the DRB file and send refreshes to users. It should do the following:
    1. Create a new mirror drb base on the current database at the Super Peer.
    2. Check for inconsistencies in the existing drb compared to the newly generated drb.
    3. Send out only the missing data from the existing drb. (Including deletes.)
    4. Replace the old drb with the new drb so future refreshes are correct.

  • Document for Opportunity Assigned to a Company, Contact, or Individual - If an opportunity and a Company, Contact, or Individual had the same ID, and a letter document was created at a remote for an opportunity, after synchronization it was incorrectly assigned to a Company, Contact, or Individual. This issue has been resolved.

  • Document Owner Information Lost in Synchronization - If you changed the owner of a Marketing Library document, after synchronization the new owner value was not reflected. This issue has been fixed.

  • New Ability to Bypass the Default FTP Port Number - A registry value was added for the FTP transport mechanism, which allows a system administrator to bypass our default port number. This greatly improves the MaxExchange functionality with firewalls.

    IF YOU WISH TO CHANGE THE DEFAULT FTP PORT NUMBER -- By default, MaxExchange listens on port 21. If you wish to change the port number you must change a Windows Registry setting. To do this follow this procedure:

    1. Shut down MaxExchange.
    2. From the Windows Start menu, choose Run.
    3. In the Open field, type REGEDIT to run the Windows Registry Editor.
      WARNING: Be extremely careful when updating the Windows Registry. Modifying the wrong entry can seriously affect your system. If in doubt, seek help from an experienced Windows user or your system administrator.
    4. Navigate to the key:
      HKEY_CURRENT_USER\Software\Maximizer Technologies\MaxExchange\Datasynch\
    5. Find the Dword Value called FTPServerMainPort and enter the port number you wish to listen on in the Value Data field. Make sure the Base value is set to decimal.
    6. Close the Registry Editor and restart MaxExchange
      (NOTE: these steps must be performed at both the Remote and Server.)

  • General Protection Fault During Packet Download - If the server closed the application at the same time the remote had finished downloading a packet, a GPF occurred. This issue has been fixed.

  • Disconnection when Uploading a Packet - If the connection was lost while a remote was uploading a packet, the remote would "hang" indefinitely. This no longer occurs.

  • Packet Not Copied to the Backup Directory - If the connection was lost while a remote was uploading a packet, the packet would not get copied to the "backup" directory. This has been fixed.

  • Possible Packet Corruption - In some cases, answering "No" or "Cancel" to a Process Refresh Packet message led to corruption of the packet. This issue has been resolved.

  • Changing a Distribution Group's Name at a Remote - In certain circumstances, if a distribution group's name was changed at a remote, an Address Book entry could be dropped from the remote. This no longer occurs.

  • Adding an Address Book Entry to a Distribution Group - If an Address Book entry was added to a group at a remote, after synchronization the entry was updated but it's corresponding documents were not. This issue has been fixed.
 
MaxExchange 5.01- Series 912
Released on March 19th, 1999
 
Type of Release: Full Release
PSN Prefix: N/A
Files Modified:  

Part Number  
CD0041 MaxExchange 5.01 CD
 
Changes:
  • Document for Opportunity Assigned to a Company, Contact, or Individual - If an opportunity and a Company, Contact, or Individual had the same ID, and a letter document was created at a remote for an opportunity, after synchronization it was incorrectly assigned to a Company, Contact, or Individual. This issue has been resolved.

  • Document Owner Information Lost in Synchronization - If you changed the owner of a Marketing Library document, after synchronization the new owner value was not reflected. This issue has been fixed.

  • New Ability to Bypass the Default FTP Port Number - A registry value was added for the FTP transport mechanism, which allows a system administrator to bypass our default port number. This greatly improves the MaxExchange functionality with firewalls.

    IF YOU WISH TO CHANGE THE DEFAULT FTP PORT NUMBER -- By default, MaxExchange listens on port 21. If you wish to change the port number you must change a Windows Registry setting. To do this, follow this procedure:

    1. Shut down MaxExchange.
    2. From the Windows Start menu, choose Run.
    3. In the Open field, type REGEDIT to run the Windows Registry Editor.
      WARNING: Be extremely careful when updating the Windows Registry. Modifying the wrong entry can seriously affect your system. If in doubt, seek help from an experienced Windows user or your system administrator.
    4. Navigate to the key:
      HKEY_CURRENT_USER\Software\Maximizer Technologies\MaxExchange\Datasynch\
    5. Find the Dword Value called FTPServerMainPort and enter the port number you wish to listen on in the Value Data field. Make sure the Base value is set to decimal.
    6. Close the Registry Editor and restart MaxExchange
      (NOTE: these steps must be performed at both the Remote and Server.)

  • General Protection Fault During Packet Download - If the server closed the application at the same time the remote had finished downloading a packet, a GPF occurred. This issue has been fixed.

  • Disconnection when Uploading a Packet - If the connection was lost while a remote was uploading a packet, the remote would "hang" indefinitely. This no longer occurs.

  • Packet Not Copied to the Backup Directory - If the connection was lost while a remote was uploading a packet, the packet would not get copied to the "backup" directory. This has been fixed.

  • Possible Packet Corruption - In some cases, answering "No" or "Cancel" to a Process Refresh Packet message led to corruption of the packet. This issue has been resolved.

  • Changing a Distribution Group's Name at a Remote - In certain circumstances, if a distribution group's name was changed at a remote, an Address Book entry could be dropped from the remote. This no longer occurs.

  • Adding an Address Book Entry to a Distribution Group - If an Address Book entry was added to a group at a remote, after synchronization the entry was updated but it's corresponding documents were not. This issue has been fixed.
 
MaxExchange 5.0 SQL Service Release 1 - Series 905
Released on January 29th, 1999
 
Type of Release: Service Release
PSN Prefix: N/A
Files Modified: Spdm.exe; Rmdm.exe; Distlist.exe
 
Changes:
SQL version of MaxExchange 5.0 Service Release 1 Updates:
  • RMDM - Processing refresh leaves records locked.

  • SPDM - Client Opportunity Doc created on Remote saved to the Client on the Server instead of to the Opportunity.

  • DistList - Were not forced to enter Email address when changing a Distribution Site from Net Direct to Email.
 
MaxExchange 5.0 SQL- Series 847
Released on December 14th, 1998
 
Type of Release: Full Release
PSN Prefix: N/A
Files Modified: Spdm.exe; Rmdm.exe; Distlist.exe
 
Changes:
  • Please note that MaxExchange 5.0 SQL includes all updates addressed in MaxExchange 5.0.

  • SQL version of MaxExchange 5.0

  • Provided the link between MaxExchange and Microsoft SQL Server 6.5 and Microsoft SQL Server 7.0
 
MaxExchange 5.0 - Series 842
Released on October 16th, 1998
 
Type of Release: Full Release
PSN Prefix: N/A
Files Modified:  
 
Changes:
  • Changed to support new Enterprise 5.0 file changes.

  • Introduced new Transport method FTP.

  • Added checking for Site Licensing, and Team Selling to the Distribution List Manager.

  • Support for Mixed Transport from the Server.

  • Fixed No Opportunities in Refresh when site has client with no *MaxExchange Distribution Group problem.

  • Fixed many other small data synchronization bugs.

  • Introduced Date Time stamping in the SPDM and the RMDM logs.