Blogging about Open Software Solutions

Consider the following scenario:

•	You have a Windows Server 2008-based writable domain controller and a Windows Server 2008-based read-only domain controller (RODC). Some client computers that exist in one site belong to the same domain.
•	The Windows Server 2008-based RODC exists in a perimeter network (also known as DMZ, demilitarized zone, and screened subnet).
•	Some users use a domain account to log on to the domain from a client computer that is in the site.

In this scenario, Event ID 1699 is logged many times in the Directory Service event log of the writable domain controller. These events resemble the following event:

Source: NTDS Replication
Date: Date
Event ID: 1699
Level: Error
Keywords: Classic
User: user name
Computer: computer name
Description:
This directory service failed to retrieve the changes requested for the following directory partition. As a result, it was unable to send change requests to the directory service at the following network address.

Directory partition: Distinguished Name (DN)
Network address: address

Additional Data
Error value: 8453 Replication access was denied.

Sometimes, Event ID 2041 may also be logged. The event that is logged resembles the following event:

Event Type: Information
Event Source: NTDS General
Event Category: Internal Processing
Event ID: 2041
Date: date
Time: time
User: N/A
Computer: computer name
Description:
Duplicate event log entries were suppressed.
See the previous event log entry for details. An entry is considered a duplicate if the event code and all of its insertion parameters are identical. The time period for this run of duplicates is from the time of the previous event to the time of this event.

Event Code: c00006a3
Number of duplicate entries: 1

These events fill the Directory Service event log and prevent administrators from troubleshooting issues according to the event logs.

Back to the top

When a Windows Server 2008 RODC tries to cache the password of a principal, a writable domain controller performs a check to determine whether this operation is permitted. If this operation is not permitted, an error code is returned. This is expected behavior. However, Event 1699 may incorrectly be logged when the error code is returned.

Back to the top

A hotfix is available to resolve this issue. After you install this hotfix, the server does not log Event ID 1699 in the scenario that is mentioned in the Cause section. In other scenarios, the event is still logged.

Back to the top

Hotfix information

A supported hotfix is 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 software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

T o apply this hotfix, you must have Windows Server 2008 installed on the writable domain controller.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

File information

The English 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.

Windows Server 2008, x86-based versions

File name	File version	File size	Date	Time	Platform
Package_1_for_kb951685~31bf3856ad364e35~x86~~6.0.1.0.mum	Not applicable	1,956	22-Apr-2008	21:15	Not applicable
Package_2_for_kb951685~31bf3856ad364e35~x86~~6.0.1.0.mum	Not applicable	1,794	22-Apr-2008	21:15	Not applicable
Package_for_kb951685_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum	Not applicable	1,367	22-Apr-2008	21:15	Not applicable
Package_for_kb951685_client~31bf3856ad364e35~x86~~6.0.1.0.mum	Not applicable	1,430	22-Apr-2008	21:15	Not applicable
Package_for_kb951685_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not applicable	1,425	22-Apr-2008	21:15	Not applicable
Package_for_kb951685_server~31bf3856ad364e35~x86~~6.0.1.0.mum	Not applicable	1,430	22-Apr-2008	21:15	Not applicable
Update.mum	Not applicable	2,082	22-Apr-2008	21:15	Not applicable
X86_fc90ec598e96b8257198feaf7ec1c337_31bf3856ad364e35_6.0.6001.22164_none_ffe88c50416adaaf.manifest	Not applicable	709	22-Apr-2008	21:15	Not applicable
X86_microsoft-windows-enhancedvideorenderer_31bf3856ad364e35_6.0.6001.22164_none_8fef3c16e5d12be0.manifest	Not applicable	10,973	22-Apr-2008	07:52	Not applicable
Evr.dll	6.0.6001.22164	485,888	22-Apr-2008	06:49	x86

Windows Server 2008, x64-based versions

File name	File version	File size	Date	Time	Platform
Amd64_a4c69a6423ef0040eced90201db417fa_31bf3856ad364e35_6.0.6001.22164_none_87501d54587c6303.manifest	Not applicable	1,066	22-Apr-2008	21:15	Not applicable
Amd64_microsoft-windows-enhancedvideorenderer_31bf3856ad364e35_6.0.6001.22164_none_ec0dd79a9e2e9d16.manifest	Not applicable	10,999	22-Apr-2008	17:06	Not applicable
Package_1_for_kb951685~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not applicable	2,195	22-Apr-2008	21:15	Not applicable
Package_2_for_kb951685~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not applicable	2,031	22-Apr-2008	21:15	Not applicable
Package_for_kb951685_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not applicable	1,375	22-Apr-2008	21:15	Not applicable
Package_for_kb951685_client~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not applicable	1,438	22-Apr-2008	21:15	Not applicable
Package_for_kb951685_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not applicable	1,433	22-Apr-2008	21:15	Not applicable
Package_for_kb951685_server~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not applicable	1,438	22-Apr-2008	21:15	Not applicable
Update.mum	Not applicable	2,096	22-Apr-2008	21:15	Not applicable
X86_microsoft-windows-enhancedvideorenderer_31bf3856ad364e35_6.0.6001.22164_none_8fef3c16e5d12be0.manifest	Not applicable	10,973	22-Apr-2008	07:52	Not applicable
Evr.dll	6.0.6001.22164	648,704	22-Apr-2008	07:16	x64
Evr.dll	6.0.6001.22164	485,888	22-Apr-2008	06:49	x86

Back to the top

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

Back to the top

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

Back to the top