May not be able to install Exchange Server 2003 on a server that previously had Mobile Information Server installed

Article translations Article translations
Article ID: 841674 - View products that this article applies to.
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
Expand all | Collapse all

Symptoms

You may not be able to install Microsoft Exchange Server 2003 on a server that previously had Microsoft Mobile Information Server installed on it, even though Mobile Information Server has been removed.

Cause

This issue may occur when some components of Mobile Information Server are not removed.

Resolution

To resolve this issue, remove any Mobile Information Server components that are on your server, and then try again to install Exchange Server 2003. To do this, follow these steps:
  1. Remove Mobile Information Server configuration data from Active Directory directory service. To do this, follow these steps.

    Note Follow these steps only if all computers that are running Mobile Information Server have been removed from the Active Directory forest.

    Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.
    1. Run the Setup program from the Support\Tools folder on the Windows 2000 CD-ROM to install the Windows 2000 Support Tools.
    2. Click Start, point to Programs, point to Windows 2000 Support Tools, point to Tools, and then click ADSI Edit.
    3. Expand the Configuration container.
    4. Expand CN=Services.
    5. Delete the CN=Microsoft-Mobile-Information-Server object.
    6. If the server is running Mobile Information Server Carrier Edition, also delete the CN=SMSGW object.
  2. Rename the MMIS directory tree, C:\Program Files\MMIS. For example, rename "MMIS" to " MMIS2."
  3. Start Internet Services Manager. (Click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.) In Internet Services Manager, remove the following virtual directories:
    • MMISNotify
    • MMISDeviceInfo
    • OMA
    • In
    • Airweb
    • MMISver
  4. Remove the following Message Queuing queues (also known as MSMQ queues).
    Collapse this tableExpand this table
    Mobile Information Server queuesLabel
    DMI Inbound Request Queue.\Private$\DmiInboundRequestQueue
    DMI Outbound Request Queue.\Private$\DmiOutboundRequestQueue
    DMI Inbound Response Queue.\Private$\DmiInboundResonseQueue
    DMI Outbound Response Queue.\Private$\DmiOutboundResponseQueue
    SMTP Outbound MSMQ.\Private$\SmtpQueue
    Collapse this tableExpand this table
    SMS Connector queues
    (on Mobile Information Server Carrier Edition only)
    Label
    Default SMSGW Outbound Queue.\Private$\default_smsgwoutboundqueue$
    Any other SMS Connector-related queue
  5. Remove any queue that has been created during the administration of SMS Connector. It is impossible to predict the name of such queues. The name could be a name such as "mmisgenericasyncconnectorresponsequeue."

    The Mobile Information Server queues are created by Mobile Information Server while the Setup program is running. Mobile Information Server Setup also creates the Default SMSGW Outbound Queue. Other queues may be created during administration of SMS Connector. Because the queues may contain useful messages, you must manually delete these queues; they are not deleted automatically when you remove Mobile Information Server.

    To manually delete queues, follow these steps:
    1. Right-click My Computer, and then click Manage to start the Computer Management snap-in.
    2. Expand Services and Applications, expand Message Queuing, and then expand Private Queues.
    3. For each Mobile Information Server-related queue in the previous table, follow these steps:
      1. Expand a queue, and then click Queue Messages in the console tree under that queue. (Messages in the queue are displayed in the Details pane).
      2. Make sure that the queue that you are about to remove does not contain important messages. In the console tree, right-click the queue, and then click Delete.
    4. Quit the Computer Management snap-in.
  6. Start the Active Directory Users and Computers snap-in. (To start Active Directory Users and Computers, click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.)
  7. Use Active Directory Users and Computers to delete the following accounts, if they exist:
    • Exchange Event Sources Global Group
    • ENTEVENTSOURCE
    • Mobile Connectors Global Group
    • HTTP Connector
    • Message Processors Global Group
    • Message Processor
    • MIS Mobile Users Global Group
    • MIS Mobility Admins Global Group
  8. Remove MMIS registry subkeys. To do this, follow these steps.

    Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
    1. Click Start, click Run, type Regedt32, and then press ENTER to start Registry Editor.
    2. Locate the
      HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services
      key.
    3. Delete the following subkeys:
      • MobiInfo (This is for the message processor service.)
      • SMTPCONN (This is for the SMTP connector.)
    4. If the following registry subkeys exist, back them up, and then delete them:
      • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\DMI
      • HKEY_LOCAL_MACHINE\Software\Classes\Wnotify.MoExSink
  9. Restart the server, log on with an account that is in the Enterprise Administrators and Schema Admins global groups, and then try again to install Exchange Server 2003.

Properties

Article ID: 841674 - Last Review: September 3, 2013 - Revision: 2.0
Applies to
  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange Server 2003 Standard Edition
Keywords: 
kbtshoot KB841674

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com