We have a weird problem that only started once SP2 was installed on our Exchange 2010 CAS servers. Anyone with a name starting with the letters OMA can now no longer access the Outlook Web App. My boss is blaming it on a newly appeared virtual directory within the \OWA directory. I'm cynical but open to it being a bug in the code. In fact, type any name, even a non-existant one, and you get the same error.
Visits to Web Access produce the following entry in the IIS log:
2013-02-11 15:53:00 172.17.5.34 GET /owa/omar.zakaria@westminster.org.uk - 443 WESTMINSTER\anthony.sheehy 172.17.24.15 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.2;+WOW64;+Trident/6.0;+.NET4.0E;+.NET4.0C;+.NET+CLR+3.5.30729;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.30729;+Tablet+PC+2.0;+InfoPath.3) 400 0 0 0
I run a failed request trace and I get the following information:
ModuleName OwaModule
Notification 4
HttpStatus 400
HttpReason Bad Request
HttpSubStatus 0
ErrorCode 0
ConfigExceptionInfo
Notification AUTHORIZE_REQUEST
ErrorCode The operation completed successfully. (0x0)
Nothing else is affected. All other (1700+) users are unaffected. Looks buggy to me...
PS. We have disabled OWAMini on both CAS servers and in the Default Outlook Web App Policy. Even removing the OMA Application does not do anything.
Anthony Sheehy - MCP, MCITP