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

Similar Messages

Exchange 2010 server (Mail,HUB and CAS) installation in new site.

We are planned to install Exchange 2010 servers(MAIL,HUB and CAS) server in new Active director site in existing exchange organization.
Kindly share best practice link for exchange server installation in new site.

The best practice for installing into a new Active Directory site is the same as installing into a new organization, except you don't need to prepare the organization or domains (unless you are also installing into a new domain that hasn't been prepared).
Install the CAS then hub, then mailbox roles, or install a multi-role server, then define your CAS Array name and IP address, and set your CAS behind a load balancer (if needed). Add your external certificate to both the CAS and the load balancer (and the
hub if you use TLS for mail transfer), and you should be golden. Also, if you intend to proxy your CAS connections, here's a link that may help:
https://technet.microsoft.com/en-us/library/bb310763.aspx?f=255&MSPPError=-2147217396
For completeness, here's a thread on the msexchange.org forums that specifically mentions adding Exchange into a second site:
http://forums.msexchange.org/New_Exchange_2010_at_another_Site/m_1800557445/tm.htm

Migrate Exchange 2010 to 2013 External Mail Flow

Dear All,
I am in the middle of Exchange Server 2010 to 2013 Migration. The scenario is I have single Exchange 2010 server with HUB/CAS/Mailbox and installed new Exchange 2013 with single CAS and single Mailbox server. The internal email flow between Exchange
2010 to 2013 and 2013 to 2010 is working. Having some issues and need assistance to resolve at earliest.
The issue with the external mail flow and I want to Exchange 2010 should be configured to send external email while migrating users to Exchange 2013. Once migrate all users to Exchange 2013 then will configure Exchange 2013 send connector.
How can I configure single name space of web URL for OWA both on Exchange 2010 to Exchange 2013, if user mailbox is in Exchange 2010 can access same OWA URL as user migrate to Exchange 2013.
How to configure SSL certificate, I have single URL certificate this would be enough for OWA, ActiveSync and Anywhere.
Is that possible if directly move the Exchange 2010 database to Exchange 2013 database, this will move all users mailboxes in one go or do I need to migrate users mailbox individual or in bulk.
Kindly guide if any thing missing that need to address during start the migration activity.
Thanks in Advance

Hi ,
Sorry for delay.
Question : Thanks for your valuable response. On
point no.2, I want to use same external URL for Exchange 2010 and Exchange 2013, is this possible if user is on exchange 2010 server or migrated on Exchange 2013 can use same external single name space URL to access OWA ?
Yes you can have the same External URL for the exchange 2010 owa and exchange 2013 owa.So users from exchange
2010 and exchange 2013 can access owa on the same URL from external world.For exchange 2010 users owa connections will be proxied from exchange 2013 to exchange 2010.
For mailbox connectivity issue in exchange 2013 :
1.From internal outlook clients ,Please check the internal outlook anywhere name is resolved to exchange
2013 server and also make sure the authentication set on the outlook anywhere is set to NTLM. Same time we need to have the internal outlook anywhere name on the SAN certificate.
2.Make sure the names used exchange on 2013 URL'S is available on the SAN certificate and also the certificate
needs to installed on the exchange server and that certificate has to be enabled for the required services like iis,pop.imap,smtp.
3.Make sure the outlook client request coming for internal outlook anywhere name and also to autodiscover
service is not reaching the proxy server if you have on your network.
In case if you have proxy server in your environment for internet access ,So for that we need to add the internal outlook anywhere name and autodiscover name
on the internet explorer proxy exceptions for all the internal outlook clients.We can globally achieve it through group policy.
4.please share me the output for the below mentioned command.
get-ClientAccessServer -Identity “server name” | fl AutodiscoverServiceInternalURI
5.If you are having outlook 2007 then make sure it fully patched with latest sp and updates.
6.On which operating system version those outlook 2007 clients are installed?
Please reply me if anything is unclear.
Thanks & Regards S.Nithyanandham

Exchange 2010 to 2013 Migration: Authentication/Proxy Settings Issue

I'm in the final stages of preparing for our Exchange 2010 to 2013 migration. I'm noticing minor authentication issues on mobile devices (android & ios) and proxy setting issues with Outlook that require user intervention. In an effort to make the migration
as smooth as possible for our internal users, I'd like to get these settings ironed out before starting the migration.
Symptoms:
Outlook - I'm aware that internal Outlook usage has changed its connection protocol from RCP/TCP to RCP/HTTP, but it appears that Outlook isn't updating its settings in the "Microsoft Exchange Proxy Settings" after a users mailbox has been migrated
from 2010 to 2013. Currently, 2010 users with Outlook 2013 have the following settings configured in Outlook's Exchange Proxy Settings:
URL to connect to my proxy server for Exchange: webmail.domain.com
Connect using SSL only: Checked
Only connect to proxy servers that have this principal name in their certificates: Unchecked
On fast networks, connect using HTTP first, then connect using TCP/IP: Unchecked
On slow networks, connect using HTTP first, then connect using TCP/IP: Checked
After migrating a user's mailbox from 2010 to 2013, the above settings remain the same in Outlook and their client disconnects from Exchange and isn't able to reconnect. After manually enabling the checkbox for "On fast networks, connect using HTTP
first, then connect using TCP/IP", Outlook clients are able to connect to Exchange via their newly migrated mailbox.
Is there a way to automatically updating these 2 proxy settings in Outlook during the migration instead of having to manually change each user's configuration in Outlook?
Android & iOS - Currently, users on Android & iOS with Exchange 2010 mailboxes have the following configuration:
domain: blank
username: their AD username
server: webmail.domain.com
After migrating a mobile users mailbox from 2010 to 2013, neither OS (Android or iOS) is able to connect due to an authentication failure. On iOS, if I manually change the domain from blank to my company's domain, authentication succeeds and their 2013 mailbox
begins to update. On Android, the option to change the domain name from null is grayed out, requiring the user to delete the Exchange profile and re-add it with the domain name intact. Is there a way to configure Exchange 2013 to not require the domain name
for mobile users in the same way that it's been working for us with Exchange 2010?
Please let me know if you require cmdlet print outs of my virtual directories to help troubleshoot the issue.

Hi,
Generally, when the user mailbox is moved from Exchange 2010 to Exchange 2013, the Autodiscover service would detect the changes and update the new configuration automatically.
Please make sure the autodiscover service in your new Exchange 2013 is configured correctly. We can create a new mailbox in Exchange 2013 and check whether the new Exchange 2013 user can setup account successfully in Outlook or not. If the new user works
fine, it indicates the autodiscover service in Exchange 2013 should be proper for internal user.
Please restart the following Exchange service to have a try:
Microsoft Exchange RPC Client Access
Microsoft Exchange Mailbox Replication
Restart IIS service by running IISReset in a Command Prompt window.
Then check whether the Outlook client can connect to Exchange 2013 or not.
As for Android & iOS issue, I suggest we can ask a question in ActiveSync forum for more suggestion:
https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
Regards,
Winnie Liang
TechNet Community Support

"Resend" option is not working for specific user. "The Operation Failed" Exchange 2010 Outlook 2013

Hi Everybody. I have a weird one for you.
I have a user that gets an "operation failed" message whenever trying to use the "resend" option on any email (It's the one right under recall). I had tested up and down on her machine. Exchange 2010 Outlook 2013
Ran in safe mode, recreated her profile, disabled virus scanning, repaired office. (weird, the font just changed sizes on me)
After all of this I tested on other computers, other users seem to be able to "resend" just fine. However her account does not work on any computer I try, internal or external to the network.
It looks more like a profile issue.
She's a very active archivist, so she only has 486MB of space used by her mailbox.
It's well under quota.
It's been really puzzling me.
MCSE 2003, Exchange. MCTS Vista, 7. Administrator of awful, neglected website http://timssims.net

Hi Timssims,
Since there is only one user in the org has this issue, it seems an issue on the Outlook client side.
I suggest asking Outlook Forum for help so that we can get more professional suggestions.
For your convenience:
https://social.technet.microsoft.com/Forums/office/en-US/home?forum=outlook
However I also have some suggestions for your reference:
1. If this issue occur on Cached Mode, I suggest turning to Online Mode for testing.
2. Please also paste the detailed error message if "operation failed" is not the
complete information.
3. If still not works after perform operations above (including suggestions from Outlook Forum), I suggest re-creating a new mailbox for the specific user just as Martin suggested.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2010 to 2013 users migration

Hi,
I am migrating users from Exchange 2010 to 2013 and facing a lot of migration issues. few of them are as follow.
1. It hung up at "syncing" and end up with a failure.
2. After a long migration i got the following errors
Error: MigrationPermanentExeception: Failed to reset the target mailbox after the move. Error Details:MaipExceptionADUnavailable: Unable to prepopulate the cache for user :: on domain controller xyz.domain.com (hr=0x80004005,ec=2414) Diagnosti Context: Lid:
65256 Lid:1494 ---- Remote Context Beg ---- Lid: 52664 StoreEc: 0x96E Lid: 35973 StoreEc: 0x96E Target Mailbox unlock operation was not replicated. If a lossy failover occurs after the target mailbox was unlocked, the target mailbox could remain inaccessible.
Error details: Target mailbox connection was lost.
3. users migration is taking a lot of time although mailbox size is not big and both servers are in same datacenter.
Need urgent help pls....

Hi,
Here are the general steps for troubleshooting mailbox moves:
1. If the move request didn't complete, view the Move Request Statistics.
2. If the move request completed with errors, view the move report.
3. View the Event log on the Client Access server running the instance of the Microsoft Exchange Mailbox Replication service that's processing the failed move request.
4. use the Exchange Management Console or the Exchange Management Shell to increase the diagnostic logging levels on the Client Access server for the Mailbox Move and Service categories of the MSExchange Mailbox Replication service.
For more detailed information about general steps for troubleshooting mailbox moves, you can refer to the article below:
http://technet.microsoft.com/en-us/library/dd638094(v=exchg.141).aspx
Additionally, in order to narrow down the cause, I’d like to confirm the following information:
1. Are the problematic target mailboxes in the same database?
2. Is there a time boundary? After that, you cannot move mailboxes:
http://social.technet.microsoft.com/Forums/en-US/90403f75-e530-478a-ab68-27823b730f68/exchange-2013-batch-to-migrate-users-from-2010-database-is-hung-at-syncing-after-a-disaster?forum=exchangesvrdeploy
Thanks,
Angela
Angela Shi
TechNet Community Support

Manually Move Public Folders from Exchange 2010 to 2013

Hi all,
I have a issue to finishing my migration from Exchange 2010 to Exchange 2013, I have been trying to migrate my Public folders but always after a couple hours, the migration state is failed.
The final error is the following:
FailureCode                      : -2146233088
FailureType                      : SourceMailboxAlreadyBeingMovedPermanentException
FailureSide                      :
Message                          : Error: Couldn't switch the mailbox into Sync Source mode.
                                   This could be because of one of the following reasons:
                                     Another administrator is currently moving
the mailbox.
                                     The mailbox is locked.
                                     The Microsoft Exchange Mailbox Replication
service (MRS) doesn't have the correct
                                   permissions.
                                     Network errors are preventing MRS from cleanly
closing its session with the
                                   Mailbox server. If this is the case, MRS may continue
to encounter this error for
                                   up to 2 hours - this duration is controlled by the TCP
KeepAlive settings on the
                                   Mailbox server.
                                   Wait for the mailbox to be released before attempting
to move this mailbox again.
So, after seeing this I started to monitoring all process and I realized that after creating hierarchy the process start to fail and keep in StalledDueMailboxlock status, and the error is:
FailureCode                      :
FailureType                      :
FailureSide                      :
Message                          : Informational: The request has been temporarily postponed because the mailbox is
                                   locked. The Microsoft Exchange Mailbox Replication service
will attempt to continue
                                   processing the request after 2/14/2015 12:38:20 PM.
Finally, digging more into reports of migration I found this:
MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to open entry ID. (hr=0x80040115, ec=6)_x000A_Diagnostic context:_x000A_ Lid: 40487 EMSMDBMT.EcDoRpcExt2 called [length=73]_x000A_ Lid: 44583 EMSMDBMT.EcDoRpcExt2
exception [rpc_status=0x6][latency=0]_x000A_ Lid: 62184 _x000A_ Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a_x000A_ Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 51452_x000A_ Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-02-14T14:25:40.9210000Z_x000A_
Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 2_x000A_ Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 6_x000A_ Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 1741_x000A_ Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0_x000A_ Lid: 11672 dwParam:
0x0 Msg: EEInfo: NumberOfParameters: 0_x000A_ Lid: 23260 Win32Error: 0x6_x000A_ Lid: 61553 StoreEc: 0x80040115_x000A_ Lid: 52176 ClientVersion: 15.0.1044.25_x000A_ Lid: 50032 ServerVersion: 14.3.181.6_x000A_ Lid: 50128 _x000A_ Lid: 50288 _x000A_ Lid: 23354
StoreEc: 0x80040115_x000A_ Lid: 25913 _x000A_ Lid: 21817 ROP Failure: 0x80040115_x000A_ Lid: 22894 _x000A_ Lid: 24942 StoreEc: 0x80040115
So, would like to know if exist any procedure to migrate/move my Public Folders from Exchange 2010 to 2013 manually, something like Export/Import.
Regards!

What script and process you are running to migrate the Public Folders?
And what do you mean by Manually?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.comTwitter:
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 2010 to 2013 Migration- orphaned 2010 servers in Edge subscription

Migration of Exchange 2010 to 2013 was carried out. Steps to decommission the 2010 servers was done, including removing the Exchange software fro the servers. Looks like some pieces were missed though as the 2010 servers still appear in the smarthostdelivery
and shadow redundancy on the 2010 edge transport server.
How can these be removed?

Hi,
I recommend you can use the following script to cleanup the queue:
Cleanup Shadow Redundancy Queues
Performs a search per server per shadow redundancy queue. If shadow redundancy queues contain
at least 1 message the receive date is inspected. If it is more then 1 day ago it will cleanup
the message.
Normally you do not have to cleanup the shadow redundancy queues because messages will automatically
expire, how long this takes depends on your config but normally 2 days.
However in some scenarios it might be necessary to clean the queues.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Pop3 connection exchange 2010 or 2013?

which is better for pop3 access?
exchange 2010 or 2013?
i have used exchange 2010 before am familar with interface

Better? In what way?
The interface is completely different (EAC compared to EMC) but that's true in general (not just for POP3).
Here's some directions on enabling it (there are now two services to enable):
http://technet.microsoft.com/en-us/library/bb124934(v=exchg.150).aspx
Some more info:
http://technet.microsoft.com/en-us/library/jj657728(v=exchg.150).aspx
If you do a search, you might be able to find a step-by-step that will guide you.
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.

Using IIS AAR as a reverse proxy for Exchange 2010 & Lync 2013

hi
i am planning to use IIS AAR as reverse proxy solution for both Exchange 2010 & Lync 2013 . need clarifications on the below.
Is it production ready proof solution of using IIS AAR as a reverse proxy solution , if yes what is the sizing considerations for the same.
Can we have exchange reverse proxy and lync reverse proxy on the same IIS ARR server.
Is there any special consideration(license/certificates/cal licenses) needs to be taken care while using this solution
4. Deployment Guide available?

hi steve.. thanks for reply..
1 have gone through that.. however having both exchange & lync reverse proxy on single server is unanswered and the reason for having this in exchange forum is to have consideration from exchange prospective as well ...
I am also wondering this. Can both exist on the same set of proxy servers? I also plan to have a load balanced solution. Has anyone had any luck with doing that?

Exchange 2010 to 2013 Public Folder Migration -- Token Serialization

Here is the log entry,Failed to save admin audit log for this cmdlet invocation. Organization: First Organization Log content:Cmdlet Name: New-PublicFolderMigrationRequestObject Modified: f0daff33-6a93-4367-b609-662cfa0b92de\71fc0595-b5d7-4f15-8b7c-bffcefbd810fParameter: SourceDatabase = Public Folder Database Parameter: CSVData = VGFyZ2V0TWFpbGJveCxGb2xkZXJQYXRoDQpDb2JvY28gUEYsXA0KQ29ib2NvIFBGLFxJUE1fU1VCVFJFRVxBcg==...Caller: ExternalAccess: FalseSucceeded: TrueRun Date: 2015-07-07T12:41:45OriginatingServer: (15.00.0995.012)Error:Microsoft.Exchange.Data.ApplicationLogic.AuditLogAccessDeniedException: The requesting account doesn't have permission to access the audit log. --- System.Web.Services.Protocols.SoapException: The requesting account does not have permission to serialize tokens. at...

Hey Guys!
I'm in the process of testing a Public Folder migration from Exchange 2010 to 2013, I've been following the recommened migration scenario from Microsoft but have ran into this issue when running New-PublicFolderMigrationRequest. I let the request sit at a queued status for over 6 hours and then decided to look at the event logs. I'm receiving an access denied, requesting account does not have permission to serialize tokens.
Luckily this is just a test and not in a production environment :-)
Any suggestion or help to point me in the right direction would be appreciated
Thanks Guys
This topic first appeared in the Spiceworks Community

Exchange 2010 to 2013

Hi Everyone,
We are currently running exchange 2010 on a 2012 server. We want to migrate our exchange 2010 to 2013. What would be the best way of upgrading? Can we install exchange 2013 on the same server as exchange 2010 and then move the roles, or we need
to purchase another server in order to install exchange 2013?
Thanks

Hi,
We can install an Exchange 2013 into an existing Exchange 2010 organization, and then move the Exchange resources, such as mailboxes, public folders, and connectors to Exchange Server 2013. However, we can't perform an in-place upgrade from Exchange Server
2010 to Exchange 2013.
For more information, here is an article for your reference.
Install Exchange 2013 in an Existing Exchange 2010 Organization
http://technet.microsoft.com/en-us/library/bb124350(v=exchg.150).aspx
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Exchange 2007 and 2013 Co-existnec - ActiveSync Issue

Hi
We have introduced Exchange 2013 servers in our existing Exchange 2007 environment. We have a customized Exchange 2007 ActiveSync setup i:e we created a custom separate website in IIS for ActiveSync to serve the ActiveSync devices. After the introduction
of Exchange 2013 CAS servers, when we installed the new certificate on them and configured the virtual directory with ActiveSync URLs, the Exchange 2013 servers seems to be receiving Activesync requests but they can't just proxy it to Exchange 2007 for some
reason. following Warning is logged on Exchange 2013 servers:
[Eas] Marking ClientAccess 2010 server MIA-EXCAS01.utg.uvn.net (https://mia-excas01.utg.uvn.net/Microsoft-Server-ActiveSync) as unhealthy due to exception: System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)
We still need to install new Certificate on the Exchange 2007 servers. Wondering what could be the issue here, can Exchange 2013 proxy the connection to Exchange 2007 on a custom website ? or it looks for one under Default Website?
Can the absence of new certificate (meaning certificate mismatch) lead to this issue?
Thanks
Taranjeet Singh
zamn

Actually 2013 can proxy ActiveSync to 2007
Please follow this.
1. Set AutodiscoverInternalURL using this command for every CAS server
Set-ClientAccessserver -identity -CAS1 -AutodiscoverInternalURI
https://mail.yourcompany.com/autodiscover/autodiscover.xml (for FQDN , using your CAS NLB name if exist)
2. Set OWA virtualdirectoy (2013) via EAC
Internal URL : https://mail.yourcompany.com/owa External URL : https://mail.yourcompany.com/owa
3. Set ECP virtualdirectory (2013) via EAC
Internal URL : https://mail.yourcompany.com/ecp External URL : https://mail.yourcompany.com/ecp
4. Set OAB virtualdirectory (2013) via EAC
Internal URL : https://mail.yourcompany.com/OAB External URL :
https://mail.yourcompany.com/OAB
5. Set EWS virtualdirectory (2013) via EAC
Internal URL : https://mail.yourcompany.com/EWS/Exchange.asmx External URL :
https://mail.yourcompany.com/EWS/Exchange.asmx
6. Set ActiveSync virtualdirectory (2013) viaEAC
Internal URL : https://mail.yourcompany.com/Microsoft-Active-Sync
External URL : https://mail.yourcompany.com/Microsoft-Active-Sync
For 2007
1. Set AutodiscoverInternalURL using this command for every CAS server
Set-ClientAccessserver -identity -CAS1 -AutodiscoverInternalURI
https://mail.yourcompany.com/autodiscover/autodiscover.xml (for FQDN , using your CAS NLB name)
2. Create DNS record
legacy.yourcompany.com = your CAS2007 NLB (if exist)
3. Set OWA virtualdirectory (2007) via EMC
External URL = https://legacy.yourcompany.com/owa
4. Set ActiveSync (2007) via EMC
Internal URL = https://serverFQDN/Microsoft-Active-Sync <<<< Using for proxy
External URL =
https://legacy.yourcompany.com/Microsoft-Active-Sync <<<< Using for redirect
5. OAB via EMC
External URL = https://legacy.yourcompany.com/OAB
6. EWS via Exchange shell
External URL = https://legacy.yourcompany.com/EWS/Exchange.asmx
FYI

Mailbox Move Issues and Errors - Exchange 2010 to 2013

I'm trying to move mailboxes from 2010 to 2013, but I'm experiencing a lot of issues.
My move batches keep hanging (stalled) for minutes and hours on end, and I can't seem to keep them going consistently.
I have two DAG's, one for Archive boxes, and one for Primary mailboxes. Each DAG has three members with DB copies of each DB. The npdes and the clusters themselves are up and healthy. However, at random some of the DB's Content Index state will go to Failed
or SuspendedandFailed. At which point I force a catalog refresh and DB index update, and it goes to healthy.
I've created the "ContentSubmitters" AD group (and assigned it permissions), reset the Search and Host controller services on each server, and restarted the Replication service. I also deleted and recreated the Index for each DB prior to restarting
services. No dice. I've also already moved the system mailboxes over to the 2013 databases.
I'm also getting some "Transient" errors in the user move log, things like this:
Transient error ResourceUnhealthyException has occurred. The system will retry"
5/4/2014 8:43:55 AM [exmb1] The job encountered too many transient failures (60) and is quitting.
5/4/2014 8:43:55 AM [exmb1] Fatal error ResourceUnhealthyException has occurred.
Error: MigrationPermanentException: Warning: Target mailbox unlock operation was not replicated. If a lossy failover occurs after the target mailbox was unlocked, the target mailbox could remain inaccessible. Error details: The store ID provided isn‎'t an ID of an item. --> MapiExceptionNetworkError: Unable to open entry ID. ‎(hr=0x80040115, ec=0)‎ Diagnostic context: Lid: 45025 Lid: 45345 StoreEc: 0x80040115 Lid: 22894 Lid: 24942 StoreEc: 0x80040115
Any ideas would be appreciated!!!

Hi
I would suggest you to run the below command for this "My move batches keep hanging (stalled) for minutes and hours on end" issue and see the result
Get-MoveRequest -Identity "Mailbox Name" | Get-MoveRequestStatistics -IncludeReport | FL Report
Just check if the MRS health is fine by running the below command
Test-MRSHealth -Identity "CAS Server" -MonitoringContext $true | Export-CliXml "C:\temp\CAS_MRSHealth.xml" and look at the xml file to get more information
When I run the Test command against either of my CAS servers, I get: " 'EXCH1' does not have the right Exchange Server version or role required to support this operation."
Run i run that command against any of the mailbox servers, it completes and generates the XML file, but I'm not sure what I need to be looking for within that file.
The first command spits out a ton of data, here's a little excerpt:
5/5/2014 8:59:28 AM [exmb1] Transient error ResourceUnhealthyException has occurred. The system will retry
(2/60).
5/5/2014 9:00:02 AM [exmb1] The Microsoft Exchange Mailbox Replication service 'exmb1.contoso.com'
(15.0.847.31 caps:03FF) is examining the request.
5/5/2014 9:00:07 AM [exmb1] Connected to target mailbox 'Primary (072dc240-bd79-495c-b7f2-c571e8f910f2)',
database 'newmbi', Mailbox server 'Exmb1.contoso.com' Version 15.0 (Build 847.0).
5/5/2014 9:00:07 AM [exmb1] Connected to target mailbox 'Archive (812ee554-4a1e-4feb-b591-a435fcbdee16)',
database 'newarci', Mailbox server 'EXARC2.contoso.com' Version 15.0 (Build 847.0), proxy server
'EXARC2.contoso.com' 15.0.847.31 caps:1FFFCB07FFFF.
5/5/2014 9:00:07 AM [exmb1] Connected to source mailbox 'Primary (072dc240-bd79-495c-b7f2-c571e8f910f2)',
database 'exmbi', Mailbox server 'Chsexmb2.contoso.com' Version 14.3 (Build 181.0).
5/5/2014 9:00:08 AM [exmb1] Connected to source mailbox 'Archive (812ee554-4a1e-4feb-b591-a435fcbdee16)',
database 'Exarci', Mailbox server 'CHSEXARC1.contoso.com' Version 14.3 (Build 181.0)
5/5/2014 9:00:12 AM [exmb1] Request processing continued, stage LoadingMessages.
5/5/2014 9:00:36 AM [exmb1] Messages have been enumerated successfully. 6657 items loaded. Total size:
332.3 MB (348,411,982 bytes).5/5/2014 9:06:14 AM [exmb1] The long-running job has been temporarily postponed. It will be picked up
again when resources become available.

Outlook 2013, Exchange 2010 error with Rules and Alerts

Hello,
I was recently informed by a user that when they open Outlook 2013 and click Manage Rules and Alerts, they get the following message:
By the way, NO Microsoft, this information is not helpful. Anyways, I found that the same problem is happening in my Outlook as well. I do not believe it is happening to all users' accounts, and I am able to set up Rules within Outlook Web Access,
so it seems to be some local setting. I found a lot of forums suggest running the Outlook /cleanrules switch, and this did not fix the problem. Other suggestions are to delete the profile on the computer and/or uninstall outlook and reinstall it.
I don't like these solutions, as they don't point to the true source of the problem and do nothing to help avoid this problem in the future. Has anybody else had this problem and been able to fix it? We are running Exchange 2010 in our environment,
although not sure if that makes a difference or not. Any answers that do not suggest the things I have already mentioned would be greatly appreciated!

Hi,
For this issue, I recommend you ask in Office forum which is staffed by more experts specializing in this kind of problems. You might get better help there.
http://social.technet.microsoft.com/Forums/office/en-us/home?forum=outlook
Thanks for your understanding.
Best regards,
Belinda Ma
TechNet Community Support

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

Similar Messages

Maybe you are looking for