Anyone have any idea why enVision parses logs as "unknown" when the ESI tool parses every record successfully? In this particular instance, the same log file not being parsed correctly was imported and used to create the UNX file. The Event Analysis report even shows the header and message being successfully parsed with the data elements in all the correct places. Looking at the events in the Event Viewer I see that the name of the File Reader has been added to the event entries. All of the message types show up under Manage Messages to Parse as well.