RE: ISAPI and IIS 10 Logging Issue

2017-11-22 Thread Thomas, Michael
-- On 17/11/17 15:47, jumiller wrote: > I finally managed to figure out what the issue is/was. The > c:\windows\system32\inetsrv\config\applicationHost.config file has a > definition for IsapiFilter in the overrideMode="Allow"> s

Re: ISAPI and IIS 10 Logging Issue

2017-11-17 Thread Mark Thomas
On 17/11/17 15:47, jumiller wrote: > I finally managed to figure out what the issue is/was. The > c:\windows\system32\inetsrv\config\applicationHost.config file has a > definition for IsapiFilter in the overrideMode="Allow"> section. The > IsapiFilterModule needs to be before the HttpLoggingModu

Re: ISAPI and IIS 10 Logging Issue

2017-11-17 Thread jumiller
I finally managed to figure out what the issue is/was. The c:\windows\system32\inetsrv\config\applicationHost.config file has a definition for IsapiFilter in the section. The IsapiFilterModule needs to be before the HttpLoggingModule in the list. I've made this change on all of my Windows 2016

Re: ISAPI and IIS 10 Logging Issue

2017-10-10 Thread jumiller
I'm having this very same issue with one slight difference. I have six Windows 2016 servers and logging works correctly on two of them. I've gone through nearly everything I can think of to determine what is different about the two boxes that work and have hit a wall. I have even done a full com

RE: ISAPI and IIS 10 Logging Issue

2017-10-10 Thread Thomas, Michael
- On 06/10/17 22:42, Mark Thomas wrote: > On 06/10/17 16:27, Mark Thomas wrote: >>> On 10.05.2017 8:54, Thomas, Michael wrote: >>> >>> Unfortunately I am not getting much traction with Microsoft. From the IIS >>> forum, it looks

Re: ISAPI and IIS 10 Logging Issue

2017-10-09 Thread Mark Thomas
On 06/10/17 22:42, Mark Thomas wrote: > On 06/10/17 16:27, Mark Thomas wrote: >>> On 10.05.2017 8:54, Thomas, Michael wrote: >>> >>> Unfortunately I am not getting much traction with Microsoft. From the IIS >>> forum, it looks like they are pointing the finger in the direction of the >>> "third-

Re: ISAPI and IIS 10 Logging Issue

2017-10-06 Thread Mark Thomas
On 06/10/17 16:27, Mark Thomas wrote: >> On 10.05.2017 8:54, Thomas, Michael wrote: >> >> Unfortunately I am not getting much traction with Microsoft. From the IIS >> forum, it looks like they are pointing the finger in the direction of the >> "third-party" that is writing the module. > > That

Re: ISAPI and IIS 10 Logging Issue

2017-10-06 Thread Igal @ Lucee.org
On 10/6/2017 8:27 AM, Mark Thomas wrote: On 10.05.2017 8:54, Thomas, Michael wrote: Unfortunately I am not getting much traction with Microsoft. From the IIS forum, it looks like they are pointing the finger in the direction of the "third-party" that is writing the module. That is consistent

Re: ISAPI and IIS 10 Logging Issue

2017-10-06 Thread Mark Thomas
> On 10.05.2017 8:54, Thomas, Michael wrote: > > Unfortunately I am not getting much traction with Microsoft. From the IIS > forum, it looks like they are pointing the finger in the direction of the > "third-party" that is writing the module. That is consistent with my experience with MS suppo

RE: ISAPI and IIS 10 Logging Issue

2017-10-05 Thread Thomas, Michael
[External Email] -- On 05.10.2017 17:09, George Stanchev wrote: > > >> Note that also in the course of my investigations, somewhere I found a >> phrase to the effect that Mirosoft would be discouraging the future use of >> ISAP

Re: ISAPI and IIS 10 Logging Issue

2017-10-05 Thread tomcat
On 05.10.2017 17:09, George Stanchev wrote: Note that also in the course of my investigations, somewhere I found a phrase to the effect that Mirosoft would be discouraging the future use of ISAPI modules in IIS, and recommends some other architecture instead now. Do you remember where you

RE: ISAPI and IIS 10 Logging Issue

2017-10-05 Thread George Stanchev
> Note that also in the course of my investigations, somewhere I found a phrase > to the effect that Mirosoft would be discouraging the future use of ISAPI > modules in IIS, and recommends some other architecture instead now. Do you remember where you saw that? Can you provide a link? --

RE: ISAPI and IIS 10 Logging Issue

2017-10-05 Thread Thomas, Michael
-- On 06.09.2017 22:07, Thomas, Michael wrote: > > -- >> On 01.09.2017 22:21, Thomas, Michael wrote: >>> All, >>> >>> When using the ISAPI Handler Mapping in IIS 1

Re: ISAPI and IIS 10 Logging Issue

2017-09-07 Thread tomcat
On 06.09.2017 22:07, Thomas, Michael wrote: -- On 01.09.2017 22:21, Thomas, Michael wrote: All, When using the ISAPI Handler Mapping in IIS 10 on Windows 2016, the IIS logs are not identifying the URI Stem (cs-uri-stem) and

RE: ISAPI and IIS 10 Logging Issue

2017-09-06 Thread Thomas, Michael
-- > On 01.09.2017 22:21, Thomas, Michael wrote: >> All, >> >> When using the ISAPI Handler Mapping in IIS 10 on Windows 2016, the IIS logs >> are not identifying the URI Stem (cs-uri-stem) and URI Query (cs-uri-query) >> as exp

Re: ISAPI and IIS 10 Logging Issue

2017-09-05 Thread tomcat
On 05.09.2017 22:42, Thomas, Michael wrote: -- On 01.09.2017 22:21, Thomas, Michael wrote: All, When using the ISAPI Handler Mapping in IIS 10 on Windows 2016, the IIS logs are not identifying the URI Stem (cs-uri-stem) and UR

RE: ISAPI and IIS 10 Logging Issue

2017-09-05 Thread Thomas, Michael
-- On 01.09.2017 22:21, Thomas, Michael wrote: > All, > > When using the ISAPI Handler Mapping in IIS 10 on Windows 2016, the IIS logs > are not identifying the URI Stem (cs-uri-stem) and URI Query (cs-uri-query) > as expected.

Re: ISAPI and IIS 10 Logging Issue

2017-09-01 Thread tomcat
On 01.09.2017 22:21, Thomas, Michael wrote: All, When using the ISAPI Handler Mapping in IIS 10 on Windows 2016, the IIS logs are not identifying the URI Stem (cs-uri-stem) and URI Query (cs-uri-query) as expected. For EVERY request that the handler processes (e.g. .cfm), the cs-uri-stem reco

ISAPI and IIS 10 Logging Issue

2017-09-01 Thread Thomas, Michael
All, When using the ISAPI Handler Mapping in IIS 10 on Windows 2016, the IIS logs are not identifying the URI Stem (cs-uri-stem) and URI Query (cs-uri-query) as expected. For EVERY request that the handler processes (e.g. .cfm), the cs-uri-stem records an entry as "/jakarta/isapi_redirect.dll"