Performing a mail merge

Issue	Solution
Mail merge fails because Tomcat is not running.	The Tomcat service is required to perform a mail merge. If the Tomcat service is not running, errors usually occur in other areas of Sage CRM that rely on this service. For example, the Interactive Dashboard. Restart the Tomcat service if it has stopped. Alternatively, you can schedule a Tomcat service restart.
Mail merge fails when a large number of records are merged.	Reduce the size of the mail merge template by resizing images or changing images to GIF format. Reduce the number of records that are merged at once. For example, perform a merge on all person records with names beginning with A-L and then perform a second merge on all person records with names beginning with M-Z.
Mail merge fields that are not included in a group's Group Content list are not merged when performing a mail merge on a static or dynamic group.	This issue can occur on upgraded versions of Sage CRM. Run the following query: Copy `UPDATE Custom_SysParams SET Parm_Value ='N' WHERE parm_name = 'AllowDupRecs'` And then perform a metadata refresh.
Mail merge fails and an SQL error 208 is displayed.	The number of columns in a view exceeds 1024 columns. Remove fields from the view and perform the mail merge again. Test this on a local test environment before you implement it on the production server. For more information, see Optimizing a custom entity list for faster loading in the System Administrator Help.

Mail merge fails because Tomcat is not running.

The Tomcat service is required to perform a mail merge. If the Tomcat service is not running, errors usually occur in other areas of Sage CRM that rely on this service. For example, the Interactive Dashboard. Restart the Tomcat service if it has stopped. Alternatively, you can schedule a Tomcat service restart.

Mail merge fails when a large number of records are merged.

Reduce the size of the mail merge template by resizing images or changing images to GIF format.
Reduce the number of records that are merged at once. For example, perform a merge on all person records with names beginning with A-L and then perform a second merge on all person records with names beginning with M-Z.

Mail merge fields that are not included in a group's Group Content list are not merged when performing a mail merge on a static or dynamic group.

This issue can occur on upgraded versions of Sage CRM. Run the following query:

Copy

UPDATE Custom_SysParams SET Parm_Value ='N' 
WHERE parm_name = 'AllowDupRecs'

And then perform a metadata refresh.

Mail merge fails and an SQL error 208 is displayed.

The number of columns in a view exceeds 1024 columns. Remove fields from the view and perform the mail merge again. Test this on a local test environment before you implement it on the production server. For more information, see Optimizing a custom entity list for faster loading in the System Administrator Help.