Last post Mar 03, 2004 03:40 AM by Anonymous
Feb 20, 2004 12:16 AM|Anonymous|LINK
I have been running logparser 2.1 (com) from cscript every hour for a few days when I got this. The server had to be restarted to recover.
Reporting queued error: faulting application wscript.exe, version 220.127.116.1115, faulting module logparser.dll, version 18.104.22.168, fault address 0x000497bf.
Feb 20, 2004 12:49 PM|Anonymous|LINK
Thanks a lot for reporting this Dave!
Do you run the script every hour, or does the script run continuously, sleeping for an hour and kicking off a query every time?
And, have you had the possibility to "send error report" to Microsoft? (you know, the little dialog that sends a crash dump to MS)
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
Feb 20, 2004 01:41 PM|Anonymous|LINK
Feb 20, 2004 03:05 PM|Anonymous|LINK
Couple of q's:
1) Are you using the "W3C" input format?
2) Are you setting its "dtLines=0" ?
Feb 20, 2004 05:44 PM|Anonymous|LINK
Yes from W3C to CSV for the first pass then from CSV to SQL for the second
detectTypeLines is default
One thing I noticed is that when I added the CSV input and output objects as part of my workaround for known SQL duplicate rows bug, I neglected to add them to my cleanup routien so they were not being destroyed
Feb 20, 2004 06:25 PM|Anonymous|LINK
Well, thanks to your post, I've found that there might be an access violation at exactly the point you have specified, but this would happen only if dtLines is zero....
BTW: if this is JScript or VBScript, you don't really need to cleanup objects - JScript will take care of that automatically.
Feb 20, 2004 06:51 PM|Anonymous|LINK
Feb 20, 2004 06:52 PM|Anonymous|LINK
Feb 20, 2004 07:20 PM|Anonymous|LINK
Oh my....that's what we get for buying forum software from a Brit company
We should be able to refer to "logparser" with impunity now.
Mar 03, 2004 12:57 AM|Anonymous|LINK
LogParser User : jenleejeff
Quote: Yes from W3C to CSV for the first pass then from CSV to SQL for the second detectTypeLines is default One thing I noticed is that when I added the CSV input and output objects as part of m...
I know this is tghe worng thread, but this is the only way i can quote the statement. Im an ASP developer tasked to use log parser for creating a custom log anayzer module.
I was wondering, how do you do W3C to CSV then to SQL? I have been digging the internet on how to use Log Parser with ASP and so far I came up with
nothing but VBscript. Any help here guys would be very much appreciated.
Thanks. Im new to log parser and ASP. I was even surprised why i was given this task, tsk,tsk,tsk.
Hope you can all help me, and thanks in advance!
Mar 03, 2004 02:43 AM|Anonymous|LINK
Mar 03, 2004 03:00 AM|Anonymous|LINK
how many steps it would take, doesnt really matter, as long as it is possible.
I have been trying on my own, but so far I have only been reading the documentation. Any codes I might be able to take a look at? All i have is the
doc file, the dll and the exe, I would like to see a working example in ASP.
Mar 03, 2004 03:16 AM|Anonymous|LINK
Mar 03, 2004 03:40 AM|Anonymous|LINK
The company im working for offers streaming video online. They would like me to make a module that will show what is download, how often and by whom, all of which are stored in the log files. it is in IISW3c format, but some are in the old legacy form. We
are using IIS5 so all server side coding is done in ASP.