Re: Write Conflict
- From: Paul Bergson [MVP-DS] <pbbergs@xxxxxxxxxxxxxx>
- Date: Thu, 13 Nov 2008 13:14:35 +0000 (UTC)
Hello soregg,
This is odd, not much to go on here.
Run diagnostics against your Active Directory domain.
If you don't have the support tools installed, install them from your server install disk.
d:\support\tools\setup.exe
Run dcdiag, netdiag and repadmin in verbose mode.
-> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
-> dnslint /ad /s "ip address of your dc"
**Note: Using the /E switch in dcdiag will run diagnostics against ALL dc's in the forest. If you have significant numbers of DC's this test could generate significant detail and take a long time. You also want to take into account slow links to dc's will also add to the testing time.
If you download a gui script I wrote it should be simple to set and run (DCDiag and NetDiag). It also has the option to run individual tests without having to learn all the switch options. The details will be output in notepad text files that pop up automagically.
The script is located on my website at http://www.pbbergs.com/windows/downloads.htm
Just select both dcdiag and netdiag make sure verbose is set. (Leave the default settings for dcdiag as set when selected)
When complete search for fail, error and warning messages.
Description and download for dnslint
http://support.microsoft.com/kb/321045
--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup This posting is provided "AS IS" with no warranties, and confers no rights.
Hi all,
I would like to ask for advice to solve the problem. I am using w2k3
server
as the DCs
Thanks, soregg
Active Directory encountered a write conflict when applying replicated
changes to the following object.
Object:
CN=Administrator,CN=Users,DC=<mydomain>
Time in seconds: 0
Event log entries preceding this entry will indicate whether or not
the update was accepted.
A write conflict can be caused by simultaneous changes to the same
object or simultaneous changes to other objects that have attributes
referencing this object. This commonly occurs when the object
represents a large group with many members, and the functional level
of the forest is set to Windows 2000. This conflict triggered
additional retries of the update. If the system appears slow, it could
be because replication of these changes is occurring.
User Action
Use smaller groups for this operation or raise the functional level to
Windows Server 2003.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
.
- References:
- Write Conflict
- From: soregg
- Write Conflict
- Prev by Date: Re: upgrade plan to 2008
- Next by Date: Re: Metadata cleanup
- Previous by thread: Re: Write Conflict
- Next by thread: Re: Write Conflict
- Index(es):
Relevant Pages
|
