Home / server / Questions / 673258
Accepted
Martin Bring
Asked: 2015-03-06 05:34:23 +0800 CST

How can I call one web service, but not another, in the same folder?

  • 772

I have two web services, of old school, asmx. Both is in the same sub folder, which have anonymous authentication, in a MVC web application that have windows authentication.

When I browse one of them I get expected result, I can Invoke the service, but when I browse the other I get "HTTP Error 401.2 - Unauthorized You are not authorized to view this page due to invalid authentication headers.".

I then rename the second one and everything works fine. Even if I remove the second asmx file I get Unauthorized, instead of "Resource not found".

I have searched the registry and the file system for references to the file name, but find nothing. I deleted ASP.NET Temporary Files, but that did not help.

Any trouble shooting suggestions?

iis

2 Answers

  1. Best Answer

    This was not easy to find, but in inetpub\temp\appPools\ there was a folder named as the application pool. In that folder there is "copy" of parts of the IIS config.

    At some point we must have accidentally marked the actual asmx file, instead of the folder when we changed autentication. So it contained a special configuration section for just the file. Like:

    <location path="Web/Services/ServiceName.asmx">
    <system.webServer>
        <security>
            <authentication>
                <anonymousAuthentication enabled="false" />
            </authentication>
        </security>
    </system.webServer>
</location>

    When we removed that section it worked again :)

    • 0

  2. After much work, I found the same thing... I think that the common theme here is that the folder in question is called "Services" <location path="Default Web Site/MyDirectory/Services">

    There was a spurious entry in the app pool config file where <anonymousAuthentication enabled="false" />

    My solution, set anonymousAuthentication = "True"

    I wonder whether this is a little bug in IIS where this part of the config is ignored for some reason.

    • 0