MaxExchange 6.0 Service Pack 3 - Series 1225
Released on July 8th, 2002
|
| |
| Type of Release: |
Service Pack |
| PSN Prefix: |
N/A |
| Files Modified: |
Maxwin.exe; MxMail97.dll; Rmdm.exe; Spdm.exe; MaxPort.exe |
| Applicability: |
Run MaximizerEnterpriseMaxExchange6.0SP3.exe on all Maximizer Enterprise and MaxExchange 6.0 machines. |
|
| |
| Changes: |
| Maximizer Enterprise Issues: |
- Creation Date for new Address Book entry - Previously, when a new Address Book entry was created, the creation date was taken from the default entry. This issue was corrected by defaulting the creation date to the systems date.
- Numeric Opportunity UDF in Opportunity view - Previously, when viewing an Opportunity numeric User-Defined Field (UDF) in the Opportunity window, the decimal place would not be displayed. This issue has been resolved.
- Error code 22 during MaxPort imports - Previously, when importing Address Book entries using MaxPort, an error code 22 would occur if transaction journalling was enabled. This issue has been resolved.
- MTI import fails when record length exceeds 1KB - Previously, when a MTI file was imported and the Field Names (Line 3 of the MTI file) exceeded 1 KB (1024 characters), the MTI import would fail. This issue has been resolved and now supports Field Names up to 4 KB (4096 characters).
- Missing columns when importing tab-delimited files - Previously, when a tab-delimited file was imported using File > Import > Address Book Entries, all header columns past 1 KB (1024 characters) do not appear in the "Fields from file" list box. This issue has been resolved and now supports header columns up to 4 KB (4096 characters).
- Emails subject truncated to 31 characters - Previously, when an email merge was performed using Maximizer Compose Email dialog box and the subject of the email was more than 30 characters, the email subject would be truncated to the first 31 characters when the "Save copy to entry's Documents" option was used. This issue has been resolved.
- Email address changes when recipient list is modified - Previously, when composing an email in Maximizer's Compose Email dialog box and the user clicks the CC button to add another recipient to the email, if the display name in the To, CC, or BCC fields match an entry in Outlook's Contact folder, the email address from Outlook would be used. This issue has been resolved.
|
| MaxExchange Issues: |
- Viewing document results in a MaxExchange packet - Previously, when any OLE document was opened, it would result in a MaxExchange transaction. Even when the OLE document was only viewed, the entire document would be synchronized. This issue has been resolved for Excel and JPG documents. The fix is that the user is prompted to determine if any changes were made. This fix is for the document and Marketing Library windows.
- Running multiple instances of MaxExchange Server - Previously, starting a second instance of MaxExchange Server would cause program conflicts. This issue was corrected by preventing a second instance of MaxExchange Server from starting.
- Error 22 on the Opportunity file - Previously, under very specific conditions an error code 22 would occur when processing. This issue has been corrected.
- Dynamic strategy synchronization issue - Previously, if a remote machine made changes to a dynamic strategy, the strategy would become unusable. This issue has been corrected.
- Opportunity completion comment synchronization - Previously, under very specific circumstances, after opportunities were modified on the remote and synchronized to the server, the completion comment of one opportunity would appear in the completion comment field for another opportunity. This would only occur when the second opportunity completion comment was blank. This issue has been corrected.
- Cleaning up distribution information - Previously, the distribution file was not updated when an Opportunity was deleted. This issue has been corrected.
- Removing Site from Team affects clients of Site - Previously, if a site was removed from a team, the clients associated with Opportunities of that team would be removed from the site, even if a distribution group for that client was assigned to the site. This issue has been corrected.
|
| |
MaxExchange 6.0 (Includes Service Pack 2 in Autorun) - Series 1129
Released on August 9th, 2001
|
| |
| Type of Release: |
Full Release |
| PSN Prefix: |
N/A |
| Files Modified: |
Not Available |
| Changes: |
See MaxExchange 6.0 Service Pack 2 - Series 1129 |
| Part Number |
|
| CD0148 |
MaxExchange 6.0 CD (series 1129) |
|
| |
MaxExchange 6.0 Service Pack 2 - Series 1129
Released on July 31st, 2001
|
| |
| Type of Release: |
Service Release |
| PSN Prefix: |
N/A |
| Files Modified: |
Not Available |
|
| |
| Changes: |
|
MaxExchange 6.0 Service Pack 2 includes all changes from MaxExchange 6.0 Service Pack 1 and Maximizer Enterprise 6.0 Service Pack 2.
|
| Service Pack 1 Issues Fixed: |
- Success/fail displayed in packlog.txt file - In the packlog.txt log file, the status of processed packets is now displayed as "successful" or "failed".
- Timing processing at midnight problem - Previously, when the timing of packet processing was set to midnight, processing would occur each time MaxExchange Server was opened. This issue has been fixed.
- Duplicated mnemonic letter at remote - Previously, under the File menu of MaxExchange Remote, the letter "C" appeared as a mnemonic letter for two menu items. This issue has been fixed.
- Adding a remote server and a remote in Network Direct mode - Previously, if you added a remote server using the Network Direct transport mode, and then immediately added a remote on this particular server, problems occurred. This issue has been fixed.
- Refresh to network remote server problem - Previously, if you processed an initial refresh on a remote server using the Network Direct transport mode, and chose an existing Btrieve database as the remote synchronized database, a problem occurred: the remote wouldn't process packets in the Inbox directory even though MEX file was deleted. The problem did not occur if you used an empty folder or a new database as the remote synchronized database. This issue has been fixed.
- Document templates not present after refresh - Previously, if you created a document template on the server and immediately did a refresh for the remote site, the template was not sent to that site. This issue has been fixed.
- Deleting remote site deletes packets in Outbox folder - Previously, when you deleted a site using Distribution List Manager, all packets in the site's Outbox folder and Backup folder were deleted. This issue has been fixed.
- Displaying users from other databases in Select User dialog - Previously, opening a database that was not synchronized with Distribution List Manager would cause the following problem: in the Add Member dialog box, pressing the Select button, then pressing Cancel, and then pressing Select again retrieved a list of users from the synchronized (incorrect) database. This issue has been fixed.
- Changing user rights for OrderDesk - Previously, changes you made to user rights were not correctly processed by the server and thereby not sent to remotes. This issue has been fixed.
- Email prompt freezes at remote - Previously, after switching from the FTP transport method to Email, and then shutting down and restarting MaxExchange Remote, a problem occurred with the Email Login dialog box. This issue has been fixed.
- Remote doesn't write in RMDMLOG file in email mode - Previously, when you switched from the FTP transport method to Email, and then restarted the MaxExchange Remote, the remote did not write to the RMDMLOG file. This issue has been fixed.
- Deletion of site's email address - Previously, the email address of a remote was deleted if you switched from the FTP transport method to Email, and then modified the transport method in the Add/Modify Site dialog box. This issue has been fixed.
- Having multiple sites with same email address - Previously, MaxExchange would allow you to have multiple remote sites with the same email address when you switched from the FTP transport method to Email. The duplicate address was blocked only when you added new sites. This issue has been fixed.
- "Idle" label problem at server - Previously, while the server was processing, the "Idle..." label was visible. This has been fixed so the message appears only when the server is finished.
- Log option level missing in email mode at remote - Previously, when you opened the Logging Preferences dialog box at a remote running email transport, the log detail was not displayed. If you chose a logging level option, closed the dialog box and reopened it, neither your new selection nor the log was displayed. This issue has been fixed.
- Switching from empty address field problem - Previously, leaving an empty address field for Network Direct or Email mode was treated as a real update of the address. This occurred if you switched from FTP to another transport mode and then back to FTP without adding a value in the address field. This issue has been fixed.
- Setting email of 2nd site to email of 1st site problem - Previously, if you had more than one remote site using the Email transport method, MaxExchange changed the second site's email address to that of the first site after a few packets were exchanged between the second email site and the server. This issue has been fixed.
- Unable to modify site name - Previously, if you attempted to change a site name using an existing transport method, you received a message saying "This site already exists..." and couldn't modify the name. This issue has been fixed.
- Displaying results when starting MaxExchange Server/Remote - The Displaying Results option is now enabled by default when you start MaxExchange Server/Remote.
- Switch from email to network problem - Previously, after you switched from the Email transport method to Network Direct, the remote placed packets into the "Trnsp" folder on the server, but the server used two processing cycles to correctly process the packets. This issue has been fixed.
- "Maximum number of sites is reached" message problem - Previously, a "Maximum number of sites is reached" message was incorrectly displayed when attempting to delete a site in the Modify Member dialog box. This has been fixed.
- Error code 22 on large refreshes when adding a new site - Previously, creating a relatively large initial refresh for a new site (i.e., a site containing many large documents and related entries) caused an error code 22 in some situations. This has been fixed.
- Enabled address text box when adding FTP site - Previously, if you added a remote site using FTP mode, the Address field was enabled instead of disabled. Note that this is a required field for a remote server.
- Changing log details level problem at remote - Previously, if you changed the log details level at a remote, the setting would be different the next time you displayed it. This issue has been fixed.
- Error code 10 on client file - Previously, after converting an Address Book record from a Company to an Individual, and then processing on the server, you received an Error Code 10 on the client file when processing at the remote. The main fix for this is in Maximizer 6.0 SP1, and a smaller portion of the fix is in MaxExchange 6.0 SP1. You must install Maximizer 6.0 SP1 to eliminate this error message.
- Empty dialog at email remote - Previously, a remote site using the Email transport method displayed an empty dialog box when the server's email address was changed. This issue has been fixed.
- No transaction for add/update of remote server's email address - Previously, adding or updating a remote server's email address did not create a transaction record. This issue has been fixed.
- Account Workspace ID reference corrected - The reference to "Account Workspace ID" in the Add/Modify Distribution Sites dialog box has been changed to "Address Book Folder ID".
- Premature ending of remote server's installation update - Previously, the installation update of a remote server was stopped by the presence of the SPDM.EXE file. This issue has been fixed.
- Server continuously writes current time to the log file - Previously, under very rare circumstances, the server continuously wrote the current time to the SPDMLOG.TXT file. This issue has been fixed.
|
| |
| SP2 Issues Fixed: |
- Error Code 22 - Previously, due to problems with documents and UDFs using a filtering routine, several Error Code 22 messages were experienced on the server. As a result, processing was halted until OK was pressed. This issue has been fixed.
- UDFs added quickly not synchronized to remotes or server - Previously, if several UDFs were added to the database in a short period of time using methods such as a mass import or global edit, many of the UDFs were not synchronized. This issue has been fixed.
- Issues with dynamic strategies - Previously, if dynamic strategies were used with opportunities, they were not handled properly by MaxExchange, and the result was unpredictable. This issue has been fixed.
- Error Code 3 - Previously, upon startup of the server or remote, it was possible to begin a processing session before the application had completely initialized. This led to an Error Code 3, as well as a connection to the server error. This issue has been fixed.
- Orphaned dynamic team records - Previously, if an opportunity that was using a Dynamic Team was deleted on the remote, the team was not deleted from the server leaving it as an orphaned record. This issue has been fixed. Also, an option has been added to allow the server or remote to delete orphaned records.
- Error Code 51 - Previously, an Error Code 51 occurred on the transaction file when a folder password was put on the database, and MaxExchange Server was launched. This issue has been fixed.
- Drag and drop into Opportunity tab - Previously, under certain circumstances, dragging and dropping an Address Book entry to the Opportunity tab resulted in creating an opportunity record with the same details as an existing record. This issue has been fixed.
- Dynamic team creation on remotes - Previously, remote users were erroneously allowed to create dynamic teams at a remote site. This should not have been possible and the issue has been fixed.
|
| |
MaxExchange 6.0 Service Pack 1 - Series 1118
Released on May 4th, 2001
|
| |
| Type of Release: |
Service Release |
| PSN Prefix: |
N/A |
| Files Modified: |
Not Available |
|
| |
| Changes: |
Service Pack 1 Issues Fixed:
- Success/fail displayed in packlog.txt file - In the packlog.txt log file, the status of processed packets is now displayed as "successful" or "failed".
- Timing processing at midnight problem - Previously, when the timing of packet processing was set to midnight, processing would occur each time MaxExchange Server was opened. This issue has been fixed.
- Duplicated mnemonic letter at remote - Previously, under the File menu of MaxExchange Remote, the letter "C" appeared as a mnemonic letter for two menu items. This issue has been fixed.
- Adding a remote server and a remote in Network Direct mode - Previously, if you added a remote server using the Network Direct transport mode, and then immediately added a remote on this particular server, problems occurred. This issue has been fixed.
- Refresh to network remote server problem - Previously, if you processed an initial refresh on a remote server using the Network Direct transport mode, and chose an existing Btrieve database as the remote synchronized database, a problem occurred: the remote wouldn't process packets in the Inbox directory even though MEX file was deleted. The problem did not occur if you used an empty folder or a new database as the remote synchronized database. This issue has been fixed.
- Document templates not present after refresh - Previously, if you created a document template on the server and immediately did a refresh for the remote site, the template was not sent to that site. This issue has been fixed.
- Deleting remote site deletes packets in Outbox folder - Previously, when you deleted a site using Distribution List Manager, all packets in the site's Outbox folder and Backup folder were deleted. This issue has been fixed.
- Displaying users from other databases in Select User dialog - Previously, opening a database that was not synchronized with Distribution List Manager would cause the following problem: in the Add Member dialog box, pressing the Select button, then pressing Cancel, and then pressing Select again retrieved a list of users from the synchronized (incorrect) database. This issue has been fixed.
- Changing user rights for OrderDesk - Previously, changes you made to user rights were not correctly processed by the server and thereby not sent to remotes. This issue has been fixed.
- Email prompt freezes at remote - Previously, after switching from the FTP transport method to Email, and then shutting down and restarting MaxExchange Remote, a problem occurred with the Email Login dialog box. This issue has been fixed.
- Remote doesn't write in RMDMLOG file in email mode - Previously, when you switched from the FTP transport method to Email, and then restarted the MaxExchange Remote, the remote did not write to the RMDMLOG file. This issue has been fixed.
- Deletion of site's email address - Previously, the email address of a remote was deleted if you switched from the FTP transport method to Email, and then modified the transport method in the Add/Modify Site dialog box. This issue has been fixed.
- Having multiple sites with the same email address - Previously, MaxExchange would allow you to have multiple remote sites with the same email address when you switched from the FTP transport method to Email. The duplicate address was blocked only when you added new sites. This issue has been fixed.
- "Idle" label problem at server - Previously, while the server was processing, the "Idle..." label was visible. This has been fixed so the message appears only when the server is finished.
- Log option level missing in email mode at remote - Previously, when you opened the Logging Preferences dialog box at a remote running email transport, the log detail was not displayed. If you chose a logging level option, closed the dialog box and reopened it, neither your new selection nor the log was displayed. This issue has been fixed.
- Switching from empty address field problem - Previously, leaving an empty address field for Network Direct or Email mode was treated as a real update of the address. This occurred if you switched from FTP to another transport mode and then back to FTP without adding a value in the address field. This issue has been fixed.
- Setting email of 2nd site to email of 1st site problem - Previously, if you had more than one remote site using the Email transport method, MaxExchange changed the second site's email address to that of the first site after a few packets were exchanged between the second email site and the server. This issue has been fixed.
- Unable to modify site name - Previously, if you attempted to change a site name using an existing transport method, you received a message saying "This site already exists..." and couldn't modify the name. This issue has been fixed.
- Displaying results when starting MaxExchange Server/Remote - The Displaying Results option is now enabled by default when you start MaxExchange Server/Remote.
- Switch from email to network problem - Previously, after you switched from the Email transport method to Network Direct, the remote placed packets into the "Trnsp" folder on the server, but the server used two processing cycles to correctly process the packets. This issue has been fixed.
- "Maximum number of sites is reached" message problem - Previously, a "Maximum number of sites is reached" message was incorrectly displayed when attempting to delete a site in the Modify Member dialog box. This has been fixed.
- Error code 22 on large refreshes when adding a new site - Previously, creating a relatively large initial refresh for a new site (i.e., a site containing many large documents and related entries) caused an error code 22 in some situations. This has been fixed.
- Enabled address text box when adding FTP site - Previously, if you added a remote site using FTP mode, the Address field was enabled instead of disabled. Note that this is a required field for a remote server.
- Changing log details level problem at remote - Previously, if you changed the log details level at a remote, the setting would be different the next time you displayed it. This issue has been fixed.
- Error code 10 on client file - Previously, after converting an Address Book record from a Company to an Individual, and then processing on the server, you received an Error Code 10 on the client file when processing at the remote. The main fix for this is in Maximizer 6.0 SP1, and a smaller portion of the fix is in MaxExchange 6.0 SP1. You must install Maximizer 6.0 SP1 to eliminate this error message.
- Empty dialog at email remote - Previously, a remote site using the Email transport method displayed an empty dialog box when the server's email address was changed. This issue has been fixed.
- No transaction for add/update of remote server's email address - Previously, adding or updating a remote server's email address did not create a transaction record. This issue has been fixed.
- Account Workspace ID reference corrected - The reference to "Account Workspace ID" in the Add/Modify Distribution Sites dialog box has been changed to "Address Book Folder ID".
- Premature ending of remote server's installation update - Previously, the installation update of a remote server was stopped by the presence of the SPDM.EXE file. This issue has been fixed.
- Server continuously writes current time to the log file - Previously, under very rare circumstances, the server continuously wrote the current time to the SPDMLOG.TXT file. This issue has been fixed.
|
| |
MaxExchange 6.0 - Series 1049
Released on December 4th, 2000
|
| |
| Type of Release: |
Full Release |
| PSN Prefix: |
N/A |
| Files Modified: |
|
| Part Number |
|
| CD0113 |
MaxExchange 6.0 CD |
|
| |
| Changes: |
- MaxExchange 6.0 can be set up to operate in an n-tier configuration: An n-tier configuration allows for a more complex tree structure, in which a Distribution Site may also function as a server for other Distribution Sites. This is referred as MaxExchange Remote Server. It synchronizes with the central Address Book folder on the Server, and passes along data packets to other Remotes on the distribution tier below it acting as a middle tier in a multi-tiered synchronization tree.
The n-tier configuration distributes much of the processing load to the Remote Servers, which dramatically improves synchronization time across the entire tree structure.
The Remote Server performs two functions:
- It synchronizes the changes from its Distribution Sites with the Server and receives updates from the Server.
- It generates and sends its own updates to its Distribution Sites.
- This version allows the synchronization of orders and inquiries.
- This version has an option to process refreshes only. MaxExchange Server and Remote Server allow you to temporarily disable normal synchronization transactions with Distribution Sites. When this option is turned on, only refreshes of a Distribution Site will be processed.
This is a useful tool if you need to send a refresh to a Distribution Site and the Server is already occupied with many other transactions. You can turn on the Process Refreshes Only option, send the refresh to the Distribution Site, then turn off the option.
|
| |