Yesterday, I tried to change the authentication server for my phone and thats when I got this error. I am aware that this is an authentication error. Today, I tried to work with this again and now I am getting CiscoIPPhoneError Number='4'. I never noticed the OK, but could well occur in this scenario.This document was generated from CDN threadĬreated by: Mayank Sharma on 04-02-2009 05:21:19 PM I think I may have seen similar behaviour when IIS can't handle authenticated traffic, it just bombs out with a 401. Consider async services to keep the thread pool free if you have long running requests. If your using a database make sure you are disposing of disposable objects etc, profile the server to monitor memory use. Is the service on a farm? It could be one server is not configured correctly.īased on your last comment you should check there are no resource leaks causing the unexpected behaviour.

Unlike a 401 Unauthorized response, authenticating will make no The request was a legal request, but the server is refusing to respond Check the actual Http Status code in Fiddler to be sure. I don't think the OK is relavent, though it is unusual. This means you don't not have permission for the resource you are trying to access, and that authenticating may make a difference. Is possible but has failed or not yet been provided.

Similar to 403 Forbidden, but specifically for use when authentication The exception only occurs intermittently and not always, the credential details passed through are valid AD user details for an account and IIS site is using Windows Authentication. I will be trying to get a WireShark packet trace for this error when I am provided with it.īoth the client and the Web Service are code that we maintain. The request failed with HTTP status 401: OK.Īt .SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)Īt .SoapHttpClientProtocol.Invoke(String methodName, Object parameters) Here's the direct exception details: Message: Why would my Web Service hosted in IIS6 be returning this? Can someone please provide me with some reasons why this would be occurring? As I can't seem to find anything on HTTP 401 and a message of OK since 200 is OK and 401 is Unauthorized. I have an ASP.NET Web Service, when I call it occasionally it returns the correct response, other times it is returning the exception The request failed with HTTP status 401: OK.

Wireshark http 401 unauthorized