Outlook Web Services - RPC/HTTP Protocol Violation (Full Version)

All Forums >> [Microsoft Exchange 2007] >> General



Message

AdmiralNemo -> Outlook Web Services - RPC/HTTP Protocol Violation (20.Jun.2008 4:33:08 PM)

I have been trying for several months now to track down some issues with my new Exchange 2007 server. At first, the only symptom I could actually find was that Outlook 2007 was constantly promoting users to enter a password, and no matter what they put in, it didn't seem to take it.  After weeks upon weeks of diving through log files and test connections, I have boiled the problem down to the OAB web distribution and Server 2008 TS Gateway.  The problem seems to lie in the /rpc/ virtual directory in IIS, because any time something changes in that directory, one or the other features stops working.  For example, if I delete and recreate the /oab/ virtual directory, the OAB works again, but TS gateway stops.  If I restart the TS gateway service, it starts working and OAB goes back to prompting for passwords and never downloading.

The IIS logs don't give a lot of information, but they do show a 401 challenge response code given when someone accesses either TS gateway or the OAB, but no authentication response is ever received.  This occurs for whichever feature is currently broken, but not the other.

The closest thing I can get to an error message is from Test-OutlookWebServices in the EMS: 

Id      : 1013                                                                 Type    : Error                                                                Message : When contacting https://mail.gosupertechs.com/Rpc received the error           The server committed a protocol violation. Section=ResponseStatusLine


If anyone could provide some help, I would really appreciate it.

Server System Software:
Windows Server 2008 Standard
Microsoft Exchange 2007 Standard
Internet Information Services 7
Microsoft .NET Framework 3.5

Client System Software:
Windows Vista Business x64 SP1
Microsoft Office Outlook 2007

Thanks,
Dustin



jveldh -> RE: Outlook Web Services - RPC/HTTP Protocol Violation (20.Jun.2008 5:18:22 PM)

Did you had this issue before .NET 3.5 ? Please check if all virtual websites are running the .NET 2.0. If you can remove .NET 3.5 and check if it works then.



AdmiralNemo -> RE: Outlook Web Services - RPC/HTTP Protocol Violation (20.Jun.2008 6:24:48 PM)

I am not sure if this issue existed before the installation of .NET Framework 3.5 or not.  I do remember that there were the password dialogs constantly in Outlook before I installed 3.5, but it was only recently that I was able to determine their exact cause, so I am not sure if those were the same ones.  I am going to guess that they were and say that the problem did in fact exist before 3.5 was installed.

We have a custom developed web service application that requires 3.5 to run, but as it is not currently functioning, I suppose I could uninstall 3.5 and see if that makes any difference.  I was just thinking about this as well, the application has the same problem as the RPC directory, throwing 401 but never authenticating the user.  They are likely related, though installed on separate sites (ports) on the same server.  I am having the developer come by soon to help debug this software, maybe we will find something then.

According to IIS manager, all of my application pools have .NET Framework Version 2.0 except ASP.NET 1.1, which of course has 1.1.  They all say "Classic" mode except the one for our custom developed application which says "Integrated."  I know nothing about .NET, so I don't know if that is what you needed to know or not.

Let me know if there is anything else I should check.

CORRECTION:
DefaultAppPool and WsusPool both say "Integrated" under "Managed Pipeline"



jveldh -> RE: Outlook Web Services - RPC/HTTP Protocol Violation (21.Jun.2008 7:46:55 AM)

What I did see once is that some .NET versions overwrite specific files which are used by both versions. This caused that OWA and other CAS related web-services didn't work anymore.

The sollution was to remove the conflicting .NET and the reinstall the CAS role.

Regards,

Johan



AdmiralNemo -> RE: Outlook Web Services - RPC/HTTP Protocol Violation (29.Jun.2008 5:52:34 PM)

I finally got the opportunity to take my Exchange server down today and try removing .NET 3.5 and reinstalling the CAS role, but now I have an even bigger problem.  I removed the CAS role, rebooted the machine, and attempted to reinstall but it failed, telling me that another version was already installed.  I then tried the Setup.com way, but it failed as well.  Basically, I can't uninstall the CAS role because Windows thinks it is not installed, but I can't install either, because Windows thinks its already installed.

What do I do? I am afraid to run the MSI Clean Up Utility for fear or removing my entire Exchange installation. Is this my only option? Please let me know what I can try.

Thanks



AdmiralNemo -> RE: Outlook Web Services - RPC/HTTP Protocol Violation (1.Jul.2008 2:32:14 PM)

I'm sorry; I am an idiot.  Apparently User Error applies to administrators as well...I had the RTM version of Exchange 2007 DVD in the drive not the SP1 [:)]

At any rate, this did not solve my problem...I am going to make another server with the exact setup and try to reproduce the problem. If I can't, I will just move everything onto that server :)



jveldh -> RE: Outlook Web Services - RPC/HTTP Protocol Violation (30.Jul.2008 2:51:21 AM)

Have you tried the repair option ?



dsantee -> RE: Outlook Web Services - RPC/HTTP Protocol Violation (28.Sep.2008 12:54:21 AM)

Identical setup here - and the identical problem.  I've even created a new Exchange VM to test - new 2008 x64 installation, new Exchange 2007 x64 SP1 installation, all updates.  Nothing else.  Installed my cert, configured my URLs, moved one mailbox to test.  When I run test-outlookwebservices I get:

ID 1013 Error
When contacting https://webmail.myrealdomainhere.com/Rpc received the error The server committed a protocol violation.  Section=ResponseStatusLine

I've tried adding a web.config to the server and using the useUnsafeHeaderParsing setting just to check, but that didn't help either.  I have absolutely everything else working the way I need it to.  Any help would be greatly appreciated!

Dan



Page: [1]