Symptoms
Assume that you move a user's mailbox from an Exchange Server 2007 server to an Exchange Server 2010 server. Or, you move a user's mailbox from an Exchange Server 2010 server to another Exchange Server 2010 server. After the mailbox is moved, the user receives the following error message when he or she opens Microsoft Outlook:Microsoft Exchange administrator has made a change that requires you to quit and restart Outlook:
Microsoft Exchange administrator has made a change that requires you to quit and restart Outlook.
Additionally, the user encounters the following symptoms:
-
After the user restarts Outlook, Outlook continues to connect to the old server.
-
If the user runs a repair on the profile, the same error message is received.
Notes
-
If you use the Test-EmailAutoConfig cmdlet and specify the user’s mailbox, the correct information for the mailbox configuration is returned.
-
If Outlook is running, it recovers from this issue by itself in 30 minutes or more.
-
The error message is not generated if the user manually updates the profile with the new mailbox server, or if the user creates a new Outlook profile.
-
This issue occurs in the release version of Exchange Server 2010 and in Exchange Server 2007 Service Pack 2 (SP2) and earlier versions.
Resolution
To resolve this issue, install Exchange Server 2007 SP3 on the Exchange Server 2007 mailbox server, and install Exchange Server 2010 SP1 on the Exchange Server 2010 mailbox server.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
After a Move-Mailbox operation, Outlook receives a referral from the Exchange mailbox server on which the mailbox was formerly located. In this referral response, an ecWrongServer value is returned to Outlook. The response includes the homeMDB attribute that points to the new Exchange mailbox server for the user's mailbox. Before you install Exchange Server 2007 on the Exchange Server 2007 mailbox server and Exchange Server 2010 SP1 on the Exchange Server 2010 mailbox server, the old Exchange mailbox server exhibits the following behavior:
-
The old Exchange server sends its own name as the new homeMDB server in the ecWrongServer response name. Therefore, Outlook continues to connect to the old Exchange server.
-
The old Exchange server provides a referral to the new Exchange server. But the profile still shows the Exchange server as the old Exchange server.
-
When you view the General tab in the Connection Status box, you see a referral to the new Exchange server.
Delay in updating the profile
If Outlook is running, this issue is eventually resolved by itself in 30 minute or more. This is especially true if the user has many connections to other servers, such as shared folders or shared mailboxes and calendars. This indicates that Mailbox Cache Age Limit is set to a value that is too high.
You can resolve this issue by reducing the cache expiration time. For more information, visit the following Microsoft website:
General information about why the mailbox size limits do not take effect immediately after a configuration change
To change the Mailbox Cache Age Limit value, follow these steps:
-
On the Exchange Server Mailbox servers, click Start
-
Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
-
Right-click ParametersSystem, click New, and then click DWORD (32-bit) Value.
-
Type Mailbox Cache Age Limit, and then press ENTER.
-
Right-click Mailbox Cache Age Limit, and then click Modify.
-
On the Base tab, click Decimal.
-
In the Value data box, type a positive integer to specify the Mailbox Cache Age Limit in minutes. The default value is 2 hours (120 minutes).
Time to update profile
After you reduce the Cache limit to a value such as 15 minutes, you may still experience delays in updating the profile.
The reason for this delay is that the Exchange server cache array on the client is currently limited to 16 entries at a time. Each entry expires in 60 seconds. The client behavior is to verify an entry that is close to expiration and replace it with the newest requested server. If there are many connections at the startup of the Outlook client, the new home server may not be inserted into the array for several minutes. A minute or more delay in updating the Outlook profile is common.
Note If the old Exchange server is turned off before you restart Outlook, clients cannot connect to the new homeMDB server if the profile is not updated.
For more information about a similar issue, click the following article number to view the article in the Microsoft Knowledge Base:
978469 A mailbox that was moved from an Exchange Server 2007 server to an Exchange Server 2010 server cannot be accessed by using Outlook For more information about how to obtain the latest Service Pack or Update Rollup for Exchange Server 2007, visit the following Microsoft website:
General information about how to obtain the latest Service Pack or Update Rollup for Exchange Server 2007For more information about Exchange Server 2010 Servicing, visit the following Microsoft website:
