The software is unable to parse my apache2 access.log file only when the month is "Sep." If I rewrite the log file so that the month is "Aug," it can be loaded by the parser. I have tried editing the parser using the parser wizard, but I could not resolve the issue. The parser is provided by default and is supposed to be able to parse the access.log file. I have updated the software to latest version

Hi Cyrillee,

Thanks for reporting this issue.

I can see the date string it is trying to parse at the bottom of the screenshot is "11/Sep/2025:00:00:14 +0800".  In this case, the target date does not have a millisecond component.  I was able to parse that timestamp successfully with:

dd/MMM/yyyy:HH:mm:ss zzzz

I did try changing the month to August while using the date format suggested in your screenshot, but I was not able to recreate the issue.  Both August and September were failing.

Hope that helps,

Toby

Dear Toby,

Thank you for your prompt reply. The parser pattern for the date should be fine, as it auto-generates when I load the access.log, which can then be parsed. I eventually fixed the issue by changing the Regional Format setting in Windows to Chinese (Traditional, Hong Kong SAR). It was previously set to "Recommended," but I’m not sure why that caused the problem.

Thanks for the update. That's very interesting.

Automatic date detection takes the current windows region into account. For example, does "sep" represent a month in the local language as defined in Windows?  It sounds like your region settings were preventing the auto-detection from making this distinction, but it is difficult to say why.

That said, the automatic detection is done on a best-effort basis.  It's always a good idea to specify the file format explicitly.

It is worth mentioning that we made a change in the last release (v3.1.22) to set the default file format to UTF-8 rather than Windows Default. However, I don't think that is the problem here because "sep" shouldn't really have an encoding problem.  So, I am not seeing anything to indicate a file encoding issue, but it may be worth trying an earlier version of LogViewPlus to see if it has the same problem.

It should not be necessary to change your Windows Region setting to get LogViewPlus to work, so it would be good to get to the bottom of this one.

Thanks again,

Toby