Hi, i really don't know why , but when i run a command similar to this: logparser -i:EVT -o:SQL -dsn:... -username:... -password:... -createTable: ON "SELECT * INTO TEST_TABLE FROM Security" (The space between the createTable: and the ON is only in order to avoid getting this ...) I get the following...

hi, i need to parse a large amount of IIS log files into an access database - i am currently using the output SQL to access using a shell script from my VB app but on a large amount of log data (in my case current around 650MB) it is taking forever - has anyone got any alternative suggestions? thanks...

I am getting the following using Log Parser 2.2: An error occurred while uploading data to SQL table SQL State: HY109 Native Error: 0 Error Message: [Microsoft][ODBC SQL Server Driver]Invalid cursor position There seems to be scant information out there on this problem. Can anyone help? Data still seems...

Using surrounding single-quotes fixes this query: LogParser "SELECT * INTO LogParserTable FROM ' \\CupidDP35D\Operations Manager'"

I'm attempting to access an Event Log called 'Operations Manager', but the query is having problems with the space between the 's' and the 'M'. I've tried a number of delimiters such as the underscore, { }, ( ), " ", ' ' but have not found a way around this error message: _____________________________...

oInput = CreateObject("MSUtil.LogQuery.XMLInputFormat") oOut = CreateObject("MSUtil.LogQuery.SQLOutputFormat.1") oOut.oConnString = "Driver={Microsoft Excel Driver (*.xls)};DBQ=c:\temp\test.xls;Extensions=xml;DriverID=790;ReadOnly=FALSE" where the input file is a persisted recordset (in xml format)....

Update: Sorry, didn't looked at the table correctly. The issue is somewhat different. In the CSV-file there are 59 entries, each one is different from the other. The first 41 in the MySQL-table have been written correctly. After that, LogParser seems to switch back to the beginning of the CSV-file and...

Hi. I got some strange problem: When I read a csv-file, which I generated before with LogParser, and try to put that into a MySQL-table, it makes two entries in the table for each entry in the CSV-file. When I look at the table, I see the entries in the following way: 1 . . n 1 . . n I am using the following...

I am getting a square followed by a - on the output of my sql input from a w3c file. (exchange tracking log. Anyone know how to reformat this?

No, I got the same error, using COM rather than commandline; that's why I asked about using Providers, Jet 4.0 and ADO does not put the same restrictions as the Excel ODBC, viz. you can use SELECT INTO... IN. The workaround is to output as either XML or CSV, then use a separate CreateObject("Excel.Application...