Errors, Hints, Samples
Error from FormTrap Spooler
FormTrap Spooler produces error messages, messages are of several types, the messages produced directly by the Spooler are partially documented below (we add errors that have been reported by users). Where FormTrap Spooler produces the error message, additional detail will be found in the log file (%fthome%\spooler-debug.txt file). Look there first please. If you do not understand the error message, ensure you send these files with your request for support (and identify the document in the project where there is more than one):
Log file (%fthome%\spooler-debug.txt)
Project file (projectname.ftxml)
Data file (that produced the error)
Messages produced by other software - particularly Windows error messages - may be obtuse.
Windows error messages have an error number, use the number as the keyword to the FormTrap Knowledge Base to see if we have addressed this error, otherwise submit the error code to Google Search to access other comments on the issue. FormTrap is not responsible for Windows errors, the system performs calls to Windows APIs to specifications. Windows error messages generally mean you have incomplete /incorrect parameters.
We may elect to assist with error messages produced by non-FormTrap software (or not) at our discretion, and may elect to charge for assistance where the resolution is:
- unique to that client
- the result of errors in Windows APIs
- produced by components included in the FormTrap Spooler by the user (Setup: Filters, Run, Applications)
- pushing beyond the scope of activity inherent in FormTrap (for example, tracking responses to emails)
- able to be resolved by an informed Windows CE
We will inform client where we intend to charge and will estimate final cost, which is NOT binding. Chargeable work will require a credit card prior to the start of work. Our fees for this work are substantial reflecting the experience and skill of our people. Our function is to write general software with wide application, one-off issues are the exception.
Specific components (generally filters) are supplied as compiled and source code in Microsoft Visual Studio (C++), have a warranty of three months, do not attract support fees and are available to either party for any purpose.
If the work results in a new generation of FormTrap components, source code is NOT supplied and that modification is warranted under the FormTrap Support and Upgrades agreement.
queuename: cannot parse XML input
Queues, Processing tab, Split / resolve: prompt.
A V8 queue normally resolves incoming data by recognizing it and converting it to FormTrap XML. User selected "Resolved" meaning the input should be FTXML, it is not.
V7 formtrap.exe, Error 15
This means input was not run through the Input Filter that converts to UTF-8, which is the operating
character set for FormTrap from Version 6.4. Go the queue where data enters FormTrap and select an
Input Filter (Western for European data).
The error is one of very few that crashes FormTrap and means a character above Hex 7F (decimal
127) was read and the program has no idea what this means. You may have run this form for years and have
just introduced the character above Hex 7F, like a trade mark, copyright or registered trade mark
symbol.