Error 13506 Errors with NTFRS on DC's

[Guest]

We are getting persistent NTFRS Errors on 4 DC's as follows:

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13506
Date: 8/7/2003
Time: 1:48:40 PM
User: N/A
Computer: <computername>
Description:
The File Replication Service failed a consistency check
(FRS_SUCCESS(FStatus) || !"ISCU_DEL_IDT_ENTRY failed")
in "ChgOrdIssueCleanup:" at line 8328.

I have applied 811370 Patch to one of the servers but it still fails within
minutes of the service restarting.

I guess I am looking at a non-authorative restore next but would like some
sort of acknowledgement that it is the only way forward.

__
Steve Wilson
Global Directory Services Team

 

[Huseyin Dursun [MSFT]]

Hi Steve,

What you are seeing is a failure to delete a record from the IDTable during the change order cleanup. We need to see logs to understand what caused this. I don't thinsk patch would help to fix this. D2 would fix the problem. Are you using SONAR for monitoring FRS? Below is the link for SONAR and troubleshooting guide:

http://www.microsoft.com/windows2000/techinfo/reskit/tools/new/sonar-o.asp (FRS Troubleshooting package - sonar v1.0.1158) + troubleshooting guide)


--
Huseyin Dursun [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights

Please post FRS related queries in newsgroup
microsoft.public.windows.file_system. Please use "FRS" in the subject to make it
immediately noticeable.

 

[Huseyin Dursun [MSFT]]

FRS logs are located at %windir%\debug and their naming schema is
NtFrs_xxxx.log.

SONAR comes with a troubleshooting guide and Chapter 4 is fully dedicated to
monitoring. You ca nget familiar with SONAR just by scanning this chapter.
For download:
http://www.microsoft.com/windows2000/techinfo/reskit/tools/new/sonar-o.asp
(FRS Troubleshooting package - sonar v1.0.1158) + troubleshooting guide)


--
Huseyin Dursun [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights

Please post FRS related queries in newsgroup
microsoft.public.windows.file_system. Please use "FRS" in the subject to
make it
immediately noticeable.

Thanks for the swift reply. you are absolutely correct
that the patch doesn't cure it!
I am using SONAR, though I am am not too sure what all of
it means.
Which logs would you like to see?

__
Steve Wilson

-----Original Message-----
Hi Steve,

What you are seeing is a failure to delete a record from

the IDTable during the change order cleanup. We need to
see logs to understand what caused this. I don't thinsk
patch would help to fix this. D2 would fix the problem.
Are you using SONAR for monitoring FRS? Below is the link
for SONAR and troubleshooting guide:

http://www.microsoft.com/windows2000/techinfo/reskit/tool

s/new/sonar-o.asp (FRS Troubleshooting package - sonar
v1.0.1158) + troubleshooting guide)

--
Huseyin Dursun [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights

Please post FRS related queries in newsgroup
microsoft.public.windows.file_system. Please use "FRS" in the subject to make it
immediately noticeable.

We are getting persistent NTFRS Errors on 4 DC's as follows:

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13506
Date: 8/7/2003
Time: 1:48:40 PM
User: N/A
Computer: <computername>
Description:
The File Replication Service failed a consistency check
(FRS_SUCCESS(FStatus) || !"ISCU_DEL_IDT_ENTRY failed")
in "ChgOrdIssueCleanup:" at line 8328.

I have applied 811370 Patch to one of the servers but it still fails within
minutes of the service restarting.

I guess I am looking at a non-authorative restore next but would like some
sort of acknowledgement that it is the only way forward.

__
Steve Wilson
Global Directory Services Team

 

[Huseyin Dursun [MSFT]]

Steve, I don't suggest you modifying "Replica Set Parent" key. Just perform
plain "D2" process.

Ultrasound beta registration is closed and it is getting close to release.
Expected release to web is end of August. So please check back microsoft.com
end of August or early Sep.


--
Huseyin Dursun [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights

Please post FRS related queries in newsgroup
microsoft.public.windows.file_system. Please use "FRS" in the subject to
make it
immediately noticeable.

Huseyin, first thanks for your assistance to date. Very helpful in
clarifying the way forward.

We are almost ready to progress but would probably like to take advantage of
the "Replica Set Parent" registry key.
We have multiple connections on our DC's both intra and inter site. This
looks like the solution to save us deleting all existing connection objects
prior to the restore. Although this key is refered to by name in several
places, the only documentation that refers to it giving the specific
location seems quite unhelpful. KB 257338 says:

"After the Dcpromo.exe program has restarted the computer, FRS first
attempts to source the SYSVOL from the computer identified in the "Replica
Set Parent" registry key under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTFRS\Parameters\SysVol
\DomainName

NOTE:This key is temporary and is deleted once SYSVOL is sourced, or the
information under SYSVOL has been successfully replicated."

Can you confirm if we recreate that key for the restore or is it under the
"Replica Sets" Key??

Finally where can we get the beta of Ultrasound?

Thanks in advance

__
Steve Wilson

FRS logs are located at %windir%\debug and their naming schema is
NtFrs_xxxx.log.

SONAR comes with a troubleshooting guide and Chapter 4 is fully

dedicated

to
monitoring. You can get familiar with SONAR just by scanning this chapter.
For download:
http://www.microsoft.com/windows2000/techinfo/reskit/tools/new/sonar-o.asp
(FRS Troubleshooting package - sonar v1.0.1158) + troubleshooting guide)


--
Huseyin Dursun [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights

Please post FRS related queries in newsgroup
microsoft.public.windows.file_system. Please use "FRS" in the subject to
make it
immediately noticeable.

Thanks for the swift reply. you are absolutely correct
that the patch doesn't cure it!
I am using SONAR, though I am am not too sure what all of
it means.
Which logs would you like to see?

__
Steve Wilson



-----Original Message-----
Hi Steve,

What you are seeing is a failure to delete a record from
the IDTable during the change order cleanup. We need to
see logs to understand what caused this. I don't thinsk
patch would help to fix this. D2 would fix the problem.
Are you using SONAR for monitoring FRS? Below is the link
for SONAR and troubleshooting guide:

http://www.microsoft.com/windows2000/techinfo/reskit/tool
s/new/sonar-o.asp (FRS Troubleshooting package - sonar
v1.0.1158) + troubleshooting guide)


--
Huseyin Dursun [MSFT]
This posting is provided "AS IS" with no warranties, and
confers no rights

Please post FRS related queries in newsgroup
microsoft.public.windows.file_system. Please use "FRS"
in the subject to make it
immediately noticeable.



We are getting persistent NTFRS Errors on 4 DC's as
follows:

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13506
Date: 8/7/2003
Time: 1:48:40 PM
User: N/A
Computer: <computername>
Description:
The File Replication Service failed a consistency check
(FRS_SUCCESS(FStatus) || !"ISCU_DEL_IDT_ENTRY
failed")
in "ChgOrdIssueCleanup:" at line 8328.

I have applied 811370 Patch to one of the servers but
it still fails within
minutes of the service restarting.

I guess I am looking at a non-authorative restore next
but would like some
sort of acknowledgement that it is the only way
forward.

__
Steve Wilson
Global Directory Services Team