InBan, since the command you provided doesn't include a -username property to accompany the DSN, the error probably indicates one of two things: SQL Server is configured to use SQL authentication only, or the Windows account you're using to launch the Log Parser command doesn't have access to the database...

I thought I already posted a reply but it doesn't seem to have come up, here I go again. A test of the DSN completes successfully. I've tried deleting and recreating it as a system and user DSN. I had this all working with an access database, but the max 255 character in the message field was causing...

Well, as with all the DSN problems, you should double-check the connection parameters you've specified for the EVENTLOGS DSN. Log Parser doesn't do anything special with a DSN - it just uses its name and asks the ODBC subsystem to connect to it. Now, the ODBC applet has a "test this connection" utility...

I'm looking at setting up a database of event logs. I'm using a VBScript to backup and clear some event logs. Then a shell script that calls logparser to query the logs and output their contents to a SQL Server. I'm just in the early stages of testing all this out, and I know about the issue of having...