Overview

Faxes sent via TextAPI, usually from a 3rd-party application, may fail with one or more of the following errors in the faxserver.gfi_log.txt file (the [template_name] part of the messages will vary):

• the template [template_name] is not allowed for user [__Text_API__@FAXmaker]
• unknown template name[template_name]
• returning error while looking for coverpage[205]

The issue does not occur when sending using the FaxMaker Web Client.

Workflow

Instructions

Test with a simple TextAPI file

Create a minimal TextAPI file and drop it directly in the pickup folder, to rule out more general transmission issues.

Set default coverpages

Try setting default coverpages (like the Generic one) for both the TextAPI and faxes in general.

If the problem persists, this indicates issues with the coverpage parameter in the TextAPI file (next step).

Check the coverpage parameter

Ensure the coverpage parameter in the faulty TextAPI file is set to a matching coverpage in FaxMaker.

Follow the steps from TextAPI fax from 3rd-party application fails with coverpage error for detailed instructions.

Ensure the coverpage file is not corrupted

Open the file (.htm or .rtf) in the appropriate application to ensure they load correctly and the structure is fine. If the file is .rtf, try saving as .htm and using it instead.

Review user-specific coverpage settings

FaxMaker lets you assign specific users to a coverpage. Review such assignments and try to clear them to isolate invalid coverpage attributions.