Issue
The Migration Worker, we installed the necessary prerequisites and CMT Worker, we ran the Connectivity Tester (success) and configured Outlook profile to the migration account (member of the Full Access group)
When running migration, it fails almost immediately with the same error message: Migration Initialization Failed. The directory at C:\Program Files(x86)\Binary Tree\CMT for Exchange\Worker\Logs remains empty.
Additionally the migration worker may report a Windows fault "Common Migration Tool has stopped working".
In the worker's event viewer, we can find the following error information:
Faulting application name: CMTProxy.exe, version: 19.3.0.0, time stamp: 0x5c9e3136
Faulting module name: mfc120u.dll, version: 12.0.21005.1, time stamp: 0x524fabbd
Exception code: 0xc0000005
Fault offset: 0x0005b7f1
Faulting process id: 0x280
Faulting application start time: 0x01d514617bcec2b9
Faulting application path: C:\Program Files (x86)\Binary Tree\CMT for Exchange\Worker\CMTProxy.exe
Faulting module path: C:\windows\SYSTEM32\mfc120u.dll
Report Id: b98e625f-8054-11e9-80d3-005056af36e0
Faulting package full name:
Faulting package-relative application ID:
Also, please find attached the Report.wer file from C:\Users\<USERNAME>\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_CMTProxy.exe_50219b8cf5e705a2794ae262cfbbf4c3e63ce9_6043d7a1_0c8406eb
Version=1
EventType=APPCRASH
EventTime=132034156512144000
ReportType=2
Consent=1
UploadTime=132034156518550551
ReportIdentifier=e2afdaae-8050-11e9-80d2-005056af36e0
IntegratorReportIdentifier=e2afdaad-8050-11e9-80d2-005056af36e0
WOW64=1
NsAppName=CMTProxy.exe
Response.BucketId=c0e89675ddf7ea3b7639a8daaa3cc507
Response.BucketTable=1
Response.LegacyBucketId=1601496799619368199
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=CMTProxy.exe
Sig[1].Name=Application Version
Sig[1].Value=19.3.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5c9e3136
Sig[3].Name=Fault Module Name
Sig[3].Value=mfc120u.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=12.0.21005.1
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=524fabbd
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0005b7f1
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.272.7
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1036
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=5861
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=5861822e1919d7c014bbb064c64908b2
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=3c39
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=3c390ead1f6678e1205760b69cf3f2fc
UI[2]=C:\Program Files (x86)\Binary Tree\CMT for Exchange\Worker\CMTProxy.exe
UI[3]=Common Migration Tool has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\Binary Tree\CMT for Exchange\Worker\CMTProxy.exe
LoadedModule[1]=C:\windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\windows\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\windows\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\Program Files (x86)\Binary Tree\CMT for Exchange\Worker\BTProgressDialog.dll
LoadedModule[5]=C:\windows\SYSTEM32\ADVAPI32.dll
LoadedModule[6]=C:\Program Files (x86)\IBM\Lotus\Notes\nNOTES.dll
LoadedModule[7]=C:\windows\SYSTEM32\XmlLite.dll
LoadedModule[8]=C:\windows\SYSTEM32\VERSION.dll
LoadedModule[9]=C:\windows\SYSTEM32\mfc120u.dll
LoadedModule[10]=C:\windows\SYSTEM32\MSVCR120.dll
LoadedModule[11]=C:\windows\SYSTEM32\USER32.dll
LoadedModule[12]=C:\windows\SYSTEM32\SHELL32.dll
LoadedModule[13]=C:\windows\SYSTEM32\SHLWAPI.dll
LoadedModule[14]=C:\windows\SYSTEM32\ole32.dll
LoadedModule[15]=C:\windows\SYSTEM32\OLEAUT32.dll
LoadedModule[16]=C:\windows\SYSTEM32\MSVCP120.dll
LoadedModule[17]=C:\windows\SYSTEM32\WS2_32.dll
LoadedModule[18]=C:\windows\SYSTEM32\GDI32.dll
LoadedModule[19]=C:\windows\SYSTEM32\msvcrt.dll
LoadedModule[20]=C:\windows\SYSTEM32\sechost.dll
LoadedModule[21]=C:\windows\SYSTEM32\RPCRT4.dll
LoadedModule[22]=C:\windows\SYSTEM32\CRYPT32.dll
LoadedModule[23]=C:\Program Files (x86)\IBM\Lotus\Notes\nxmlproc.dll
LoadedModule[24]=C:\Program Files (x86)\IBM\Lotus\Notes\js32.dll
LoadedModule[25]=C:\Program Files (x86)\IBM\Lotus\Notes\NLSCCSTR.DLL
LoadedModule[26]=C:\Program Files (x86)\IBM\Lotus\Notes\nsdhelp.dll
LoadedModule[27]=C:\windows\SYSTEM32\USERENV.dll
LoadedModule[28]=C:\Program Files (x86)\IBM\Lotus\Notes\ndgts.dll
LoadedModule[29]=C:\windows\SYSTEM32\IMM32.dll
LoadedModule[30]=C:\windows\SYSTEM32\UxTheme.dll
LoadedModule[31]=C:\windows\SYSTEM32\combase.dll
LoadedModule[32]=C:\windows\SYSTEM32\NSI.dll
LoadedModule[33]=C:\windows\SYSTEM32\SspiCli.dll
LoadedModule[34]=C:\windows\SYSTEM32\MSASN1.dll
LoadedModule[35]=C:\Program Files (x86)\IBM\Lotus\Notes\MSVCP71.dll
LoadedModule[36]=C:\windows\SYSTEM32\MSVCR71.dll
LoadedModule[37]=C:\windows\SYSTEM32\MPR.dll
LoadedModule[38]=C:\windows\SYSTEM32\PSAPI.DLL
LoadedModule[39]=C:\windows\SYSTEM32\profapi.dll
LoadedModule[40]=C:\windows\SYSTEM32\MSCTF.dll
LoadedModule[41]=C:\windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[42]=C:\windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[43]=C:\Program Files (x86)\IBM\Lotus\Notes\nmailman.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Common Migration Tool
AppPath=C:\Program Files (x86)\Binary Tree\CMT for Exchange\Worker\CMTProxy.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=AB6FF81CC708CD95D8B69ACB1506EC22
Solution
Confirm 32-bit version of Outlook Professional Plus 2013 or 2016 (Office 365 ProPlus). Office Home, Workgroup or any other specialized version is not supported on any migration workstation.
Confirm Microsoft Visual C++ 2013 runtime (only x86 on Workstations) and .NET 4.5.2 are installed.
Confirm there are no Windows AD GPO's that would be operating on the Outlook install for the worker.
If all is correct, run a repair of Outlook, verify patching for Outlook/Office and try again.
Repair process
Run a repair on the Outlook installation on this worker.
Go to Control Panel
Programs...
Select the Outlook install
Select 'Change'
Select run a Repair.
Run Fixmapi.exe from Windows\System32
Load Outlook and configure new MAPI profile using the migration account(s)
Does the mailbox open?
When complete, try the migration again going to this particular worker. You can do that by highlighting this user, choosing from the notes menu while in the Notes Migrator database
Actions/other/set migration workstation.
Choose this worker and this user will go to that user specifically and then see if the migration kicks off.
If this still fails, uninstall the Notes Migrator application and Outlook then install Outlook (patch Outlook) and the Notes Migrator application. Verify the Connectivity Tester and try the migration again.
Run a migration
Contact support@binarytree.com if this does not resolve the issue
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité Cookie Preference Center