Article ID: 277845 - View products that this article applies to.
This article was previously published under Q277845
This article has been archived. It is offered "as is" and will no longer be updated.
This article is part two of a two-part article that contains the Release Notes for Microsoft Exchange 2000 Server. To see part one, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/277844/ )Exchange 2000 Release Notes, part I
The public folder inter-organizational replication tool only works for MAPI public folder treesThe public folder inter-organizational replication tool consists of two applications, one to configure replication (Exscfg.exe), and one to use with Exchange (Exssrv.exe). These tools are provided on the Microsoft Exchange 2000 Server CD in the Support/Exchsync folder. The two applications that make up the public folder inter-organizational replication tool only work for the default MAPI public folder tree.
No quota warning is sent for general purpose public folder tree foldersAll new public folder tree folders you create, that exist outside of the default MAPI public folder hierarchy, are called general purpose public folder trees. If you set the Issue Warning At (kb) option on a general purpose public folder tree, no warning message will be sent to the administrator if the posting limit is met or exceeded. In addition, after the quota is reached, new items cannot be created.
Issues with alternate public folder hierarchies in a mixed environmentIn Exchange 2000, you can create new public folder hierarchies, and each folder hierarchy can be represented by its own database in Web Storage System. However, the alternate public folder databases are not replicated in a mixed environment if the replication messages are sent at any point through an Exchange Server 5.5 Internet Mail Connector. Additionally, mail will not be delivered to a public folder in an alternate public folder hierarchy if the public folder does not have a replica in your local site or administrative group, and if your sites use any Exchange Server 5.5 connectors.
Adding non-mail-enabled users or groups to a public folder ACL hides contentIf you add an access control list (ACL) on a MAPI public folder hierarchy that grants access to a user or group that is not mail-enabled, and the hierarchy is replicated to an Exchange Server 5.5 computer, users will not be able to see the contents of the MAPI public folder. To allow users to see the contents of the MAPI public folder hierarchy, remove the non mail-enabled user from the ACL.
To check permission consistency:
Public folder store replication settings not preservedAfter upgrading a public folder server from Exchange Server 5.5 to Exchange 2000, customized replication schedules and limit setting are lost. If you configured your Exchange Server 5.5 computer to use the customize replication settings of Replicate always interval or Replication message limit, you will need to manually reset these settings in Exchange System Manager.
To reset replication limits:
Limiting the creation of top-level public foldersBy default, all users in the Exchange Organization can create top-level public folders. You can manually change these permissions in ADSI Edit.
To deny all users the right to create top-level folders:
Only set public folder ACLs in Exchange System ManagerAlthough Exchange 2000 allows you to set security on public folders in the public folder hierarchy and using Exchange System Manager, Outlook, and the Windows 2000 version of Windows Explorer, the tools are not interchangeable. This is because Windows Explorer uses the Windows 2000 access control list (ACL) format to set security permissions on the MAPI public folder hierarchy, and Exchange System Manager and Outlook use the MAPI ACL format. Exchange Web Storage System can correctly interpret both ACL formats, but the tools are not interchangeable. For this reason, you should only use Exchange System Manager when editing security on the MAPI public folder hierarchy. This problem does not exist on general purpose or application folder hierarchies. For example, if you originally use Windows Explorer to set permissions on a public folder, and then try to use Outlook or Exchange System Manager to change the settings, you will not be able to change public folder security until you follow the work around steps provided below. Then you should only use Exchange System Manager to set ACLs on public folders. If the folder in question is a subfolder of Public Folders (Public Folders\TopLevelFolder), complete the following steps so that Exchange System Manager can be used to modify permissions. To allow ACLs to be set in Exchange System Manager:
Routing and connectors
Do not use some characters in connector display names in pure Exchange 2000 administrative groups in mixed-mode rganizationsIf you create an SMTP, X.400, or Routing Group Connector in a new pure Exchange 2000 administrative group and the Exchange organization is in mixed-mode, the connector name can include only US ASCII alpha-numeric characters, embedded spaces, one or more of the following characters: !"%&()+-,./:<>=?@_|, and some of the upper ASCII diacritical characters. This restriction does not apply if the administrative group previously contained Exchange Server 5.5 computers. If you have already created a connector with restricted characters in the name, you can safely delete it, and then recreate it using only the allowable characters.
If it is necessary for you to include characters outside this range in the names of SMTP, X.400, or Routing Group Connectors, it is possible to configure Exchange 2000 to support this. Use a directory editor, such as ADSI Edit or LDP.exe, to modify the legacyExchangeDN attribute on each connector with restricted characters in its name.
First, discover the new legacyExchangeDN value to be set on the connector by using your directory editor to read the attributes of the connector from an Exchange Server 5.5 directory service or from the Exchange 2000 Site Replication Service. The value you need to copy is contained in the Obj-Dist-Name attribute on the connector.
Next, use your directory editor to modify the legacyExchangeDN attribute of the connector in Windows 2000 Active Directory. Replace the existing value of this attribute with the new value obtained from the previous step. After a period of time governed by Active Directory replication latency and Exchange 2000 directory caching, mail will be able to flow over this connector. To reduce this period, perform the modification on an Active Directory that is used for configuration information by one of the Exchange 2000 servers hosting this connector.
Connector restriction checking is disabled by defaultIf you need to apply a distribution list-based restriction to a connector, you must manually enable the checking of these restrictions. Restriction checking is controlled by a registry key that must be set on the Exchange 2000 bridgehead that is the source for the connector being checked. To enable restriction checking, in the following registry key, create a REG_DWORD key, name it CheckConnectorRestrictions, and then set it to 1:
HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Resvc/Parameters/If you specify a restriction, but do not create the registry key, the restriction will not be checked.
Connecting to foreign systems
Exchange 2000 does not support Dynamic RAS ConnectorIf you use a Dynamic RAS Connector in Exchange Server 5.5, you must remove it and the associated transport stack (RAS MTA Transport Stack) before upgrading to the released version of Exchange 2000. Exchange 2000 does not include this connector or the associated transport stack. Specific details and upgrade recommendations will be available in Microsoft Knowledge Base articles, as well as upgrade and migration documentation. One recommended alternative is to perform an in-place upgrade.
To perform an in-place upgrade of Exchange Server 5.5:
Simple Mail Transfer Protocol
SMTP connector is not required for Internet mail capabilitiesExchange 2000 can send and receive Internet mail by default. All servers can connect directly to any external Simple Mail Transfer Protocol (SMTP) addresses if all servers can reach the Internet and if you have set the domain name servers on all network connections. The only reason to create an SMTP connector is to route all outbound SMTP mail through a particular server or set of gateway servers.
Set smart host after Internet Mail Service upgradeIf you used the Internet Mail Service to connect to another Exchange Server 5.5 site in the same organization, you must manually set the smart host field on the Exchange 2000 SMTP connector that is created as a result of the upgrade. In Exchange Server 5.5, the destination host information was commonly put on the Routing Address tab of the remote site information. In Exchange 2000, that information must be entered as the smart host of the connector. If you previously used Internet Mail Service to connect to multiple sites, you must create multiple SMTP connectors, each with one connected routing group entry and the appropriate smart host. You can set the smart host either on the Delivery tab of the SMTP virtual server or on the General tab of the SMTP connector.
If both sides of the connection are Exchange 2000 servers, consider replacing the Internet Mail Service with a Routing Group Connector, which is much simpler to configure and will use the SMTP protocol if both sides of the connection are Exchange 2000 servers.
Content configurations set on Internet Mail Service need to be manually moved when using Exchange 2000 as an SMTP bridgeheadIn Exchange Server 5.5, if you have specified a per-domain content configuration on an Internet Mail Service (for example, all messages in your domain are formatted in rich text and all attachments are formatted in MIME), you must manually enter those content configuration settings into Exchange System Manager. Additionally, Exchange Server 5.5 allowed you to set the content configurations on each instance of Internet Mail Service, so you might have different settings on each instance of Internet Mail Service, while Exchange 2000 consolidates all settings in one global container per organization. All settings from all Internet Mail Services need to be migrated to Exchange System Manager. This must be done even if you have only one SMTP connector outside of your Exchange organization hosted on an Exchange 2000 server.
To view the settings on an Exchange Server 5.5 computer:
You must manually upgrade some Internet Mail Service configuration dataSome Exchange Server 5.5 Internet Mail Service configuration data is not upgraded when a server is upgraded from Exchange Server 5.5 to Exchange 2000. To view the configuration state of the Exchange Server 5.5 Internet Mail Service before it was upgraded, use Exchange Server 5.5 Administrator to connect to another Exchange Server 5.5 computer in the same organization. Open the properties of the newly upgraded connector. The Extension-Data attribute remains in the Exchange Server 5.5 directory and Exchange Server 5.5 Administrator can use it to display the Exchange Server 5.5 configuration details. After viewing the pre-upgrade configuration, you can then upgrade the Exchange 2000 configuration accordingly, through Exchange System Manager or the Internet Information Services Microsoft Management Console (MMC) snap-in.
A cluster server cannot be a front-end serverBecause clustering provides Exchange mailbox servers failover capability if they are connected to shared storage, and front-end servers only relay Internet client protocol commands to mailbox servers, there is no benefit to using a cluster server as a front-end server. However, front-end servers can be made more fault tolerant by using multiple front-end servers and a load balancing scheme.
Configuring Recipient Update Service on a clusterThe network name resource for an Exchange 2000 server must be available to designate that server as the owner for a Recipient Update Service. If the server's network name resource is not available, or the server name is no longer registered with Domain Name System (DNS), attempting to designate a server as the owner will fail with an error stating "the network name was not found." If this error occurs, you can either select another server, which may or may not be a cluster, as your Recipient Update Service server, or make sure that the network name resource of the cluster virtual server group is available before you select Cancel or OK.
Message Transfer Agent
Do not remove the Message Transfer Agent from the original Exchange virtual server in a mixed-mode environmentExchange 2000 virtual servers include several resources, one of which is the message transfer agent (MTA). Do not remove the MTA resource from the original Exchange virtual server that it was created in while the server is in a mixed-mode environment. Note that you cannot delete the original virtual server with the MTA resource unless it is the last virtual server in the cluster. If the original virtual server with the MTA resource is deleted, you must add a replacement Exchange 2000 virtual server back to the cluster, using the same network name as the original virtual server. Then you must move all users from the replacement server, before removing all other applications and data from the cluster again.
Event Viewer may contain an incorrect server name on clustersIf you use Event Viewer to read an event message generated by Web Storage System, the server name listed in the Computer field may be incorrect. To view the correct server where the event message was generated, use the description of the event message. The correct server name is listed in the database path displayed in the description of the message.
Protocol virtual servers
Protocol virtual servers on a cluster must accept connections from their own IP addressAll protocol virtual servers, including Hypertext Transfer Protocol (HTTP), Simple Mail Transfer Protocol (SMTP), Post Office Protocol version 3 (POP3), and Internet Message Access Protocol (IMAP), allow you to reject all connections from all servers. If a protocol virtual server is configured to reject all connections, the protocol virtual server will reject the IsAlive calls from Exres.dll. Each protocol virtual server must accept connections from its own Internet Protocol (IP) address. To verify a protocol server can accept connections from its own IP address, open the Properties dialog box for the protocol virtual server. On the Access Tab, click Connection. If the option to accept connections from Only the list below is selected, verify that the Exchange 2000 virtual server's IP address is listed.
Using Secure Sockets Layer on clustersTo use Secure Sockets Layer (SSL) with protocols on a cluster, you must install a certificate with Exchange System Manager and an Exchange 2000 virtual server on the same node. After installing the first certificate, failover the virtual server to the second node, and then use Exchange System Manager on the second node to install another certificate.
Installing Exchange 2000 on a cluster requires a Physical Disk resourceExchange 2000 does not work on all cluster hardware and requires a disk resource of type "Physical Disk." Do not upgrade or install Exchange 2000 on a cluster that does not have a disk resource named "Physical Disk." Unless your cluster hardware uses the Windows NT cluster resource "Physical Disk" do not install or upgrade your cluster to Exchange 2000.
Chat, Instant Messaging, and Multimedia Messaging
Exchange 2000 Chat Service can run on Exchange Chat Service 5.5 SP1 or laterTo migrate configuration data to the Exchange 2000 Chat Service, you must have Chat Service version 5.5 Service Pack 1 (SP1) or later installed on the server that will be running Exchange 2000 Chat Service. Although it is recommended that only one version of Chat Service be running on one server at a time, you can run both versions simultaneously to migrate data. To run both versions of the Chat Service, the Profanity and Transcription server extensions must be enabled on only one version. In addition, each version of the Chat Service must use a different client port number. By default, the Chat Service uses port 6667, so you must change one version of the service to use an alternative port.
Uninstall Instant Messaging virtual servers before removing an IIS serverIf you want to remove an Internet Information Services (IIS) server that is associated with an Instant Messaging virtual server, you must first delete the Instant Messaging virtual server, and then delete the IIS server. If you delete the IIS server first, the Instant Messaging virtual server cannot be deleted from Exchange System Manager. Instead, the Instant Messaging virtual server must be removed from the directory using an Active Directory editing tool. For more information regarding this manual removal process, contact Microsoft Product Support Services.
Users with double-byte character set display names cannot log onInstant Messaging user display names cannot contain any double-byte character set (DBCS) characters. You must configure an ASCII Simple Mail Transfer Protocol (SMTP) address before enabling the user for Instant Messaging. If an ASCII SMTP address is not set, the user will not be able to log on to the Instant Messaging server.
Users must supply a password to authenticate by digestTo log on to an Instant Messaging server, a user must supply a user name and password when authenticating with the server by Digest Authentication. The server allows two authentication methods: Windows Integrated Authentication (NTLM) and Digest Authentication. Windows Integrated authentication will accept blank passwords, but Digest authentication will not. If the user is authenticating by Digest, they must type a password in the Log On dialog box, or authentication will fail and the user will not be allowed to log on to the server.
Uninstalling Instant MessagingTo uninstall Instant Messaging, you must first remove all Instant Messaging virtual servers from your organization. After successfully removing virtual servers, all users assigned to these servers are automatically disabled for instant messaging. If you do not remove an instant messaging virtual server, then you need to manually disable the associated users for instant messaging. If this is not done, users will still be enabled for Instant Messaging if a reinstallation takes place.
Changing the Instant Messaging database locationTo change the location of the Instant Messaging data files, you must change the database location, and then restart the associated service.
To change the location of the Instant Messaging database and log files:
Disabling promotional bannersTo disable the promotional banners that are displayed at the bottom of the Instant Messaging client, the following two registry settings need to be set:
Note The following combinations of registry settings will also disable MSN Messenger connectivity.
Home servers must have an FQDN in multiple domain environmentsIf you have multiple domains that host Instant Messaging users, you must use Fully Qualified Domain Names (FQDN) for all home servers. For example, instead of naming a home server InstMsgServer1, include the entire domain name, such as InstMsgServer1.microsoft.com. If you do not use an FQDN, your domain's Domain Name System (DNS) server will not able to determine the correct server to use when querying for a home server in a different domain. Additionally, if Integrated Windows authentication is being used, the client's proxy exclusion list should include all home servers in each domain.
To add home servers to the client proxy exclusion list:
Configuring VPIM inbound and outbound conversionExchange 2000 supports the VPIM message format by converting VPIM version 2 messages to the Microsoft Multimedia Message format. This operation can be performed inbound by converting inbound VPIM messages to Microsoft Multimedia Message format, or outbound by converting Microsoft Multimedia Message to VPIM, if the message is sent to a VPIM recipient. By default, the conversion in both directions is disabled. If your users will be communicating with VPIM users, you can enable conversion using a directory editor, such as ADSI Edit or Ldp.exe. For each Exchange 2000 server that you want to enable VPIM conversion on, you must set the following attributes, which are located on every msExchExchangeServer object in Active Directory.
Install Outlook 2000 extensions to enable Exchange Multimedia MessagingUsers need to install Outlook 2000 extensions for Exchange Multimedia Messaging. These extensions can be found at the following location:
http://MachineName/Exchweb/Bin/Emsetup.aspThe Outlook 2000 extensions for Exchange Multimedia Messaging enable users to record audio and video messages with Exchange 2000 controls in the Outlook 2000 user interface. Each piece of multimedia is rendered in the message as a bookmark, which a recipient can click to start the playback of the audio or video message. Users also have the option of integrating this multimedia information with text.
Windows 98 First Edition and non-USB cameras not supported for Multimedia MessagingOutlook 2000 and Outlook Web Access multimedia extensions are supported with USB cameras on Windows 98 Second Edition and Windows 2000 Professional. Non-USB camera devices are not supported. Windows 98 First Edition is not supported.
Key Management Service
Publishing certificates requires a global catalog in every user domainBefore enrolling users in security through Key Management Service, a global catalog must exist in the same domain as the users, or clients will not be able to publish certificates into the directory. Additionally, a registry entry must be set on every client computer in order for clients to publish to that global catalog.
To set the registry key:
Outlook client needs specific registry key to use Certification Revocation List Distribution PointsOutlook does not use Certification Revocation List Distribution Points by default. You must set a registry key to allow Outlook to locate a valid Certification Revocation List when it receives secure mail and does not already have a valid Certification Revocation List for the issuer. Setting the registry key will allow Outlook to use the Certification Revocation List Distribution Points in the certificate to get a valid Certification Revocation List for the issuer, providing that the certificate includes a Certification Revocation List Distribution Point.
Create the following registry key on the client:
Key Management Service needs a server registry key to publish Certification Revocation Lists after upgrading to Exchange 2000If you have an Exchange Server 5.5 certificate authority (CA) with the Exchange policy module installed, the CA does not add the Certification Revocation List Distribution Point extension to certificates. If a user is enrolled in security through an Exchange Server 5.5 version of Key Management Service, their certificates will not have a Certification Revocation List Distribution Point. A valid Certification Revocation List can still be located, as long as the Key Management Service version is Exchange Server 5.5. This is because in Exchange Server 5.5 Key Management Service published Certification Revocation Lists, and Outlook will by default check the CA object for Certification Revocation Lists. If a CA that previously had the Exchange Server 5.5 Key Management Service policy module installed has been upgraded to the Exchange 2000 version of Key Management Service, you must set a registry key on the server to allow Key Management Service to publish Certification Revocation Lists. This registry key can contain multiple CAs, and Key Management Service will publish the Certification Revocation Lists for all listed.
To set the registry key on the server:
Key Management Service database must be backed up locallyFor security reasons, the Key Management Service database cannot be backed up from a remote computer. Windows NT Backup will only allow backup of the Key Management Service database from the local server.
Key Management Service administration in a mixed environmentThe Key Management object in Exchange 2000 is administered only by an Exchange 2000 Key Management Service. The certification authority object in Exchange Server 5.5 is only administered from an Exchange Server 5.5 Key Management Service. The Encryption Configuration object in Exchange 2000, known as a Site Encryption object in Exchange Server 5.5, is administered from Exchange 2000's System Manager in all instances except in a pure Exchange Server 5.5 site. In a pure Exchange Server 5.5 site, the Site Encryption object is administered from the Exchange Server 5.5 Administrator.
Domain administrators assign security permissions to administer ExchangeAdministrative rights for managing user and contact objects are assigned by domain administrators and are separate from the Exchange Administrator rights. If you are not given permissions to manage Exchange 2000 objects, you will not be able to make your groups, contacts, and users mail-enabled. If you do not have permissions to manage Exchange 2000 objects, you can still create a new user. However, you cannot create an e-mail address for that user. To create a new user, group, or contact without an e-mail address, in Active Directory Computers and Users, in New Object Wizard, click to clear the Create an Exchange Mailbox check box.
HTTP virtual servers
Double-byte character sets not supported in virtual directory namesExchange 2000 does not support double-byte character sets (DBCS) in virtual directory alias names. In Exchange System Manager, you can create virtual directories for a virtual server. When you are creating the path or the folder used by the virtual directory, DBCS characters, also known as extended characters, should not be used.
IMAP virtual servers
IMAP message format is set to HTML by defaultIn Exchange 2000, the default for converting MAPI messages to MIME format has been changed to HTML. If you have users who are using an Internet Message Access Protocol (IMAP) client that does not handle HTML, such as Microsoft Pocket Outlook, you must change this message format on either the server or on a per-user basis. For more information on changing the message format, see the Exchange 2000 online documentation.
NNTP virtual servers
To use NNTP to post messages to a moderated newsgroup requires Windows 2000 Service Pack 2NNTP posts to a moderated newsgroup will fail and a "441 Article Rejected" error message will be returned to the NNTP client. Windows 2000 Service Pack 2 (SP2) must be applied to the Exchange 2000 NNTP server to correct this problem. Contact Microsoft Product Support Services for updates related to this issue.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Date Time Version Size File name
11/08/2000 11:27p 5.0.2195.2304 137,488 Nntpfs.dll
For additional information about how to obtain this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/277687/ )Posting to an NNTP moderated newsgroup may not work
Web Storage System
Event sinks set to run as "Launching User" have system account privilegesSinks for Web Storage System events are implemented as Component Object Model (COM) components, either as a COM dynamic-link library (DLL) hosted in a Microsoft Transaction Server (MTS) package, or as a COM executable. If an MTS package or COM executable is set to run as "launching user," the System account will be used because this is the user context of the Web Storage System process. An event sink running under the System account will have access to all data in all stores, including any user’s mailbox.
Recovering a database after a disasterAfter you run Setup in disaster recovery mode, and before using Ntbackup.exe to restore a database, you must verify that there are no files with the .log or .chk extension in the storage group where you want to restore a backup. The presence of either type of file results in failure during recovery if the log signatures on the existing logs do not match the signatures on the backup logs. These types of files can be created if you create a new database in a new storage group and cancel the creation of the .edb file.
The restore process must complete before using the temporary log directory for another restoreIf you want to restore two databases successively from the same storage group at the same time, choose different directories to save the temporary logs. Otherwise, if you successively restore two databases that are part of the same storage group to the same temporary log directory, the first restore process must be complete before starting a second restore process of another database in the same storage group. To complete a restore process, in Windows NT Backup, you must click the Last Backup Set check box, and then the log file replay must complete. To verify that the restore process and log file replay is complete, check the Application Log.
Deleting a persisted search folder through installable file system deletes all referenced itemsA persisted search folder can be programmatically created using HTTP/DAV. If you delete a persisted search folder through Installable File System (IFS), all referenced items in the search folder are deleted. Persisted search folders are not created by default, and must be manually created in custom code.
Safely deleting a database to avoid affecting mail that is in transitIf you want to delete a database on a server, you need to complete the following steps to ensure that you will not accidentally delete any mail that is in transit to or from any database on the server. These steps are necessary because the Exchange 2000 server's transport and message transfer agent (MTA) components may be using the database to transfer all messages on the server to and from Web Storage System. If that is the case, deleting the database will result in the deletion of any messages in transit on that server, and no non-delivery reports will be generated.
To delete the database:
Application Converter for Lotus Notes
MXOCX2 queries do not support the currency data typeIf you create a form that uses the MXOCX2 query method, and you use the currency data type in the query, you will receive an error stating that the query contains incompatible data types. Queries containing currency data type are not supported in MXOCX2.
Public folder items may not replicate correctly to Lotus NotesIf you add items to public folders using message classes that have no Lotus Notes counterpart, such as Discussions or Tasks, those items will not replicate to Lotus Notes correctly. The From and Subject fields will appear in the replicated item, but the body content will not.
Insufficient memory causes replication to failYou may experience replication failures when replicating an Exchange 2000 public folder with a Lotus Notes folder (or visa versa) than has a large number of messages (tens to hundreds of thousands). To prevent this problem, allocate more memory to the Exchange 2000 server or the Lotus Notes server.
Cannot directly upgrade from previous versions of ASN toolsYou cannot directly upgrade previous versions of Microsoft Exchange Application Converter (ASN) for Lotus Notes. This is because the upgraded Application Converter combines functionality from two previous products, Application Conversion Assistant and Application Connector. You do not need to upgrade Application Conversion Assistant because the Outlook forms it generates are unaffected by installation of the new Application Converter. However, you must upgrade Application Connector. The connector, which replicates data periodically between Lotus Notes databases and Exchange folders, is replaced by the Connection Manager component of Application Converter.
To update Application Connector to Connection Manager:
Need to reset the JIT debugger after Notes client setupYou should reset the Just-in-Time (JIT) debugger setting after installing a Lotus Notes client on an Exchange 2000 server. This will allow Connectivity Controller to restart a Lotus Notes e-mail connector process if it failed to handle an exception, and to continue with normal operation. Otherwise, after installation, Lotus Notes uses its "Quincy" utility to handle an exception, and this requires administrator intervention for termination of the failed process.
To reset the debugger setting:
MXCheck, MXRadio, and MXCombo queries fail on the serverQueries submitted using the MXCheck, MXRadio, and MXCombo controls provided in Mxocx2.dll will fail if they are run on an Exchange 2000 server.
Errors when installing Application Converter for Lotus Notes on a Windows 2000 computerIf you install Application Converter for Lotus Notes on a computer running Windows 2000, before you install Microsoft Office 2000 or Outlook 2000, Setup may fail and the following error may occur when you run Office Setup: "Internal Error 2343." To prevent this error from occurring, install Microsoft Office 2000 or Outlook 2000 before you install Application Converter for Lotus Notes, or use an Office utility to fix the problem after you install Application Converter for Lotus Notes.
For additional information about this problem and utility, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/228668/ )You receive an "Internal Error 2343" error message after you remove Lotus Notes and then install Office 2000
(http://support.microsoft.com/kb/234435/ )Utility to repair internal error 2343 available