Exchange 2013 + 2007 OWA coexistance not redirecting properly (HTTP 400)

Hello. I am using this document to funnel our new Exchange 2013 external traffic through an IIS ARR reverse proxy, much like we already do for MIcrosoft
Lync 2013 on this machine.
http://blogs.technet.com/b/exchange/archive/2013/08/02/part-2-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx
I followed this guide to a T. especially the part on the page 2 that I linked above about creating the legacy.domain.com server farm and URL rewrite rule. This
IIS ARR proxy seems to work fine for Outlook Anywhere, ActiveSync, OWA if the user's mailbox is on the Exchange 2013 server, but it does not work if an OWA user logs in with a mailbox on 2007.
When the user has a mailbox on 2007, after logging into OWA they get HTTP 400 error. The URL bar in the browser is changed to https://legacy.domain.com/owa/auth/owaauth.dll
The Exchange 2007 server IIS logs show this:
70.x.x.x, -, 11/1/2014, 9:45:48, W3SVC1, MAIL, 10.1.1.3, 0, 523, 132, 400, 0, POST, /owa/auth/owaauth.dll, -,
I can't figure out why this is happening. DNS is correct. legacy.domain.com points to the 2007 Exchange server. webm.domain.com points to the
Exchange 2013 server.
Any ideas?

Doing more testing, I almost think the Exchange 2007 server keeps redirecting. So the HTTP 400 is because when you hit legacy.domain.com, it redirects
to webm.domain.com which redirects back to legacy.domain.com and vice versa.
I put a test.txt file in the Exchange 2007 owa virtual directory and I cannot access it in any browser. I tried https://legacy.domain.com/owa/test.txt and
It redirects me to https://webm.domain.com(Exchange 2013). I can however go
one level (or more) deep on the legacy server and get a file such as https://legacy.doamin.com/owa/8.3.342.1/themes/base/logon.css and
in the browser I see the code (both externally AND internally, so I know DNS and firewall is working).
I can't find anywhere on IIS 6.0 on the Exchange 2007 server where any kind of redirection is taking place though. Virtual Directory properies for owa say
"A directory located on this computer: "C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa" Enable default content page is checked with default.aspx but I looked at default.aspx in notepad and I don't see ANY code telling it to
redirect.
In Exchange 2007 management console OWA internal URL and External URL both sayhttps://legacy.domain.com/owa .
I have no idea what is causing this redirection. I did an iisreset and also recycled the OwaAppPool and no change.

Similar Messages

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

Exchange 2013 with CU3 and silent redirection to different AD site

After updating
Exchange 2013 CU2 to Exchange 2013 CU3, OWA silent site redirection feature become not available. The customer has two Exchange 2013 sites. Before we updated to CU3, user whose mailbox located on site A, could be automatically redirected to OWA on
site A, after he logged on to OWA on site B. IE gives Error page and bring out link to the OWA page on site A. Here is screenshot about issue workaround.
Hopefully someone will help with some hint because it is quite anoying.
All other stuff works good, Outlook anywhere, autodiscover, only this remained.
Thanks in advance,
Fajar

Hi Angela,
According to your description, OWA request cannot be automatically redirected after upgrade.
YESS after upgrade Exchange 2013 CU2 to CU3. CU2 not problem.
1. Will OWA work well if you manually click the OWA URL in the web page?
If i click manual, OWA Url in web page, OWA work well...
PS Command "Get-OWAVirtualDirectory | fl CrossSiteRedirectType"
ONLY HAVE ON EXCHANGE 2010 NOT ON EXCHANGE 2013.
2. Do you can login OWA in site A?
My Mailbox on Site-A, if i login OWA Site A (owa-A.domain.com), OWA work well & i can access my email.
But... if i login from OWA Site-B (owa-B.domain.com), OWA not automatic silent redirect to Site-A, and i must click link below "Use following link to open to mailbox with the best performance https://owa-a.domain.com/owa/auth.owa
My friend Mailbox on Site-B, if he login to OWA Site B (owa-B.domain.com), OWA-B work well & he can access email.
But.. if he login from OWA Site-A (owa-A.domain.com), OWA not automatic silent redirection to Site-B, and he must click link below "Use following link to open to mailbox with the best performance https://owa-b.domain.com/owa/auth.owa
3. Check the IIS log on site B CAS server and find if there is any error about the redirection.
whether there is a bug in CU3?
Hopefully someone will help with some hint because it is quite anoying on our custommer.
Regards,
Fajar

Exchange 2013/2007 coexistence: The Name on the Security Certificate is Invalid or Does Not Match the Name of the Site.

In the midst of Exchange 2013/2007 coexistence configuration.
Currently:
Exchange 2007:
2 CAS\HUB
1 Mailbox server
Exchange 2013 (2 sites):
LA:
1 CAS
2 MBX servers
MKE:
1 CAS
2 MBX servers.
We purchased a certificate from Digicert and added every SAN name we could think of including "legacy.companyname.com", just to be sure. Added certificate to Exchange 2013 CAS servers and 2007 CAS\HUB boxes. Configured virtual directories on Exchange
2013 MKE-CAS01 but not on Exchange 2013 LA-CAS01. Configured virtual directories to on Exchange 2007 CAS\HUB to point to "legacy.companyname.com".
Mailboxes have not been moved yet. I just wanted to get the coexistence between Exchange 2013/2007 up first but some users (not all) receiving
"The name of the security certificate is invalid or does not match the name of the site" for
"LEGACY.COMPANYNAME.COM". I remember configuring the AUTODISCOVER virtual directory for Exchange 2007. Any ideas? Thank you.

Hi,
Please make sure that the certificate with "legacy.companyname.com" name is enabled for IIS service. We can check it by running the following command in Exchange server 2007:
Get-ExchangeCertificate | FL
Thanks,
Winnie Liang
TechNet Community Support

RPC over HTTP trouble Exchange 2013/2007 coexistence, 2013 RPCProxy cannot ping GC.

I currently have an Exchange 2013/2007 coexistence scenario which gives me trouble with the RPC over HTTP part with users with a 2007 mailbox. the MS RCA website performs 2 tests with the MAPI address book endpoints, once against a 2007 mailbox server and
once a against a GC/DC, the last one fails. The logs are from our test domain, but the exact same happens in the production domain. running CU8 (recently upgraded, but problem was exactly the same with CU7)
Testing the MAPI Address Book endpoint on the Exchange server.
The address book endpoint was tested successfully.
Additional Details
Elapsed Time: 7872 ms.
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity: exmb11.domain.test:6004.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 156 ms.
Elapsed Time: 4153 ms.
Testing the MAPI Address Book endpoint on the Exchange server.
An error occurred while testing the address book endpoint.
Additional Details
Elapsed Time: 3079 ms.
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity: tdc01421.domain.test:6004.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl09_ctl00_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 3079 ms.
texmb11 = ex2007 mailbox
texfr11 = ex2007 CAS
tdc01421 = DC/GC
texch31 = 2013 multirole
other symptoms :
Browser test
https://texch31.domain.test/rpc/rpcproxy.dll?texmb11:6004
--> 503 (which is correct)
https://texch31.domain.test/rpc/rpcproxy.dll?tdc01421:6004
--> 404.0 Not Found
RPCPing
rpcping -t ncacn_http -s texmb11 -o RpcProxy=texch31.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success
rpcping -t ncacn_http -s tdc01421 -o RpcProxy=texch31.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Fails!
so the Ex2013 RPCProxy doesn't proxy to the DC/GC, but the RPCProxy to an ex2007 mailbox server works fine, so the authentication methods configured are correct i'd say..
the same tests using the ex2007CAS server as RPC proxy all succeed!:
MS RCA is all green
https://texfr11.domain.test/rpc/rpcproxy.dll?texmb11:6004
--> 503
https://texfr11.domain.test/rpc/rpcproxy.dll?tdc01421:6004
--> 503
rpcping -t ncacn_http -s texmb11 -o RpcProxy=texfr11.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success
rpcping -t ncacn_http -s tdc01421 -o RpcProxy=texfr11.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success!!
Logs
all tries against the 2013 CAS server generate '404' log entries in several logs int the Logging directory, the most explicit being the one in Program Files\Microsoft\Exchange Server\V15\Logging\HttpProxy\RpcHttp : HttpProxy_xxxxxx.LOG
2015-04-30T19:58:00.153Z,895cdf07-f2eb-4beb-b787-da02ba11b0c2,15,0,1076,0,,RpcHttp,webmail.domain.test,/rpc/rpcproxy.dll,,Basic,true,DOM\user,,,MSRPC,10.10.142.132,TEXCH31,404,,MailboxGuidWithDomainNotFound,RPC_IN_DATA,,,,,,,,,4,,,,1,,,0,,0,,0,0,,0,2,0,,,,,,,,,1,1,0,,1,,2,2,,?TDC01422.domain.test:6004,,BeginRequest=2015-04-30T19:58:00.153Z;CorrelationID=<empty>;ProxyState-Run=None;ProxyState-Complete=CalculateBackEnd;EndRequest=2015-04-30T19:58:00.153Z;,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:
RPC server name passed in by client could not be resolved: TDC01422.domain.test at Microsoft.Exchange.HttpProxy.RpcHttpProxyRequestHandler.ResolveToDefaultAnchorMailbox(String originalRpcServerName String reason) at
Microsoft.Exchange.HttpProxy.RpcHttpProxyRequestHandler.ResolveAnchorMailbox() at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalBeginCalculateTargetBackEnd(AnchorMailbox& anchorMailbox) at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<BeginCalculateTargetBackEnd>b__3b();
the error suggests the name could not be resolved. but nslookup works fine. i can ping the tdc01421 correctly form texch31, it returns me the ipv4 address. i can telnet to port 6004 from texch31 server to tdc01421 giving me the correct 'ncacn_http' answer..
i look at the 'ValidPorts' and ValidPorts_Autoconfig_Exchange reg keys and filled them with the same i have on the 2007cas servers (all ex servers, all dc/gc's, all of them with netbios & fqdn ports 6001,6002 & 6004..) but also no success.
im out of ideas by now..

Hello togehter,
if anyone is using the Interim Update (Hotfix) "Exchange2013-KB2997209_2997847-x64-en.msp" please be aware of the following bug in this hotfix:
NOTE: Another issue that we have seen only from some E2013 On-Premises customers who installed
fixes for any of the above E2013 CU6 related issues is that “Using OWA, users cannot create new messages or reply to existing messages” – These are mostly installer issues where OWA files are not copying correctly in the new version directory. Ideally the
content of these two folders, i.e. “V15\ClientAccess\Owa\prem\15.0.995.31” and “V15\ClientAccess\Owa\prem\15.0.995.29” should be identical, now if for any reason, they are not then it can break the OWA experience like described above. Take these steps if you
run into related issues:
-Backup the contents of “15.0.995.31” folder to a different folder/directory
-Copy the files and folders from “15.0.995.29” to “15.0.995.31” folder – this should fix the issue …
Best,
Martin

In Exchange server 2007, is syncing notes to iOS device supported?

In Exchange server 2007, is syncing notes to iOS device supported? Specially iPhones, and iPads.
Thanks.

Hi,
Here is an article about how to set up Exchange 2007 on iPhone, iPad and iPod:
http://www.rackspace.com/knowledge_center/article/setting-up-exchange-2007-on-iphone-ipad-ipod-ios-7
When setting up, you can select the services that you wish to sync with the Exchange Server.
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.

Exchange 2013 CU2 OWA Redirection not working

Hi,
I installed Exchange 2013 RTM in existing environment with Exchange 2010 Sp3 in our test environment. After installing Exchange 2013 RTM I checked when I access OWA using Internal URl it redirected to Exchange 2010 CAS server's Internal URL and I was
able to access Exchange 2010 mailbox.
I upgraded to CU2 and now Exchange 2013 internal URl not re-directing it to Exchange 2010 mailbox anymore. I checked all the settings on virtual directories and made sure that FBA authentication is selected. It is a test environment and I just wanted
to test the re-direction in co-existence environment using Internal URL. It should work out of the box but not sure what happened. There was no issue in CU2 instllation.
Exchange 2013 CAS and mailbox roles are on separate servers. Same with Exchange 2010. There is no certificate 3rd party certificate install on CAS servers since it is a test environment.
Not sure what else can I check.
I appreciate if any help I can get.
Thanks,
Regards
Raman
Raman

I have been seeing issue where 2013 OWA was not re-directing to Exchange 2013, as mentioned on top of this thread. After spending days over it.
Finally it resolved for me after doing the following: -
Go to CAS 2010 IIS
OWA directory -> Authentication -> Windows Authentication -> Add provider
Negotiate and NTLM.
Although, now when I click on "Options" once OWA is redirected to 2010. ECP does
not work. It just open up ECP page but no link works not even sign out. I had to click back on the browser's back button go get back to main OWA mail page.
OWA and ECP directory settings are same. I have checked several times.
Thanks,
Raman

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.

Exchange 2013 - 2007 coexistence - activesync 2007 does not work correctly

Exchange 2013 SP1. On going Saga- Last night we cut over to full co-existence with DNS changes for use of legacy namespace and had to roll back again. We had only two issues but one was considered a show stopper.
The main issue was that Active Sync would not work correctly for 2007 users. It failed the exchange connectivity test and would only work on a device if the domain was entered - or if the legacy namespace was entered manually. That would have meant
chaos for several thousand users so we rolled back. (It worked perfectly for 2013 users).
The error given by the test was "foldersync failed" when I drilled down into the detail. It found autodiscover but failed after the initial handshake. (All other tests passed for 2007 and 2013 users)
We tried:
1. Populating both Autodisover internal and external urls with the legacy namespace
2. Populating only the internal url and leaving the external blank (both 1 and 2 had the same result)
3. Leaving both URLs blank to force 2013 to proxy to the 2007 cas (totally broke it- would not resolve at all)
I don't know if this is related but SSO is failing for 2007 OWA - two prompts.
Environment notes- all internal co-existence is working and the internal LTM F5's are working. Externally we use 2 GTM F5 to the LTM f5's to Ex2013. 2007 has SSL being passed through all the way to the CAS. Servers are split into CAS and MBX over 2 DC's.
Everything else externally was working when we cut over.
any and all help appreciated
Tony

Hi,
Glad to know that you have found the solution.
Thanks for your generous sharing.
Have a nice day : )
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2013 - 2007 coexistence legacy namespace issues

Got an odd config here. Exchange 2007 CCR mode co-existing with split role 2013 servers over 2 Data Centers. Each DC has its own subnet so DAG has 2 IPs. New Certificate purchased with extra legacy namespace and loaded onto ISA and F5 as well as the
exchange servers.
I can send and receive from the Exchange 2013 servers. But I'm struggling to deploy the legacy namespace
Here's where it gets ugly. The client wants to continue (short term) to put legacy.company.com through ISA2006 servers and 2013 traffic through F5 load balancers. On the f5 side the path goes through a firewall then an f5 to the mailgateway
When we cut over to legacy (dns changes etc) OWA suffered intermittent Internal 500 errors. Active sync had to be pointed to webmail to work (we had it set blank as per Steve Goodmans recommendation) and Outlook Anywhere had no connectivity.
Urls were set correctly
Outlook Anywhere -> webmail.company.com
Autodiscover -> webmail.company.com
WebServices -> legacy.company.com
OWA -> legacy.company.com
OAB -> legacy.company.com
UM -> legacy.company.com
ActiveSync -> legacy.company.com
This is our 4th attempt to get this working. We can only work in the small hours so we are all fairly tired. Pointers anyone?

Hello,
Do you mean when the user access mailbox from internet, the load balancing will not occur? If so, I recommend you check your configuration as the following article:
http://technet.microsoft.com/en-us/library/aa997148.aspx .
The user of ISA Server load balancing will eliminates the need for setting up the load balancing cluster on the exchange server CAS side.
If I have any misunderstanding, please free let me know.
Cara Chen
TechNet Community Support

Exchange 2013 CU7 OWA 400 Bad Request after successful login

Scenario:
Exchange 2007/2013 Migration
One
Exchange 2007 Server [removed]
One
Exchange 2013 Server Std, Windows 2012
All mailboxes moved to 2013
- November 27-30 2014
All public folders moved to
2013 - December 2, 2014
Exchange
2007 is still running and has not been removed from the domain, yet. [update]
Exchange
2007 removed from domain - 12-13-14
SSL
Certs are current for: Autodiscover.ExtDom.com, ex13.ExtDom.com, ex13.IntDom.com
Applied
CU6 (Dec 3, 2014) to fix Mobile access issues. Since applying CU6, OWA does not work with the exception of mobile browsers (Chrome - Nexus 7) or Safari 5.1.7 on Windows 7. These browsers get the OWA 2010 theme (Yellow).
User
logs into OWA with Domain\UserName and PWD(IE). After clicking Sign In, page returns Bad Request. No errors logged in w3scv logs.
[update]
CU7 applied 12-11-2014
All
users can connect using Outlook 2013 or Mobile (iPhone & Android)
Exchange
Admin Center (ECP) still works!
Browsers
tested: IE10 (windows 7 x64),Chrome 39.0.2171.71m, Opera 26.0, FireFox 34.0.5, Safari 5.1.7
Attempted:
https://ex13.ExtDom.com/owa
https://ex13.IntDom.com/owa
https://ex13.ExtDom.com/owa?ExchClientVer=15
https://ex13.IntDom.com/owa?ExchClientVer=15
https://localhost/owa
(on Ex 2013 server)
https://localhost/owa?ExchClientVer=15
(on Ex 2013 Server)
Fixes
attempted:
remove
| create Virtual Directories for OWA
Change
authentication through Exchange PowerShell - Integrated/Basic from FBA/Basic
reverted
since change didn’t work.
Run
UpdateCas.ps1
Run
UpdateConfigFiles.ps1
IISReset
(iisReset /NoForce fails)
OWA
(Default Web Site) displays as Version 15.0 (Build 995.29) in EAC. [update] Build 1044.25 (CU7)
Links
used for troubleshooting:
http://community.spiceworks.com/topic/514617-exchange-2013-unable-to-login-to-owa-ecp
https://social.technet.microsoft.com/Forums/ie/en-US/f8aa95d4-19e4-483c-8c4b-b039ab0d0127/400-bad-request-when-logging-in-to-owa-exchange-2013?forum=exchangesvrclients
http://tecfused.com/2013/09/23/exchange-2013-ecp-double-login-error-400/
https://social.technet.microsoft.com/Forums/lync/en-US/c25ce81c-76ea-471a-93ae-eeaf9e5015ac/exchange-2013-owa-error-400-bad-request?forum=exchangesvradmin
http://support.microsoft.com/kb/2871485/en-gb

Hi,
Does it work if you disable the FBA and only use the basic authentication?
Please also let us know the authentication settings on the Default Web site.
Thanks,
Simon Wu
TechNet Community Support

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 Server 2007 OWA users can receive email but can't send

Hi,
I have an Exchange server 2007 in an SBS 2008 environment with POP3 connector configured and working fine , smtp send mail connector configured.
Now users can connect to OWA, receive email but cant not send.
smtp connector works fine from Outlook client. Tried to track the emails from exchange server management console and I get the
SEND DELIVER SUBMIT TRANSFER.
The emails go to the sent items folder, but it never reach the recipients.
Have been troubleshooting for a while without succes. Any help will be most appreciated.
Regards
Faisal

POP3 is a single mailbox client mail retrieval protocol, not a mail transport protocol.
Any attempt to use it as a mail transport protocol is a great big kludge.
Exchange is designed to connect to the Internet using SMTP.
No version of Exchange has a POP3 connector.
I recommend that you post this in the SBS Forum: http://social.technet.microsoft.com/Forums/en/smallbusinessserver/threads
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Cross-forest access to public folders Exchange 2013-2007

Dear.
We have an Exchange 2007 org in one forest and an Exchange 2013 org in another forest.
User accounts remain in the 2007 AD, mailbox moved to Exchange 2013 in the other forest, so a linked mailbox.
What do I need to do in the Exchange 2007 public folders to give the migrated mailboxes (not migrated users) access to these public folders?
Thanks for the support.
Regards.
Peter Van Keymeulen, IT Infrastructure Solution Architect, www.edeconsulting.be

Hi Stephen,<o:p></o:p>
<o:p> </o:p>
Do you have trust between Exchange 2007 forest and Exchange 2013 forest? Please set up a trust between the two forests. Then set the public folder client permission
to see if we can access the
public folders.<o:p></o:p>
<o:p> </o:p>
If not, since Public folder cross forest migration is not supported in from an Exchange 2007/2010 forest to an exchange 2013 forest, refer to forum:
http://social.technet.microsoft.com/Forums/office/en-US/51da1b97-fbb1-4f81-87da-c3370960c4ab/crossforest-public-folder-migration?forum=exchangesvrdeploy
http://social.technet.microsoft.com/Forums/office/en-US/663f0dc3-a977-408a-93c7-94584fbefc62/public-folder-issue-cross-forest-migration-exchange-2010-to-2013?forum=exchangesvrdeploy
<o:p></o:p>
Title: Migrate Public Folders to Exchange 2013 From Previous Versions<o:p></o:p>
Link:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx<o:p></o:p>
<o:p> </o:p>
So for public folder migration,
the only supported path is cross forest 2007/2010 to 2007/2010 and then inter forest 2007/010 to 2013. Or
we can first export all the public folder to PST from the Exchange 2007 forest, then import the PST to the Exchange 2013 forest.
<o:p></o:p>
Regards, Eric Zou

Outlook 2007 - single profile connecting to Exchange 2013 / 2007 mailboxes

Hi,
I am in the early part of a migration from Exchange 2007 to Exchange 2013. So far I have 2013 installed and running in a DAG and just moved my own mailbox to the new server.
I set up a new profile in Outlook 2007 which connects to my mailbox on Exchange 2013. The problem is that I need to add additional mailboxes to my profile which are still hosted on Exchange 2007, however this is not working.
I thought at one stage I tested this and was able to get it work with a test mailbox also hosted on Exchange 2013.. but maybe I never did.
Does anyone know if this is possible at all (single Outlook profile, primary mailbox hosted on Exchange 2013 and other mailboxes on Exchange 2007). Most of our users have an additional mailbox mapped in their profile so I hope there is some way around this.
Thank you!

Hi,
It is possible to open a shared mailboxes on a legacy server.
Your problem could be caused by:
Not having one of the later CU installed (read CU4 or CU5)
Incorrect authentication methods configured (see link below)
Outlook is not at the latest patch level
Users of Exchange Server 2013 can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
http://support.microsoft.com/kb/2834139
Martina Miskovic

Exchange 2013 + 2007 OWA coexistance not redirecting properly (HTTP 400)

Similar Messages

Maybe you are looking for