GP Core Failure

[JCLSB]

On a DC with an Appliciation Log error of 1030 and the Administrator logged
on I opend the GPMC.MSC and open the GPResults(becuse it had a red check and
a + sign). It showed "administrator on MUSTANG" (MUSTANG is the server name)
and under "User Configuration Summary", under "Component Status" there is a
Red circle with an x in it. Selecting Show reveals the following
Group Policy Infrastructure failed due to the error listed below.
Overlapped I/O operations is in progress.
Note: Due to the GP Core failure, none of the other Group Policy
components processed their policy. Consequently, status information for the
other components is not available.

DCDIAG shows MUSTANG failed test frsevent and kccevent.
NETDIAG shows no errors.

In the File Replication Log there are 13505 NtFrs warnings to only 1 of the
other 3 DCs, as follows;
The File Replication Service is having trouble enabling replication from
GPSERVER to MUSTANG for c:\windows\sysvol\domain using the DNS name
gpserver.DOM01.local. FRS will keep retrying.

On the other DCs in the Domain where the Administrator logs on, there is no
proplem with the Group Policy. This DC holds the FSMO rolls.

What must be done to correct the Group Policy problem.

[G3S]

Hi there,

I just wondered if you had resolved this problem yet?
I have 4 DC's and one of them has the same problem - not processing
GPO's or forcing them onto clients, even though replication al appears
OK.
Although DCDiag showed no errors I had the same errors in GPMC.MSC

I would be grateful for any feedback, as I have tried everything I can
find at the moment - and I am now facing a complete re-format and
staring from scratch with this DC.

Thanks,

[JCLSB]

Hello,

No , I have the same problem, I have found that when I ran a program
called DumpSec it showed the Sysvol on 3 of the 4 DC's but one of the DC's
the Sysvol did not show up. The Sysvol was not on the DC that was
experiencing the 1030 error however. The DC where the Sysvol did not show
up, I did a dcpromo. The first time I did it, it would only let me perform
it as if was the last domain controller. After I ran the DC promo I noticed
it was still an active directory DC controller. Wehn I ran it a second time,
it would only let me run it as if it was an additional DC in the Domain.
Once out of the DC role, I removed it from the domain and then rejoind it to
the domain. I then ran a DC promo again and everything appeared to run fine,
however the DumpSec still shows that the DC is not sharing the Sysvol. When
I compare the DumpSec on the 3 DC's that I can locate the Sysvol, they all
show the same permissions. I realy do not want to start over on the DC that
I am receiving the error on because SharePoint Services is running on it.