This article provides information regarding Maximizer CRM 10 Service Release 1 - Series 1833

On this page

Applicability Overview Issues Resolved Viewing Email in Maximizer Web Access XML Import/Export of Email Messages Maximizer IIS Components and Windows 2008 Server Download Install Instructions Post Installation Instructions

Applicability

This service release applies to the following releases:

• Maximizer CRM 10 - Series 1743
• Maximizer CRM 10 Hot Fix 1 - Series 1804
• Maximizer CRM 10 Service Pack 1 - Series 1817

It applies to the following editions:

• Maximizer CRM 10 Enterprise Edition
• Maximizer CRM 10 Professional Edition
• Maximizer CRM 10 Group Edition

All issues fixed in Maximizer CRM 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. All Maximizer CRM 10 users are recommended to apply this update.

top

Issues Resolved

The following issues are resolved when this update is applied

1. Address Book Entry Issues
   • Pressing F7 in an Address Book entry brings up the wrong dialog box.
   • The Relationship Type drop-down list ignores the sort order specified in the Set Up Items dialog box.
   • The Export Address Book Entries command does not save all selected fields to export catalogs.
   • Users who do not have Read permission for user-defined fields cannot access the “Sales Lead” and “Lead status” fields, even though these fields are system fields.
   • When deleting a Contact in Maximizer Web Access, the Contact's notes and documents are not moved to the Company entry and are deleted.
   
   
2. Database Issues
   • When Transaction Journaling is enabled, you cannot directly update the AMGR_Notes view using SQL Server 2005.
   • When upgrading a Pervasive.SQL database to an SQL database, the Appointment_Id field is not generated for all records in the AMGR_Appointments table.
   • When upgrading a Pervasive.SQL database to an SQL database, users are not created if their passwords do not follow the SQL Server 2005 password policy.
   • When upgrading a version 7.x–9.x Pervasive.SQL database to an SQL database, private column setups are given public read access.
   • When restoring a database in Administrator, selecting a backup (.bak) file on a different computer causes the restore to fail.
   
   
3. Reporting and Printing Issues
   • In certain circumstances, the "Print Hotlist tasks" option in the Print Detailed Report command causes Maximizer to close unexpectedly.
   • When printing Hotlist reports, the reports do not display properly after you modify the Hotlist column setup.
   • Maximizer closes unexpectedly when previewing detailed reports for entries with alphanumeric user-defined fields containing 255 characters.
   • When creating Appointment Details calendar reports with the "Include name/addr/tel." option selected, the reports do not always display the main phone numbers of Address Book entries.
   • When the Address Book list is cleared, the Print Labels command does not display the Delivery Address dialog box prompting the user to supply text for labels.
   
   
4. Calendar and Hotlist Issues
   • Date user-defined fields with the "Include in Hotlist" and "Annually occurring event" attributes do not get built into the Hotlist. This issue only occurs when you assign the user-defined fields from the Address Book entry dialog box.
   • Email reminders for appointments with multiple users list the location twice.
   • Conflicting appointments do not appear in the Hotlist window.
   
   
5. Email Issues
   • When sending Company Library documents to Address Book entries, the documents are not saved to the entries even if you select the "Save copy of message to entry’s Documents" option in Email Preferences.
   • In rare circumstances, the text "SMTP" is added to the beginning of email addresses when using the Reply All option in email messages saved as documents.
   • When using GroupWise email client, changing the Windows layout causes Maximizer to close unexpectedly.
   • If the "Inbox", "Sent Items", and "Deleted Items" email folders do not use the default names, Maximizer Web Access does not recognize the email folders.
   
   
6. Microsoft Office Integration Issues
   • The "Maximizer Link Document" option in Microsoft Word 2007 does not properly link documents when specifying Universal Naming Convention (UNC) file paths.
   • Some User information merge fields do not merge properly when you insert them into documents in Word.
   • In Outlook 2007, the Save Email to Contact in Maximizer command does not remove email messages from the Draft folder after messages are sent.
   • When using Outlook 2007 on a Windows Vista machine, Maximizer closes unexpectedly when sending email messages separately to multiple Address Book entries and saving the messages as documents with the entries.
   
   
7. Maximizer CRM Group Editions Issues
   • When installing Group Edition Workstation, "\MAXIMIZER" is automatically appended to the end of the Microsoft SQL server name, even if you browse to an existing SQL server that already has "\MAXIMIZER" appended to the end of its name.
   • The Utilities > System Configuration option in Administrator is not available.
   • When logging in to an Address Book on a Group Edition server with security disabled, users are forced to log in if their Windows user accounts do not exist on the server machine.
   • When restoring a database in Administrator, selecting a backup (.bak) file on a different computer causes the restore to fail.
   
   
8. Document Issues
   • When you use Document Administration to convert embedded documents to linked documents, documents with file extensions longer than three characters are not converted.
   • If a user has Read and Insert but not Modify permissions for documents, MaxWord closes unexpectedly when saving a document with a name longer than 32 characters.
   
   
9. 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.
   
   
10. MaxSync for Microsoft Exchange Issues
    • When MaxSync for Microsoft Exchange inserts appointments for users, other Microsoft Outlook users do not see the time span of the appointments marked as busy for the affected users.
    • If you are using Microsoft Outlook 2003 Service Pack 2 or later, multiple-user appointments created in Maximizer get deleted by MaxSync for Microsoft Exchange after other users accept the appointments.
    • When using the User Administration dialog to create MaxSync for Microsoft Exchange users, the dialog box stops responding if the Microsoft Exchange server contains a large number of users.
    
    
11. Other Issues
    • When adding a Traditional campaign, user-defined fields are not retained when you move between tabs in the Add Traditional Campaign dialog box.
    • Using the Name_and_Address field in the Format Preferences causes the address format to display incorrectly.
    • Numeric user-defined fields in Web Forms do not support values larger than 2147483647.
    • In certain configurations, TAPI works on only the first incoming call. You must restart Maximizer for TAPI to work again.
    • OrderDesk does not work on new installations of Windows Vista until Maximizer is run under an Administrator user.
    • Logging in to Maximizer generates "Login failed" events in Windows Event Viewer, even after you log in successfully.
    
    

Viewing Email in Maximizer Web Access

A MAPI client (Microsoft Outlook) must be installed on the server in order to view email messages from the Documents window of an entry in Maximizer Web Access.

XML Import/Export of Email Messages

When importing or exporting data using XML, email messages saved in the Documents tab are not imported/exported.

top

Maximizer IIS Components and Windows 2008 Server

If you are using Windows 2008 Server, you must enable the .NET Framework feature in order to install Maximizer IIS components.

To enable the .NET Framework feature, follow these steps:

• Click on the Turn Windows features on or off option.
• Click on Features and then click Add Features.
• Select the Microsoft .NET Framework feature.
• Click OK.

top