Tuesday, May 25, 2010

Home /Migration /Outlook /QMM /Quest Migration Manager /Sync / Outlook has encountered a Problem – Mailbox Migration

Outlook has encountered a Problem – Mailbox Migration

In my recent Active Directory and Exchange migration project using Quest Migration Manger (QMM), I encountered an issue during the mailbox migration.  I added a couple of mailboxes to the mailbox synchronization collection, after a few hours users started complaining that they can’t login to their mailboxes using Outlook.  There were getting the following error message:

Microsoft Office Outlook has encountered a problem and needs to close.  We are sorry for the inconvenience.  

clip_image002[4]

These mailboxes were not migrated.  They were only in the mailbox synchronization collection.  I opened these mailboxes using MFCMAPI tool (http://portal.sivarajan.com/2010/05/mailbox-and-outlook-troubleshooting.html) and  noticed that, these mailboxes have duplicate “Calendar” folder as displayed in the following screenshot:

Outlook_QMM

Since outlook was pointing to calendar (outlook today) users were not able to open the outlook.
On some other mailboxes I have seen duplicate “Sync Issues” folder.

Outlook_QMM_2

Cause:
According to Quest support professionals, they have seen duplicate calendar issue before but this is the first time they were seeing duplicate folder issue on different folders.  It may be due to other 3rd party applications such as backup and antivirus software logging into the mailbox while the data is being synchronized. You can see the details on the Quest Solution article SOL42312. 

I implemented the workaround as described in the SOL43372 article but that didn’t help me with the issue.
I was using 8.4 version of the QMM.  According to Quest, this issue will be fixed in 8.6 and they told me they can provide a hotfix for 8.5 version of the product. Unfortunately, they don’t have a fix for 8.4.  Since I had completed 70% of the migrations, I decided not to upgrade it to 8.5 or 8.6 version.

I also noticed that, this issue is happening only from one mailbox server and it is happening whenever I leave the mailboxes in the collection overnight.  It could be because of backup or antivirus scanning on the server in the night.

Workaround:
Since the issue is happening in the night, I decided to schedule the agent synchronization from 7 AM to 7 PM.  This configuration will avoid any third party software (backup, antivirus etc) logging into the mailbox while the data is being synchronized.  After that, I was able to successfully migrate mailboxes from this server. 

Other Related Articles and Blogs:

Active Directory Migration Using ADMT - http://www.sivarajan.com/admt.html

Computer Migration - Things to Consider - http://www.sivarajan.com/cm.html

User Account Migration and Merging Using ADMT - http://www.sivarajan.com/

SS

Santhosh Sivarajan

Microsoft MVP · Identity & Cybersecurity Architect

Santhosh has 30+ years of hands-on enterprise experience in Identity and Access Management, Microsoft Entra ID, Active Directory, Microsoft 365 and Zero Trust architecture. He is the author of two books on Windows Server and security, and leads consulting, assessments and training at SAG Business Group.

0 comments:

Post a Comment

Popular Posts
Workstation Trust Relationship Issue Issue: You receive the following error message, when you try to login to the domain.  The security database on the server does not have ... ADMT Service Account - Permission and Configuration The ADMT service account needs to have proper permission in source and target domains.  You don’t need to use 2 separate accounts.  You can ... My First Peek into Microsoft Exchange 2010 By Santhosh Sivarajan Before I really dive into Exchange 2010, I thought I would install and play with it first. I took some screen shots and notes during the ins... ObjectSID and Active Directory What is an objectSID in Active Directory? When a new object is created in Active Directory, Domain Controller assigns a unique value used ... AD Group Report - List Group Members in Active Directory–PowerShell Script Updated Script - http://portal.sivarajan.com/2011/10/search-ad-collect-local-admin-group.html Script #1 This script... Add Users to a Group–PowerShell Script Purpose – Add users to a group from an input file – PowerShell V2 Script.  Input file – Input file (Users.csv) contains samAccountName in... User Account Migration and Merging – Part I (ADMT) Part I - User Account Migration and Merging Using ADMT Part II - User Account Migration and Merging Using QMM pre-creating user account ... User Account Migration and Merging – Part II (Quest Migration Manager) Part I - User Account Migration and Merging Using ADMT Part II - User Account Migration and Merging Using QMM Pre-creating user account in... Delete Stale or Inactive Computer Accounts from Active Directory Here is an easy way to identify and delete inactive or stale computers in an Active Directory environment.  Using the dsquery command you c... Converting PowerShell (PS1) to EXE / Standalone Application As we know, there many applications available to convert a PowerShell file to a standalone executable file.  Based on my experience, PowerSh...