Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1012
  • Last Modified:

CDO MAPI 1.2.1 Will not Install on Server 2003 That Previously had Exchange Server 2003 Management Tools Installed

I am trying in vain to install Blackberry Enterprise Server Express for Exchange Server 2007 on a Server 2003 Server that previously had Exchange 2003 Management Tools installed. I successfully removed the Exchange 2003 Management Tools, using add/remove programs, but there seems to be a residual side effect. When I now try to install the MS MAPI CDO 1.2.1 package, it acts like it installs (says it's successful), but never really does. There's no evidence of it in add/remove programs and the mapi and cdo files don't exist. Plus, Blackberry tech. support confirmed that it's not installing. They think it's a registry issue, but don't know how to fix. I'm stumped. It's driving me nuts. Anyone have any ideas?
0
philodendrin
Asked:
philodendrin
  • 4
  • 2
1 Solution
 
Shreedhar EtteCommented:
Hi,

Verify that the following files are not present in C:\Windows\System32
(or any other directory in the path):
CDO.DLL
EMSABP32.DLL
EMSMDB32.DLL
EMSUI32.DLL
EMSUIX32.DLL
GAPI32.DLL
MAPISP32.EXE
MSPST32.DLL
WMSUI32.DLL
- Run FixMapi.exe (in C:\Windows\System32).
- Install the MAPI and CDO client download.

Hope this helps,
Shree
0
 
philodendrinAuthor Commented:
No luck. The last six files were present in c:\program files\ExchangeMapi. I renamed them to .old, ran fixmapi.exe, and then the MAPI and CDO download... it runs through the install lightning fast and says "successful" but installs nothing.

Very frustrating.  
0
 
j_crow1Commented:
I am having the same issues, was this ever resolved?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
philodendrinAuthor Commented:
I did finally resolve it by removing the registry keys related to Exchange 2003. Follow Microsoft KB833396.

Once the keys are removed, restart, remove the CDO package from add/remove programs if it's there. Make sure no MAPI files are present on the server. If there are, rename them all to .old.

Reinstall the CDO MAPI package. It should fully install as long as the ESM is gone, the old MAPI files are gone, and the registry keys are gone.
0
 
j_crow1Commented:
Thanks.
0
 
philodendrinAuthor Commented:
Thanks for all who tried... wound-up fixing this one on my own.
0
 
philodendrinAuthor Commented:
Answered on my own... see above.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now