Microsoft KB Archive/916694

= Mailbox rule synchronization may be delayed when you move mailboxes from a server that is running Exchange 2000 Server to a server that is running Exchange Server 2003 SP2 =

Article ID: 916694

Article Last Modified on 10/30/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Service Pack 2

-





Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
When you move several mailboxes from a server that is running Microsoft Exchange 2000 Server to a server that is running Microsoft Exchange Server 2003 Service Pack 2 (SP2), mailbox rule synchronization may be delayed. Therefore, the mailbox rules may not work for some time after the mailboxes are moved.



Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
Because of file dependencies, you must be running Exchange Server 2003 Service Pack 2 (SP2) to install this hotfix.

Note This hotfix resolution is for Exchange Server 2003 SP2 only. Therefore, you can use this hotfix only for migration scenarios in which the target or destination server is an Exchange Server 2003 SP2 server.

Restart requirement
You do not have to restart the computer after you apply the hotfix. However, the Microsoft Exchange Information Store service and all dependent services will be restarted.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

How to change the frequency with which rules are synchronized
When you move mailboxes from a server that is running Exchange 2000 Server to a server that is running Exchange Server 2003 SP2, the rules are moved in a server-independent format. Eventually, the rules are converted to rule messages that are appropriate for the new target server.

Mailbox rule synchronization occurs in a background process that fires periodically. A single mailbox is synchronized every time that the background process fires. This behavior occurs even if the following conditions are true:
 * Several mailboxes have been successfully moved.
 * Mailboxes are ready to be synchronized.

After you install this hotfix, rule synchronization is faster for all mailboxes that have already been moved.

By default, mailbox rules are synchronized every hour after you install this hotfix. However, you can change the frequency with which rules are synchronized. To do this, change the following registry entry:

This registry entry is a DWORD value. This value for this registry entry represents seconds. The minimum value that you can use is 60 seconds. The maximum value that you can use is 2,592,000 seconds (30 days). By default, the value is set to 3600.

Warning If you set the value to 60 seconds to achieve the fastest possible synchronization time, you may actually cause the synchronization process to take longer. This behavior occurs because the average sized mailbox takes two to three minutes to move. Additionally, only those mailboxes that have been moved can be synchronized.

How to change the number of mailboxes that are synchronized
If you find that Exchange synchronizes rules for too may mailboxes at a time after you install this hotfix, you can limit the number of mailboxes that are synchronized at a time. To do this, change the following registry entry:

This registry entry is a DWORD value. The minimum value that you can use is 1. The maximum value that you can use is 0xFFFFFFFF. By default, this registry entry is set to the number of mailboxes that are ready to be synchronized.

The value of this registry entry is based on the number of mailboxes that you want to synchronize at a time. For example, if you set the value to 1, you want one mailbox to be synchronized every time that the synchronization process occurs. Additionally, the value of 0xFFFFFFFF is a special value that means that you want all the mailboxes to be synchronized during the synchronization process.

How to change the number of times that Exchange will retry synchronization
You can set the number of times that Exchange will retry synchronization if synchronization is not successful. To do this, change the following registry entry:

This registry entry is a DWORD value. The minimum value that you can use is 0. The maximum value that you can use is 250. By default, this registry entry is set to 24.

How to monitor the synchronization process
If rule synchronization is not successful, the following event is logged if the diagnostic level for rules is set to Medium or to Maximum.

Note These events are logged only when synchronization is not successful because the mailbox move is still in progress. Event ID: 115

Source: MSExchangeIS Mailbox

Description: A rule synchronization error (1144) has occurred on Mailbox Store&quot;. The mailbox folder is Top of Information Store\Inbox. The distinguished name of the owning mailbox is /O=  /OU=   /CN=Recipients/CN=s140605. There are 24 of 24 retries remaining.

If synchronization is successful, the following event is logged when you set diagnostic level for rules to Maximum: Event ID: 1154

Source: MSExchangeIS Mailbox

Description: Rule synchronization has successfully completed. The mailbox folder is Top of Information Store\Inbox on database&quot;  &quot;. The distinguished name of the owning mailbox is /O=  /OU=   /CN=Recipients/CN=s140605.

For more information about terminology used in Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

For more information about the naming schema for Exchange software updates, click the following article number to view the article in the Microsoft Knowledge Base:

817903 New naming schema for Exchange Server software update packages

Additional query words: XADM

Keywords: kbhotfixserver kbqfe kbfix kbbug kbpubtypekc KB916694

-

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

© Microsoft Corporation. All rights reserved.