All Tags > IISODBC input format (RSS)
Sorry, but there are no more tags available to filter with.
  • RE: MySQL Connection.

    Thanks to Icery's help, this has been fixed in the upcoming 2.2 release. Now Log Parser ignores errors occurring while turning off bookmarks.
    Posted to Forum by LogParser User : Gabriele Giuseppini on 01-18-2005, 8:10 AM
  • RE: MySQL Connection.

    Wow! This might be the last bug fixed in 2.2 :-) The SQL output format turns off bookmarks, and it complains if an error occurs. It seems it should not complain when bookmarking is not supported by the target DB... I'm seeing to get this fixed in the upcoming 2.2 release. Thanks for reporting the problem...
    Posted to Forum by LogParser User : Gabriele Giuseppini on 01-15-2005, 9:26 AM
  • MySQL Connection.

    Has anyone had any luck conecting to Mysql? I tried using the ODBC drivers but I get this error. C:\Program Files\IIS Resources\Log Parser>LogParser "SELECT EventLog, RecordNumber,TimeGenerated, EventID,EventType,EventTypeName, EventCat egory, SourceName,ComputerName, Message FROM System, Application...
    Posted to Forum by LogParser User : icery on 01-14-2005, 1:12 PM
  • RE: ODBC DSN Error

    I'll keep my eyes peeled for it. Thanks again, Ian Bagnald
    Posted to Forum by LogParser User : InBan on 12-08-2004, 2:52 AM
  • RE: ODBC DSN Error

    It was due today, but we had a tiny slip on the schedule. I'll be able to know better in a couple of days.
    Posted to Forum by LogParser User : Gabriele Giuseppini on 12-07-2004, 7:26 PM
  • RE: ODBC DSN Error

    That sounds like the way to do it. I'll have to try that out. Thanks alot Gabriele, it's a great tool. PS I imagine you're getting sick of this question but; when will 2.2 be available?
    Posted to Forum by LogParser User : InBan on 12-07-2004, 7:23 AM
  • RE: ODBC DSN Error

    No, LP won't tell you the DLL's......but you can figure that out from the registry (you can actually use the new LP 'REG' input format to parse the remote registry and obtain the list of dll's).
    Posted to Forum by LogParser User : Gabriele Giuseppini on 12-07-2004, 7:09 AM
  • RE: ODBC DSN Error

    So it wont actually register the dll's locally. Would there be a way to log the dll's that are being cached so that they could be registered locally either manually or programaticaly?
    Posted to Forum by LogParser User : InBan on 12-07-2004, 4:52 AM
  • RE: ODBC DSN Error

    Glad to see the DSN problem resolved. Regarding the EVT question, yes, 2.2 caches the remote DLL's locally, so LP will only load a remote DLL when it encounters it for the first time (or when the cache is full, which I believe means > 64 dll's accessed).
    Posted to Forum by LogParser User : Gabriele Giuseppini on 12-06-2004, 9:09 PM
  • RE: ODBC DSN Error

    Alright, it works, forget about the DSN, I looked at the syntax again and realized you were right on the money, I was neglecting the username and password. This line works. Sorry for the dumb question! LogParser -i:EVT -o:SQL "SELECT * FROM *_application.evt To APPLICATION" -server COMPUTER -database...
    Posted to Forum by LogParser User : InBan on 12-06-2004, 12:02 PM
Page 1 of 2 (14 items) 1 2 Next >
Microsoft Communities