Failed to Start the Exchange Mailbox Task - MAPI Error
- 14 years ago
ISSUE: MAPI Error when starting Archiving Task
ROOT CAUSE ANALYSIS: mapi32.dll was not the correct version Enterprisevault was looking for.
TROUBLESHOOTING STEPS:
- Event ID: 3329 The task controller cannot start the following MAPI-dependent.
- ran thru solution of
Solution:
1. Browse to: c:\program files\common files\system\msmapi\1033.2. Find the file MAPISVC.INF and take note of the file size.
3. Browse to: c:\windows\system32.
4. Find the file MAPISVC.INF. Compare to the one above, they need to match. If they do not, copy the larger file over the smaller.
5. From command prompt, run the following: Fixmapi.exe
Note: This command is instantaneous and provides no confirmation that it is completed, this is normal.
6. Reboot the EV server.
If above solution does not resolve the issue
1. Browse to c:\windows\system32
2. Find msmapi32.dll and verify file size to be 134 KB
3. If msmapi32.dll is larger than 134 KB, copy msmapi32.dll from c:\program files\common files\system\msmapi\1033 folder overwriting the msmapi32.dll located in C:\windows\system32
4. Run fixmapi from command line
5. Reboot
This did not fix the issue.
Removed the esm.
This caused the windows search to complain about mapi32.dll being missing. Could the esm install a different version of the mapi32.dll
Checked the windows system folder and the mapi32.dlll was no present however a mapi32_evbal.dll did.
Renamed the file to mapi32.dll but this still didn't resolve The task failing issue.
Checked my lab and the file size was only 113 k as aopposed to the 623 of the evbk file
Copied the mapi32.dll from another server to this server.Restarted the service and now the 3329 errors are no longer but 3411 are present.
Added the closest GC to the VAC but did not fix this issue.
Added the closest GC key to the registry which fixed this issue.
Tested restoring items and items fail also we get prompted for a password.
Check add and remove program and many of the required iis component have been remove presumably during the ESM un-install.
Installed the required components and rebooted the server.
We now can restore but with prompting.
Added the ev server to the policy to push out the trusted sites.
Synch'ed the users and tested, work correctly.THANKS BRAD SISSON!!!!!