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

    Question

  • 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...

    Monday, November 4, 2013 11:46 AM

Answers

  • Hi,

    Based on my research, here is an article describing a similar issue:

    http://2008release2en.blogspot.in/2013/08/gelost-ms-exchange-2013-owa-login.html

    you can refer to the solution:

    1. On the Exchange Server (CAS) go to directory : *\Exchange\ClientAccess\owa\15.0.516.30\owa2\ext\killbit
    2. verify if the file killbit.xml is present. If there is, please delete or cut it.
    3.  run iisreset.

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

    If you have any question, please feel free to let me know.

    Thanks,

    Angela


    Angela Shi
    TechNet Community Support

    • Marked as answer by JVanstone Tuesday, November 12, 2013 2:41 PM
    Tuesday, November 12, 2013 3:22 AM

All replies

  • Hi,

    Firstly, to understand more about the issue, I’d like to confirm the following information:
    1. Does the OWA issue happen on all users? Does the issue still exist if login on the CAS server?
    2. Does the OOF issue happen on all Outlook clients except Outlook 2013?

    For the issue that OWA cannot be used and the error code 3005, I recommend you collect IIS log to catch the cause:
    1. On the Exchange 2013 Client Access Server, locate the folder “c:\inetpub\logs\logfiles\W3SVC1” (If the IIS log is not enabled, please enable it and try to reproduce this issue.)
    2.  Check the log files inside the folder and post the related error codes.

    For the OOF issue, I recommend we can try to update Outlook to the latest version.

    For the issue that OWASelfTestMonitor is unhealthy, I hope the following article can help you:
    http://technet.microsoft.com/en-us/library/ms.exch.scom.owa.protocol(v=exchg.150).aspx

    Thanks,
    Angela


    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.

    Tuesday, November 5, 2013 11:23 AM
  • Hi Angela,

    Thanks for the reply, will run through your comments below.

    1)  OWA issue is for all users and happens on the CAS server as well as on clients.

    2)  Out Of Office issue is on all clients, on all outlook versions.  (Outlook running all the latest patches.)

    IIS Log from OWA Access below.  This looks to be the relevant bit. I put brackets around the https bit to stop the Forum moaning about links.

    2013-11-06 08:11:40 192.168.0.250 POST /owa/auth.owa &cafeReqId=67a2f68e-bb1c-43b0-99e3-ba527b5178b0; 443 mydomain\f4t 192.168.0.250 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) (https)://mail.mydomain.co.uk/owa/auth/logon.aspx?replaceCurrent=1&url=(https)%3a%2f%2fmail.mydomain.co.uk%2fowa%2f%3fbO%3d1 302 0 64 15
    2013-11-06 08:11:40 192.168.0.250 POST /owa/auth.owa &cafeReqId=60b7c49b-7aa1-4284-a1fc-eff976a42a5e; 443 mydomain\f4t 192.168.0.250 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) (https)://mail.mydomain.co.uk/owa/auth/logon.aspx?replaceCurrent=1&url=(https)%3a%2f%2fmail.mydomain.co.uk%2fowa%2f%3fbO%3d1 302 0 0 0
    2013-11-06 08:11:40 192.168.0.250 GET /owa/ bO=1&cafeReqId=2773be91-2f53-4d5f-87a3-356d4ae6f79d; 443 mydomain\f4t 192.168.0.250 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) (https)://mail.mydomain.co.uk/owa/auth/logon.aspx?replaceCurrent=1&url=(https)%3a%2f%2fmail.mydomain.co.uk%2fowa%2f%3fbO%3d1 302 0 0 46
    2013-11-06 08:11:40 192.168.0.250 GET /owa/auth/errorFE.aspx httpCode=500&cafeReqId=66c70514-8534-4cc6-bce1-a876ad92f346; 443 - 192.168.0.250 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0) (https)://mail.mydomain.co.uk/owa/auth/logon.aspx?replaceCurrent=1&url=(https)%3a%2f%2fmail.mydomain.co.uk%2fowa%2f%3fbO%3d1 200 0 0 0

    I've tried to use the directions on the linked webpage but unfortunately when I use the Invoke Command I get the following;

    Warning:  Invoke Now items must be enabled and without recurrence.

    Wednesday, November 6, 2013 8:27 AM
  • Hi,

    From the IIS log, I can see some 302 error codes which means redirection error. Thus, I'd like to confirm whether you set any redirections on the default web site before.

    Additionally, let’s also double check if we can access EWS virtual directory.
    And here are the steps you can refer to :
    1. Test Email auto-configuration on Outlook only with Use AutoDiscover.
    2. Check the Results, find the OOF URL which Outlook client trying to access.
    3. Input OOF URL in IE and see whether it can be accessed successfully.

    If you have any question, please feel free to let me know.
    Thanks,
    Angela


    Angela Shi
    TechNet Community Support

    Friday, November 8, 2013 6:29 AM
  • 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 :(

    Friday, November 8, 2013 8:44 AM
  • Hi,

    Based on my research, here is an article describing a similar issue:

    http://2008release2en.blogspot.in/2013/08/gelost-ms-exchange-2013-owa-login.html

    you can refer to the solution:

    1. On the Exchange Server (CAS) go to directory : *\Exchange\ClientAccess\owa\15.0.516.30\owa2\ext\killbit
    2. verify if the file killbit.xml is present. If there is, please delete or cut it.
    3.  run iisreset.

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

    If you have any question, please feel free to let me know.

    Thanks,

    Angela


    Angela Shi
    TechNet Community Support

    • Marked as answer by JVanstone Tuesday, November 12, 2013 2:41 PM
    Tuesday, November 12, 2013 3:22 AM
  • Hello, we have the exact same problem. OWA is not working 'something went wrong' and cannot set out of office reply. We found the killbit.xml file and removed it. But after the reset still the same problem. Do you have more ideas? We need the out of office now because of the summer holidays. I would appreciate any help.....
    Saturday, July 26, 2014 7:27 PM