Logparser: Redirect Errors on Windows Server 2019
Last post Oct 13, 2020 03:24 PM by DavidAC
Oct 13, 2020 03:24 PM|DavidAC|LINK
The errors do not occur on Windows Server 2019 if "Use legacy console" is selected for the interactive command-prompt properties. Disabling the non-legacy options without doing the above doesn't help (it's all or nothing). I have not yet found a means
to effect this change for non-interactive batch processes.
Also, the errors do not occur on Windows 10 Pro, Version 2004, OS build 19041.572, Feature Experience Pack 120.2212.31.0, regardless of the "legacy console" setting.
Original Problems (they still exist, so any advice is appreciated):
I'm getting errors redirecting Logparser's STDOUT on
Windows Server 2019 Standard, Version 1809, OS Build 17763.1369 and I wonder if anyone else can explain or confirm the behavior I'm seeing. Redirecting query output has the same result, but it can be reproduced simply by using "-h" in the example below.
Note that the "Usage:" portion of the help text is displayed to the console below, while part of the rest is written to the file.
Redirecting STDERR seems to work fine, and writing output to files via 'INTO' in queries also works fine without error. Thanks for any thoughts!
There are two Application event log entries generated from this:
Error 10/12/2020 1:25:54 PM Application Error 1000 (100)
Faulting application name: LogParser.exe, version: 184.108.40.206, time stamp: 0x423a0654
Faulting module name: MFC42u.dll, version: 6.6.8063.0, time stamp: 0xa17d0d2a
Exception code: 0xc0000005
Fault offset: 0x00035f6f
Faulting module path: C:\Windows\SYSTEM32\MFC42u.dll
Information 10/12/2020 1:25:55 PM Windows Error Reporting 1001 None
D:\>date /t > tmp.txt
D:\>logparser -h > tmp2.txt
Microsoft (R) Log Parser Version 2.2.10
Copyright (C) 2004 Microsoft Corporation. All rights reserved.