Comments
-
A possible commonality I'm finding is for the cs-method field, the lines that it says it can read either have OPTIONS as the method for either that event specifically or the event previous. Is the connector tripping up when it sees that?
-
For reference, here are the fields I'm currently using directly from the logfile. I've seen other forum posts where these work, but it just doesn't seem to do the trick on our servers: * #Fields: date time s-computername s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus…
-
Thanks for the reply. I've been working on this issue off-and-on, but I'm still having some trouble getting this connector to work. I've enabled the field as suggested (and fiddled around with a few others), but for whatever reason, I'm still getting the same issues as above. Mostly, though, it just says that it failed to…
-
Thanks!
-
Righto, will do. Thanks!
-
I've seen a couple errors. The first occurs when the log file path is configured in these ways: * C:\\inetpub\\logs\\LogFiles\\W3SVC1\\u_ex140118.log * C:\inetpub\logs\LogFiles\W3SVC1\ * C:\\inetpub\\logs\\LogFiles\\W3SVC1\\ * C:\inetpub\logs\LogFiles\W3SVC1 I get: Event Field Information Description Failed to start FAST…
-
The page looks good, but it looks like the link to the upgrade guide is dead!
-
A bit of extra info, the server is still logging events, but they're just not showing up in the tabs I mentioned.