1. Have you been able to merge successfully before? If no, refer to the Compatibility Fact Sheet for your version of GIFTS to make sure that your version of Word is certified as compatible with GIFTS. If yes, continue to the next step.

2. Have you recently upgraded to a new version of Word? If yes, refer to the Compatibility Fact Sheet for your version of GIFTS to make sure that your version of Word is certified as compatible with GIFTS. Otherwise, continue to the next step.

3. Log in to GIFTS on another workstation and try to merge from the same template. Does the problem occur on all workstations? If the problem is specific to one workstation (or some workstations but not all), proceed to Workstation-Specific Errors. If it occurs on all workstations, proceed to the next step.

4. Do you run Microsoft Word from a network server? If yes, proceed to Network Installations of Word. Otherwise, continue to the next step.

5. Does the GIFTS user have access rights to the network directory that contains your GIFTS correspondence templates? By default, templates are located in the Template directory within your GIFTS directory. Contact your IT department to verify that the GIFTS user has read and write permissions for all of your Template directories, and retry the merge. If the error still occurs, proceed to the next step.

6. Try to merge correspondence using a different template. Does the error occur with other templates? If the problem is specific to one template, please proceed to Template-Specific Errors. Otherwise, proceed to the next step.

7. Please contact MicroEdge Technical Support for additional assistance.


Note: If the problem does not occur on all workstations, it is an environmental issue rather than an issue with your GIFTS software. It is the client's responsibility to reconcile the differences between operational and problematic workstations.

Workstation-Specific Errors - If the error occurs on one workstation only, the most common cause of the error is a problem with the copy of Microsoft Word on that workstation. Take the following steps to resolve the issue:
-Reboot the workstation, and retry the merge. Rebooting can resolve intermittent problems.
-Run the Detect and Repair feature of Word (from the Word menu, select Help > Detect and Repair). For complete information about this Word utility, please refer to your Word documentation.
-If the error still occurs, please go to Step 5 of the troubleshooting procedure in Cause and Troubleshooting.

Network Installations of Word - The most common cause of the error is a problem with your installation of Microsoft Word. Take the following steps to resolve the issue:
-Reboot the server that runs Word, and retry the merge. Rebooting can resolve intermittent problems.
-Run the Detect and Repair feature of Word (from the Word menu, select Help > Detect and Repair ). For complete information about this Word utility, please refer to your Word documentation.
-If the error still occurs, please go to Step 5 of the troubleshooting procedure in Cause and Troubleshooting.

Template-Specific Errors - There is likely a problem with the template you are using when the error occurs. Take the following steps to resolve the issue:
-Open the template from the GIFTS Administrator Module to ensure that the merge file still exists. Note the exact location of the template.
-Does the body of the template include merge fields? If there are no merge fields in the body of the text, GIFTS generates the error because it cannot find any fields.
-Does the GIFTS user have access rights to the directory that contains the template? If your templates are stored in different directories, or subdirectories within the Template directory, the GIFTS user may not have access rights to all of your template files. Contact your IT department to ensure that the user has both read and write permissions to the directory that contains the template.
-Re-create the problematic template and attempt to generate correspondence with this newly created template. Does the issue persist? If no, then it may be possible the original Template became corrupt; you may wish to replace the old template with this new copy.