Glad to hear it - thanks for letting me know!

OK, I worked around it by just creating the parser maps that I needed.  So that problem is taken care.  Thank you.

Thanks for the update.

The parser mappings being locked is a very specific problem which should only be impacting one particular license key.  A customer who specifically requested that feature.  It may be best if you contact us offline so we can take a closer look.

Hi Awags,

I am not sure where the problem could be.  It looks like these are Windows event logs, so the parser should be built in (no configuration necessary). 

Did you try changing the encoding settings as discussed above?

Thanks,

Toby

Hi Awags,

Thanks for reporting this issue.

We did make a major change in v3.1.22.  The default file encoding has changed from "Windows Default" to UTF-8.  This has had an impact on some users.  Especially those with a parser configuration containing unusual characters.

Can you please try changing your encoding and reloading the file?



Other settings should be unchanged after the upgrade.

Hope that helps,

Toby

I was running 3.0.2 and now just loaded 3.1.22.  Loading the same file on both versions looks completely different.  The older version shows 227,275 records and the newer version shows 0-10.  Is there a way to import settings from the older version?