All Tags > EVT input format (RSS)
  • RE: Event Log to MDB "Message" field size

    Unless I'm mistaken, Access doesn't support larger string fields and LogParser doesn't support memo fields. I believe you are a bit out of luck.
    Posted to Forum by LogParser User : DEinspanjer on 04-11-2007, 7:16 AM
  • Event Log to MDB "Message" field size

    I am using the following command to successfully dump an Event log to an MS Access DB. The problem I am having is with some of the fields like the "Message" field. The "message" field can be very large by default and I think the only data type in MS Access that could handle all the data would be a MEMO...
    Posted to Forum by LogParser User : jgus on 04-11-2007, 3:35 AM
  • RE: Error when collecting Security Logs containing "%20"

    Hi John, I trust you've investigated all the double %% workarounds? and substring options? When Microsoft say they wont correct it, I'm sure they meant, they cant just change the codebase willy nilly as those changes might fix one thing but break 10 million other working things. Regression testing is...
    Posted to Forum by LogParser User : Lecky on 04-09-2007, 1:05 AM
  • RE: Problem with Checkpoint

    Hi Valery, It seems you have done a fair bit of research into this behaviour. Are you still encountering this problem or did you find a workaround? My 2 cents is to first investigate the network issues causing SQL Server to become unreachable. Obviously, if you can resolve that then you wont encounter...
    Posted to Forum by LogParser User : Lecky on 04-09-2007, 12:56 AM
  • RE: Error reading event log: The event log file is corrupted

    Hi Issam Andoni (Sam), The log file is most likely corrupt. It does seem a trifle odd that some servers run the query successfully and others dont, is there significant differences between the machines? Are you always inserting into the HDQNCOSCSQL1 server? I assume the query changes depending on the...
    Posted to Forum by LogParser User : Lecky on 04-09-2007, 12:43 AM
  • RE: Logparser crashes - i:evt o:datagrid

    Hi JD, Do you want to upload the Evt log somewhere for me to download it and reproduce the problem. I might be able to help you get around it Usual info pc/server specs, OS, Service Pack level & etc would certainly aid troubleshooting. If it is a problem thats reproducible, then I'm sure the LogParser...
    Posted to Forum by LogParser User : Lecky on 04-09-2007, 12:21 AM
  • RE: Help

    Hi, As usual Daniels advice is spot on, check the manual! Also see the Repository. If you want a cheap way to export the results add a > C:\TheResults.txt to the command line query, eg: logparser -stats:off "SELECT TimeGenerated, EventID, SourceName, Strings FROM Application WHERE SourceName = 'NTBackup...
    Posted to Forum by LogParser User : Lecky on 04-09-2007, 12:00 AM
  • RE: Remote Event Logs, the definitive way?

    [QUOTE User="LogParser User : Lecky"]Quote: Quite a few times people seem to have asked this question: How can I access eventlogs on a remote server use logParser? The anwser seems to be that the user running logparser needs to have admin righ...[/QUOTE] http://support.microsoft.com/default.aspx?scid...
    Posted to Forum by LogParser User : Lecky on 04-08-2007, 11:48 PM
  • RE: Help

    You need to specify an output format and file name. I'd suggest reading the help file that was installed in the same directory as LogParser.exe. It has lots of details on how to do this.
    Posted to Forum by LogParser User : DEinspanjer on 04-04-2007, 2:38 PM
  • RE: Remote server EVT username/password

    I was having problems with this as well, however a way round it is, if you can map a drive prior to running the logparser script this will validate your credentials and allow the script to run there are lots of examples of how to do vb script via google if you want to incorporate this method HTH George
    Posted to Forum by LogParser User : GeoMacG on 04-04-2007, 9:05 AM
Page 3 of 65 (642 items) < Previous 1 2 3 4 5 Next > ... Last »
Microsoft Communities