Microsoft KB Archive/199964

= XADM: Error Message: The Delegate Page Is Not Available. Unable to Access Outlook Folder =

Article ID: 199964

Article Last Modified on 10/28/2006

-

APPLIES TO

 Microsoft Outlook 97 Standard Edition, when used with:  Microsoft Windows 95

 Microsoft Windows 98 Standard Edition  Microsoft Outlook 98 Standard Edition, when used with:  Microsoft Windows 95

 Microsoft Windows 98 Standard Edition</li></ul> </li> Microsoft Outlook 2000 Standard Edition, when used with:  Microsoft Windows 95</li></ul>

 Microsoft Windows 98 Standard Edition</li></ul> </li> Microsoft Exchange Server 5.5 Standard Edition</li> Microsoft Exchange 2000 Server Standard Edition</li></ul>

-

<div class="notice_section">

This article was previously published under Q199964

<div class="symptoms_section">

SYMPTOMS
When you try to access the Delegate tab in the Microsoft Outlook client, you may receive the following error message:

The Delegate page is not available. Unable to access Outlook folder.

<div class="cause_section">

CAUSE
This error may be caused by a corrupted Exchange Server mailbox. In an Exchange 2000 mixed mode organization, this error may be caused by an incorrect homeMTA attribute.

Note When this issue is caused by an incorrect homeMTA attribute, users cannot add users from the Exchange Global Address List to their personal distribution lists.

<div class="workaround_section">

WORKAROUND
To work around this problem, use one or both of the following methods, as appropriate to your situation:

Method 1: Re-create the Exchange Mailbox

 * 1) Download all the information in the mailbox to a .pst file (personal folder) by changing the delivery location in the properties for the Exchange Server service.
 * 2) Remove the corrupted mailbox by using the Exchange Server Administrator program, and then create a new Exchange Server mailbox.
 * 3) Mail from the personal folders can be uploaded to the server again by manually copying the messages back to the mailbox folders.

By Using the Microsoft Active Directory Directory Service
To resolve this behavior by using Active Directory, perform both of the following steps:

Important You must complete step 1 and step 2 in succession for each user who experiences this behavior.

Step 1: Verify the Information That Is Associated with the HomeMTA Attribute
Use the ADSI Edit utility to obtain the information that is associated with the homeMTA attribute of the user account that experiences this problem. To do so, 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 Exchange 2000 Server, or both. 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. <ol> Start ADSI Edit. To do so, click Start, click Run, type adsiedit.msc in the Open box, and then click OK.

Note The ADSI Edit tool is located in the Microsoft Windows 2000 Support Tools. If this tool is not installed, you can install the tool from the Microsoft Windows 2000 CD-ROM. The full path is:

Support\Tools\Setup.exe.

</li> Expand Domain NC  (where  is the name of the domain controller and where   is the name of the domain), expand DC= example,DC= com.</li> Expand the container that contains the user account that you want; for example, expand CN=Users.</li> Right-click the user account container that you want; for example, right-click CN= , and then click Properties.</li> In the Select which properties to view list, click Both.</li> In the Select a property to view list, click homeMTA.</li> In the Value(s) box, note the value for the homeMTA property.</li></ol>

If the value of the homeMTA attribute is not correct, you must update the user account by entering the correct value.

For example, the following is an incorrect value for the homeMTA attribute:

CN=Microsoft MTA\DEL:e8b60430-4dfc-4902-8891-6651a6d141c8,CN=Deleted Objects,CN=Configuration,DC=Example,DC=com;

Note In this example, the value of the homeMTA attribute is in the Deleted Objects folder of the domain. In this scenario, the value of the homeMTA attribute must be in CN= .

The following is an example of a correct value for the homeMTA attribute:

CN=Microsoft MTA,CN= ServerName,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=Example Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=example,DC=com

To change the value of the homeMTA attribute:
 * 1) In the Value(s) box, note the value for the homeMTA property.
 * 2) Type the correct value in the Edit Attribute box, click Set, click Apply, and then click OK.

Note The easiest way to enter the correct value for the homeMTA attribute is to use ADSI Edit to obtain the correct value for a user who is in the same Exchange Server 5.5 site and who does not experience the issue that is described in the "Symptoms" section of this article. Copy the value of the homeMTA attribute from the user who has the correct value, and then paste it in the Edit Attribute box of the user who has the value that is not valid.

If there are no users in the Exchange Server 5.5 site that you can copy the correct value from, use the examples that are provided earlier in this article to type the correct value manually. You must adapt the examples for your Exchange Server organization.

<div class="workaround_section">

Step 2: Update the Recipient Information
<ol> <li>In the Select a property to view list, click msExchALObjectVersion.</li> <li>In the Value(s) box, note the value for the msExchALObjectVersion property.</li> <li>Increment the value for the msExchALObjectVersion property by 500.

For example, if the value is 40, change it to 540. To do so, in the Edit Attribute box, type, click Set, click Apply, and then click OK.

Note An alternative to incrementing msExchALObjectVersion by 500 is to verify the msExchALObjectVersion attribute in Active Directory by using ADSI Edit, and then verify the Object-Version on the mailbox in the raw directory of Exchange Server 5.5. Compare the numbers, and then increment the value in Active Directory to 10 more than the value that appears in the Exchange Server 5.5 raw directory. This procedure makes sure that you have correctly incremented this value. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

258257 XADM: How to Verify the Object-Version When You Troubleshoot Directory Replication Problems

</li> <li>Quit ADSI Edit.</li></ol>

After you have edited the information that is associated with the homeMTA attribute for each user who experiences this behavior, start Active Directory Connector Manager, right-click the recipient connection agreement that is associated with the Exchange Server 5.5 site that the user belongs to, and then click Replicate Now to force replication.

<div class="workaround_section">

By Using the Exchange Administrator Program
When the homeMTA information in the Exchange 5.5 directory is correct for the Exchange 5.5 mailbox, but the information is incorrect in Active Directory, you can use Exchange Administrator to resolve this issue. To do so: <ol> <li>Start Exchange Administrator. To do so, click Start, point to Programs, point to Microsoft Exchange, and then click Microsoft Exchange Administrator.</li> <li>On the Tools menu, click Directory Export.</li> <li>In the Home server list, click All.</li> <li>Click to select the Include subcontainers check box.</li> <li>Under Export objects, click to select the following check boxes: <ul> <li>Mailbox</li> <li>Custom recipient</li> <li>Distribution list</li></ul> </li> <li>Under Logging level, click High.</li> <li>Under Character set, click ANSI (if it is not already selected).</li> <li>Click Export File, locate the folder where you want to save the file, type the file name that you want in the File name box, click Open, and then click Yes when you are prompted to create a new file.</li> <li>Click Container, expand the domain object, click the Recipients container, and then click OK.</li> <li>Click Export to export the information to the comma-separated values (.csv) file that you created.</li> <li>On the message that appears that indicates that the directory export is complete, click OK.</li> <li>Start Microsoft Excel, and then open the .csv file that you exported the directory information to.</li> <li>Delete all the columns except for the Obj-Class column and the Directory Name column in the .csv file.

Important Delete the actual columns and not just the information that they contain. Make sure there are no empty columns between the Obj-Class and the Directory Name columns.</li> <li>In row 1 of a new column, type Custom Attribute 15 .</li> <li>In the Custom Attribute 15 column, type 1 in each row that corresponds to an item. Make sure that the worksheet appears similar to the following table: </li> <li>Save the file, and then quit Excel.</li> <li>Start Exchange Administrator.</li> <li>On the Tools menu, click Directory Import.</li> <li>Click Import File, click the .csv file that you saved, and then click Open.</li> <li>Under Multivalued Properties, click Overwrite, and then click Import.</li> <li>In the message that indicates that the directory import is complete, click OK.</li> <li>Repeat steps 1 through 21 for the recipients containers in each site in your Exchange organization.</li> <li>Start the Active Directory Connection Manager, and then replicate both the Recipient Connection Agreement and the Configuration Connection Agreement (config_CA).</li></ol>

To remove the Custom Attribute 15 values from your Exchange 5.5 directory, open the .csv file that you saved in step 16, type ~del under the Custom Attribute 15 column for each row that corresponds to an item. Make sure that the worksheet appears similar to the following table:

Save and then import this new .csv file into the directory. When you do so, click Overwrite under Multivalued Properties.

Additional query words: 8.0 8.01 8.02 8.03 8.04 8.5 9.0 GAL

Keywords: kbprb KB199964

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.