Article ID: 301585 - View products that this article applies to.
This article was previously published under Q301585
This article describes workarounds for the following known problems in Mbconn version 6.0.4417:
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/301378/EN-US/ )XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
To work around the Mbconn problems that are listed in the "Symptoms" section of this article, use the workarounds in the following sections (as applicable):
Mbconn Sets Uppercase LegacyExchangeDN DelimitersAn Outlook client will not process free/busy information correctly if the legacyExchangeDN attribute of the owning user object has uppercase delimiters. For example, a typical legacyExchangeDN looks similar to this:
/o=Organization/ou=Site/cn=Recipients/cn=UserAn MBCONN-generated legacyExchangeDN will look similar to this:
/O=Organization/OU=Site/CN=Recipients/CN=UserThe Fbfix.exe tool can be used to automatically correct this problem. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
286783Alternatively, you can export and import the affected objects by using Ldifde.exe, which is installed by default on Windows 2000 server.
(https://support.microsoft.com/kb/286783/EN-US/ )XADM: Error Message Updating Free and Busy Data in Exchange 2000
LDIFDE -I -F LEGACY.LDFAll objects should import successfully. If there are any problems, Ldifde reports the line on which a problem was encountered. Investigate such problems by carefully examining the affected record in the import file. For most errors, Ldifde stops the import procedure at the first error, even if records after the error are good. If the cause of an error is not immediately obvious, it may be more efficient to remove the problem record, finish the import, and then manually modify the object that did not import by using ADSIEdit or Ldp.
You can verify that all objects were modified by running the ldifde command that you used previously to export the objects. You should no longer be able to find uppercase /O, /OU or /CN values in the file.
After you modify the legacyExchangeDN values, you need to stop and restart all Exchange 2000 services, including the system attendant.
Mbconn Quits Suddenly After You Type a Log File Name in the Browse Dialog BoxMbconn automatically generates a log file of Mbconn operations in the folder that Mbconn.exe resides in. If this location is not writeable (for example, if Mbconn.exe is on a read-only share), Mbconn prompts you to select a different log file location. A standard file selection dialog box is displayed. Regardless of the location or file name that you select, Mbconn quits unexpectedly.
To work around this problem, either copy Mbconn to a writeable location, or click Cancel in the file browse dialog box to use Mbconn without logging.
Mbconn Quits Suddenly After You Browse for an Export File LocationWhen you create an export file, if you click the file Browse button, Mbconn quits suddenly.
To work around this problem, type the file name, and then click Generate to create an export file.
Mbconn Does Not Enumerate Exchange DatabasesAfter you define the domain controller and Exchange computer to which you want Mbconn to connect, you may receive either of the following error messages:
No private databases found on this Exchange Server
This problem can occur if the administrator is not logged on with a Microsoft Windows account that belongs to the parent domain of the Active Directory Configuration container. The Configuration container is created as a sub-container of the first domain that is installed in an Active Directory forest. If the forest contains multiple trees, it may not be obvious which tree holds the Configuration container. To discover which domain is the parent of the Configuration container:
Connection to server failed.
ExServer : Exchange1
DC : DC1
HRESULT : ERROR_DS_NO_SUCH_OBJECT
AD Error : 0000208D: NameErr: DSID-031001C9, problem 2001 (NO_OBJECT), data 0, best match of:
There is no such object on the server.
Mbconn Reports That Reconnection Does Not Work Even If Reconnection SucceedsIf Mbconn successfully reconnects a mailbox to a user, but Mbconn may still report that all reconnections did not work. If an administrator starts Exchange System Manager, and then runs the Cleanup Agent to verify the connection state of all of the mailboxes, the Cleanup Agent does not work, and you receive the following error message:
The following error message is logged simultaneously in the Application event log:
An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both.
ID no: c1041724
If you try to reconnect a single failed user in the Mailboxes window in Exchange System Manager, you may receive the following error message:
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9562
Time: 6:30:42 PM
Description: Failed to read attribute msExchUserAccountControl from Active Directory for /O=MICROSOFT/OU=EXCHANGE/CN=RECIPIENTS/CN=COMMONNAME.
If you restart services or System Manager, it does not clear the error. In most cases, approximately 10 minutes pass before the mailboxes become accessible. (When you can run the Cleanup Agent again successfully, the reconnection process has completed.)
The operation cannot be performed because this mailbox was already reconnected to an existing user.
You can use Ldifde to examine the homeMDB and mailNickname attributes of a user. If these attributes exist, the Mbconn portion of the reconnection process actually succeeded. To use Ldifde to examine the homeMDB and mailNickname attributes of a user, you must know the distinguished name of the user account. In its preview mode, Mbconn displays the distinguished name of the user account that Mbconn intends to link with a mailbox. For example, if you run the following command
LDIFDE -F CON -D "CN=Common Name,OU=Container,DC=Domain,DC=COM" -L homeMDB,mailNicknamethe following is a sample of the output that is generated:
E:\>LDIFDE -F CON -D "cn=Common Name,ou=Container,dc=domain,dc=com" -L homeMDB,mailNicknameNOTE: Regardless of whether you find the homeMDB and mailNickname attributes for the user, Ldifde should report "1 entries exported." If Ldifde reports "No entries found," Ldifde was unable to read the user object from the directory. You may have typed the distinguished name incorrectly, you may not have sufficient permissions to view the object, or you may not have escaped characters that require escape. (For additional information about characters that require escape, see the "Export File Reports Errors During Active Directory Import" section of this article.)
Connecting to "dc1.domain.com"
Logging in as current user using SSPI
Exporting directory to file con
Searching for entries...
Writing out entries.dn: CN=Common Name,OU=Container,DC=domain,DC=com
CN=Private Information Store (DC1),CN=First Storage Group,CN=InformationStore,CN=DC1,CN=Servers,
CN=Exchange,CN=Administrative Groups,CN=Microsoft,CN=Microsoft Exchange,CN=Services,CN=Configuration,
1 entries exported
The command has completed successfully
If the homeMDB and mailNickname attributes are present, and you can run the Cleanup Agent successfully, it is possible that the Recipient Update Service cannot complete the reconnection process by stamping additional attributes on the user object. If user objects do not have a proxyAddresses attribute, the Recipient Update Service has not yet processed the object.
To work around this problem and avoid most apparent reconnection problems, add the following line to each record in the Mbconn export file:
msExchUserAccountControl: 0For additional information about the msExchUserAccountControl value, see the "Export File Reports Errors During Active Directory Import" section.
Export File Reports Errors During Active Directory ImportThe following is the general format of each LDIF record in the export file:
dn: CN=Common Name,OU=Container,DC=Domain,DC=comThe following is the typical command syntax for importing the file:
displayName: Common Name
cn: Common Name
LDIFDE.EXE -I -K -F MBCONN.TXTIf syntax or formatting errors occur during import, Ldifde stops the import and reports the line in the file at which the problem record begins. (For example, an error in the first record is reported as an error at line 1.) If an entry already exists in Active Directory, the second attempt to import the file results in an error unless you use the -K switch. You cannot modify previously created entries by adding attributes to a record and re-importing the record. The LDIF standard does provide for modifications of existing directory objects, but the format and syntax are very different from the format for creating records.
In general, to troubleshoot an LDIF import, you need to locate the line that contains the record that is in error, and then examine the record for a specific problem.
The following are common problems that are encountered in Mbconn export files:
This batch file does four things:
There are two mandatory parameters: the name of the Mbconn export file, and a new file name for the changes, for example:
E:\>MBCONNFIX.BAT MBCONN.TXT MBCONNFIX.TXTClip and paste the batch file into a plain text editor, and then save the batch file as Mbconnfix.bat.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.
The Mbconn.exe utility is included on the Exchange 2000 Server CD-ROM. It is used most often in conjunction with Exmerge.exe during alternate server database recoveries. In an alternate server recovery, an Exchange 2000 database from one Active Directory forest is started on a recovery server in another forest, usually to salvage data from that database. In this scenario, you can use Mbconn to generate Active Directory user accounts for each mailbox that you want to recover. You can then use Exmerge to merge data from the recovery database back to a production database.
Mbconn can generate an LDIF format file, which you can import into Active Directory with Ldifde.exe. The Mbconn export file performs a function that is similar to that of the DS/IS consistency adjuster in earlier versions of Exchange Server; the Mbconn export file creates directory accounts that match "orphaned" mailboxes in an Exchange database, which allows you to gain access to those mailboxes again. You can edit the export file to remove accounts or add attributes before you import the export file.
NOTE: Because the mailbox table in a database contains only a small set of attributes that link the mailbox to a particular user account, it is not possible to automatically repopulate the directory with optional attributes, such as telephone numbers.
For additional information about general procedures to set up alternate server recoveries, see the "Exchange 2000 Server Database Recovery" white paper at the following Microsoft Web site:
Article ID: 301585 - Last Review: February 27, 2007 - Revision: 2.2