Error -2147352567 Unsupported Code 265:164:132 received during Test Merge of FormDocs form template

From Support

If you have a question or seek clarification, please call Technical Support.

Problem:

A customer is getting the following error whenever they attempt to perform a test merge:

"-2147352567 Unsupported Code[265:164:132]"

Solution:

This error is coming directly from FormDocs. I have found more than one possible solution.

Try performing a test merge on the Invoice form that is included with the RJS Text Layer Designer. If this errors as well, then there is a problem with the FormDocs installation. If not, then it could simply be that the form template itself is corrupt. However, I am still unsure whether a bad install could lead to the corrupt form template.

Solution 1: According to FormDocs, this issue can arise when the user that installed FormDocs does not have enough authority. As a result, the PDF writing capability is missing. First, check that the "FormDocs Utility" is in your printer list. If the "FormDocs Utility" is in your printer list, you will need to check if it was installed properly. To test this, open the form in the FormDocs Filler. You can then attempt to manually create a PDF by going to File > Export and changing the "Save As Type" to PDF. If PDF is missing, then you will need to reinstall FormDocs. If you find that either of these steps failed, log into the PC as an administrator, uninstall FormDocs (make sure that the FormDocs print drivers are gone) and then reinstall FormDocs from our website (http://www.rjssoftware.com/files/ws_eforms/formdocs/fdw70.exe).

Solution 2: I have also found that this error can also occur if the form template is corrupt. I am unsure if a bad install of FormDocs (resolved in Solution 1) could lead to the corrupt form template, but I cannot rule it out.

I am beginning to think that the amount of editing that has been done to a form is directly related to this issue. I am finding that forms that have had major revisions done to them seems to increase the potential for saving a corrupt form. It may have to do with some sort of internal field indexing. Adding and removing fields or groups of fields may be increasing the chance of the form becoming corrupt. At this point we must find a way to reset all the internal field indexes...

If this is the case, other forms should be able to be merged without problem. The Invoice template that is included with the Text Layer Designer is a perfect form to test with. If the Invoice form merges with no errors, I would find it safe to say that your form template is corrupt.

To fix the corrupted form: Make a backup copy of the corrupted form. Rename it so that it does not get used by mistake. Create a new form and save it over the original corrupted form. Open the backup copy or the corrupt form and copy over the fields and graphics into the new form. Save and attempt a test merge. If the errors persist, repeat the above steps, but copy over the fields and graphics individually (or a few at a time) and try some test merges along the way. That will help you narrow down where the corruption may be originating.

If my theory above is correct, by copying the corrupt form into a new form, we should be resetting the internal field indexes and resolving any internal conflicts leading to this issue.