OWA :( something went wromg -exchange 2013

hi
I have another fresh exchange 2013
i cant login to owa with error : :) something went wrong
It seems authentication issue
Ecp is working with no issues .
Identity : EXCHCASSRV1\owa (Default Web Site)
Name : owa (Default Web Site)
InternalUrl : https://exchcassrv1.corp.net/owa
ExternalUrl :
ClientAuthCleanupLevel : High
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Identity : EXCHCASSRV2\owa (Default Web Site)
Name : owa (Default Web Site)
InternalUrl : https://exchcassrv2.corp.net/owa
ExternalUrl :
ClientAuthCleanupLevel : High
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Identity : EXCHMBXSRV1\owa (Exchange Back End)
Name : owa (Exchange Back End)
InternalUrl :
ExternalUrl :
ClientAuthCleanupLevel : High
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication : False
WindowsAuthentication : True
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Identity : EXCHMBXSRV2\owa (Exchange Back End)
Name : owa (Exchange Back End)
InternalUrl :
ExternalUrl :
ClientAuthCleanupLevel : High
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication : False
WindowsAuthentication : True
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
[PS] C:\Windows\system32>^A
need help
MCP MCSA MCSE MCT MCTS CCNA

Hi,
Since your ECP can work fine, please run the following command and post the results here:
Get-EcpVirtualDirectory | FL Identity,*Authentication*,*URL*
Please note to set the Authentication method by using EMS or EAC instead of IIS manager. Just restart IIS service after changing any authentication settings in Exchange.
Regards,
Winnie Liang
TechNet Community Support
[PS] C:\Windows\system32>Get-EcpVirtualDirectory | FL Identity,*Authenticat
Identity                      : EXCHCASSRV1\ecp (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication        : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
InternalUrl                   :
https://exchcassrv1/ecp
ExternalUrl                   :
https://exchcassrv1/ecp
Identity                      : EXCHCASSRV2\ecp (Default Web Site)
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication           : False
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
InternalUrl                   :
https://exchcassrv2.corp.net/ecp
ExternalUrl                   :
[PS] C:\Windows\system32>
Also find the same from EXCHCASSRV2:
[PS] C:\Windows\system32>Get-EcpVirtualDirectory | FL Identity,*Authentication*,*URL*
Identity                      : EXCHCASSRV1\ecp (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
InternalUrl                   :
https://exchcassrv1/ecp
ExternalUrl                   :
https://exchcassrv1/ecp
Identity                      : EXCHCASSRV2\ecp (Default Web Site)
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication           : False
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
InternalUrl                   :
https://exchcassrv2.corp.net/ecp
ExternalUrl                   :
[PS] C:\Windows\system32>
MCP MCSA MCSE MCT MCTS CCNA

Similar Messages

Exchange 2013 SP1 OWA something went wrong

Hi,
I have a three node exchange 2013 DAG cluster that I upgraded to SP1 three days ago.   All email flows currently work and ECP is available on all node on all browsers for all users.   OWA was working on 2013 CU3.   After
the upgrade to SP1 and I confirmed that all email flows were working, I did change the administrators username. I noticed OWA problems after that, but they would have happened before the administrator rename. I have confirmed
certificates and binding are correct on all three nodes. I did rebuild the OWA directory on one node with no success.
However OWA is only available using Firefox (tested on several users on several machines) .   Logging on to ECP using IE 11 works fine (multiple users) Logging on to OWA using IE 11 give me the error. This is happening on
all three nodes using IE 11 but not Firefox 27
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.
X-OWA-Error: ClientError;exMsg='_u' is undefined;file=ReferenceError: '_u' is undefined at $LE (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:155) at Anonymous function (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:305913) at $8J (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:60172) at $E (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:59789) at $4pj (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:57814) at $6JC (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:58302) at Anonymous function (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:306768) at $8J (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:60172) at $E (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:59789) at $4pj (https://exch02.loran3.net/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:57814):406
X-OWA-Version: 15.0.847.32
X-FEServer: EXCH02
X-BEServer: null
Date: 1/2/1601 2:43:20 PM
Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          3/13/2014 11:45:50 PM
Event ID:      10028
Task Category: None
Level:         Error
Keywords:      Classic
User:          SYSTEM
Computer:      exch01.loran3.net
Description:
DCOM was unable to communicate with the computer EXCH02.loran3.net using any of the configured protocols; requested by PID     115c (c:\windows\system32\inetsrv\w3wp.exe).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="0">10028</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-14T05:45:50.109325400Z" />
    <EventRecordID>12481</EventRecordID>
    <Correlation />
    <Execution ProcessID="596" ThreadID="1372" />
    <Channel>System</Channel>
    <Computer>exch01.loran3.net</Computer>
    <Security UserID="S-1-5-18" />
</System>
<EventData>
    <Data Name="param1">EXCH02.loran3.net</Data>
    <Data Name="param2">    115c</Data>
    <Data Name="param3">c:\windows\system32\inetsrv\w3wp.exe</Data>
    <Binary>3C5265636F726423313A20436F6D70757465723D286E756C6C293B5069643D3539363B332F31342F3230313420353A34353A35303A3130393B5374617475733D313832353B47656E636F6D703D323B4465746C6F633D313436313B466C6167733D303B506172616D733D303B3E3C5265636F726423323A20436F6D70757465723D286E756C6C293B5069643D3539363B332F31342F3230313420353A34353A35303A3130393B5374617475733D313832353B47656E636F6D703D323B4465746C6F633D3135333B466C6167733D303B506172616D733D343B7B506172616D23303A2D323134363839333030367D7B506172616D23313A347D7B506172616D23323A36383132367D7B506172616D23333A317D3E</Binary>
</EventData>
</Event>                   ---------------------                 I am also getting
the following error
Log Name:      Application
Source:        ASP.NET 4.0.30319.0
Date:          3/14/2014 12:46:26 AM
Event ID:      1309
Task Category: Web Event
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      exch01.loran3.net
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 3/14/2014 12:46:26 AM
Event time (UTC): 3/14/2014 6:46:26 AM
Event ID: 7741cd563e154a14a0ba52343b4e30ee
Event sequence: 328
Event occurrence: 87
Event detail code: 0
Application information:
    Application domain: /LM/W3SVC/2/ROOT/owa-1-130392504882416692
    Trust level: Full
    Application Virtual Path: /owa
    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
    Machine name: EXCH01
Process information:
    Process ID: 8756
    Process name: w3wp.exe
    Account name: NT AUTHORITY\SYSTEM
Exception information:
    Exception type: MapiExceptionIllegalCrossServerConnection
    Exception message: MapiExceptionIllegalCrossServerConnection: Monitoring mailbox [] with application ID [Client=OWA] is not allowed to make cross-server calls from [EXCH01.loran3.net] to [EXCH03.loran3.net]
   at Microsoft.Mapi.CrossServerDiagnostics.BlockCrossServerCall(ExRpcConnectionInfo connectionInfo, String mailboxDescription)
   at Microsoft.Mapi.CrossServerConnectionPolicy.CheckAndBlockMonitoringMailboxes(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.CrossServerConnectionPolicy.Apply(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.ExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, Boolean unifiedLogon, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout,
TimeSpan callTimeout, Byte[] tenantHint)
   at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, ClientIdentityInfo
clientIdentity, String applicationId, Byte[] tenantPartitionHint, Boolean unifiedLogon)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore, Boolean unifiedSession)
Request information:
    Request URL:
https://localhost:444/owa/proxylogon.owa
    Request path: /owa/proxylogon.owa
    User host address: 127.0.0.1
    User: LORAN3\SM_ae42d22c64ff48a5a
    Is authenticated: True
    Authentication Type: Kerberos
    Thread account name: NT AUTHORITY\SYSTEM
Thread information:
    Thread ID: 39
    Thread account name: NT AUTHORITY\SYSTEM
    Is impersonating: False
    Stack trace:    at Microsoft.Mapi.CrossServerDiagnostics.BlockCrossServerCall(ExRpcConnectionInfo connectionInfo, String mailboxDescription)
   at Microsoft.Mapi.CrossServerConnectionPolicy.CheckAndBlockMonitoringMailboxes(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.CrossServerConnectionPolicy.Apply(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.ExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, Boolean unifiedLogon, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout,
TimeSpan callTimeout, Byte[] tenantHint)
   at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, ClientIdentityInfo
clientIdentity, String applicationId, Byte[] tenantPartitionHint, Boolean unifiedLogon)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore, Boolean unifiedSession)
Custom event details:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="ASP.NET 4.0.30319.0" />
    <EventID Qualifiers="32768">1309</EventID>
    <Level>3</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-14T06:46:26.000000000Z" />
    <EventRecordID>115079</EventRecordID>
    <Channel>Application</Channel>
    <Computer>exch01.loran3.net</Computer>
    <Security />
</System>
<EventData>
    <Data>3005</Data>
    <Data>An unhandled exception has occurred.</Data>
    <Data>3/14/2014 12:46:26 AM</Data>
    <Data>3/14/2014 6:46:26 AM</Data>
    <Data>7741cd563e154a14a0ba52343b4e30ee</Data>
    <Data>328</Data>
    <Data>87</Data>
    <Data>0</Data>
    <Data>/LM/W3SVC/2/ROOT/owa-1-130392504882416692</Data>
    <Data>Full</Data>
    <Data>/owa</Data>
    <Data>C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\</Data>
    <Data>EXCH01</Data>
    <Data>
    </Data>
    <Data>8756</Data>
    <Data>w3wp.exe</Data>
    <Data>NT AUTHORITY\SYSTEM</Data>
    <Data>MapiExceptionIllegalCrossServerConnection</Data>
    <Data>MapiExceptionIllegalCrossServerConnection: Monitoring mailbox [] with application ID [Client=OWA] is not allowed to make cross-server calls from [EXCH01.loran3.net] to [EXCH03.loran3.net]
   at Microsoft.Mapi.CrossServerDiagnostics.BlockCrossServerCall(ExRpcConnectionInfo connectionInfo, String mailboxDescription)
   at Microsoft.Mapi.CrossServerConnectionPolicy.CheckAndBlockMonitoringMailboxes(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.CrossServerConnectionPolicy.Apply(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.ExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, Boolean unifiedLogon, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout,
TimeSpan callTimeout, Byte[] tenantHint)
   at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, ClientIdentityInfo
clientIdentity, String applicationId, Byte[] tenantPartitionHint, Boolean unifiedLogon)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore, Boolean unifiedSession)
</Data>
    <Data>https://localhost:444/owa/proxylogon.owa</Data>
    <Data>/owa/proxylogon.owa</Data>
    <Data>127.0.0.1</Data>
    <Data>LORAN3\SM_ae42d22c64ff48a5a</Data>
    <Data>True</Data>
    <Data>Kerberos</Data>
    <Data>NT AUTHORITY\SYSTEM</Data>
    <Data>39</Data>
    <Data>NT AUTHORITY\SYSTEM</Data>
    <Data>False</Data>
    <Data>   at Microsoft.Mapi.CrossServerDiagnostics.BlockCrossServerCall(ExRpcConnectionInfo connectionInfo, String mailboxDescription)
   at Microsoft.Mapi.CrossServerConnectionPolicy.CheckAndBlockMonitoringMailboxes(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.CrossServerConnectionPolicy.Apply(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.ExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, Boolean unifiedLogon, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout,
TimeSpan callTimeout, Byte[] tenantHint)
   at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, ClientIdentityInfo
clientIdentity, String applicationId, Byte[] tenantPartitionHint, Boolean unifiedLogon)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore, Boolean unifiedSession)
</Data>
</EventData>
</Event>

Thanks
I have three servers exch01,exch02,and exch03. All three have both CAS and mailbox server roles.   This problem does not occur using firefox (OWA and ECP are available) but the problem occurs with IE 11 and safari (ECP
work, OWA dos not) I have tried this from different machines and different users. I have cleared the browser's cache and have even reloaded the client machines. The problem occurs across all three exchange servers.
I have used iis manager to confirm the binding are correct. (works on Firefox)
From the local server , If I browse to
https://localhost/ecp I get my ecp page.   If I browse to
https://localhost/owaI get the something went wrong page (X-OWA-Error: ClientError;exMsg='_u' is undefined;file=ReferenceError: '_u' is undefined)
If I try to browse to https://localhost:444/owa/proxylogon.owa I get the error page "this page cannot be displayed"
I confirmed port 444 bindings are correct

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

OWA SSO issues in Exchange 2013 - 2007 co-existence

This may not be possible. For a multitude of reasons the client needs OWA authentication of Windows Integrated and Basic. As a result I''ve got a double prompt for users still on 2007 for OWA externally.
Do you have to use Forms Based Authentication to get SSO to work? Is it possible to enable FBA as well as basic and Windows auth?

FBA is required on the source and destination, yes. You would need to enable that and not use Basic or Windows Auth.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
CAS2013 in Site1 will authenticate the user, do a service discovery, and determine that the mailbox is located within the local AD site on an Exchange 2007 Mailbox server.
CAS2013 will initiate a single sign-on silent redirect (assumes FBA is enabled on source and target) to
legacy.contoso.com. CAS2007 will then facilitate the request and retrieve the necessary data from the Exchange 2007 Mailbox server.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

OWA/ECP Custom Theme Exchange 2013

Hello,
I've read numerous posts on customizing OWA themes and currently have them in place in my 2010 Exchange environment. I've also used them in 2007 Exchange infrastructures. I've been trying to roll out a similar design in my lab before we go live
with our 2013 migration but I have a few questions. I've read the tech net article (http://technet.microsoft.com/en-us/library/bb201700%28v=exchg.150%29.aspx)
and found no issues with it. Everything works as it should. However, in my current 2010 environment, the paths to the image files are slightly different than they are in 2013.
The biggest problem is that I have to place the headerbgmain.png and headerbgright.png in the ECP folder (Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp\version\Themes\Default) in addition to the OWA folder (Program Files\Microsoft\Exchange
Server\V14\ClientAccess\Owa\version\themes\default). If I don't do this, the header and the OWA logo won't match when switching between OWA and ECP. So this has worked since the 2010 release of Exchange. Not certain if this is supported or
not.
Moving forward, how do I ensure that the two image files get propogated between OWA and ECP without a disconnect as the file path no longer exists for ECP and there is no documentation on how to go about doing this? I've got the OWA part working
without any issues in 2010. Just not certain how to go about it in my 2013 lab and would like to know before I can go ahead with the migration. Thanks for any help!

Hi,
Please refer to the following article :
How to Customize the Outlook Web App (OWA)Sign-In page in Exchange 2013
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.
Best regards,
Niko Cheng
TechNet Community Support

Use Exchange 2010 OWA Login Page with Exchange 2013

We are planning on upgrading our exchange server from 2010 to 2013. We want to keep 2010 OWA login page with this upgrade. Partly due to educating users to new OWA interface and no plan to upgrade to office 2013 anytime soon.
Questions:
1. Do you or do you not recommend?
2. Is it possible?
3. How to keep 2010 OWA login page during and after migration to 2013 (instructions)?
Thank you!

Hi, EthenLEC
I agree with Andy David.
For additional information, we can change OWA 2013 back to OWA 2010 interface to use light version by the following steps.
Log in to OWA 2013.
Once logged in, click on the settings gear in the upper right corner, choose
Display Settings.
From the Display settings menu, choose Outlook Web App version, then check the box to use the light version.
Sign out of OWA and sign back in. Now it has the OWA 2013 light version.
Best Regards.

Redirect emails in OWA and Outlook 2010 not working in Exchange 2013

I have an new install of Exchange 2013 with all updates.
When I setup an inbox rule to redirect messages to another contact it is not working.
When I used Outlook 2010 and ran the rule manually I received this error:
"the redirect action is not currently supported with run rules now"
It seems that I didn't setup up something correctly in Exchange 2013 or a feature is not turned on. Please assist.
In the EM console when I setup forwarding that is working. Its the inbox rule redirect not working.

Hi,
From your description, I recommend you use the following cmdlet to ensure that the DeliverToMailboxAndForward parameter is set to $True.
Get-Mailbox <identity> | fl DeliverToMailboxandForward
If this parameter is false, you can use the Set-Mailbox cmdlet to set it and check the result.
Hope this can be helpful to you.
Best regards,
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]
Amy Wang
TechNet Community Support

Exchange 2013 Public Folder Migration Problem

Hi All,
Wonder if any of you can assist with a public folder issue I am having with Exchange 2013. We have migrated from Exchange 2010 to 2013.
I have followed the guide for public folder migration here
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
Everything went fine and as per the document - except I had to use the "largeitemlimit" parameter to get the public folder migration to complete.
We tested the public folder migration by adding content to public folders and creating public folders and it all appeared to be OK, we completed the migration and removed our old public folder databases from Exchange 2010.
However we noticed later that users cannot CREATE folders in SOME public folders. It appears from some testing that any folder that does not lie in the first public folder mailbox, end users cannot create public folders. Administrators can create them
fine from the ECP - just not from outlook.
It also appears some users cannot see some folders that they have permissions to.
Can anyone assist with some ideas to resolve ?
Thanks.

Question?
Are you able to create the Folder in OWA?
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
www.exchangeranger.com
Twitter:
   LinkedIn:
Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
it is not functionally possible to create Public Folders in OWA user interface in Exchange 2013!.... From admin ECP it works fine!
My Bad, that's what I was trying to say.
Testing the same thing in the LAB, should have some update tomorrow morning.
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
www.exchangeranger.com
Twitter:
LinkedIn:
Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 CU1 Outlook Web App LogOff with Basic or Windows Integrated Authentication

Hi all,
Exchange 2013 CU1 has a new OWA LogOff behaviour when Basic or Windows Integrated Authentication is configured. When clicking the LogOff Button you receive the message "Close All your Browser Windows.." but OWA does not sign out. This is not the
case when using Formbased Authentication...
The problem in our case is the OWA publishing over the Internet via TMG. When publishing via TMG, only Basic and NTLM authentication is supported. This means you have to change the Authentication for the OWA Virtual Directory to basic or Windows Integrated.
OK so far, now we can use the TMG Authentication Form. but... TMG is not able to Catch the OWA LogOff. So we will still receive "Close all your Browser Settings.." and no log out from OWA.
It is a known issue that TMG cannot catch the OWA Logoff with the Exchange 2013 CU1 Release..So my Question:
Does anyone get that "Real LogOut" fixed via TMG or directly on the CAS Server for Exchange 2013 CU1?
I know another possibility is to activate Form Based Authentication on the CAS Servers and external users directly authenticate against the CAS Server without pre-authentication at TMG Level, but this of course does not provide the highest security
we can have.

Hi SLShare,
As far as I know, if there is no TMG involved, with Exchange 2013 when the user signs out of mail, the authentication tokens are cleared and the user will be presented with the
Login Screen. There will not be a need to click on "Close Window" or any other pop ups that may appear.
Therefore, you may ask the TMG forum about this question and see whether there are still some other workaround we can temporary bypass this issue. For your convenience:
Forefront TMG and ISA Server Forum - TechNet - Microsoft
http://social.technet.microsoft.com/Forums/forefront/en-US/home?forum=Forefrontedgegeneral
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2010/2013 coexistence: OWA proxy not working properly ":-( Something went wrong"

Hi
Exchange 2010 users are NOT able to connect to their mailboxes when they go through exchange 2013 OWA address. We get a message that says following ---> "Something went wrong"
Following is our URL. The address is pointing to 2013 CAS loadbalancer VIP. Outlook anywhere is working fine. What is going on?
Important: All my exchange 2010 / 2013 URIs are the same as suggested by Microsoft (Owa, ecp, activesync, ews, autodiscover): --> mail.domain.com/XXX

Hello Rawa,
Can you log on Exchange 2010 OWA using its localhost address?
Please make sure the intenralurl value is set to Exchange 2010’s local host name and set the Externalurl to Null.
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).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

OWA Exchange 2013: Something went wrong error

Getting this error on event log for owa. when we log in to owa, error shows :"something went wrong" 500
tried to recreated owa virtua directories and webconfig file but same issue, please help.
Event code: 3008
Event message: A configuration error has occurred.
Event time: 15/9/2014 11:05:36 PM
Event time (UTC): 15/9/2014 3:05:36 PM
Event ID: ec79c7b2c1ef4b95adbb445c80939fc4
Event sequence: 1
Event occurrence: 1
Event detail code: 0
Application information:
    Application domain: /LM/W3SVC/2/ROOT/owa-45-130552671349946251
    Trust level: Full
    Application Virtual Path: /owa
    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\
    Machine name: LBVSMX01
Process information:
    Process ID: 17484
    Process name: w3wp.exe
    Account name: NT AUTHORITY\SYSTEM
Exception information:
    Exception type: ConfigurationErrorsException
    Exception message: Could not load file or assembly 'Microsoft.Exchange.Flighting, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (C:\Program Files\Microsoft\Exchange
Server\V15\ClientAccess\Owa\web.config line 117)
   at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
   at System.Web.Configuration.AssemblyInfo.get_AssemblyInternal()
   at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig)
   at System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded)
   at System.Web.Compilation.BuildManager.ExecutePreAppStart()
   at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)
Could not load file or assembly 'Microsoft.Exchange.Flighting, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection,
Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection,
Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
   at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(String assemblyString)
   at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
Request information:
    Request URL: https://localhost:444/owa/exhealth.check
    Request path: /owa/exhealth.check
    User host address: ::1
    User:
    Is authenticated: False
    Authentication Type:
    Thread account name: NT AUTHORITY\SYSTEM
Thread information:
    Thread ID: 42
    Thread account name: NT AUTHORITY\SYSTEM
    Is impersonating: False
    Stack trace:    at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
   at System.Web.Configuration.AssemblyInfo.get_AssemblyInternal()
   at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig)
   at System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded)
   at System.Web.Compilation.BuildManager.ExecutePreAppStart()
   at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)
Custom event details:


no they are not shared mailboxes.
here are the logs.
Not sure if this will make any difference, but there are 2 domains on exchange one is mail.domain1.com and another is webmail.domain.com
we have added another owa virtual directory for the second domain when we were having issues but i think since we are having a problem on the first domain owa, the second one will have the same.
just wondering why ecp can still work when owa doesnt. outlook clients can connect and so are phones.
#Software: Microsoft Internet Information Services 8.5
#Version: 1.0
#Date: 2014-09-15 10:10:56
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken
2014-09-15 10:10:56 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 1531
2014-09-15 10:10:56 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
2014-09-15 10:11:02 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.70 Microsoft+BITS/7.5 - 404 0 2 249
2014-09-15 10:11:15 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 62
2014-09-15 10:11:15 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
2014-09-15 10:11:15 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
2014-09-15 10:11:15 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 0
2014-09-15 10:11:26 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 14
2014-09-15 10:11:26 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
2014-09-15 10:11:26 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
2014-09-15 10:11:26 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 0
2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.70 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.70 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.70 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.70 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
2014-09-15 10:11:51 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
2014-09-15 10:11:51 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.80 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.80 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.80 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
2014-09-15 10:11:51 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.80 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:11:53 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.84 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:11:53 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.84 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:11:53 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.84 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:11:53 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.84 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:12:31 192.168.1.44 GET /owa &ActID=d0e541bb-2726-473a-9891-74afd643bd53&CorrelationID=<empty> 443 - 192.168.1.17 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+rv:30.0)+Gecko/20100101+Firefox/30.0 - 401 2 5 22905
2014-09-15 10:13:08 192.168.1.44 GET /ecp/ - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 400 0 0 10240
2014-09-15 10:13:28 192.168.1.44 POST /Microsoft-Server-ActiveSync User=andrew.solis2&DeviceId=ApplC38LTUR3FRC5&DeviceType=iPhone&Cmd=Ping 443 - 172.16.0.33 Apple-iPhone6C2/1102.55400001 - 404 0 2 0
2014-09-15 10:13:31 192.168.1.44 GET /ecp/ - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 400 0 0 15
2014-09-15 10:13:38 192.168.1.44 GET /ecp/ - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 400 0 0 15
2014-09-15 10:13:40 192.168.1.44 GET /ecp/ - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 400 0 0 15
2014-09-15 10:13:40 192.168.1.44 GET /ecp/15.0.995.28/themes/default/clear1x1.gif - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko https://webmail.domain.com.sg/ecp/ 400 0 0 78
2014-09-15 10:13:40 192.168.1.44 GET /ecp/15.0.995.28/themes/default/main_default.css - 443 - 192.168.0.6 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko https://webmail.domain.com.sg/ecp/ 400 0 0 109
2014-09-15 10:15:51 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.76 Microsoft+BITS/7.5 - 404 0 2 218
2014-09-15 10:15:55 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:15:55 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:15:55 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:15:55 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
2014-09-15 10:16:26 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.70 Microsoft+BITS/7.5 - 404 0 2 203
2014-09-15 10:16:44 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.70 Microsoft+BITS/7.5 - 404 0 2 218
2014-09-15 10:16:56 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
2014-09-15 10:16:56 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.75 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
2014-09-15 10:17:07 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.70 Microsoft+BITS/7.5 - 404 0 2 218
2014-09-15 10:17:38 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.97 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6425;+Pro) - 404 0 2 0
2014-09-15 10:17:38 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.97 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6425;+Pro) - 404 0 2 0
2014-09-15 10:18:48 192.168.1.44 GET /owa &ActID=5c208db7-3a44-43d0-b5d8-24f107542a81&CorrelationID=<empty> 443 - 192.168.1.44 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko - 401 2 5 0
2014-09-15 10:20:51 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
2014-09-15 10:20:51 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
2014-09-15 10:20:52 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 31
2014-09-15 10:20:52 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
2014-09-15 10:20:52 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 15
2014-09-15 10:20:52 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.147 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro) - 404 0 0 0
2014-09-15 10:21:19 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.107 Microsoft+BITS/7.5 - 404 0 2 218
2014-09-15 10:25:04 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.190 Microsoft+BITS/7.5 - 404 0 2 218
2014-09-15 10:25:22 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.190 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:25:22 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.190 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:25:22 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.190 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
2014-09-15 10:25:22 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.190 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:25:40 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.190 Microsoft+BITS/7.5 - 404 0 2 203
2014-09-15 10:25:54 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 0
2014-09-15 10:25:54 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.76 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 2 15
2014-09-15 10:27:16 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.65 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6213;+Pro) - 404 0 2 15
2014-09-15 10:27:22 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.65 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6213;+Pro) - 404 0 2 15
2014-09-15 10:27:25 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.65 Microsoft+Office/12.0+(Windows+NT+6.0;+Microsoft+Office+Outlook+12.0.6213;+Pro) - 404 0 2 15
2014-09-15 10:28:22 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.81 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.6023;+Pro) - 404 0 2 15
2014-09-15 10:28:41 192.168.1.44 POST /Autodiscover/Autodiscover.xml - 443 - 172.17.0.81 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.6023;+Pro) - 404 0 2 15
2014-09-15 10:29:20 192.168.1.44 HEAD /OAB/391e4f87-9e04-4176-aa12-bb90e3d8596c/oab.xml - 443 - 172.17.0.107 Microsoft+BITS/7.5 - 404 0 2 203
2014-09-15 10:29:45 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.107 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:29:45 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.107 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:29:45 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.107 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 15
2014-09-15 10:29:45 192.168.1.44 POST /EWS/Exchange.asmx - 443 - 172.17.0.107 Microsoft+Office/12.0+(Windows+NT+6.1;+Microsoft+Office+Outlook+12.0.6683;+Pro) - 404 0 0 0
2014-09-15 10:31:40 192.168.1.44 GET /owa/ &ActID=cdc5aa77-7e17-4a56-83ed-2e7047c12c5b&CorrelationID=<empty> 443 - 172.17.0.198 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/37.0.2062.120+Safari/537.36
https://webmail.domain.com.sg/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2fwebmail.domain.com.sg%2fowa 401 2 5 16
2014-09-15 10:32:00 192.168.1.44 GET / - 80 - 172.17.0.198 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/37.0.2062.120+Safari/537.36 - 200 0 0 31
2014-09-15 10:32:00 192.168.1.44 GET /iis-85.png - 80 - 172.17.0.198 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/37.0.2062.120+Safari/537.36 http://webmail.domain.com/ 200 0 0 265

2013 OWA - Open Another Mailbox, :-( something went wrong, Error 500

Our client is experiencing an issue where they are not able to open another mailbox even if the user has full access to the account under mailbox delegation. The user would click on the 'Open Another Mailbox" and they receive the following error
something went wrong
The URL shows the following:
https://domain.com/owa/auth/errorfe.aspx?httpCode=500
The problem I have is similar to the following post but my client is also behind a UAG 2010 server, and I cannot change to forms based authentication.
http://social.technet.microsoft.com/Forums/exchange/en-US/9345d396-b5a6-4d26-a498-7d1539f85d13/exchange-2013-owa-http-500-error-when-opening-another-mailbox?forum=exchangesvrclients
The error within the IIS OWA logs shows as follows.
2014-02-04 17:48:04 10.100.2.10 GET /owa/auth/errorfe.aspx httpCode=500&cafeReqId=f9be7757-b123-4ce1-a585-b9c4ef45cd4b; 443 - 10.100.2.42 Mozilla/5.0+(compatible;+MSIE+10.0;+Windows+NT+6.2;+WOW64;+Trident/6.0)
https://domain.com/owa/[email protected]/?offline=disabled 200 0 0 0
I'm running out of ideas on what could be the issue and but our users will need to manage other mailboxes pretty soon.
Edit: I should also add that the permissions are correct as the user can connect to the target mailbox via Outlook 2013.

Hi Bryan
It should be happening for most of the mailboxes since we ran into similar kind of problem recently
There could be 2 reasons for not happening
IIS Settings not configured properly
Permission issues
Check SSL Settings on DWS and ensure Ignore Client Certificates is selected
Also remove SSL from DWS for HTTP to HTTPS Redirect
Check the permission under ADUC
Check if Exchange Server Object is member of tab of Domain Admins if so remove them. Also remove Exchange Organization Administrators and Exchange Servers group from Organization Management if they are added
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
Regards,
Sathish

Can't get OWA to work on Essentials 2012 R2 with Exchange 2013 on second server 2012 R2 std.

I have previously with success setup a working solution with server 2012 essentials, and a second server 2012 std. with exchange 2013, I did it following this guide: http://technet.microsoft.com/en-us/library/jj200172.aspx
Unfortunately I lost the server due to a cooling error which led to an un-repairable essentials 2012, since this was a new setup and also a test setup I didn't have any working backup solution setup at the time...tsk.tsk.
Since I had to make a complete do over I chose to try out the new R2 server editions, and set it up following the same guide, when it came to this part:
Download KB2732764 for ARR 2.5, and then install the update on the server that is running Windows Server 2012 Essentials.
Copy the SSL certificate file for Exchange Server to the server that is running Windows Server 2012 Essentials. The certificate file must contain the private key, and it must be in the PFX file format.
Note
If you are using a self-issued certificate, follow the instruction in the Exchange Server article Export an Exchange Certificate to export the certificate.
Open a command window as an administrator, and then open the %ProgramFiles%\Windows Server\Bin directory.
Based on you installation scenario, follow one of these steps to configure ARR:
If you are performing a clean setup, run the following command:
ARRConfig config –cert “path to the certificate file” –hostnames “host names for Exchange Server”
I noticed that the version of "Application request routing" had changed to version 3, so obviously I didn't need to dl the 2.5 update.. When I came to the part where I wa instructed to run arrconfig config etc. I noticed
that the ARRconfig file no longer where placed where the setup guide indicated, I then went ahead and tried som manual configuration regarding certificates and such. In the end I have a working solution where Exchange and OWA is working locally but OWA isn't
working outside my local domain, the link get's placed in the RWA and is indicating the correct link for the exchange server www.remote.clinten.dk I have a certificate which include to separate domain names aforementioned and remote.clinten.dk and
I get no errors indicating certificate errors, when I try to connect to www.remote.clinten.dk/owa from outside I get a 404 error, and when I connect to www.remote.clinten.dk I get the RWA login screen for the essentials RWA. Obviously I need to set up something
in ISS probably in the url rewrite section, but I can't seem to find the right setting.. Can someone help with this?
Btw. I have found the missing arrconfig file in c:\windows\system32\essentials" and tried to run the command as described in the guide "ARRConfig config –cert “path to the certificate file” –hostnames “host
names for Exchange Server”" but it doesn't seem to work, it just prompts with a guide for using the arrconfig command and examples of correct use, I also tried removing the "" from the guide, like this "ARRConfig
config –cert path to the certificate file –hostnames host names for Exchange Server",
when I ran it without the "" It didn't prompt me with anything nor did It indicate any errors, it did not however make my OWA work either..
I am aware that exchange 2013 atm. isn't officially supported on the R2 server, but the exchange works fine inside my domain, and the pop3/smtp also works from outside, since this Is a test environment, using only my own private domain and not a company
domain I figured it would be ok to run the risk.. ;)

Hi
found this on
https://social.technet.microsoft.com/Forums/en-US/1f099068-b3ed-44f3-a8c4-c22d760a8621/arr-broken-or-bad-syntax-exchange-2013-essentials-2012-r2?forum=winserveressentials
"Ok just an update for anyone else how has this issue.
The problem has been solved by Microsoft and I have included their findings below, but basically it comes down to a typo!
I often use notepad to have all the commands I need on hand, and I must have copied the command direct from the TechNet article or other website and customised the required fields. The issue with this is one of the characters did not “convert” - for want
of a better word. I should have retyped the whole command from scratch and it would have been right!
Thanks for everyone’s input and for Microsoft for getting to the bottom of it.
From Microsoft:
We have tested on your environment and here is the investigation result from our senior engineer:
================================================================
Basically the command fails due to invalid parameter, the invalid one is the ‘-‘. I think the one customer used is copied from the online document sample which translate to the unicode is 0x8211 means “en dash”, it
can’t be input by normal keyboard, so I pretty sure it is from web (mostly HTML document).
The one we check (compare) is ‘-‘ which has the code 0x45.
So it always failed to compare the parameter and ARRconfig.exe thought it is invalid parameter.
The solution is quite simple, just using keyboard to retype the command, using normal ‘-‘ and I have tried the password prompt shows
Best Regards,
Johnny Chen
Microsoft Partner Support Community Technical Support Engineer
Microsoft Global Partner Services"

OWA Exchange 2013 SP1 Security Update KB3011140 December 2014

After performing this update on our server, I noticed now users can no longer recover items from deleted items in OWA. The page always errors out now.
The KB installed was KB3011140
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.
X-OWA-Error: ClientError;exMsg=Sys.ArgumentException: Value does not fall within the expected range.Parameter name: Unknown type _d.$Vq was requested;file=$7CD@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.1.mouse.js:1:1170608_t.PopoutStartupViewModelFactory.prototype.$E/<@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.1.mouse.js:1:1171022_a.$Z0.prototype.$5V3/<@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:294125_a.$2r.$5e5@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:601482_a.$2r.$iS@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:600669_a.$Sd.$9lW@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:369272$1mX@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:27237$4pt@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:27789_js.$J.prototype.$6Kk@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:32733Function.createDelegate/<@https://whatever.com/OWA/prem/15.0.847.34/scripts/preboot.js:34:39109_a.$2r.$5e5@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:601482_a.$2r.$iS@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:600669_a.$Sd.$9lW@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:369272$1mX@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:27237$2gl/s@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:28216:1170608
X-OWA-Version: 15.0.847.34
X-FEServer: SERVERNAME
X-BEServer: null
Date: 1/2/1601 3:22:42 PM

Hi,
From the above description, "Something went wrong" error shows an incorrect date. The date information is calculated based on the date of the Exchange server to which the user is connected. In some scenarios, such as network connectivity failure,
the Outlook Web App client-side script is unable to connect to the server to obtain the correct date. When this occurs, a generic "1/2/1601" date is used. In order to resolve this issue, you need to install the Cumulative Update 6 for Exchange
Server 2013.
For more information, here is a KB for your reference.
"Something went wrong" error in Outlook Web App may show an incorrect date
https://support.microsoft.com/kb/2961715?wa=wsignin1.0
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Outlook 2013 something went wrong sorry we ran into a problem

my outlook started hanging and causing problems a few days ago where sent messages were sitting in outbox without sending. and when you closed and reopened outlook the messages has vanished completely without sending. I'm unable to get outlook
to open. I keep getting the message something went wrong sorry we ran into a problem. All other office 2013 programs will function correctly. I have also tried to open the control panel/mail (outlook 2013) (32 bit) icon, but this pauses
for a while and then brings up no window to configure an account. I managed to get my exchange account set up in the mail app but I'm not interested in using the mail app when i should be able to utilize all the functionality of outlook.
I have spent a couple days reading all the posts and tried uninstalling office 2013 pro and the mail app thinking i'd clean install the 64-bit version of office but to no avail. Looks like the preloaded office 13 cannot be uninstalled, so I then
downloaded the O15CTRRemove tool which worked in removing office 2013, but did not fix the problem of outlook not opening. This is driving me crazy and I have tried many suggestions from the online forums, and have got outlook to open a couple of times where
it was then asking for a product key, and when the key was entered outlook would close straight away and not allow it to open again. I have tried running the repair tool many times, and this does not work. Every other program I have had zero issues with; autocad,
adobe suite, everything runs perfect. I just want to get my outlook all set up.Please advise!

Hi,
Please check whether you can send message in OWA. If there is no issue in OWA, it should be an Outlook issue. It seems that there is just one user encontered this issue in your environment. If so, please start Outlook in safe mode by using "Outlook /safe"
in Run windows to check whether the issue persists. If it fails, please change a computer to try again.
Thanks,
Winnie Liang
TechNet Community Support

OWA :( something went wromg -exchange 2013

Similar Messages

Maybe you are looking for