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

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

  • Exchange OWA Page Blank For Random Users After Mailbox Moves

    We have three Exchange server. msexch1, msexch2, msexch3. msexch1 is currently offline. msexch1 and msexch have the CAS and MBX roles installed and are in a DAG. We moved all mailboxes from msexch1 to the other two servers. Since then we have users reporting
    that when they logon to owa they get a blank page. The resulting url is owa/auth.owa. The domain we use is exchange.ourdomain.com. The fqdn of each exchange server is msexch2.ourdomain.com, etc. We use round robin dns for our exchange servers, therefore we
    have two entries for exchange.ourdomain.com. For the purposes of this question lets say the ip of msexch2.ourdomain.com is 10.10.10.52 and msexch3.ourdomain.com is 10.10.10.53 and we have two entries in our dns for exchange.ourdomain.com, one for 10.10.10.52
    and the other 10.10.10.53.
    When a user experiences this issue I have found that when I ping exchange.ourdomain.com to determine which exchange server they are "connected" to; if I force them to use the other one they are then able to access owa just fine. For example, I
    have a user whom is getting a blank page after they logon to owa. I ping exchange.ourdomain.com which returns 10.10.10.52 for an ip address, which tells me they are connected to msexch2.ourdomain.com. When I enter in the url https://msexch3.ourdomain.com/owa
    to force them to logon using the other server, they are able to owa owa without any issues. When I use the url https://msexch2.ourdomain.com they receive a blank page after logon (as expected because this is the server they are trying to contact via dns exchange.ourdomain.com)
    I have tried recreating both owa virtual directories which did nothing. I am at my wits end here and would greatly appreciate any assistance.

    Hi,
    According to your description, I understand that OWA get blank after move mailbox to another mailbox server, and you deploy DNS round robin in your environment.
    If I misunderstand you concern, please do not hesitate to let me know.
    It may be caused by OWA proxy cannot work correctly, please try below steps to double check:
    1. Get a mailbox place in msexch3 and login OWA with
    https://msexch3.ourdomain.com/owa.
    2. Get other mailbox place in msexch2 and login OWA with
    https://msexch3.ourdomain.com/owa.
    If the steps 2 cannot proxy URL to https://msexch2.ourdomain.com/owa, it may be the key reason.
    Please clarify the environment of your Exchange:
    1. Which version are you used?
    2. Check the authentication of OWA: Get-OwaVirtualDirectory | FL Identity,*URL*,*Auth*
    OWA is configured to use integrated windows authentication on each virtual directory, and the external URL under is blank.
    Also, please run below command to double check the health of Outlook Web App service:
    Get-ServerHealth “msexch3” |?{$_.AlertValue –Eq “Unhealth”}
    Thanks
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Allen Wang
    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.

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

  • 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

  • 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 cros site blank page OWA/ECP

    Hello,
    I have an issue with a fresh installation of Exchange 2013 SP1.
    The are two AD site in different cities, connected by WAN link (site-to site VPN organized by Cisco ASA).
    I installed two Exchange servers in Site A (MBX1 and MBX2, both with MBX+CAS roles), and one Exchange server MBX3 in Site B (also both with MBX+CAS roles).
    Each Exchange hosts its own mailbox database (DB1, DB2, DB3 respectively), there are no DAG.
    Users spread over all databases. For example, user1 has mailbox in DB1, user2 - in DB2, user3 in DB3.
    When user1 opens OWA/ECP on CAS server MBX1 or MBX2, he successfully get into his mailbox.
    But, if user1 opens OWA/ECP on CAS server MBX3, he get blank page (no error at all).
    And vise versa:
    When user3 opens OWA/ECP on CAS server MBX3, he successfully get into his mailbox.
    But, if user3 opens OWA/ECP on CAS server MBX1 or MBX2, he get blank page (no error at all).
    I know, that Exchange 2013 is able to proxy request cross site.
    Where are no custom redirects set on IIS.
    Also I check IIS (Back End Site) for right certificate.
    There are no error in Windows Event log and IIS event Log.
    All ports are allowed between sites.
    Everything looks good.
    What I did wrong? May be I need to enable cross-site OWA proxy in Exchange somewhere?
    Or it is a CISCO ASA misconfiguration?
    Any help would be appreciated!
    Thank You!
    Pavel

    Hi,
    Firstly, I’d like to confirm if all your Exchange server are internet facing servers.
    We can try to clear the Forms based authentication on the non-internet facing server.
    And here is a similar thread you can refer to:
    http://social.technet.microsoft.com/Forums/exchange/en-US/85983a21-3922-46f4-b64a-d53c0a2271a7/issues-with-crosssite-cas-redirect-of-owa-users?forum=exchange2010
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Angela Shi
    TechNet Community Support

  • Exchange 2013 : OWA failing after login with error "HTTPS 400"

    Greetings,
    I am in phase of Upgrading my existing Exchange 2007 Infra to Exchange 2013.
    The environment is as mentioned below:
    4 Mailbox Server (DAG)
    4 CAS Servers (NLB)
    Everything has been configured and working properly, except Only one CAS server is able to pass the login request
    https://servername/owa
    Rest of all the CAS servers are failing with error "HTTPS 400" while accessing OWA
    https://localhost/owa
    Its happening only while accessing OWA, ECP works fine.
    Please let me know the fix to counter this strange issue.
    Thanks in advance.
    Regards

    Hi,
    Please check if IIS log is enabled on the CAS server, if not, please enable it.
    Then check the detailed error code from IIS logs (Path: inetpub\logs\Logfiles\W3SVC1 ) , some code like 400.1, 400.2 ect.
    Refer to this KB for more details
    http://support.microsoft.com/kb/943891
    After that, please post the OWA related login entry with error code shows 400.
    Thanks for your time and patience.
    Meanwhile, please check the OWA authentication method by command
    Get-OWAVirtualDirectory –Server “Ex2013 CAS server” | fl *authentication*
    We should set the authentication as the below:
    Get-OWAvirtualdirectory -Server “Ex2013_CAS_server” | set-OWAvirtualdirectory -windowsAuthentication $False -BasicAuthentication $True -FormsAuthentication $True
    Then perform iisreset and try to access OWA again.
    Best Regards.

  • 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 "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 CAS incorrectly proxying after mailbox move to Exchange 2013

    Hi,
    I am moving Exchange 2010 mailboxes to Exchange 2013 SP1 in production. When I move 2010 mailbox Outlook, OWA works fine right after the move but ActiveSync (HTTPProxy log shows
    on CAS 2013 server that it is still re-directing it to Exchange 2010 CAS servers). Exchange 2013 CAS server ActiveSync takes hours before it starts to see that mailbox is moved to Exchange 2013. I am certain it is not ActiveDirectory replication since all
    other clients are working.
    This time I move another user this time it did not work for 3.5hrs.  I had to reboot Exchange 2013 CAS server after that it worked.
    There is must be something that is not refreshing on Exchange 2013 CAS server.  
    Is there anything I can do right after the move to make it quick, I can not re-start server after every mailbox move.  Currently we are in Pilot mode and only moving few
    mailboxes at a time.
    Thanks,
    Raman

    Hi,
    I am moving Exchange 2010 mailboxes to Exchange 2013 SP1 in production. When I move 2010 mailbox Outlook, OWA works fine right after the move but ActiveSync (HTTPProxy log shows
    on CAS 2013 server that it is still re-directing it to Exchange 2010 CAS servers). Exchange 2013 CAS server ActiveSync takes hours before it starts to see that mailbox is moved to Exchange 2013. I am certain it is not ActiveDirectory replication since all
    other clients are working.
    This time I move another user this time it did not work for 3.5hrs.  I had to reboot Exchange 2013 CAS server after that it worked.
    There is must be something that is not refreshing on Exchange 2013 CAS server.  
    Is there anything I can do right after the move to make it quick, I can not re-start server after every mailbox move.  Currently we are in Pilot mode and only moving few
    mailboxes at a time.
    Thanks,
    Raman
    Does simply recycling the ActiveSync app pool speed things up?
    Also, I would recommend installing CU6 instead of SP1.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Maybe you are looking for