Handling of unsupported encodings

If an unsupported encoding is specified in the NetConfig file, then the thread enters an error state immediately during startup and no messages are processed. The GUI does not permit entry of an invalid value, so this should be extremely rare.

If XML encoding is used and an unsupported encoding is encountered in an XML declaration, then the offending message is transferred to the error database. This encoding is given error state 416: Inbound encoding conversion error. In this case, the data that is stored in the error database is the raw byte stream that was received. Error state 416 is the only time that raw data is stored in the error database. All other errors are stored in UTF-8 Unicode.