Replication Does Not Update Administrative Subentry Automatically (268973)
The information in this article applies to:
- Microsoft Metadirectory Services 2.2
This article was previously published under Q268973 SYMPTOMS
After you successfully run a replication agreement between Microsoft Metadirectory Services (MMS) 2.2 servers, changes that are made to administrative subentries in the supplier computer are not automatically refreshed in the consumer computer.
CAUSE
This problem occurs because Replica.exe does not force a refresh of the administrative cache on the consumer computer at the conclusion of the replication agreement.
RESOLUTIONA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next version of Microsoft Metadirectory Services that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
--------------------------------------------------
08-25-2000 21:35 1124 1,503,744 Replica.exe
WORKAROUND
To compensate for the lack of automation without applying the hotfix, use either of the following methods:
- Manually disable the administrative subentries manually and then re-enable them.
- Shut down and restart the entire server.
Note that you should use these workarounds only when administrative subentry changes occur on the supplier computer. You must use the workaround on each consumer computer each time the replication agreement runs.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Minor | Last Reviewed: | 10/7/2005 |
|---|
| Keywords: | kbbug kbfix kbQFE KB268973 |
|---|
|