Solved

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

Posted on 2010-11-29
7
992 Views
Last Modified: 2012-05-10
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
Comment
Question by:philodendrin
  • 4
  • 2
7 Comments
 
LVL 34

Expert Comment

by:Shreedhar Ette
ID: 34235476
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
 

Author Comment

by:philodendrin
ID: 34235548
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
 

Expert Comment

by:j_crow1
ID: 34559169
I am having the same issues, was this ever resolved?
0
6 Surprising Benefits of Threat Intelligence

All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

 

Accepted Solution

by:
philodendrin earned 0 total points
ID: 34606817
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
 

Expert Comment

by:j_crow1
ID: 34607681
Thanks.
0
 

Author Comment

by:philodendrin
ID: 34631558
Thanks for all who tried... wound-up fixing this one on my own.
0
 

Author Closing Comment

by:philodendrin
ID: 34675544
Answered on my own... see above.
0

Featured Post

Get up to 2TB FREE CLOUD per backup license!

An exclusive Black Friday offer just for Expert Exchange audience! Buy any of our top-rated backup solutions & get up to 2TB free cloud per system! Perform local & cloud backup in the same step, and restore instantly—anytime, anywhere. Grab this deal now before it disappears!

Join & Write a Comment

Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
This video discusses moving either the default database or any database to a new volume.

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now