Knowledge Base

An Exchange 2000 Server user in a mixed Exchange organization receives a 5.1.6 non-delivery report when the user sends an e-mail message to an Exchange Server 5.5 public folder

Article ID: 924169

Article Last Modified on 10/9/2006

APPLIES TO

Microsoft Exchange 2000 Server Standard Edition
Microsoft Exchange 2000 Enterprise Server

SYMPTOMS

Consider the following scenario:

You have a mixed Microsoft Exchange Server organization. This organization has one or more computers that are running Microsoft Exchange 2000 Server in a Microsoft Exchange Server 5.5 site.
You have a mail-enabled public folder that is located on a computer that is running Exchange Server 5.5.
You have an Active Directory Connector (ADC) connection agreement that is configured to replicate public folder directory objects to the Active Directory directory service.

In this scenario, a user whose mailbox is located on an Exchange Server 5.5-based computer sends an e-mail message to the public folder. When this occurs, the e-mail message is delivered successfully as expected.

However, if a user whose mailbox is located on a computer that is running Exchange 2000 Server sends an e-mail message to the public folder, the message is not delivered successfully. The user receives a non-delivery report (NDR) delivery status notification (DSN) message that resembles the following 5.1.6 NDR:

From: System Administrator 
Sent: <date> <time> 
To: Info 
Subject: Undeliverable: Test 
Your message did not reach some or all of the intended recipients. 

      Subject: Test 
      Sent: <date> <time> 

The following recipient(s) could not be reached: 
      Info on <date> <time> 
        The message was undeliverable because the recipient specified has 
        changed address permanently and forwarding was not applicable 

      <mail.server.com #5.1.6>

CAUSE

This problem may occur if the homeMDB attribute for the public folder directory object in Active Directory is missing.

To determine whether the homeMDB attribute is missing, follow these steps.

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.

Start the Active Directory Service Interfaces (ADSI) Edit tool. To do this, click Start, click Run, type adsiedit.msc, and then click OK.

Note The ADSI Edit tool is included with the Windows Support Tools. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

301423 How to install the Windows 2000 Support Tools to a Windows 2000 Server-based computer

For more information about how to obtain the Windows 2000 Service Pack 4 (SP4) Support Tools, visit the following Microsoft Web site:

http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/supporttools.mspx
Connect to a domain controller if the ADSI Edit tool is not already connected to a domain controller.
Expand Domain NC [domainController.example.com], expand DC=example,DC=com, and then click CN=Microsoft Exchange System Objects.
In the right pane, right-click CN=PublicFolderName, and then click Properties.
In the CN=PublicFolderName Properties dialog box, click Both in the Select which properties to view list. Then, in the Select a property to view list, click homeMDB.
Determine whether a value appears in the Value(s) box.
Click Cancel, and then exit the ADSI Edit tool.

If no value appears in the Value(s) box for a particular public folder object, the homeMDB attribute is missing from that public folder object.

RESOLUTION

To resolve this problem, follow these steps.

Step 1: Stop the ADC service

Stop the ADC service that is running the public folder connection agreement. To do this, follow these steps:

On the domain controller on which the public folder connection agreement is configured, click Start, click Run, type services.msc, and then click OK.
In the Services Microsoft Management Console (MMC) snap-in, right-click Microsoft Active Directory Connector, and then click Stop.

Step 2: Remove the "ADC-Global-Names" attribute from the public folders

Remove the ADC-Global-Names attribute from the Exchange Server 5.5 public folders. To do this, follow these steps.

Warning If you use the raw mode of the Exchange Server Administrator program (admin /r) incorrectly, serious problems may occur that may require you to reinstall Microsoft Windows NT Server, Microsoft Exchange Server, or both. Microsoft cannot guarantee that problems that result from using raw mode incorrectly can be solved. Use raw mode at your own risk.

Use the DSExport.exe tool to export the Exchange Server 5.5 public folder directory objects. To do this, follow these steps:
1. Copy the DSExport.exe file to the Exchsrvr\Bin folder on the computer that is running Exchange Server 5.5.
2. In the Exchsrvr\Bin folder, create a text file that contains only the following text entry:
```
Obj-Class,Directory Name,Display Name,Obj-Dist-Name,ADC-Global-Names
```
  Note You can add any other attribute that you want to this header line.
3. Save the text file as PFList.csv.
4. Start a command prompt, change directory to the Exchsrvr\Bin directory, type the following command, and then press ENTER:
  
  dsexport /FILE=PFLIST.CSV /DSA=ServerName /BASEPOINT=/o=Organization/ou=Site /CLASSES=PUBLIC-FOLDER /HIDDEN /SUBTREE
  
  Notes
  - Replace ServerName with the name of the computer that is running Exchange Server 5.5. This entry is case sensitive.
  - Replace Organization with the name of the Exchange organization. This entry is case sensitive.
  - Replace Site with the name of the Exchange Server 5.5 site. This entry is case sensitive.
  The public folder directory objects are exported to the PFList.csv file. One public folder directory object is on each line in the PFList.csv file.
  
  Note Alternatively, you can export a list of all the public folders in the whole Exchange organization instead of only the public folder information for one particular site. To do this, use the following command:
  
  dsexport /FILE=PFLIST.CSV /DSA=ServerName/BASEPOINT=/o=Organization/CLASSES=PUBLIC-FOLDER/HIDDEN /SUBTREE
For more information about how to obtain and to use Dsexport.exe, click the following article number to view the article in the Microsoft Knowledge Base:

185018 How to export public folder directory data to a CSV file
Use Microsoft Excel to modify the value of the ADC-Global-Names attribute for each public folder. To do this, follow these steps:
1. Start Excel, and then open the PFList.csv file to which you exported the public folder directory objects.
2. For each public folder entry, replace the value that appears in the ADC-Global-Names column with the following value:
  
  ~DEL
3. Save the file as PFList2.csv, and then exit Excel.
Use the Admin.exe command to import the PFList2.csv file to the Exchange Server 5.5 directory. To do this, follow these steps:
1. Copy the PFList2.csv file to the Exchsrvr\Bin folder on the computer that is running Exchange Server 5.5.
2. Start a command prompt, and then change directory to the Exchsrvr\Bin directory.
3. Type the following command, and then press ENTER:
  
  admin /i PFList2.csv /d ServerName
  
  Important This import operation is successful only if the public folder directory objects are in the default location. By default, these objects are located in the Recipients container. If you have moved the public folder directory objects, perform one of the following actions:
  - Follow the steps that are described in the following Microsoft Knowledge Base article:
    
    268485 Directory import is unsuccessful when you use a command line
  - Use the Microsoft Exchange Administrator program to import the directory objects. To do this, follow these steps:
    1. Start the Exchange Administrator program.
    2. On the Tools menu, click Directory Import.
    3. In the Directory Import dialog box, click Container, click the container to which you want the directory objects to be imported, and then click OK.
    4. Click Import File, click PFList2.csv, click Open, and then click Import.
    5. Click OK when you receive the following message:
      
      The directory import from c:\exchsrvr\bin\PFList.csv is complete.
      
      No errors were encountered.
  Note Import errors are logged in the Application log.

Step 3: Remove the affected public folder directory objects from Active Directory

Locate and then remove the public folder directory objects that are missing the homeMDB attribute in Active Directory. These objects are located in the Microsoft Exchange System Objects container in Active Directory.

Important Do not remove all the objects from the Microsoft Exchange System Objects container. This container contains other objects, such as system mailboxes, that should not be removed.

To remove the affected public folder directory object or objects, follow these steps.

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.

Start the ADSI Edit tool. To do this, click Start, click Run, type adsiedit.msc, and then click OK.
Connect to a domain controller if the ADSI Edit tool is not already connected to a domain controller.
Expand Domain NC [domainController.example.com], expand DC=example,DC=com, and then click CN=Microsoft Exchange System Objects.
In the right pane, locate the public folder object that is missing the homeMDB attribute. To verify that the object is missing the homeMDB attribute, follow the steps that are mentioned in the "Cause" section.
Right-click the affected object, and then click Delete.
Click OK to confirm that you want to remove the object.
Repeat steps d through f to remove each public folder object from which the homeMDB attribute is missing.
Exit the ADSI Edit tool.

Step 4: Use the public folder connection agreement to replicate information to Active Directory

Start the ADC service that is running the public folder connection agreement, and then replicate the public folder connection agreement. To do this, follow these steps:

On the domain controller on which the public folder connection agreement is configured, click Start, click Run, type services.msc, and then click OK.
In the Services MMC snap-in, right-click Microsoft Active Directory Connector, and then click Start.
Start the Active Directory Connector Manager tool.
In Active Directory Connector Manager, click Active Directory Connector (domainControllerName).
In the right pane, right-click the public folder connection agreement, and then click Replicate Now.
Use the ADSI Edit tool to examine the newly created public folder object or objects in Active Directory. Do this to verify that each object has a value for the homeMDB attribute. To do this, follow the steps that are mentioned in the "Cause" section.

MORE INFORMATION

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

284204 Delivery status notifications in Exchange Server and in Small Business Server

Additional query words: XADM pf CA

Keywords: kbtshoot kbprb KB924169

Microsoft KB Archive/924169

Contents