Outlook cannot connect after mailbox move from Exchange 2007 to 2013
I am in the middle of migrating an Exchange Server 2007 to 2013. Everything went fine up until I moved the first mailbox. I can access the mailbox via OWA, but not Outlook 2010. When I checked the account settings, the server is incorrect. It shows [email protected]
If I manually enter the name of the Exchange 2007 server, it changes to the Exchange 2013 server, as it should. I save the settings, open Outlook, the connection fails, and the server setting is changed to [email protected]
I then ran the Microsoft Connectivity Analyzer. There are 2 lines which caught my attention:
AutoDiscoverInternalRpcClientServer
[email protected]
AutoDiscoverHomeMdbDn
/o=mydomainMail/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=[email protected]/cn=Microsoft Private MDB
I've checked and rechecked everything and can't seem to locate my error.
Any thoughts? Thanks.
Totally correct!
If you don't plan to maintain Outlook then you plan to fail :(
Additional links etc are in here:
http://blogs.technet.com/b/rmilne/archive/2013/07/18/patching-exchange-don-t-overlook-outlook.aspx
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter: LinkedIn:
Facebook:
XING:
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.
Similar Messages
-
Concurrent mailbox moves from Exchange 2007 to 2013
We are in the process of migrating from Exchange 2007 to Exchange 2013. We have about 200 mailboxes and we want to move them in groups of 40-50 at a time. I am trying to get more then 1 mailbox to actually sync to the new database at once.
I start the batch with 49 mailboxes but only 1 mailbox is showing any progress when I go to details. They all have a status of "syncing" but only one has any "items synced".
I have run multiple articles about increasing concurrent migrations from 2007 to 2010 and 2010 to 2013 and they all mention going to MsExchangeMailboxReplication.exe.config on the destination server and setting the “MaxActiveMovesPerTargetMDB" value
to something larger. By default 2013 has it set to 20 would should be more than enough for me. However despite this setting I still only see 1 mailbox syncing at a time.
Is there someplace I should be making a similar change on the 2007 box? I can't find a file with that name so I am not sure if there is something to change or if it's even needed.
Why is this not working? Any help is much appreciated. Thanks!Outlook will show the infamous login popup and users will not be able to access Exchange 2013 Public Folders.
You can check the Outlook Clients version in Exchange Management Shell with Get-LoginStatistics (ex. Outlook 2010):
Get-Logonstatistics | select-object username,clientversion | where {$_.clientversion -gt "14.0*" -AND $_.clientversion -lt "14.0.6117.5001"}
Step by Step Screencasts and Video Tutorials -
Inter-Org Mailbox moves from Exchange 2007 to Exchange 2013
G'Day All,
Is it possible to move Exchange 2007 mailboxes to Exchange 2013 in a different forest? Both environment has all the required patches and service packs.
There is a two way trust, and I don't want to introduce Exchange 2010 CAS in the source forest if I don't need to.
I have read the following article http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/ but it is not clear what is the required to setup in Exchange 2007. I have read many other articles to do with Exchange 2013 mailbox moves, endpoints,
etc, but non of them is clear of how does it work having Exchange 2007 source.
Thanks in advance.Hi Atonal,
Could you please take a look at this technet blog that has been well elaborated about your concern :
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
The blog provides step-wise assistance while you are planning to move from exchange 2007 to 2013.
Here is another library available from technet team that includes all the terms while preparing mailboxes for cross-forest move request : http://technet.microsoft.com/en-us/library/ee633491%28v=exchg.150%29.aspx
Alternatively, you can checkout this proficient application (http://www.exchangemigrationtool.com/) in order to avoid any interruption and proceed hassle-free migration from exchange 2007 to 2013. -
Mailbox Move from Exchange 2007 to Exchange 2013
I was surpprised to see that when I move mailboxes from exchange 2007 to Exchange 2013, that the mailbox being moved does not get disconnected during the move process (client Outlook connection). That is great news but supprising to me. I know
moving from 2010 - 2013 or 2013 - 2013 is a background process. Did something change with this recently or has it always been this way? Does the mailbox move flag inside the mailbox just jet ignored?
ThanksWhen you do a mailbox move it stays connected during the initial sync. Once the initial sync is performed, there is another phase where it completes the mailbox move (basically updates some AD attributes) when this piece happens users will not be able
to access their mailboxes.
You can control this behavior by setting the SuspendWhenReadyToComplete
switch either by command line when creating the move request via the EMS
https://technet.microsoft.com/en-us/library/dd351123%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
Or if you are doing this via the the EAC select "Manually Complete the batch" option before starting the move.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread -
Can only access emails through OWA after migration from exchange 2007 to 2013
can only access emails through OWA after migration from exchange 2007 to 2013, in other words unable to access mails through outlook or from other Applications services.
needed RCA ... plz help..Hi,
From your description, you can send and receive messages only when you use OWA after migration from Exchange 2007 to Exchange 2013. If I have misunderstood your concern, please let me know.
In your case, I recommend you create a new test mailbox in your Exchange 2013 and check if you can send and receive messages on Outlook. If yes, it is recommended to create a new profile to solve this issue.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support -
Migration from Exchange 2007 to 2013 gives error "Failed to communicate with the mailbox database'
I have been trying to migrate several databases from Exchange 2007 to Exchange 2013. The migration started successfully, and many of the mailboxes moved successfully (about 70). The remaining mailboxes, failed. Looking deeper, we found a few issues; The
two 2013 Mailbox servers were on different versions. The Server had run out of disk space, and the NIC drivers needed to be updated.
Now when we try to migrate a mailbox that had failed in the earlier batch, we get the following error:
Data migrated:
Migration rate:
Error:
MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80040115, ec=-2147221227) Diagnostic
context: ...... Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 501 Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam:
0x0 Msg: EEInfo: NumberOfParameters: 4 Lid: 8856 dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp Lid: 8856 dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: <Server
FQDN> Lid: 12952 dwParam: 0x0 Msg: EEInfo: prm[2]: Long val: 3749909585 Lid: 12952 dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662 Lid: 45169 StoreEc: 0x824
Lid: 50544 ClientVersion: 15.0.847.32 Lid: 52080 StoreEc: 0x824 Lid: 44273 Lid: 49064 dwParam: 0x1 Lid: 37288
StoreEc: 0x6AB Lid: 49064 dwParam: 0x2 Lid: 59431 EMSMDB.EcDoConnectEx called [length=203] Lid: 51239 EMSMDB.EcDoConnectEx exception [rpc_status=0x6D9][latency=0]
Lid: 62184 Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 3460 Lid: 12696 dwParam: 0x0 Msg: EEInfo:
Generation Time: 0414-04-07T16:32:03.2100000Z Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 2 Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 1753 Lid: 9624
dwParam: 0x0 Msg: EEInfo: Detection location: 501 Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 4 Lid: 8856
dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp Lid: 8856 dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: <Server FQDN> Lid: 12952 dwParam: 0x0 Msg: EEInfo:
prm[2]: Long val: 2767313664 Lid: 12952 dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662 Lid: 59505 StoreEc: 0x824 Lid: 50544 ClientVersion:
15.0.847.32 Lid: 52080 StoreEc: 0x824 Lid: 36081 Lid: 51152 Lid: 52465 StoreEc: 0x80040115
Lid: 60065 Lid: 33777 StoreEc: 0x80040115 Lid: 59805 Lid: 52487 StoreEc: 0x80040115 Lid: 19778 Lid: 27970
StoreEc: 0x80040115 Lid: 17730 Lid: 25922 StoreEc: 0x80040115
All of the issues listed above have been corrected, and all of the databases are mounted. Users are able to send and receive mail, but I can not migrate mail using the Migration Batch utility.
The destination server is a Hyper-V Guest running Server 2012, SP1, and Exchange 2013
The Source Server is Running Exchange 2007.
I have tried doing a test move to another destination server that is also Server 2012, and Exchange 2013, and the migration also failed.
I would appreciate any help you can give me!
Thanks,
JonAny update if you have resolved the issue.
Not similar, but this thread can be helpful while you migrate the mailboxes from exchange 2007 to 2013. Please check :http://social.technet.microsoft.com/Forums/exchange/en-US/721f0ae4-623a-4b02-adaf-f561d86c0426/move-mailboxes-and-public-folders-from-exchange-2007-to-exchange-2013?forum=exchangesvrdeploy&prof=required -
Issue moving remote user from exchange 2007 to 2013
have moved over 60 people so far from exchange 2007 to 2013, it was going well with no major problems.
during migration I have created a DNS setting called legacy.mydomain.com, and it points to the old exchange server, while mail.mydomain.com points to the new exchange server.
outlook was working connecting to both servers, and OWA was working on both servers.
couple of remote users who connect via SSL-VPN and outlook 2010 had issues connecting, but as soon as I moved them to 2013 exchange they connected without vpn using outlook anywhere.
but - I have one remote user who even though the mailbox move to the new 2013 server was successful, their outlook still points to the 2007 exchange server.
if I try creating a new profile in outlook 2013, it fails because it cannot contact exchange server, even when ssl-vpn is running.
when I started troubleshooting I found lots of spyware on his laptop, symantec had been blocking some trojans, obviously he had downloaded something he shouldnt have.
could this have caused my outlook connectivity issue?
I ran malawarebytes, and it shows clean now, but still unable to get his outlook to connect.
I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
any suggestions?I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
Hi,
Have you done this step? Sometimes moving mailbox to another database can auto-fix problems.
According to your description, I know that all migrated mailboxes work well except a specific user. I notice that the user's laptop has a lots of spyware, and symantec has been clocking some trojans.
Please try to logon OWA to check whether this user works.
If works in OWA, it seems that the mailbox has been migrated to 2013 successfully.
Generally, re-creating profile can fix this issue. Unfortunately, you have tried it and failed.
Please try to run Outlook under safe mode to avoid AVs and add-ins.
Thanks
Mavis Huang
TechNet Community Support -
How to migrate from exchange 2007 to 2013 step by step tutorials please
Hi
I am running Windows Server 2008 standard, with exchange 2007 SP2 on it.
We have 800 mailbox in total
Our domain controllers are
Win2012 R2 and I would like to upgrade to Exchange 2013 on Windows server 2012 R2.
I am running a VM, on VMware environment, so my Windows 2012 R2 is a VM.
Is there a website or document that explains in detail, step by step how to upgrade from 2007 to 2013.
I currently only have 1 exchange server 2007, with all the roles on the one server. I would like to keep that same as
well with exchange 2013.
ThanksExchange server deployment assistant is always a good service provider to achieve this task as it simply ask few questions about your current environment and proceed further accordingly.
You can refer to this blog explained by technet team that will assist you further to gather more information in depth : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Moreover, to avoid the interruptions and proceed a hassle-free migration from exchange 2007 to 2013, this application (http://www.exchangemigrationtool.com/) could also be a good approach to accomplish
migration task in more secure way. -
Hello, everyone, my name is rafl
I have a problem with exchange 2013 active sync.
I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
(legacy.domain.com)
the process of moving mailboxes successfully without error.
Access OWA for exchange 2007 and exchange 2013 is running normally
access mail from Outlook running normally
Certificate request has been installed and has no problem with it
The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
user mailboxes are still on exchange 2007 is not problematic.
only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
any ideas for this problem, and what should I check on the exchange server ..?i have run the activesync test connectivity and get some error :
Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 3091 ms.
Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21072 ms.
Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21049 ms.
I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server" -
OWA still redirects to Exchange 2007 (legacy) after mailbox-move to Exchange 2013
Hi,
I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.
We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.
All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa
url) also redirects me to https://legacy.domain.com/owa just fine.
HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.
Anyone any tips where to search?
Many thanks in advance.
Best regards and many thanks in advance, Eric VegterThis seems to be an outstanding issue.
We just performed a fresh install of Exchange 2013 on a Windows Server 2012 R2 operating system. We're migrating from our existing Exchange 2007 server. At the moment we have everything properly setup in a co-existence state. All we lack is to complete the
migration of our mailboxes from the 2007 DB to the 2013 DB.
In performing the first mailbox move, to test the migration process and make certain mail flows as expected, we noticed this same problem. Before reading through this thread, I was able to assign Full Access to a delegate user and then perform the "Open
Mailbox" feature from a 2013 user's account. This was successful in opening the mailbox within OWA 2013. However, I still could not access the account by simply logging into the Outlook Web App. It would login, then proxy back to OWA 2007 with the message,
"Use the following link to open this mailbox with optimal performance:
http://mail.domainname.com/"
After reading about cycling the OWA app pool, I immediately tried it as a workaround and it worked. It is a little frustrating going about it in this way. Hoping to see more activity on this thread.
-Lorne -
Public Folder Migration from Exchange 2007 to 2013 fails RelinquishedWlmStall budget limitations
I have been trying to migrate approx 50 public folders from Exchange 2007 to Exchange 2013 for several months. I have followed every link I can find on how to do the migration properly. It will stay in a queued state for hours until the MRS is
restarted. It will then start copying messages. After reaching 28% I get RelinquishedWlmStall as Status Detail. Running the Get-PublicFolderMigrationRequestStatistics -IncludeReport | fl command I get the following: (truncated)
Status : InProgress
FailureTimestamp :
IsValid : True
ValidationMessage :
OrganizationId :
RequestGuid : ff4af794-f31e-4334-959f-7d6c4ccbe310
RequestQueue : PublicFolders
ExchangeGuid : b12c1f83-c4ae-46bb-a26a-0422d90800e4
Identity : eddf983d-5827-4a2a-98ef-820321ebebd0\ff4af794-f31e-4334-959f-7d6c4ccbe310
DiagnosticInfo :
Report
4/23/2015 8:49:37 AM [pionexxxx] Request processing started.
4/23/2015 8:49:37 AM [pionexxxxx] Cleared sync state for request
00000000-0000-0000-0000-000000000000 due to 'CleanupOrphanedMailbox'.
4/23/2015 8:49:38 AM [pionexxxxxx] Stage: CreatingFolderHierarchy. Percent complete:
10.
4/23/2015 8:49:38 AM [pionexxxxxx] Initializing folder hierarchy from mailbox '': 50
folders total.
4/23/2015 8:49:38 AM [pionexxxx] Folder creation progress: 0 folders created in
mailbox 'b12c1f83-c4ae-46bb-a26a-0422d90800e4'.
4/23/2015 8:49:38 AM [pionexxxxx] Warning: Failed to find or link recipient object
'FF-D5-EF-1A-0A-95-D7-4B-89-02-A6-9E-DA-4D-23-4B' in active directory for mail
enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes' with EntryId '00-00
00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-C3-C1-30-22-E0-BE-4E
98-03-B9-14-4F-B4-12-C1-00-00-00-0F-C3-4C-00-00'. This folder can be linked
manually by running Enable-MailPublicFolder cmdlet after the migration completes.
4/23/2015 8:49:39 AM [pionexxxx] Warning: Failed to find or link recipient object
'D8-46-09-BE-0B-3D-6E-4A-95-10-8F-C5-AA-0B-88-50' in active directory for mail
enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes/CashRec/Inventory'
with EntryId '00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-
3-C1-30-22-E0-BE-4E-98-03-B9-14-4F-B4-12-C1-00-00-00-12-6A-F5-00-00'. This folder
can be linked manually by running Enable-MailPublicFolder cmdlet after the
migration completes.
4/23/2015 8:49:39 AM [pionexxxx] Warning: Failed to find or link recipient object
'A6-12-DA-05-7D-21-DE-44-90-61-64-23-8C-62-41-F4' in active directory for mail
enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes/CashRec/Ulysses'
with EntryId '00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-
3-C1-30-22-E0-BE-4E-98-03-B9-14-4F-B4-12-C1-00-00-00-0F-C3-7C-00-00'. This folder
can be linked manually by running Enable-MailPublicFolder cmdlet after the
migration completes.
4/23/2015 8:49:40 AM [pionexxxx] Warning: Failed to find or link recipient object
'96-76-90-F1-A5-B7-DB-41-A7-A3-D6-8D-86-AE-45-A5' in active directory for mail
enabled public folder 'Public Root/IPM_SUBTREE/CSR Schedule' with EntryId '00-00-00
00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-C3-C1-30-22-E0-BE-4E-98
03-B9-14-4F-B4-12-C1-00-00-00-0E-34-FF-00-00'. This folder can be linked manually
by running Enable-MailPublicFolder cmdlet after the migration completes.
4/23/2015 8:49:40 AM [pionexxxx] Warning: Failed to find or link recipient object
'82-72-47-AA-D7-68-85-4C-91-92-41-45-8A-20-EA-6D' in active directory for mail
enabled public folder 'Public Root/IPM_SUBTREE/DC 24 Hr Schedule' with EntryId '00-
0-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-85-62-89-2A-52-C3-92-
5-93-F8-5A-6F-56-5D-D1-D4-00-00-00-00-27-37-00-00'. This folder can be linked
manually by running Enable-MailPublicFolder cmdlet after the migration completes.
4/23/2015 8:49:41 AM [pionexxxx] Folder hierarchy initialized for mailbox
'b12c1f83-c4ae-46bb-a26a-0422d90800e4': 46 folders created.
4/23/2015 8:49:41 AM [pionexxxx] Stage: CreatingInitialSyncCheckpoint. Percent
complete: 15.
4/23/2015 8:49:41 AM [pionexxxx] Initial sync checkpoint progress: 0/50 folders
processed. Currently processing mailbox 'b12c1f83-c4ae-46bb-a26a-0422d90800e4'.
4/23/2015 8:49:42 AM [pionexxxx] Initial sync checkpoint completed: 46 folders
processed.
4/23/2015 8:49:42 AM [pionexxxx] Stage: LoadingMessages. Percent complete: 20.
4/23/2015 8:49:43 AM [pionexxxx] Messages have been enumerated successfully. 40607
items loaded. Total size: 149 MB (156,253,810 bytes).
4/23/2015 8:49:43 AM [pionexxxx] Stage: CopyingMessages. Percent complete: 25.
4/23/2015 8:49:43 AM [pionexxxx] Copy progress: 0/40607 messages, 0 B (0
bytes)/149 MB (156,253,810 bytes), 11/50 folders completed.
4/23/2015 9:04:37 AM [pionexxxx] Stage: CopyingMessages. Percent complete: 28.
4/23/2015 9:04:37 AM [pionexxxxx] Copy progress: 3660/40607 messages, 7.015 MB
(7,355,409 bytes)/149 MB (156,253,810 bytes), 11/50 folders completed.
4/23/2015 9:04:37 AM [pionexxxx] Relinquishing job because of large delays due to
unfavorable server health or budget limitations.
ItemsTransferred : 3660
PercentComplete : 25
4/23/2015 9:04:37 AM [pionexxxx] Relinquishing job because of large delays due to
unfavorable server health or budget limitations.
It never tries to restart. Can anyone please help? The server checks for health all come back ok. I will be more than glad to include further information.Hi,
Basic on the error message, I notice that public folder migrate slow and display that “Relinquishing job because of large delays due to unfavorable server health or budget limitations” .
If I misunderstand your concern, please do not hesitate to let me know.
Since it is just slow and not failing, please do not stop the batch, it might connect to another server for sync.
Meanwhile, please refer to below link so that get details about Exchange Online migration performance and best practices:
https://technet.microsoft.com/library/dn592150(v=exchg.150).aspx
If the issue persists, please collect the relevant migration report for further troubleshooting.
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 -
Public Folder Migration from Exchange 2007 to 2013
Hi Guys,
I have a general Exchange 07-13 migration question about migrating the PF's and System Folder Information, I read somewhere that the SystemFolder info doesn't come across, can someone shed some light on this for me please?
Thanks,
RayHi Ray,
Free/Busy information is stored in system public folder. If you want to decommission the Exchange 2007 Server, you need to add the replicas to Exchange 2013 Server.
What's more, if the users use Outlook 2003, they will rely on the Free/Busy folders. If the users are using Outlook 2007 or newer, then Outlook utilizes something called the Availability Service and no longer relies on the Free/Busy folder.
Please refer to the following article to migrate public folders from Exchange 2007 to Exchange 2013.
Migrate Public Folders to Exchange 2013 From Previous Versions
http://technet.microsoft.com/en-us/library/jj150486.aspx
Besides, here is a helpful thread for your reference.
move/migrate Public Folder from Exchange 2007 to Exchange 2010
http://social.technet.microsoft.com/Forums/exchange/en-US/44b29a93-0149-4734-8e19-6679ad7701ce/movemigrate-public-folder-from-exchange-2007-to-exchange-2010?forum=exchange2010
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support -
I have moved a handful of mailboxes from my Exchange 2007 server to my new Exchange 2013 server. When the users logon to Outlook, usually Outlook 2007 Pro, they have a new default Contacts folder and Junk Email folder that are empty. I
have to copy all the user's contacts into the new default folder and delete the old one. Not sure why this is happening. Any information would be appreciated. Thanks.Are you sure your Outlook 2007 is compatible with Exchange 2013?
http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
http://support.microsoft.com/default.aspx?kbid=2687404
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." -
Multiple eventlog errors after mailbox-move to Exchange SP1
After a mailbox move completes on a Exchange 2013 SP1 server, multiple errors are logged in the eventlog. I opened a ticket with MS Support and they confirm this is a bug in SP1, but the moves itself aren't affected. They state the errors can be ignored.
About 10 error per move are being logged.
These are the errors occurring after completion of a mailbox move:
Event 1003:
An asynchronous Microsoft Exchange Server Information Store task has not handled an Exception gracefully. Exception text is (Microsoft.Exchange.Server.Storage.Common.StoreException: ErrorCode: NotSupported, LID: 43296 - Invalid counter range allocation at
this time.
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn
nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache, Boolean& needNewGlobCountSet, UInt64& globCount)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn
nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateChangeNumberCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.GetNextChangeNumber(Context context)
at Microsoft.Exchange.Server.Storage.LogicalDataModel.Folder.Save(Context context)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.Save(Context context)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskContext.EndTaskRequest(Boolean commitTransaction, Boolean pulseOnly)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.RunMailboxTaskStep(MailboxTaskContext mailboxTaskContext, QueueItem queueItem, Func`1 shouldTaskContinue)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.TaskExecutionWrapper`1.<>c__DisplayClass6`1.<WrapExecute>b__5(TaskExecutionDiagnosticsProxy diagnosticContext, TTaskContext taskContext, Func`1 shouldCallbackContinue)).
Event 1050:
Global counter allocation in mailbox 3add23e8-7a32-4fb5-bc32-f5b1eae7f98c on database 0afbb5dc-b967-4ebd-acb0-15f85b8bad53 by source MailboxTask during operation 28 on call stack at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context
context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache, Boolean& needNewGlobCountSet, UInt64&
globCount)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn
nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateChangeNumberCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.GetNextChangeNumber(Context context)
at Microsoft.Exchange.Server.Storage.LogicalDataModel.Folder.Save(Context context)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.Save(Context context)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskContext.EndTaskRequest(Boolean commitTransaction, Boolean pulseOnly)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.RunMailboxTaskStep(MailboxTaskContext mailboxTaskContext, QueueItem queueItem, Func`1 shouldTaskContinue)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.TaskExecutionWrapper`1.<>c__DisplayClass6`1.<WrapExecute>b__5(TaskExecutionDiagnosticsProxy diagnosticContext, TTaskContext taskContext, Func`1 shouldCallbackContinue)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.WorkerTaskCallback(TaskExecutionDiagnosticsProxy diagnosticsContext, Func`1 shouldCallbackContinue)
at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.WorkerTaskCallback(TaskExecutionDiagnosticsProxy diagnosticsContext, MailboxTaskQueue mailboxTaskQueue, Func`1 shouldCallbackContinue)
at Microsoft.Exchange.Server.Storage.Common.Task`1.Invoke()
at Microsoft.Exchange.Server.Storage.Common.SingleExecutionTask`1.Invoke()
at Microsoft.Exchange.Server.Storage.Common.Task`1.<Worker>b__0()
at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch[T](TryDelegate tryDelegate, GenericFilterDelegate filterDelegate, GenericCatchDelegate catchDelegate, T state)
at Microsoft.Exchange.Server.Storage.Common.WatsonOnUnhandledException.Guard(IExecutionDiagnostics executionDiagnostics, TryDelegate body)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
is temporary not allowed.Here's the technical descpription from MS support:
Description of problem: “During the mailbox move finalization stage the Store move is finalized followed by MRS move. In this state MRS executes MRS specific functionality. The state might take
a pretty long time in some cases. During this state the destination mailbox cannot be changed. The defensive code on the global counters depicts that the task with task ID 28: TaskTypeId.PropertyPromotionBootstrap is trying to allocate new global counter values
as seen in the event below.”
This is not a critical issue, and the production team also suggest safely ignore this warning, also they are now making progress to fix this issue, hoping to release the solution in the next CU or SP.
Frank. -
Exchange 2013 CAS incorrectly proxying after mailbox move to Exchange 2013
Hi,
I am moving Exchange 2010 mailboxes to Exchange 2013 SP1 in production. When I move 2010 mailbox Outlook, OWA works fine right after the move but ActiveSync (HTTPProxy log shows
on CAS 2013 server that it is still re-directing it to Exchange 2010 CAS servers). Exchange 2013 CAS server ActiveSync takes hours before it starts to see that mailbox is moved to Exchange 2013. I am certain it is not ActiveDirectory replication since all
other clients are working.
This time I move another user this time it did not work for 3.5hrs. I had to reboot Exchange 2013 CAS server after that it worked.
There is must be something that is not refreshing on Exchange 2013 CAS server.
Is there anything I can do right after the move to make it quick, I can not re-start server after every mailbox move. Currently we are in Pilot mode and only moving few
mailboxes at a time.
Thanks,
RamanHi,
I am moving Exchange 2010 mailboxes to Exchange 2013 SP1 in production. When I move 2010 mailbox Outlook, OWA works fine right after the move but ActiveSync (HTTPProxy log shows
on CAS 2013 server that it is still re-directing it to Exchange 2010 CAS servers). Exchange 2013 CAS server ActiveSync takes hours before it starts to see that mailbox is moved to Exchange 2013. I am certain it is not ActiveDirectory replication since all
other clients are working.
This time I move another user this time it did not work for 3.5hrs. I had to reboot Exchange 2013 CAS server after that it worked.
There is must be something that is not refreshing on Exchange 2013 CAS server.
Is there anything I can do right after the move to make it quick, I can not re-start server after every mailbox move. Currently we are in Pilot mode and only moving few
mailboxes at a time.
Thanks,
Raman
Does simply recycling the ActiveSync app pool speed things up?
Also, I would recommend installing CU6 instead of SP1.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.
Maybe you are looking for
-
After upgrading to ios6 my iphone will not open .xls files in emails with the default viewer. Is there a fix for this? The same emailed .xls files still open on my ipad using ios5 while viewing email like they did on my iphone prior to upgrading. I h
-
Installation 11.1.2 (32 bit binaries) on win 64 bit server
Hi, I downloaded 11.1.2 and extarcted in one folder. double click on InstallTool.cmd---> error "windows cannot find 'D:Hyperion11.1.2\jre\winAMD64\1.6.0\bin\java'. Make sure you typed the name correctly and try again. to search for a file, click the
-
Testing ha-nfs in two node cluster (cannot statvfs /global/nfs: I/O error )
Hi all, I am testing HA-NFS(Failover) on two node cluster. I have sun fire v240 ,e250 and Netra st a1000/d1000 storage. I have installed Solaris 10 update 6 and cluster packages on both nodes. I have created one global file system (/dev/did/dsk/d4s7)
-
Application server connection issue with jdev
Hi, we have a fusion application instance, deployed in amazon cloud. I am able to connect to this instance/console using the browser. I am able to login to weblogic - console, so credentials and everything is correct, now when I am giving same inform
-
Is the portal "dead"? What comes after EP 6.0? Rumours...
In the last weeks I have heard quite a few times from other customers and also from more or less "internals" that there will be no new development on the Portal side. I´m aware that EP 6.0 is supported until the end of the maintenance of NW 7.0, I´m