LogViewPlus Support

Next button is disabled

https://www.logviewplus.com/forum/Topic2529.aspx

By hgneoh - 27 Jan 2026

Why the Next button is grey out? Which field am i missing?
By LogViewPlus Support - 27 Jan 2026

Hi,

Thanks for bringing this issue to my attention.  It looks like you have the information needed to continue (primarilly the timestamp).  Are you able to share a log entry with the parser configuration shown?  This would allow me to recreate the issue locally.

In the meantime, I would recommend ignoring the Parser Wizard and attempting to use the parser configuration shown directly using the standard parser configuration dialog.

Hope that helps,

Toby
By hgneoh - 28 Jan 2026

Here you go. The ideal here is to extract all the SECSMessage as individual log entry, then the log message content would be those enclosed in SECSData tag.
By hgneoh - 30 Jan 2026

I got error by using parser configuration dialog too:
By LogViewPlus Support - 30 Jan 2026

Thanks for the update.

The correct way to parse this file would be to use the XML Parser and not the default PatternParser.

Unfortunately, the XML parser currently does not support parsing child nodes collectively.  It only supports text nodes.  I have addressed this issue, so this functionality will be supported in the next release.

Beginning with the next release (scheduled for Feb), you should be able to parse the file with:

<SECSMessage time="%d">
    <SECSData>%m</SECSData>
</SECSMessage>



Hope that helps,

Toby
By hgneoh - 1 Feb 2026

Thanks, Toby! Right now, the application is parsing the entire SECSData block into a single 'Message' column. Is it possible to flatten this structure? I would like to extract the nested fields (like TaskName, EPTState, and CEID) into separate columns for detailed analysis.
By LogViewPlus Support - 1 Feb 2026

Flattening the XML data isn't something that is supported by default.  You could use standard Message Parser, but in this case I think you are going to be limited because the data is so complex.

A better alternative would be to write a custom extension.  I would suggest using a Custom Message Parser.  Our example code should provide a good head start for this use case.

Hope that helps,

Toby