HTTP 401 error on Web Service call, anonymous allowed

I am at a loss as to why I am unable to make a web service call. I am
getting a 401 return code even though anonymous access has been enabled. I
even tried running aspnet_regiis -i, but that didn't seem to help either.

Anyone have any suggestions?

David
Wed Jun 28 01:41:54 CDT 2006

Enabling Anonymous does not mean that you will never see "access denied".
Determine the 401 substatus code, then determine what user is *actually*
configured to run on the server for that request, and go from there.

http://blogs.msdn.com/david.wang/archive/2005/07/14/HOWTO_Diagnose_IIS_401_Access_Denied.aspx
http://blogs.msdn.com/david.wang/archive/2005/05/27/Access_Denied_to_Administrators_or_Anonymous_User.aspx
http://blogs.msdn.com/david.wang/archive/2005/12/31/HOWTO_Basics_of_IIS6_Troubleshooting.aspx

aspnet_regiis -i is irrelevant for a 401. I recommend against running random
commands with no correlation to the issue because it can worsen the
situation. Always start from the current configuration and situation, track
down all details, and go from there. See the blog entries for details and
rationale.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

"William" <nfr@nospam.com> wrote in message
news:eLboS$gmGHA.1488@TK2MSFTNGP02.phx.gbl...
>I am at a loss as to why I am unable to make a web service call. I am
>getting a 401 return code even though anonymous access has been enabled. I
>even tried running aspnet_regiis -i, but that didn't seem to help either.
>
> Anyone have any suggestions?
>

William
Wed Jun 28 12:23:01 CDT 2006

"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:urJAN9nmGHA.464@TK2MSFTNGP05.phx.gbl...
> Enabling Anonymous does not mean that you will never see "access denied".
> Determine the 401 substatus code, then determine what user is *actually*
> configured to run on the server for that request, and go from there.
>
> http://blogs.msdn.com/david.wang/archive/2005/07/14/HOWTO_Diagnose_IIS_401_Access_Denied.aspx
> http://blogs.msdn.com/david.wang/archive/2005/05/27/Access_Denied_to_Administrators_or_Anonymous_User.aspx
> http://blogs.msdn.com/david.wang/archive/2005/12/31/HOWTO_Basics_of_IIS6_Troubleshooting.aspx
>
> aspnet_regiis -i is irrelevant for a 401. I recommend against running
> random commands with no correlation to the issue because it can worsen the
> situation. Always start from the current configuration and situation,
> track down all details, and go from there. See the blog entries for
> details and rationale.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //

Those were excellent sources of information and I have bookmarked them.

Unfortunately, looking at the logs it appears I am recieving a 401.5, which
is harder to diagnose. I have a simple test webservice using ASP.NET 2.0
that is doing nothing more than receiving an XmlDocument and returning
another, so I am thinking the problem is likely related to the code-behind,
but am not sure where to go from here.