Exchange Server 2000 : mounting an information store


Due to a crash, I have created a new exchange 2000 server and I would like to mount an old Exchange 5.5 information.
The problem is that when I try to mount it, it says

The information store could not be loaded because the distinguished name (DN) /O=BASTIDE/OU=BASTIDE/CN=RECIPIENTS/CN= of message database "First Storage Group\Public Folder Store (MAIL)" does not match the DN of directory /O=BASTIDE/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=.

 The database may have been restored to a computer that is in an organization or site different than the original database.

Do you have any clue to do that ?


Who is Participating?

Improve company productivity with a Business Account.Sign Up

GUEENConnect With a Mentor Commented:
This is the path that is inside the DB: (DN) /O=BASTIDE/OU=BASTIDE/CN=RECIPIENTS/CN=
The 2nd path that you listed above is the one that is currently listed in Active Directory (AD):
So your naming is incorrect here.

Note that one has OU=BASTIDE and the other has OU=FIRST ADMINISTRATIVE GROUP.
According to technet you have two options:
1. Start over again.
2. Use the methods that are described in Appendix A "Changing legacyExchangeDN Attribute Values" to change the names in the current installation to the correct names.

Method 2 of Appedix A listed below:
Appendix A: Changing legacyExchangeDN Attribute Values
This appendix describes how to change legacyExchangeDN values on an existing Exchange 2000 computer so that the server can accommodate a database that is stamped with different values. Some situations in which you may want to change legacyExchangeDN values include the following:
?You set up a recovery server incorrectly, and you want to avoid completely uninstalling and reinstalling the recovery server.
?You create a dedicated recovery server, and you want to use the dedicated recovery server to recover databases from more than one administrative group or organization.
The procedure that is described in this appendix is intended only for use in a laboratory environment. In a complex production environment, this procedure may have unintended consequences, and may cause databases to stop responding or may cause mail flow to stop. The instructions in this section assume that you are performing this procedure in a single-server Active Directory forest, and that communication and mail flow with other servers is not essential.
At first, this procedure may seem complex and confusing, but after you practice the procedure a few times, you can change a server from one organization and administrative group to an entirely different organization and administrative group in a matter of minutes.
Keep in mind that you can no longer start existing databases after you make these changes. In most cases, this is not a concern. However, the Exmerge utility requires the database that houses the system attendant mailbox to be running. In most cases, this database is the first mailbox store that is created during installation. (While a database is running, you can inspect the Mailboxes table to determine where the system attendant mailbox is located.)
If you cannot start the system attendant?s database, you can delete that database (assuming that there is no other critical data in that database), or move that database temporarily out of the way. During the next attempt to mount the database, a new database is created, along with a new system attendant mailbox.
To wipe a database, stop the information store, and then move the .edb and .stm files that are defined in the database properties. Restart the information store, and then mount the database in Exchange System Manager.
To alter the legacyExchangeDN values for an existing Exchange 2000 computer:
1. If necessary, change the organization and administrative group names.
You cannot change an organization name by using Exchange System Manager, but you can change the organization name by using the Active Directory Sites and Services Microsoft Management Console (MMC) snap-in.
Important   Never change the organization name in a production environment.
To change the Exchange 2000 organization name, open the Active Directory Sites and Services MMC snap-in, and then click Show Services Node on the View menu. Click to expand the Services container, click to expand the Microsoft Exchange container, right-click the organization object, and then click Rename. You can continue to expand Exchange 2000 containers and change other names as well, including administrative groups.
Note   You can also change administrative group names in Exchange System Manager, but only after you switch the organization to native mode.
2. Generate an LDIF export file that contains all of the objects that must be changed.
Export all objects in the Microsoft Exchange container, including the Microsoft Exchange container, by using an ldifde command that is similar to the following:
ldifde -f e:\legacy.ldf -p subtree -l legacyexchangedn -d "CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=corp,DC=mycompany,DC=com"
-r "(legacyexchangedn=*/ou=First*)"
(Refer to the "Exchange 2000 Alternate Server Recovery" section of this white paper for more details about how to use Ldifde and how to determine existing legacyExchangeDN values.)
In the preceding command, the ?l LDAP_attribute_list parameter restricts the output for each object that is found to only the legacyeExchangeDN attributes. This parameter is very important because you need to edit this file to re-import the file. Any extra attributes are clutter that you need to delete before you can successfully import the file.
The ?r LDAP_filter parameter returns only objects that have a legacyExchangeDN value that includes the string ?First?. In most cases, the current legacyExchangeDN value on your recovery server includes /ou=First Administrative Group. But if the current legacyExchangeDN value is different, you can substitute an appropriate search string.
This command should generate an export file that contains several entries similar to the following:
dn: CN=RECOVERY1,CN=Servers,CN=First Administrative Group,
CN=Administrative Groups,CN=ORGANIZATION1,
CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mycompany,DC=com
changetype: add
/o=Organization1/ou=First Administrative
There may be anywhere from six objects to several dozen objects, depending on how many storage groups or databases are defined for this administrative group.
3. Modify each legacyExchangeDN value.
You can modify each legacyExchangeDN value manually, one by one, by using the Ldp or ADSI Edit utility with the Legacy.ldf file that you just generated as a guide. But it is likely to be much easier to modify each legacyExchangeDN value by performing a bulk import.
To perform a bulk import, you must modify the Legacy.ldf file significantly; this modification is not as simple as just changing the /ou= value and importing the file. The Ldif import format to make modifications to existing objects differs considerably from the format to add new objects, and the file that you exported is a ?new object? file.
It is much easier to change the export file into a proper import file if you have a text editor that supports search and replace across line breaks. Notepad does not support this capability, but Microsoft Word does. If you do not have an appropriate text editor, it still only takes several minutes to make the modifications that you need.
A simple LDIF import file that is designed to modify an existing attribute on an existing object consists of records in the following format:
dn: distinguished name of the object to be modified
changetype: modify
replace: attribute name
attribute name: new value
<blank line>
next record . . .
You need to change each record from the following
dn: CN=RECOVERY1,CN=Servers,CN=First Administrative Group,
CN=Administrative Groups,CN=ORGANIZATION1,
CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=microsoft,DC=com
changetype: add
/o=Organization1/ou=First Administrative
to the following:
dn: CN=RECOVERY1,CN=Servers,CN=First Administrative Group,
CN=Administrative Groups,CN=ORGANIZATION1,
CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=microsoft,DC=com
changetype: modify
replace: legacyExchangeDN
/o=Organization1/ou=New Administrative
Group Name/cn=Configuration/cn=Servers/cn=RECOVERY1
The items that you need to change are formatted in bold type and are red in the preceding example. Specifically, you need to make the following changes:
?You must change the changetype value from add to modify.
?You must add a line that reads replace: legacyExchangeDN under the changetype line.
?You must change the administrative group name to the correct value.
?You must add a hyphen on a line by itself after each entry, and there must also be an additional blank line after every hyphen.
Note   The LDIF import format is strictly adhered to; even minor deviations cause errors when you try to import the file. There must be one space and only one space after each colon in each entry. If you need to break long lines, you must indent the continuation of each line exactly one space. At the end of the file, the last entry must also contain a hyphen, and a blank line under the hyphen, or the file does not import correctly.
Many text editors, including Word, use the characters ^p to represent line breaks. ("^p" does not stand for ?CONTROL+P?, but for the caret (^) character followed by a lower case p.) The following table uses the ^p convention to represent a line break.
Search for . . .      Replace with. . .

/ou=current_value      /ou=new_value
^p^p (line break, line break)      ^p-^p^p (line break, hyphen, line break, line break)
changetype:[space]add^p      changetype:[space] modify^preplace:[space] legacyExchangeDN^p
Important   If you use Word or another word processing program to edit the file, be sure to save the file as plain text. Inspect the file in Notepad after you save the file to be sure that the file is readable and is formatted correctly as plain text.
After you generate the import file, import the file back into Active Directory by using the following command:
ldifde -i -f legacy.ldf
All 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 ADSI Edit or Ldp.
You can verify that all objects were modified by running the ldifde command that you used previously to export the objects. The command should now locate no objects to export because all legacyExchangeDN values have been changed.
Note   To avoid overwriting your import file, change the ?f filename parameter to con so that Ldifde output is sent only to the screen.
After you modify the legacyExchangeDN values, you need to stop and restart all Exchange 2000 services, which include the system attendant. Before you do this, the previous naming is cached, and the system performs as if you did not make any changes.

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.

All Courses

From novice to tech pro — start learning today.