Search results matching tag 'IISODBC input format'

RE: MySQL Connection.

LogParser User : Gabriele Giuseppini — Tue, 18 Jan 2005 13:10:00 GMT

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.

RE: MySQL Connection.

LogParser User : Gabriele Giuseppini — Sat, 15 Jan 2005 14:26:00 GMT

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!!! You've made Log Parser a better tool!!!!

P.S.: I've sent you a private message.

MySQL Connection.

LogParser User : icery — Fri, 14 Jan 2005 18:12:00 GMT

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, Security TO tblEvents"-o:SQL -server Server1 -driver "MySQL
ODBC 3.51 Driver" -database mydatabase -username win

Task aborted.
Error turning off Bookmarks
SQL State: HYC00
Native Error: 536
Error Message: [MySQL][ODBC 3.51 Driver][mysqld-4.1.8-nt]Optional feature
not implemented

Statistics:
-----------
Elements processed: 0
Elements output: 0
Execution time: 0.09 seconds

Any input?

RE: ODBC DSN Error

LogParser User : InBan — Wed, 08 Dec 2004 07:52:00 GMT

I'll keep my eyes peeled for it.

Thanks again,

Ian Bagnald

RE: ODBC DSN Error

LogParser User : Gabriele Giuseppini — Wed, 08 Dec 2004 00:26:00 GMT

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.

RE: ODBC DSN Error

LogParser User : InBan — Tue, 07 Dec 2004 12:23:00 GMT

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?

RE: ODBC DSN Error

LogParser User : Gabriele Giuseppini — Tue, 07 Dec 2004 12:09:00 GMT

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).

RE: ODBC DSN Error

LogParser User : InBan — Tue, 07 Dec 2004 09:52:00 GMT

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?

RE: ODBC DSN Error

LogParser User : Gabriele Giuseppini — Tue, 07 Dec 2004 02:09:00 GMT

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).

RE: ODBC DSN Error

LogParser User : InBan — Mon, 06 Dec 2004 17:02:00 GMT

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 EVENTLOGS -username USER -password PASS