I am using LogParser 2.1 and sending the output to XML so
I can review the results.  Unfortunately, it appears as
though LogParser (or perhaps the underlying log) is
generating a linefeed character (0x0A) and two spaces
after the contents of each element value.

Any ideas how to remove any LF's from the output so that
my XML DB can find records?

Thanks in advance
Craig

[ Post a follow-up to this message ]

On Wed, 23 Jun 2004 23:07:11 -0700, "Craig Dunstan"
<anonymous@discussions.microsoft.com> wrote:

>I am using LogParser 2.1 and sending the output to XML so
>I can review the results.  Unfortunately, it appears as
>though LogParser (or perhaps the underlying log) is
>generating a linefeed character (0x0A) and two spaces
>after the contents of each element value.
>
>Any ideas how to remove any LF's from the output so that
>my XML DB can find records?

This isn't related to IIS Security.  Might want to check a XML group
or logparser.com for help.  You could alwyas remove the characters
with a script, but without knowing if they're in the underlying log
file it would be tough to say it's a log parser setting.

Jeff

[ Post a follow-up to this message ]

>-----Original Message-----
>On Wed, 23 Jun 2004 23:07:11 -0700, "Craig Dunstan"
><anonymous@discussions.microsoft.com> wrote:
> 
so[vbcol=seagreen] 
that[vbcol=seagreen] 
>
>This isn't related to IIS Security.  Might want to check
a XML group
>or logparser.com for help.  You could alwyas remove the
characters
>with a script, but without knowing if they're in the
underlying log
>file it would be tough to say it's a log parser setting.
>
>Jeff
>.
>

Sorry about that. The tool is part of the IIS Resource
Kit and I am using it to review the IIS Logs for security
purposes. You say tomato, I say tomato.

[ Post a follow-up to this message ]

On Thu, 24 Jun 2004 16:10:00 -0700,
<anonymous@discussions.microsoft.com> wrote:

> 
>so 
>that 
>a XML group 
>characters 
>underlying log 
>
>Sorry about that. The tool is part of the IIS Resource
>Kit and I am using it to review the IIS Logs for security
>purposes. You say tomato, I say tomato.

No big deal, just figured that some of the logparser experts don't
frequent the security group as much as the other locations.

If this is the IIS logfile, there shouldn't be a LF but rather a CRLF
at the end of each line, so I suspect LogParser is adding it.  I see a
post in the LogParser.com forums, so this may be you checking that
resource.

Jeff

[ Post a follow-up to this message ]