Exchange 2013: owa page shows up but returns bad request when logged in

Environment: Exchange 2013 CU6 /Windows Server 2012 R2
Just installed the patch yesterday, owa and ecp was working fine after the install but it broke for some reason.
was able to get ecp and powershell running but still cant up owa.
owa website can be accessed online, but once logged in it will throw errors below:
Firefox:bad request
IE:https://mail.domain.com/owa/auth.owa
tried to recreate Virtual directories for ecp and owa but to no avail.
both default website authentication shows basic,forms and fba (for ecp/owa)
checked IIS settings: no redirection details for both http redirect by default didnt touch it as well.
just wondering if anyone experienced the same and how they got it to be resolved, also is there a way to check what is the current authentication method for the backend server
not sure if i am checking it correctly but when i go to IIS>exchange back end, i cannot enable basic and forms as the same time...
thanks in advance

Hi,
From your description, I recommend you use the following cmdlet to change the authentication method of the "owa" virtual directory to Windows authentication.
Set-Owavirtualdirectory -identity "servername\owa (Exchange Back End)" -WindowsAuthentication $True -Basicauthentication $false -Formsauthentication $false
And then run the following command on both the Client Access and Mailbox servers to restart IIS and check the result.
iisreset /noforce
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Similar Messages

Redirection loop detected while opening Exchange 2007 mailboxes through Exchange 2013 OWA page

Team, in our infra Exchange 2013 CU8 & Exchange 2007 SP3 RU15 running. Exchange 2013 recently deployed but while opening exchange 2007 users mailbox through 2013 OWA getting error "Redirection loop detected". Want to update you few things :
Public DNS record created as mail.myinfra.in with x.x.x.2 IP and legacy.myinfra.in with x.x.x.3 IP.
Virtual directory modified mail.myinfra.in for 2013 & legacy.myinfra.in for 2007.
All the OWA request need to pass through public DNS only no internal DNS record for OWA.
Through ISA already rule created and tested also like https://mail.myinfra.in/owa giving me 2013 OWA page & https://legacy.myinfra.in/owa giving 2007 owa page. Only problem while opening https://mail.myinfra.in/owa with 2013 mailbox id/pwd working fine
but with 2007 mailbox id/pwd giving error "Redirection loop detected".
Appreciate if you can help quickly.

Hello
tip: check iis log on both of exch servers and check owa application haven't got "HTTP redirect" enabled.
sorry my english

Exchange 2013 OWA page blank after login

When logging into the OWA from *most* browsers (Chrome, firefox, Opera) OWA does not show up, just shows a blank page with the proper website title. OWA works fine on my mac with safari.
This is a picture of the network option in chrome development console, so there is data/files getting transferred..
http://imgur.com/yOUbAsR
This issue is leaving me dumbfounded because:
1. Everything works as expected in safari on my mac.
2. OWA worked fine a few days ago and I made no changes since then.
I have tried re-creating the SSL certificate with netsh, removing and creating a new OwaVirtualDirectory and disabling/enabling OWA on my account.

Hi,
Does the issue happen to all users or only one specific user? Please check whether the issue happens in Internet Explorer in Windows.
Please make sure all browsers are using the latest version with Compatibility view. Also change a computer to have a try.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 OWA internal only

Hi all,
Does anyone know how to restrict Exchange 2013 OWA for internal only, but can't impact Exchange ActiveSync service?
I guess IP Address and Domain Restrictions can make it, but it may impact ActiveSync.
Any good solution?
Thank,
Ian

Hi,
Based on my research, we can install the CAS and Mailbox roles in separate two servers. Then we can create new website with a unique IP and only adding ActiveSync to that website. That would give us a website hosted on the box that served the ActiveSync
devices but nothing else, leaving the OWA open for internal access. The firewall would point to this website/IP on the CAS. We could also create a virtual directory under there for /OWA and /Exchange which would serve up the generic ““this service is no longer
available, please contact the help desk” message as the default webpage
http://blogs.technet.com/b/messaging_with_communications/archive/2011/05/02/how-to-block-owa-for-external-users.aspx
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 OWA IM to federated users

Hi I configured Exchange 2013 OWA IM for Lync server and everything is working fine except that I can't IM federated Lync users when the conversation is initiated from OWA. When I start an IM conversation from the federated user to my OWA, everything is
working fine. Also the replies arrive then! So it must be something with initiating the session. I don't have issues with federated users form normal Lync desktop clients or mobile clients.
In the lync logs I notice the following when starting the conversation from OWA:
1027;reason="Cannot route this type of SIP request to or from federated partners";
I also notice there's a KB2977259 (http://support.microsoft.com/kb/2977259) that discusses similar things but I'm not working with contacts like that and I guess they don't mean that you have to do this for every federated contact a Lync user has.
Does somebody else also experience this issue?
Update: following this KB I tried to add a new outlook contact in owa and add my sip address as "sip:[email protected]". When doing this it actually work to IM this federated user. But this is actually a workaround you can't expect your users
to implement. I can't believe nobody else has issues with this.

Hi DS_Kevin,
Please post a little more log information. It seems that IM from OWA can’t locate the federated user’s SIP address without the sip prefix.
Best Regards,
Lisa Zheng
Lisa Zheng
TechNet Community Support

Exchange 2013 owa integration with ADFS and cooexistance with exchange 2007

Team,
I have successfully integrated adfs 3.0 and Exchange 2013 owa and ecp. However, we have a coexistence environment with exchange 2007. When you access owa, which then redirects you to adfs, sign-in, and then get redirected back to owa. If your
mailbox is still within exchange 2007, you get a blank login page. If you mailbox is in exchange 2013 then you successfully get the owa page for 2013. The problem is that all exchange 2007 mailbox users get blank pages at login. So I have determined
that exchange 2013 cas is not doing the service location lookup on the mailbox to determine if a redirect to the legacy owa address is needed. Is there a configuration setting that I might be missing? Or does the integration with adfs and owa not support
the much needed mailbox lookup for a coexistance environment? A side note: if we enable FBA with owa, both login scenarios work just fine (legacy and new 2013). The legacy namespace has been created, and applied to the exchange 2007 urls.

Hi,
Try using AD FS claims-based authentication with Outlook Web App and EAC
http://technet.microsoft.com/en-us/library/dn635116(v=exchg.150).aspx
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Publish Exchange 2013 OWA + Active Sync + Outlook Anywhere using TMG 2010

We plan to publish our new Exchange 2013 SP1 servers (3 in DAG) outside corporate network using TMG 2010. I am looking for some guide how to do it in the proper way. What I found is little old and does not take into consideration Exchange 2013
SP1
http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx
Any advice how to publish Exchange 2013 OWA using form-based authentication and how to use Kerberos Constrained Delegation?

Hi,
The blog below describes some scenarios about publishing Exchange. You could have a look the Scenario 2.
Exchange publishing after TMG/UAG
http://dizdarevic.ba/ddamirblog/?p=168
Note: Microsoft provides third-party contact information to help you find technical support. This contact
information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How to configure Exchange 2013 OWA with Single Sign On

Hi All ,
How to configure Exchange 2013 OWA with Single Sign On ?
Thanks .

Hi,
From your description, I am not quite sure what you really want to achieve. Could you explain it furthermore? If you need to set up Exchange 2013 OWA single sign on with Exchange 2010, here is a helpful thread for your reference.
Exchange 2013 OWA Single Sign on with Exchange 2010
https://social.technet.microsoft.com/Forums/en-US/2899ebfc-8622-4cdc-8d77-d76b607618f7/exchange-2013-owa-single-sign-on-with-exchange-2010?forum=exchangesvrdeploy
If that is not your case, please feel free to tell me.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Exchange 2013 Issue: Outlook 2010 auto populating the From Tab when forwarding email

Exchange 2013 Issue: Outlook 2010 auto populating the From Tab when forwarding email
I am running Exchange 2013 and I have an end user who connects to it via Outlook 2010. All was going well till he went to forward an email and he noticed that the From button appeared and auto populated the sender's email address.
I have clicked the Empty Auto Complete List in Outlook's Send messages... still displayed the From tab when forwarding.
I recreated the profile in outlook... same thing.
I created the profile with outlook 2013... same thing.
There is only one user profile setup in Outlook.
(I know the from tab usually appears when you have multiple profiles setup in Outlook and/or when you configure the "From" tab.)
I opened the end user's email in Exch 2013's OWA... what was different here was when I clicked on the email and it opened, it did NOT have the Reply or Forward option... and it displayed as a "Draft" email.
Does anyone have any ideas?

So are you saying that the from button is filling the option with the original senders address (eg the person who sent the message to your user), or that it's filling in the your users address (in which case I don't understand what the issue is, since
it IS going from your user)?

404 can't find page Error when logging into Exchange 2013 OWA, after a refresh, login works

Hi,
I've upgrade two of my customers to Exchange 2013.
On of them was coming from 2007, and the other was already running 2010.
Migration from both of the servers went good.
However with the customer which upgraded from 2010 to 2013 i'm experiencing strange OWA behavior:
When I login to OWA on https://owa.contoso.com/owa, and input my credentials and click sign in: I receive this error:
404
can't find page :-(
The page you're looking for couldn't be found on the server.
X-FEServer: JVBMAIL01
Date: 11-6-2014 11:54:48
Fewer details..
-> Refresh the page
In the addressbar, the following URL is displayed: https://owa.contoso.com/owa/auth/errorFE.aspx?httpCode=404
But... when I click: "Refresh the page" of just hit F5, the login proceeds, and my OWA is displayed and working fine.
This behavior only happens with my customer which was upgraded from 2010 to 2013.
The customer which i've upgraded from 2007 to 2013 doesn't experience this problem.
I've matched the IIS settings and redirect/ssl options on both servers. They are the same.
I've tried other users and i've experienced that on one user, the error message didn't appear.
When I try to delete the Exchange atributes from the user, (after exporting the mail to a PST file) and re-add the Exchange attributes, the message is gone. This isn't a solotuion however, since i've got 166 users, and about 150 of them, get the error message.
New users don't get the error.
Anybody got any clues?

Hi,
From your description, I would like to verify the following thing for troubleshooting:
Please make sure that the authentication is set to Basic Authentication and Forms Authentication is disabled on OWA and ECP virtual directly in IIS. After the above settings, please restart IIS by running IISReset /noforce command.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2013 RPC URL shows Error 404 Page Not Found

Hi,
I have been told by Barracuda Support to verify my Exchange 2013 RPC url is working correctly using the following address in a Web Browser:
https://RoH server address/rpc
When I hit this URL I input my credentials and get a Error 404 - Page Not Found.
I dont have any issues with Outlook Anywhere and clients are working fine. The tests come from this article and I am wondering if they are still valid for Exchange 2013 so need some help:
https://techlib.barracuda.com/BMA/EnableRoH
Does anyone else get the 404 error when they try the RPC virtual directory? If I got rpc/rpcproxy.dll that works fine and no issues.
We have Outlook Anywhere configured for NTLM authentication so maybe this is an issue and should be Basic?

I did some digging in the CAS RPC logs and I found this connection attempt:
<snip>
2014-06-18T15:22:40.902Z,CAS-SERVER,RpcHttp,"S:Stage=EndRequest;S:UserName=domain\admin;S:OutlookSessionId=""{1A731432-5548-402F-892A-C9FE489BB78D}"";S:AuthType=Basic;S:Status=404 Not Found;S:HttpVerb=RPC_IN_DATA;S:UriQueryString=?pdc.domain.local:593;S:RequestId=7b1e355e-6448-4ed4-8112-8ab13d88a76f;S:ClientIp=192.168.0.17"
</snip>
As you can see the 404 Not Found is for the request to /rpc. I am wondering if maybe this has changed in Exchange 2013 SP1? Or have I got a bigger issue here?

Exchange 2013 - OWA "Something Went Wrong", Out of office in Outlook "Server unavailable"

Hi,
We have a new deployment of Exchange 2013 CU2 V2 running on a Windows 2012 server. Everything has been running without issues and then without any real clue to why, we are now getting an issue where OWA says "Something Went Wrong" after processing
your login, (it appears to process the login as if I type in incorrect details it tells me the password/username is wrong).
At the same time we have also lost the ability to run the Out Of Office in Outlook which comes back saying the server is not available and we can't seem to share calendars correctly either. (Can set Out Of Office via the Management Shell without issues).
When running a Get-Serverhealth on the OWA.Protocol it tells me the OWASelfTestMonitor is unhealthy.
I've tried re-creating the OWA, EWS Virtual Directorys and also the autodiscover but with no effect. I've also restarted the server.
Outlook 2013 and mobile phones are working fine on the server and the Exchange Admin Centre is also working without issues.
I am getting tempted to apply CU2 again to see if this sorts it but don't really like doing this on a server with 50 live users on it...
In the eventlog I can see lots of the 2 errors listed below which seems to line up. (System Log and Application Log seem to be clear of other errors or warnings.)
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 04/11/2013 11:25:00
Event time (UTC): 04/11/2013 11:25:00
Event ID: 2fcdb9112c794b63a9ea9577a23e4603
Event sequence: 2
Event occurrence: 1
Event detail code: 0
Application information:
    Application domain: /LM/W3SVC/2/ROOT/owa-411-130280378905273269
    Trust level: Full
    Application Virtual Path: /owa
    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
    Machine name: SERVERNAME (I altered this for post)
Process information:
    Process ID: 9648
    Process name: w3wp.exe
    Account name: NT AUTHORITY\SYSTEM
Exception information:
    Exception type: HttpException
    Exception message: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
Lots more code.......
AND
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 04/11/2013 11:24:24
Event time (UTC): 04/11/2013 11:24:24
Event ID: 2586a044b2d74b97a1095aec478bf4ae
Event sequence: 2
Event occurrence: 1
Event detail code: 0
Application information:
    Application domain: /LM/W3SVC/2/ROOT/EWS-668-130280378564324526
    Trust level: Full
    Application Virtual Path: /EWS
    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\exchweb\EWS\
    Machine name: SERVERNAME (I have changed this for post)
Process information:
    Process ID: 9840
    Process name: w3wp.exe
    Account name: NT AUTHORITY\SYSTEM
Exception information:
    Exception type: HttpException
Exception message: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
lots more data...

Hi Angela,
I can't see any re-directions on the website and have certainly not set any intentionally. I did try installing the Remote Web Gateway on the server and then found that it doesn't work on an exchange box and removed it but the server was working after
this.
The HTTP Redirect in Default Web Site is not showing anything set and the same for the Back End.
The bindings on the default site all look normal with;
http     80   127.0.0.1
https   443 127.0.0.1
http     80    *
http    443   *
The same is mirrored in the Exchange Back End site but with ports 81 and 444.
Running the Outlook auto configure just using Autodiscover all looks good with the URLs listed all pointing to (http)://mail.mydomain.co.uk/whatever... and the log says Autodiscover to (https)://mail.mydomain.co.uk/Autodiscover/Autodiscover.xml Suceeded
(0x00000000)
But, if I type in the OOF address of (https)://mail.mydomain.co.uk/EWS/exchange.asmx I get a login prompt but once user details are entered I then get;
'.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.]
   System.Xml.XmlTextReaderImpl.Throw(String res, String[] args) +163
   System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() +7572550
   System.Xml.XmlTextReaderImpl.ParseDocumentContent() +62
   System.Xml.XmlReader.ReadToFollowing(String name) +112
   Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitHelper.ReadKillBitXmlContent(XmlReader reader, Int32& refreshRate) +185
   Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitHelper.TryReadKillBitFile(Int32& refreshRate, DateTime& lastModifiedTime) +710
   Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitTimer.Start() +202
   Microsoft.Exchange.Services.Global.Application_Start(Object sender, EventArgs e) +975
[HttpException (0x80004005): '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.]
   System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +12864205
   System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +175
   System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +304
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +404
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +475
[HttpException (0x80004005): '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12880948
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12722137
Really wishing I had installed Exchange 2010 at this point!! Just can't see why its not working :(

Exchange 2013 OWA HTTP 500 error when opening another mailbox

We have an Windows Server 2012 Exchange 2013 server with OWA.
All users can login fine, but when I open another mailbox with my Admin account, having enabled access to that user's mailbox, the URL redirects to /owa/auth/errorfe.aspx?httpCode=500 and shows:
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk
Google won't help me in this instance. Where in the eventlog are OWA events logged?

Hello,
I am joining to the thread opener, however, we do not use exchange server. we are using the Cloud services through Microsoft and as far as I know, the version is 2013 wave 15 (again, through Microsoft's cloud).
when I open the outlook, I can see the shared mailbox just fine.
when I open the office web access, and I search the mailbox through the 'add another mailbox..' It finds it however when I press the add button I get the HTTP 500 error.
when I tried to open a different mailbox (another shared mailbox I gave myself permissions for), it opens just fine.
it seems (from what I can tell) it is this specific shared mailbox that I cannot open through OWA while others I can.
when I try to open the mailbox in question through a different internet browser (Chrome) I get this Error:
NegotiateSecurityContext failed with for host 'db3pr04mb138.eurprd04.prod.outlook.com' with status'LogonDenied'
the error seems to be persistent on this specific mailbox only regardless to what browser I am trying to access with.
I can only assume that the solutions you (Winnie) offered isn't relevant in my case.
thanks in advance for any attempt to help me with this issue.

Exchange 2013 OWA Login Error HTTP 500

I installed Exchange 2013 on Windows Server 2012.
After restarting the Host I could not login into owa or ecp the login screen showed up but after entering my correct credentials I would get a
HTTP 500 Error on https://localhost/owa/auth.owa
The error persited after multiple reboots of the Exchange server.
Some googling revealed to me that this might be caused by the Forms Based Authentication Serivce not running.
But looking at the Services List I cant seem to even locate it. (I believe that the service belongs to MS-exchange 2010 only)
Anyone got any idea why this might happen or could give me the exact name of the service or help solve the problem.
tnx

Hi
Anonymous Authentication is enable and SSL is checked on but enabling those you said above gave me this error :
challenge-based and login redirect-based authentication cannot be used simultaneously
here is the result of executing those commands:
Identity                      : SRV01-EX2013\ecp (Exchange Back End)
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication           : False
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Identity                      : SRV01-EX2013\ecp (Default Web Site)
InternalAuthenticationMethods : {}
BasicAuthentication           : False
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Identity                      : SRV01-EX2013\owa (Exchange Back End)
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication           : False
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Identity                      : SRV01-EX2013\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
please help !
thank you in advance

Exchange 2013 OWA user must change password at next logon not working

Hi,
I have installed Exchange 2013 on Windows 2012 Server. I create users in ECP and select "user must change password at next logon" option. When newly created user logs in, the OWA page doesn't prompt for password change and just throws error "The
user name or password you entered isn't correct. Try entering it again"
I have enabled Change Password feature in CAS server, but still not working.
Any answers, suggestions would be great help
Regards
Sunil

Hi Sunil,
Have you tried as Martina said and does it work?
If not, please try to set the Minimum Password Age to 1 according to link below. I found some threads which are similar to yours and were solved by this way in Exchange 2013 environment.
http://support.microsoft.com/kb/827614
And for further troubleshooting, please create a new user with "user must change password at next logon" option checked and see if he can log on domain-joined PC.
In addition, please check the event log to see if there is any related error message.
Regards,
Rebecca

Exchange 2013: owa page shows up but returns bad request when logged in

Similar Messages

Maybe you are looking for