Exchange 2007, rollup 9 on Windows Server 2008, hosts HT\CAS\MB roles with Outlook Anywhere enabled. Original issue is continual password prompting on Outlook 2007 users that happens to everyone, but only after the server has been running for some time, rebooting clears the issue. Previously server was on rollup 2, so hoping the current rollup does not require disabling IPv6 (in network adapter properties, registry, and removing the localhost IPv6 from the hosts file) which some people have flagged as causing continual password prompting. Using a certificate with one common name, which both internal and external URLs are configured to use for web services, test autodiscover from oulook shows all the appropriate names in the XML tab.Performing the Test-OutlookWebServices provides the results below, the two RPC related errors used to indicate the password prompting would be occurring on the client's workstation, but after the rollup9 installation, the errors remain and the users are not being prompted for passwords. I'm not having any luck finding anything to resolve the issues below, any suggestions?Id : 1003Type : InformationMessage : About to test AutoDiscover with the e-mail address administrator@domain.com. Id : 1006Type : InformationMessage : The Autodiscover service was contacted at https://host.domain.com/Autodiscover/Autodiscover.xml. Id : 1016Type : SuccessMessage : [EXCH]-Successfully contacted the AS service at https://host.domain.com/EWS/Exchange.asmx. The elapsed time was 93 milliseconds. Id : 1015Type : SuccessMessage : [EXCH]-Successfully contacted the OAB service at https://host.domain.com/EWS/Exchange.asmx. The elapsed time was 0 milliseconds. Id : 1014Type : SuccessMessage : [EXCH]-Successfully contacted the UM service at https://host.domain.com/UnifiedMessaging/Service.asmx. The elapsed time was 0 milliseconds. Id : 1016Type : InformationMessage : [EXPR]-The AS is not configured for this user. Id : 1015Type : SuccessMessage : [EXPR]-Successfully contacted the OAB service at . The elapsed time was 0 milliseconds. Id : 1014Type : InformationMessage : [EXPR]-The UM is not configured for this user. Id : 1013Type : ErrorMessage : When contacting https://host.domain.com/Rpc received the error The server committed a protocol violation. Section=ResponseStatusLine Id : 1017Type : ErrorMessage : [EXPR]-Error when contacting the RPC/HTTP service at https://host.domain.com/Rpc. The elapsed time was 15 milliseconds. Id : 1006Type : SuccessMessage : The Autodiscover service was tested successfully. Id : 1021Type : InformationMessage : The following web services generated errors. Contacting server in EXPR Please use the prior output to diagnose and correct the errors.

Hi,Where did you run the command Test-Outlookwebservices? CAS, Mailbox server or Hub server?As the error persists in the output of Test-OutlookWebServices. I did more research on the error. The message "The server committed a protocol violation" actually is an error reported in ASP.Net 2.0. When Test-OutlookWebServices performs the tests, requests are sent in HTTP (with TLS) and then IIS server replies. In case the HTTP response can't be correctly handled by the .Net code, the error will be returned.Based on my research, this issue only occurs when querying on local computer. Would you please try to running the command on server mailbox server. In case the error only occurs on the CAS server itself, we can safely ignore it as other clients won't encounter this issue.ThanksAllen

Based on my research, this issue only occurs when querying on local computer. Would you please try to running the command on server mailbox server. In case the error only occurs on the CAS server itself, we can safely ignore it as other clients won't encounter this issue. Well, I can tell you that I have seen the problem when running from another computer on the domain. Any other ideas? Command: Test-OutlookWebServices -identity YehudaK | fl Response: Id : 1013 Type : Error Message : When contacting https://remote.example.com/Rpc received the error The server committed a protocol violation. Section=ResponseStatusLine

I have a similar issue to this and haven't found a good solution to this yet. I also run the https://www.testexchangeconnectivity.com and come accross one unresolvable error. HOpefully someone here could help. RunspaceId : a8413e9d-bf32-44c6-bb30-fb751477e8ec Id : 1013 Type : Error Message : When contacting https://exchange.mydomain.com/rpc received the error The remote server returned an er ror: (403) Forbidden. RunspaceId : a8413e9d-bf32-44c6-bb30-fb751477e8ec Id : 1029 Type : Error Message : [EXPR] Error contacting the RPC/HTTP service at https://exchange.mydomain.com/rpc. Elapsed time was 3 1 milliseconds. the testexchange website's only error is RPC Proxy can't be pinged. I"m pretty much stuck on this. Chances are, I don't have IIS configured right. I also have our company website running on the same box which creates issues. I might have to setup another system to handle this functionality specifically if I can't get it resolved. My thoughts were to setup another website within the IIS and move our website to that and change the bindings to receive incomming requests then change the default website and set it up for exchange. I currently do have bindings for our exchange address listed above and I made the common name of our godaddy cert the same as the autodiscover because of issues outlook has with it not being the common name. I just don't know at this point.