ok, here's what I'll do:
Enable a new directive in the IirfGlobal.ini, it looks like this:
# Turn off windows event logging for vdirs that lack ini files
This tells IIRF to not log a system event when an ini file is missing. This will occur when there is a vdir that has no IIRF.ini file. As you saw, the current behavior of IIRF is to log an event in the Windows application event log when this
happens. This directive disables that behavior.
The reason IIRF used the event log in this condition, is that lacking an ini file for a vdir, there is no IIRF logfile for that vdir, so it's not possible to log a message in the IIRF logfile. Therefore, I chose to log a message in the event log. But
using the event log this way was not well thought-out. Lots of people install IIRF for use on a subset of vdirs in IIS. This common case would result in lots of events in the Windows event log.
The new directive will turn off that event logging.
I won't make it the default behavior; in other words you will by default still get Windows Event log spam. The reason is, I want people to be aware that the vdir ini file is missing.
I've made those changes and they work.
Now, supposing the new directive is not present in IirfGlobal.ini.... Above I proposed to modify IIRF to spool only ONE event to the Windows Event Log per vdir, per lifetime of IIRF. I'm still working on that. That shouldn't
be hard to do. I'll keep you updated.
This will be available in v188.8.131.52 of IIRF (not yet released).