Oh Geesh - I didn't even think about looking at the .chm help file. I was
looking at the docs located here -
http://docs.activestate.com/activepython/2.7/pywin32/win32evtlog.html. This
is my first time using Python on Windows, so I apologize for the n00b
mistake.
I'll check out EvtQuery->EvtNext->
Mark is right, the handles are not interchangable between the older event
log functions and the newer Evt* functions. You can still use the older
APIs on Vista and later, though. OpenEventLog returns a handle
compatible with ReadEventLog.
To use the newer functions, try EvtQuery->EvtNext->EvtRend
Thanks for the reply, Mark!
I took a look and didn't see the EvtGetLogInfo() implemented anywhere in
the source. Hopefully Roger will be able to figure out what's going on here.
-Tim
On Thu, May 3, 2012 at 4:35 PM, Mark Hammond wrote:
> I'm afraid I'm not familiar with that API, but the crash i
I'm afraid I'm not familiar with that API, but the crash is because
EvtOpenLog is returning a handle with a value of 1 and ReadEventLog is
crashing with that handle. A quick google doesn't find anyone trying to
use ReadEventLog with a handle returned by EvtOpenLog but instead uses
EvtGetLogInf
Hello,
I'm having a problem with win32evtlog and reading events from an event log
channel on Windows Server 2008 R2. I'm using the following code and get the
following error (python.exe APPCRASH no exceptions):
#!/usr/bin/python
# Windows Event Log Viewer
import win32evtlog # requires pywin32 pr