Invalid argument

When trying to import logs into Access

[Sinner_G]

Everytime I try to import one of my log files (IIS) into M$ Access (using file/external data/import) I get an error msg saying 'Invalid argument'. The log is then not imported. If I just link tables, no problem.

Has anyone already run across that? And maybe even found a solution?

A search on G told me too install Office 2000 Service Release 1a, which I did without any success.

[jpirelli]

I have not had that problem with Access, but you may check to see if it is the actual data in the file. Sometimes JS hack attempts throw things in the log that will make importing htem difficult, you may consider using the Microsoft Log Parser to create a database type of connection directly to the logs, it is very very simple to do.

search google for the log parser 2.0 page, it is well worth it

Joe

[Sinner_G]

Can't really look at the actual data, as the log file is over 2 GB and so too big for any text program I know.

I will have a go at log parser, thanks.

[Sinner_G]

Ok, log parser did the job, thanks a lot, Joe!

But it also told me that there had been 33 parse errors. Is there any way to have it tell me what these errors were exactly? E.g. write out those lines in another file?

Thanks
Sinner

[gsx]

Awkward, but could you write a simple query/macro to copy a linked table into a new fixed table?

[jpirelli]

I have not encountered the log parser errors ever, you must have some very very strange data, I would say that you should find out what lines those errors are on and try to see what is being written, I bet it is some cross-site scripting hack attempt that is causing so much trouble.

If I knew how to handle the errors I would let you know, but that is something I am just unfamiliar with.

I use URLScan to prevent as much of that as I can from hitting the webserver.

I am pretty familiar with Log Parser, a great tool. Let me know if you need anything else, I am always willing to try and help :)

Joe

[Sinner_G]

Well, I guess I will try and hack the files int small pieces using Windows Commander. Pieces I can than look at in text editors and where I might find the error.

Although I have the feeling it is just a question of 'unwanted' spaces, e.g. in the URL.

I will post if I find anything.

Thanks for the help.
Sinner

[jpirelli]

Do you know windows scripting or anything? It is very simple to write a file tool which (run from the command line) will split your logfile.

The more I have thought about the problem, the more I think I would use the COM interface of the log parser, then you can use regular VBScript to catch any errors instead of using the command line tool.