> I love that typo the tool gives... *Could* not find parent for 2 entrie(s)
> in IDTable. Bleh.
>
> Anyways, this situation is incredibly rare to get into - somehow two folders
> have had their parent folder deleted without they themselves being deleted,
> at least in the FRS database's view of things. Don't ask me how, I don't
> have a good answer for you, but it's some kind of timing issue.
>
> You have two options to fix this:
>
> 1. Find these two folders on any server wehere they are being replicated and
> delete them. You can use
>
> NTFRSUTL IDTABLE > idtable.txt
> NTFRSUTL OUTLOG > outlog.txt
> Frsdiag's GUID2NAME function to identify where everything is and who your
> originating server was.
>
> Then delete these two folders or move them entirely out of FRS. It should
> replicate the proper deletion and clear all this up.
>
> 2. If that doesn't work, you can use a D2 BURFLAG to simply force the
> machine having the issue to rebuild its data and database from another
> working server, using
>
> 290762 Using the BurFlags registry key to reinitialize File Replication
> Service replica sets
>
http://support.microsoft.com/default.aspx?scid=kb;EN-US;290762>
>
> --
>
> Ned Pyle
> Microsoft Enterprise Platform Support
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Please read
http://www.microsoft.com/info/cpyright.htm for more information.
>
>
> "Rj" <Rj[ at ]discussions.microsoft.com> wrote in message
> news:705A0908-E239-4814-91EE-4491D00DC886[ at ]microsoft.com...
> > Hi , Ultrasound alerted us to an error " Two days in sharing violation
> > install/staging"
> >
> > So I followed the suggestion and KB articles and ended up running FRSDiag
> > with and got the report from it (copied below. Now how do i remove these
> > enteries from the AD ? Please help. thanx.
> >
> > -------------------------------------------------------------------------------------------
> > FRSDiag v1.7 on 3/07/2007 2:19:01 PM
> > .\Logs\W3xxxDC1 on 2007-07-03 at 2.19.01 PM
> > ------------------------------------------------------------
> >
> >
> > Checking for missing parent entries in IDTable ...
> > ERROR -- Cound not find parent for 2 entrie(s) in IDTable! Listing them
> > below (and also on the IDTable output)...
> > 1778db57-2cfb-4d42-838b3128c501f68d 3b0e36f5-8432-4ee5-82618bf525bbe606
> > Thu Jul 4, 2002 11:08:44 e11345f1-a5db-4254-a263b9d3901758d1 True
> > BRANDING
> > 3b0e36f5-8432-4ee5-82618bf525bbe606 c7ee6756-6ac7-4d3a-b4b9aedeaf90d0fe
> > Thu Jul 4, 2002 11:08:00 e11345f1-a5db-4254-a263b9d3901758d1 True IEAK
> > ......... failed
> >
> > -------------------------------------------------------------------------------------------
> >
>
>