Event ID 1955 after upgrade to WINDOWS 2003
Spale
upgrade my servers at central location and then i upgrade two servers in
other site.Now i've found Event ID 1955:
Active Directory encountered a write conflict when applying replicated
changes to the following object.
Object:
CN=75459748-e1d0-4d90-9452-34fe5dc149b3,CN=NTDS
Settings,CN=SA2DC2,CN=Servers,CN=SA2,CN=Sites,CN=Configuration,DC=vbba,DC=vo
lksb
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.
How to deal with this?
Jack Wang [MSFT]
Thank you for posting!
Please help me to collect the following information.
1. Does the error event appeer on all the three servers?
2. Which server in which site did you find the error?
3. Use the MPSRPT_DirSvc.EXE tool to collect the computer information to me
at jac...@microsoft.com.
http://www.microsoft.com/downloads/details.aspx?FamilyID=cebf3c7c-7ca5-408f-
88b7-f9c79b7306c0&DisplayLang=en
4. Did you encounter a problem in the domain or site? What is the exact
symptom of it?
I am looking forward to your reply!
Sincerely,
Jack Wang, MCSE 2000, MCSA, MCDBA, MCSD
Microsoft Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Spale" <king2...@hotmail.com>
| Subject: Event ID 1955 after upgrade to WINDOWS 2003
| Date: Wed, 23 Jun 2004 13:41:42 +0200
| Lines: 44
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
| Message-ID: <eUceHcRW...@TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: 80.65.160.165
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12
phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.windows.server.migration:11618
| X-Tomcat-NG: microsoft.public.windows.server.migration
Spale
Jack Wang [MSFT]
Thank you for the detailed information.
The 1955 event is just a information that reports the write conflict on the
object.
I suggest you use ADSI Editor to check if the object is.
CN=75459748-e1d0-4d90-9452-34fe5dc149b3,CN=NTDS
Settings,CN=SA2DC2,CN=Servers,CN=SA2,CN=Sites,CN=Configuration,DC=vbba,DC=vo
lksb
If it is a corrupted object, you may remove it.
Also, I think the event may not related with the replication issue. Please
let me know the replication issue you encountered in detail. I need to know
the detail steps to reproduce the issue in Windows Server 2003.
I found that the FRS events contains the 13508 and 13509 warning events.
So, I suggest you install the following fix.
823230 Issues that are resolved in the pre-Service Pack 1 release of
Ntfrs.exe
http://support.microsoft.com/?id=823230
We are not equipped to send out and track hotfixes here in the Newsgroups
forum.
Please contact Microsoft Product Support Services directly 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:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
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.
Have a great day!
Sincerely,
Jack Wang, MCSE 2000, MCSA, MCDBA, MCSD
Microsoft Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Spale" <king2...@hotmail.com>
| References: <eUceHcRW...@TK2MSFTNGP12.phx.gbl>
<KCPSn5cW...@cpmsftngxa10.phx.gbl>
| Subject: Re: Event ID 1955 after upgrade to WINDOWS 2003
| Date: Thu, 24 Jun 2004 14:55:20 +0200
| Lines: 3
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
| X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
| Message-ID: <eXlh7peW...@tk2msftngp13.phx.gbl>
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: 80.65.160.165
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13
phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.windows.server.migration:11655
| X-Tomcat-NG: microsoft.public.windows.server.migration
Spale
servers.Also i don't have any more 13508 and 13509 events in my event viewer
butt i still have a lot of backlog files in my server on staging area.My
users from distance sites are complaining that they are having slow
connection and when i restart FRS everything seems to be ok.Latest test that
i do with Repl Mon including retired partner is this:
Active Directory Replication Domain Controller Replication Failure Output
Printed at 25.6.2004 9:36:08
Below are the replication failures detected on Domain Controllers for this
domain:
Domain Controller Name: SA3DC1
Directory Partition: DC=vbba,DC=volksbank,DC=ba
Replication Partner: **DELETED SERVER #13
Failure Code: 8524
Failure Reason: The DSA operation is unable to
proceed because of a DNS lookup failure.
Domain Controller Name: SA3DC1
Directory Partition:
CN=Configuration,DC=vbba,DC=volksbank,DC=ba
Replication Partner: **DELETED SERVER #13
Failure Code: 8524
Failure Reason: The DSA operation is unable to
proceed because of a DNS lookup failure.
Domain Controller Name: SA3DC1
Directory Partition:
CN=Schema,CN=Configuration,DC=vbba,DC=volksbank,DC=ba
Replication Partner: **DELETED SERVER #13
Failure Code: 8524
Failure Reason: The DSA operation is unable to
proceed because of a DNS lookup failure.
Domain Controller Name: SA3DC1
Directory Partition:
DC=DomainDnsZones,DC=vbba,DC=volksbank,DC=ba
Replication Partner: **DELETED SERVER #13
Failure Code: 8446
Failure Reason: The replication operation failed
to allocate memory.
Domain Controller Name: SA3DC1
Directory Partition:
DC=ForestDnsZones,DC=vbba,DC=volksbank,DC=ba
Replication Partner: **DELETED SERVER #13
Failure Code: 8446
Failure Reason: The replication operation failed
to allocate memory.
This is taken from the server in main site and this server SA3DC1 is live
server from the site where i demote old server.I was just delete AD
connection from this server SA3DC1 to server SA1DC2 in main site beaucouse
SA3DC1 is establish connection with other server in main site SA1DC1.Only
error i've found is this.How to deal with this?
Spale
with excessive replication.I send you an email.
Thanks in advance
Jack Wang [MSFT]
Thank you for the reply.
The reason for this error may be that the other domain controllers were
still trying to replicate because the KCC had not removed the objects yet.
The
other machine think that the old machine was still there.
So, I suggest you delete all the connection objects for SA3DC1 and recreate
it to try again.
Also, you may open the properties of this object and change the following
attribute
repltopologystayofexecution from <notset> to 1. If this value is not set
it
defaults to 14 days. The value is in days. This value is replicated to the
other domain controllers and it is up to the KCC on each machine to clean
up the replication objects. Once it is replicated and it has been 24 hours
the old replication objects will be removed. This value shoudl then be set
back to <not set>
If convenience, you may rebuild the SA3DC1 server after cleaning the server
information in the domain.
Let me know how it works!
Sincerely,
Jack Wang, MCSE 2000, MCSA, MCDBA, MCSD
Microsoft Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Spale" <king2...@hotmail.com>
| References: <eUceHcRW...@TK2MSFTNGP12.phx.gbl>
<KCPSn5cW...@cpmsftngxa10.phx.gbl>
<eXlh7peW...@tk2msftngp13.phx.gbl>
<10O$o3oWE...@cpmsftngxa10.phx.gbl>
<OgdfgipW...@tk2msftngp13.phx.gbl>
| Subject: Re: Event ID 1955 after upgrade to WINDOWS 2003
| Date: Fri, 25 Jun 2004 11:57:34 +0200
| Lines: 7
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
| Message-ID: <utYpRrpW...@TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: 80.65.160.165
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12
phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.windows.server.migration:11681
| X-Tomcat-NG: microsoft.public.windows.server.migration