IIS Logs - Install, Configure, Forget!

Stand-alone EXE or a Windows Service version).">

Powered by

HOME

HELP

PURCHASE

FAQ

CHANGE LOG

QUICK INSTALL HELP

DOWNLOADS

FORUMS

Windows Service Version Guide

Stand-Alone EXE Guide

IISLogs Overview

Side-by-Side comparison of IISLogs

IISLOGS Lite Version

100% Money Back Guarantee

Get answers to your most asked questions

Home | Log In | Register | Search | Help

IIS Logs – Install, Configure, Forget! > General Information > Bug reports > IISLogs doesn’t process specificDirectories correctly when using IISLogsGUI

Forum Quick Jump

[ << Previous Thread | Next Thread >> | Show Newest Post First ]

Forum Administrator
Forum Moderator

Date Joined Jul 2004
Total Posts : 31

Posted 9/5/2023 11:47 PM (GMT -4)

Problem

When using EasyConfig option inside the IISLogsGYI to configure SpecificDirectories tab, the directory path would be placed in the Grid (i.e. c:inetpubiislogslogfiles) but IIS would create the W3SVCXXXXXX below the logfiles directory (i.e c:inetpubiislogslogfilesw3svcXXXXXX. IISLogs service and stand-alone EXE would just process c:inetpubiislogslogfiles which doesn’t have any logfiles.

Solution

The EasyConfig option was moved to the MonitoredDirectories tab from SpecificDirectories tab. After further testing, this appears to be an design alteration. The root of the issue is IIS creates the web name below the specific Directory.

* —————————————– *
* Steve Schofield – MCP, CCA
* [email protected]
*
* Microsoft MVP – ASP.NET
* http://www.deviq.com
* —————————————– *

Forum Information

Currently it is Tuesday, October 17, 2022 10:42 PM (GMT -4)
There are a total of 30 posts in 23 threads.
In the last 3 days there were 0 new threads and 0 reply posts. View Active Threads

Need Support? | Forum Help Manual

tio