OWA Exchange 2010 and 2013 Co-Existance

Hi All
I have 2 new Exchange 2013 Multi role servers in a test environment. I have setup the namespace's in the following way
Communcal OWA URL - exchange.domain.co.uk/owa
Server 2013 Boxes
OWA URL Internal and External - owa.domain.co.uk/owa
Server 2010 Boxes
OWA Internal - legacy.domain.co.uk
OWA External - legacy.domain.co.uk
Authentication on Exchange 2010 boxes is set to basic, form based.
Authentication on Exchange 2013 boxes is set to basic and form based.
When users hit are exchange.domain.co.uk/owa it is sent to 2013 servers. This we then want to process all requests and proxy connections to 2010. Accessing a 2013 mailbox is fine, however 2010 users just get the message, opening mailbox, it then sticks on
Still Working on it for indefinite and never progress'.
Have tried removing the External URL from 2010 as I have seen suggested elsewhere but this makes no difference.
ECP address' match what OWA are and certificates include all 3 namespaces.
Many THanks in advance for any assistance
Jason

Hi All
I have 2 new Exchange 2013 Multi role servers in a test environment. I have setup the namespace's in the following way
Communcal OWA URL - exchange.domain.co.uk/owa
Server 2013 Boxes
OWA URL Internal and External - owa.domain.co.uk/owa
Server 2010 Boxes
OWA Internal - legacy.domain.co.uk
OWA External - legacy.domain.co.uk
Authentication on Exchange 2010 boxes is set to basic, form based.
Authentication on Exchange 2013 boxes is set to basic and form based.
When users hit are exchange.domain.co.uk/owa it is sent to 2013 servers. This we then want to process all requests and proxy connections to 2010. Accessing a 2013 mailbox is fine, however 2010 users just get the message, opening mailbox, it then sticks on Still
Working on it for indefinite and never progress'.
Have tried removing the External URL from 2010 as I have seen suggested elsewhere but this makes no difference.
ECP address' match what OWA are and certificates include all 3 namespaces.
Many THanks in advance for any assistance
Jason

Similar Messages

Exchange 2010 and 2013 coexistence Internal and external URL

Hi all,
been reading alot of threads about Outlook anywhere and virtual directories in co-existence exchange 2010 and 2013.
Still i dont get any smarter.
Here is scenario:
Exchange 2010
Cas1
Cas2
Mailbox1
Mailbox2
Casarray is Exchange.casarray,com ( internal dns pointed to CAS1 in exchange 2010).Seems like by default both exchange 2013 cas servers are added to the casarray.
Exchange 2013
CAS+Mailbox
Cas+Mailbox
DNS
mail.exchange.com pointing to VIP (kemp loadbalancer)
Autodiscover ( pointed to same vip ,kemp load balancer)
Outlook anywhere on all servers (2010 and 2013)
Internal ( pointing to VIP on Kemp)
External ( pointing to external IP,then it passes firewall that again passes to kemp)
Problem we are having is when migrating users from Exchange 2010 - 2013.
Users using Outlook 2010
restart of outlook and mail works fine.
OWA works fine
Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
Users using Outlook 2013
Outlook in disconnected status,only fix is to create new profile.
OWA works fine
Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
Question is,what should be set for internal and external url (active sync,owa,ews)on 2010 and 2013 servers?
Where is the config wrong?
Thanks!
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. Thank you! Off2work

Hi Martina,
did the test as mentioned,even tried both CAS 2013 servers.Flush and registerdns didnt help.
Still Outlook is Connected to the cas.exchange.as (which again Points to 1 of Exchange 2010 servers),
Tried repair Outlook profile,no og.Only fix is to setup New account.
Any more tips?
thanks!
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. Thank you! Off2work

Mail is Slow between Exchange 2010 and 2013 During Co-Existance Transition

Hello,
I recently migrated from a single Exchange 2003 server to a single Exchange 2010 server
I am now trying to Migrate from Exchange 2010 to Exchange 2013.
I have a test user on Exchange 2013, and Internet Mail works fine and quickly both inbound and outbound.
However, when I try and send between a 2010 user to my 2013 user, delivery takes around 10 minutes.
On the 2013 server I see health check messages, and my 2010 user's message stuck in retry status. The messages eventually clear and the mail is delivered. Any ideas what is causing this delay?
In terms of connectors I have all the defaults. And I created 1 for internal relays from devices. Which works fine.
I have two Exchange 2013 servers configured in a DAG, but I don't have a load balance in place as of yet. So only server 1 is being accessed as the CAS.
Thanks

Hi,
According to your description, the mail flow is slow only between Exchange 2010 and Exchange 2013 server. If I misunderstand your meaning, please feel free to let me know.
If yes, I’d like to confirm if there are multiple NICs on your Exchange servers. And you can refer to the following thread:
http://social.technet.microsoft.com/Forums/exchange/en-US/66f0629f-21fb-444b-b3f1-99ed8a4f52b2/slow-mail-flow?forum=exchangesvrsecuremessaging
We have ONLY 1 network adapter, but if we select "All network adapters" instead of Hyper-V, we will get delays.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Single name space in between Exchange 2010 and 2013

Hi,
In my current environment I have 2 Exchange 2010 servers with DAG no CAS NLB. I installed Exchange 2013 with 2 CAS with WNLB and 2 Mailboxes with DAG. The main requirement is to configure Single name space to access in between Exchange 2010 and Exchange
2013. On Exchange 2010 DAG there is a URL using is owa.domain.com and I also configured in Exchange 2013 all the virtual directories with this name owa.domain.com but having an issue that when I open explorer and use the owa.domain.com URL the user on Exchange
2013 gets their mailbox but user on Exchange 2010 gets error HTTP 403 blank page.
I observed that in Exchange Organization settings CAS settings one server OWA, ECP etc shows their internal external URL but the other server unable to open the OWA, ECP URL and give error message that "An IIS directory entry
couldn't be created. The error message is Access is denied. HResult = -2147024891"
Please guide how to resolve this issue and use the same name URL in Exchange 2010 and Exchange 2013
Thanks,

Hi,
See the below brief:
User will connect to mail.contoso.com as his namespace endpoint. CAS2013 in Site1 will authenticate the user, do a service discovery, and determine that the mailbox version is 2010 and is located within the local AD site. CAS2013 will proxy the
request to an Exchange 2010 Client Access server which will retrieve the necessary data from the Exchange 2010 Mailbox server
Go through the full blog for better understanding of the redirection.
Client Connectivity with Exchange 2013
Hope you have changed your DNS records to direct connections only to your new Exchange 2013 server. You'll move the host names (for example, mail.contoso.com) users have been using to connect to Outlook Web Access, Autodiscover, and so on, from your
Exchange 2010 server to your Exchange 2013 server. When an Exchange 2010 user tries to open their mailbox, the Exchange 2013 server will proxy their request and communicate with the Exchange 2010 server on their behalf.
Configuring DNS includes the following:
Change the primary host names, such as mail.contoso.com, autodiscover.contoso.com, and owa.contoso.com (if used) to point to the external, publically-accessible, IP address of the Exchange 2013 Client Access server with your public DNS provider.
Change the primary host names, such as mail.contoso.com (or internal.contoso.com if you're using different internal host names) and owa.contoso.com (if used) to point to the internal machine name of the Exchange 2013 Client Access server on your internal
DNS servers.
NOTE- Go through the Exchange Deployemnt Assitant - Configure DNS Records section
Regards,
Satyajit
Please“Vote As Helpful”
if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2010 and 2013 "OWA and ActiveSync" co-existance 1 Public IP.

Hello Everyone.
I find myself in a bit of a dilemma and in a desperate need for some well educated help.
Scenario: Server 1 (Small Business Server 2011 Standard) with Exchange 2010
Server 2 (Server 2012 Standard) with Exchange 2013
1 Static Public IP Address
This used to be one domain that split into two separate entities that are still occupying the same office space.
All port forwarding is currently pointing to the SBS and everything there is working properly. I setup a new receive connector on the SBS that is forwarding the mail for domain 2 to the "Exchange 2013" server and mail flow in and out is working
100%.
The problem lies with OWA and ActiveSync.
I tried changing the SSL port in IIS on Server 2 from 443 to 1443 and forwarded those ports to server 2 from the router, then OWA works externally, but for some reason the clients on the local network can't connect anymore, so I had to drop that idea after
being unable to find the cause.
The only other thing I can think to try, is to setup HTTP redirection on the SBS IIS or adding the mail.domain2.com in the SBS DNS or something.
I have searched for hours but can't find anything specific to my scenario. Any and all help will be greatly appreciated.
Any and all help will be greatly appreciated.
Thank you in advance.
Hentie Loots

I recommend that you post this in the SBS Forum since SBS is different:
http://social.technet.microsoft.com/Forums/en/smallbusinessserver/threads
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2010 and 2013, Coexisting "OWA" and "ActiveSync" 1 Public IP.

Hello Everyone.
I find myself in a bit of a dilemma and in a desperate need for some well educated help.
Scenario: Server 1 (Small Business Server 2011 Standard) with Exchange 2010
Server 2 (Server 2012 Standard) with Exchange 2013
1 Static Public IP Address
This used to be one domain that split into two separate entities that are still occupying the same office space.
All port forwarding is currently pointing to the SBS and everything there is working properly. I setup a new receive connector on the SBS that is forwarding the mail for domain 2 to the "Exchange 2013" server and mail flow in and out is working
100%.
The problem lies with OWA and ActiveSync.
I tried changing the SSL port in IIS on Server 2 from 443 to 1443 and forwarded those ports to server 2 from the router, then OWA works externally, but for some reason the clients on the local network can't connect anymore, so I had to drop that idea after
being unable to find the cause.
The only other thing I can think to try, is to setup HTTP redirection on the SBS IIS or adding the mail.domain2.com in the SBS DNS or something.
I have searched for hours but can't find anything specific to my scenario. Any and all help will be greatly appreciated.
Any and all help will be greatly appreciated.
Thank you in advance.
Hentie Loots

You need to use ARR.
http://www.iis.net/downloads/microsoft/application-request-routing
It is essentially like a basic proxy service. So the SBS would receive an SSL connection for mail.domain2.com and instead of it failing it would be redirected internally to the second server.
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

Exchange 2010 and 2013 coexisting in separate trusted AD Forests, same email domain.

Im in a bind here.
Here is my scenario: We have domain 1, lets call this old-domain.corp that has an exchange server 2010 with MBX, CAS and HT role. We created a new domain, lets call this new-domain.corp that we migrated all our users AD accounts using ADMT from our old domain
to our new-domain.corp. We have both domains trusted two way, and we converted all our mailboxes on our old exchange 2010 server in our old domain to “linked mailboxes” with the owners of the mailboxes belonging to their new-domain.corp accounts.
This all works well currently.
What im trying to do now is have mailboxes live natively in the new-domain.corp on the new exchange 2013 server (only MBX role) I just built, whilst still having mailboxes working on our old-domain.corp while we migrate the mailboxes to the new. What
is the best way to achieve this? Right now I can create new mailboxes on the new server and send emails (using owa), but receiving is an issue since once mail is routed to my exchange 2010 (old) server it doesn’t keep going to the new exchange 2013 server.
Some details
Exchange 2010 – old-domain.corp – MBX, CAS, HT – latest rollup and exchange updates as of a week ago.
Exchange 2013 – new-domain.corp trusted two way with old domain - MBX
140 users - Single email domain name space
All on premise
Thank you,

Hi
In your case first you would need to bring Exchange 2013 CAS into the new domain.
Point all the web services URL to the Exchange 2013 CAS server
Redirect your firewall to receive all the emails to Exchange 2013 server
Then you would need to preparemove request and then once the objects are created then you would need to run new move request to move all the mailboxes from old domain to the new domain
One good article for your reference
http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/
Remember to 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 Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Exchange 2010 and 2013 Monitoring with SCOM 2012

HI all,
I have exchange 2013 and 2010 in my environment , Iwant monitor both in SCOM 2012,
Can you all please tell can i implement 2013 monitorinng first later can i go to 2010 Monitoring, Please advise in that supported or do i need to go with exchange 2010 monitoring first

There are no dependencies on the 2010 MP so you should be good to go, see the following:

Exchange 2010 and 2013

Hi All can some one guide me in correct path on exchange journalDB restore? I have Journal DB on exchange 2010 i need to mount the journalDB to exchange 2013 once this is successful i can decom the exchange 2010 servers. until i dont get journal DB restore
right i will not be able to decom my exchange 2010.i have tried restoring using DPM backup server but not having any luck. i have followed following link to restore the DB.
http://exchangeserverpro.com/restore-individual-mailbox-exchange-2010/
Regards
Ravi

According to your description, I would like to refer you on this well explained blog that covers all the required parts and would be a good start-up while need to restore Journal mailboxes using DPM :
http://www.techrepublic.com/blog/data-center/eight-steps-to-restore-an-individual-exchange-2010-mailbox-with-system-center-data-protection-manager/
Moreover, you may also consider on this automated option (http://www.exchangeserverrecovery.com/) that could also be a better alternative approach for the same concern.

Activesync URL in Exchange 2010 and 2013 co-existence environment

I am running a 2013 / 2010 coexistence environment, and have a question about activesync external URl setting on the Exchange 2010 servers. Do I need to set it to $null? Thanks

I am running a 2013 / 2010 coexistence environment, and have a question about activesync external URl setting on the Exchange 2010 servers. Do I need to set it to $null? Thanks
Set it to the same externalURL as the 2013 ExternalURL .
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Lync 2010 and 2013 coexistence - DNS

Hi all,
we are planning to upgrade from Lync server 2010 to 2013.During this mode,what is best to do regarding DNS?
Should we just keep existing ones and let Lync server proxy users, or do we need to point dns (internal and external) to the new 2013 server?
Like in Exchange 2010 and 2013 coexistence we had to point all dns to 2013 server,or users wont be proxied.
These are the DNS:
lyncdiscoverinternal
meet,dialin,admin
_sipinternaltls._tcp.domain.com
_sipfederationtls._tcp
sip.domain.com
Other DNS i might forgot?
thanks!
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. Thank you! Off2work

If you don't want to cut everyone over at once, you'll need different FQDNs for external web services between the pools, because mobility and meetings will use them both, regardless of where lyncdiscover and meet point.
If you want to keep the same name, that's fine, but you'll have to cut over in one big shot.
Also, pick a different name for the internal vs external web services. Mobility uses the external name, even when connecting on internal WiFi, so you'll want to redirect requests on port 443 to port 4443 for that and make it available internally.
If you have the same name for the internal web services, then internal requests will also use that path, which can cause issues or at the least route through a reverse proxy for no good reason.
Correct about pool FQDN being unique, also internal and external web service FQDNs unless you move everyone in one shot and don't care.
Everything else is pretty much a repoint when you're ready situation.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Exchange 2010 to 2013 Co-Existence Reverse DNS Issue

We are running a Exchange 2010 and 2013 coexistence. Mail Flow is fine on the 2013 side, but for mailboxes still on 2010, some are getting mail delivery failures only for certain external addresses. One of the deliveries says the Sending IP
does not have a valid rDNS. The IP Address it sent back is the main Public IP and not the Public IP assigned to our mail servers. Not understanding why the 2013 mailbox users can send to these external addresses no problem when 2010 mailbox users
are being routed through 2013. Thanks for any help.

Hi,
According to your post, I understand that account in Exchange 2010 deliver message failed for certain external addresses, however the user in Exchange 2013 works fine.
If I misunderstand your concern, please do not hesitate to let me know.
Whether all user in Exchange 2010 or some special account experience this question?
If this issue only occur on some specific external address, please contact its administrator to double confirm the configuration of anti-spam filter.
Besides, I recommend run Message tracking log and Protocol log to check the deliver process. More details about “Analyzing the protocol logs and Message tracking logs in Exchange 2013”:
http://social.technet.microsoft.com/wiki/contents/articles/23182.analyzing-the-protocol-logs-and-message-tracking-logs-in-exchange-2013.aspx
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

OWA receives mail long before Outlook (Exchange 2013 with Outlook 2010 and 2013)

I recently upgraded my Exchange environment to Exchange 2013 SP1. The Outlook users are now experiencing a delay when receiving email. When they do arrive they appear in batches, often 20-45 minutes after they were sent, from a mailbox on the same server.
Additionally, the mail appears instantly when you monitor the inbox using OWA. The users are experiencing this on both Outlook 2010 and 2013 clients configured in both cached and non-cached modes. This appears to be a problem with Outlook connecting to Exchange.
Any suggestion about how to correct this would be greatly appreciated. Thanks!

Hi,
From your description, when users use OWA, they can receive emails normally. But if they use Outlook 2010 or Outlook 2013, there is a delay in receiving emails.
I recommend you use the Outlook safe mode to determine whether the problem is caused by add-ins. Also, please make sure users have installed the Outlook latest Service Pack.
If the issue persist, please create a new profile and check the result.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Outlook 2010 and 2013 are unable to connect but OWA (and mail routing) works fine

Hi-
Not sure why but this past Sunday (just after DST adjustment) outlook clients (using 2010 and 2013) were unable to connect to an Exchange 2013 server. OWA and mail routing (internal and external) is working fine. I've even tried on multiple machines
and all of them experience the same issue. On a new machine with a fresh version of outlook 2013 installed here is what happens:
Click on Outlook 2013
Click Next until the account setup is displayed.
Name and email is auto-populated
Established network connection is good
Searching for email address settings is good (once the self-signed exchange 2013 cert is accepted)
And then the logging onto the mail server fails. The first pop-up is:
The Connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
Clicking "OK" is followed up with a window with the Microsoft Exchange connection info.
It lists Microsoft Exchange server which is populated with: GUID@<domain suffix>
Mailbox which is populated with: =SMTP:<Valid Email address>
On the Exchange Server I have noticed that the Web Management Service (WMSVC) is stopped and will not start. Starting the service outputs:
EventID 7024
"The Web Management Service terminated with the following service-specific error: Unspecified error"
Not really helpful :)
Since this is only happening with Outlook on multiple clients I'm expecting something with Exchange or the ability for outlook to connect to exchange.
Thanks in advance!

Hi
I know this is an old post, but I'm having a very similar issue. I have CU6 installed and all other client connectivity apart from internal Outlook connectivity is working fine. I have distributed the new Self-Signed Certificate and the tested to verify
the clients trust it. I have tried on multiple machine with multiple accounts and none of them connect.
I'm at the stage of reinstalling, but I would rather troubleshoot the problem, just in case ever hit the same wall in the future. I have run Test-OutlookConnectivity with the following output;
RunspaceId : 71f8d740-c499-4bbe-8baf-9cbb12566fb8
Server : PW-SC-01.companyname.local
MonitorIdentity : Outlook.Protocol\OutlookRpcDeepTestProbe\NEW2013
RequestId : 75641e34-aa49-4fce-aad7-181b56dd7b29
ExecutionStartTime : 10/11/2014 13:50:03
ExecutionEndTime : 10/11/2014 13:50:03
Error : Error 0x6ba (The RPC server is unavailable) from ClientAsyncCallState.CheckCompletion:
RpcAsyncCompleteCall
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 2
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1710
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: 0 (0x00000000)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 13
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1352
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: -1073606646 (0xC002100A)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0xC002100A
EEInfo: Detection location: 1380
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 12175 (0x00002F8F)
EEInfo: prm[1]: Unicode string: /rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0x00010000
EEInfo: Detection location: 1385
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 8 (0x00000008)
EEInfo: prm[1]: Binary Buffer: [48-1263-10248-1262-126-9632122164676121-3988104-118-11373-61-94
-111-112-98-1217048136942-12272-122-91311550483449324830638543192311910198979999101115115461121199
91111091091154699111461171074830231349524949485349505348484990231349574949485349505348484990483449
324830638543192311910198979999101115115461121199911110910911546991114611710748-12613448136942-1227
2-122-913111503-126115048-1261102-126110-22103-15-109-16-121-119-3121-4-106119-119-9369122-5779121
719-98-24-67-32918-98-236-19-10715326827-76102-61100108-12718-438331-37109-102-57-9942-11389-10374
-77-5-4-107109-11847342222-63-48-7468-17-1067033-56111-33-54-16-105-62-76-1282011-1664-12158-4915-
88-53-9-29-2994-49-54-5211-1364-212121-12396-127-353-396185117-681229-434246070-109818119-4858-128
-106-1279248-49110-44-81-121494199-118-17-106-71106828294-93-110-110-106-415084-127126-45-12331421
-61-2757-24-128-28-25111-52113121-56-98-5821527282-47255245104-111-55-1099747-115-11172-287-12526-
79-12430-119421360-107-6430-5410282-52-51-128533354-116672757-77-75-111-72-118-10114-84484825-40-1
8-70-24-9111-61-5391-8034125-12632-16-19-128112030-8-427523101-93-127-5348-127-5648146385291511-14
4325-9648-127-110638529174-127-11848-127-121-12623119101989799991011151154611211999111109109115469
911146117107-1262211211945115994548494611211999111109109115461081119997108-12626651171161116810511
59911111810111446808767111109109115461081119997108-12626651171161116810511599111118101114468087671
11109109115469911146117107-12613808767111109109115461081119997108-12613808767111109109115469911146
11710748196385293741248106843615573148126385291911-14248048136942-12272-122-913115503-12611081-930
6613-74953718-12745-14-25-94107-80-5-45-2231536-1728-12897-8587577-1252765-892896-83-10267-7926-20
-9841-1079-12-29-4315671111357-684036-40-5129-91-24-461066-12306-65-9118-89115191071-30-20-1067161
-83-91-74105-931649-48-96126-13-71-118-8967567-40-64-104-113-31-51-102357125100-50113-103-113123-9
873-627067-25-908-10131118125122-71-115-37-1850-1055851-31410-77-7312-36848124-26104-10711043-2048
-48-12666611759121127-2960-1571-9-95-98-1036911610-74221-32-25114-108749933-7147562114-3635-101-81
-1058-73108-61-78-128-116-715155112714-37-18-84-8331-2716-1174257-76-5-1598-15-12875-98-7329632178
-10714-123-6312212-1028359-56-76-683-873987-2120-845954-7617-71-57999828110], size=926
Exception : Microsoft.Exchange.Rpc.ServerUnavailableException: Error 0x6ba (The RPC server is unavailable)
from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 2
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1710
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: 0 (0x00000000)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 13
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1352
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: -1073606646 (0xC002100A)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0xC002100A
EEInfo: Detection location: 1380
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 12175 (0x00002F8F)
EEInfo: prm[1]: Unicode string: /rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0x00010000
EEInfo: Detection location: 1385
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 8 (0x00000008)
EEInfo: prm[1]: Binary Buffer: [48-1263-10248-1262-126-9632122164676121-3988104-118-11373-61-94
-111-112-98-1217048136942-12272-122-91311550483449324830638543192311910198979999101115115461121199
91111091091154699111461171074830231349524949485349505348484990231349574949485349505348484990483449
324830638543192311910198979999101115115461121199911110910911546991114611710748-12613448136942-1227
2-122-913111503-126115048-1261102-126110-22103-15-109-16-121-119-3121-4-106119-119-9369122-5779121
719-98-24-67-32918-98-236-19-10715326827-76102-61100108-12718-438331-37109-102-57-9942-11389-10374
-77-5-4-107109-11847342222-63-48-7468-17-1067033-56111-33-54-16-105-62-76-1282011-1664-12158-4915-
88-53-9-29-2994-49-54-5211-1364-212121-12396-127-353-396185117-681229-434246070-109818119-4858-128
-106-1279248-49110-44-81-121494199-118-17-106-71106828294-93-110-110-106-415084-127126-45-12331421
-61-2757-24-128-28-25111-52113121-56-98-5821527282-47255245104-111-55-1099747-115-11172-287-12526-
79-12430-119421360-107-6430-5410282-52-51-128533354-116672757-77-75-111-72-118-10114-84484825-40-1
8-70-24-9111-61-5391-8034125-12632-16-19-128112030-8-427523101-93-127-5348-127-5648146385291511-14
4325-9648-127-110638529174-127-11848-127-121-12623119101989799991011151154611211999111109109115469
911146117107-1262211211945115994548494611211999111109109115461081119997108-12626651171161116810511
59911111810111446808767111109109115461081119997108-12626651171161116810511599111118101114468087671
11109109115469911146117107-12613808767111109109115461081119997108-12613808767111109109115469911146
11710748196385293741248106843615573148126385291911-14248048136942-12272-122-913115503-12611081-930
6613-74953718-12745-14-25-94107-80-5-45-2231536-1728-12897-8587577-1252765-892896-83-10267-7926-20
-9841-1079-12-29-4315671111357-684036-40-5129-91-24-461066-12306-65-9118-89115191071-30-20-1067161
-83-91-74105-931649-48-96126-13-71-118-8967567-40-64-104-113-31-51-102357125100-50113-103-113123-9
873-627067-25-908-10131118125122-71-115-37-1850-1055851-31410-77-7312-36848124-26104-10711043-2048
-48-12666611759121127-2960-1571-9-95-98-1036911610-74221-32-25114-108749933-7147562114-3635-101-81
-1058-73108-61-78-128-116-715155112714-37-18-84-8331-2716-1174257-76-5-1598-15-12875-98-7329632178
-10714-123-6312212-1028359-56-76-683-873987-2120-845954-7617-71-57999828110], size=926
at Microsoft.Exchange.Rpc.ClientAsyncCallState.CheckCompletion()
at Microsoft.Exchange.Rpc.ExchangeClient.ClientAsyncCallState_Connect.End(IntPtr&
contextHandle, TimeSpan& pollsMax, Int32& retryCount, TimeSpan& retryDelay, String& dn
PoisonedCount : 0
ExecutionId : 63105129
SampleValue : 33.5194
ExecutionContext : Mailbox logon verification
EMSMDB.Connect()
Task produced output:
- TaskStarted = 10/11/2014 13:50:03
- TaskFinished = 10/11/2014 13:50:03
- Exception = Microsoft.Exchange.Rpc.ServerUnavailableException: Error 0x6ba (The RPC
server is unavailable) from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 2
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1710
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: 0 (0x00000000)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 13
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1352
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: -1073606646 (0xC002100A)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0xC002100A
EEInfo: Detection location: 1380
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 12175 (0x00002F8F)
EEInfo: prm[1]: Unicode string: /rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0x00010000
EEInfo: Detection location: 1385
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 8 (0x00000008)
EEInfo: prm[1]: Binary Buffer: [48-1263-10248-1262-126-9632122164676121-3988104-118-11373-61-94
-111-112-98-1217048136942-12272-122-91311550483449324830638543192311910198979999101115115461121199
91111091091154699111461171074830231349524949485349505348484990231349574949485349505348484990483449
324830638543192311910198979999101115115461121199911110910911546991114611710748-12613448136942-1227
2-122-913111503-126115048-1261102-126110-22103-15-109-16-121-119-3121-4-106119-119-9369122-5779121
719-98-24-67-32918-98-236-19-10715326827-76102-61100108-12718-438331-37109-102-57-9942-11389-10374
-77-5-4-107109-11847342222-63-48-7468-17-1067033-56111-33-54-16-105-62-76-1282011-1664-12158-4915-
88-53-9-29-2994-49-54-5211-1364-212121-12396-127-353-396185117-681229-434246070-109818119-4858-128
-106-1279248-49110-44-81-121494199-118-17-106-71106828294-93-110-110-106-415084-127126-45-12331421
-61-2757-24-128-28-25111-52113121-56-98-5821527282-47255245104-111-55-1099747-115-11172-287-12526-
79-12430-119421360-107-6430-5410282-52-51-128533354-116672757-77-75-111-72-118-10114-84484825-40-1
8-70-24-9111-61-5391-8034125-12632-16-19-128112030-8-427523101-93-127-5348-127-5648146385291511-14
4325-9648-127-110638529174-127-11848-127-121-12623119101989799991011151154611211999111109109115469
911146117107-1262211211945115994548494611211999111109109115461081119997108-12626651171161116810511
59911111810111446808767111109109115461081119997108-12626651171161116810511599111118101114468087671
11109109115469911146117107-12613808767111109109115461081119997108-12613808767111109109115469911146
11710748196385293741248106843615573148126385291911-14248048136942-12272-122-913115503-12611081-930
6613-74953718-12745-14-25-94107-80-5-45-2231536-1728-12897-8587577-1252765-892896-83-10267-7926-20
-9841-1079-12-29-4315671111357-684036-40-5129-91-24-461066-12306-65-9118-89115191071-30-20-1067161
-83-91-74105-931649-48-96126-13-71-118-8967567-40-64-104-113-31-51-102357125100-50113-103-113123-9
873-627067-25-908-10131118125122-71-115-37-1850-1055851-31410-77-7312-36848124-26104-10711043-2048
-48-12666611759121127-2960-1571-9-95-98-1036911610-74221-32-25114-108749933-7147562114-3635-101-81
-1058-73108-61-78-128-116-715155112714-37-18-84-8331-2716-1174257-76-5-1598-15-12875-98-7329632178
-10714-123-6312212-1028359-56-76-683-873987-2120-845954-7617-71-57999828110], size=926
at Microsoft.Exchange.Rpc.ClientAsy
FailureContext :
ExtensionXml :
ResultType : Failed
RetryCount : 0
ResultName : 75641e34aa494fceaad7181b56dd7b29-OutlookRpcDeepTestProbe/NEW2013
IsNotified : False
ResultId : 1748063
ServiceName : InvokeNow
StateAttribute1 : Momt
StateAttribute2 : UnknownIssue
StateAttribute3 : PW-SC-01.companyname.local
StateAttribute4 : Unknown
StateAttribute5 : {C54AD38D-1E00-4F53-ABAE-26518C3FF82F}
StateAttribute6 : 0
StateAttribute7 : 0
StateAttribute8 : 0
StateAttribute9 : 0
StateAttribute10 : 0
StateAttribute11 : Momt
StateAttribute12 :
StateAttribute13 : VgEAVAdXaW5kb3dzQwBBCEtlcmJlcm9zTA9QV0NPTU1TXG5hdGhhbmhVLlMtMS01LTIxLTIwNTc0OTEwMzItMzE4NDA2NDk3OC
0xNTQ2MTE0ODM1LTI2MzJHHQAAAAcAAAAtUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNTEzBwAA
AAdTLTEtMS0wBwAAAAdTLTEtNS0yBwAAAAhTLTEtNS0xMQcAAAAIUy0xLTUtMTUHAADAE1MtMS01LTUtMC0zNDc3ODcxMTMHAA
AALlMtMS01LTIxLTIwNTc0OTEwMzItMzE4NDA2NDk3OC0xNTQ2MTE0ODM1LTQxODcHAAAALVMtMS01LTIxLTIwNTc0OTEwMzIt
MzE4NDA2NDk3OC0xNTQ2MTE0ODM1LTUxMgcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtND
E3NAcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtMzU3MAcAAAAuUy0xLTUtMjEtMjA1NzQ5
MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNDEyMgcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMT
Q4MzUtMTE2NAcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtMTE0MQcAAAAuUy0xLTUtMjEt
MjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNDE1MwcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LT
E1NDYxMTQ4MzUtNDE0NQcAAAAtUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNTE4BwAAAC5TLTEt
NS0yMS0yMDU3NDkxMDMyLTMxODQwNjQ5NzgtMTU0NjEx
StateAttribute14 :
StateAttribute15 :
StateAttribute16 : 0
StateAttribute17 : 0
StateAttribute18 : 0
StateAttribute19 : 0
StateAttribute20 : 0
StateAttribute21 : /o=companyname/ou=first administrative group/cn=Recipients/cn=NathanH
StateAttribute22 : EMSMDB.Connect()
StateAttribute23 : https://pw-sc-01.companyname.local:444/rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
StateAttribute24 : Negotiate
StateAttribute25 : [33]10/11/2014 13:50:03 [FAILED!] EMSMDB.Connect();
Identity : fcd6159dd8fe42aebf10100cc4934356
IsValid : True
ObjectState : New

OWA still lands at Exchange 2010 for users migrated from Exchange 2010 to 2013

I never had any issues with OWA redirection for a few users that I migrated from Exchange 2010-2013 initially. For users that I am migrating in the past few days, the OWA 2013 is landing on Exchange 2010 despite the mailbox being successfully migrated to
Exchange 2013.
Troubleshooting:
1. I have restarted the IIS Services
2. I have restarted MSExchangeOWAAppPool.
3. I have also checked the homeMDB attribute of the 2013 migrated user with the Exchange 2013 database.
I would really appreciate if anyone could share their experiences on similar issues.

I have checked it, the migration status is completed. In regard to the namespaces, both CAS 2010 and 2013 are set to mail.domain.com; CAS 2013 is the internet facing. I have also checked the internal access for OWA, it's the same scenario. Migrating them
back to 2010 and 2013 won't resolve the issue in my case, because the issue persists for every new user that I am migrating.
I recently found the following when I login with a user who is not effected and then logout:
1. Login in back with the affected user without closing the browser or clearing the cache, it lands at CAS 2013 OWA.
2. However, I get the below listed error message when I logout.
Your request couldn't be completed.
Click here to continue working.
This may have occurred for security reasons or because your session timed out.

OWA Exchange 2010 and 2013 Co-Existance

Similar Messages

Maybe you are looking for