Event ID 13568

Chicago Area Laptop for rent: $35 per day plus $10 for additional day

Event ID 13568 - The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Event ID 1058 - Windows cannot access the file gpt.ini for GPO

Logon scripts don’t synchronize between two domain controllers

Group Policies may not update between DCs

“INFO: The policy object does not exist”

“RSoP data invalid. Likely causes are, data is corrupt, data has been deleted or data has never been created."

Symptoms: If you have the following symptoms, you may have a File Replication Service issue:

1. In DC, you may receive Event ID 13568 - The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

2. In client, you receive Event ID 1058 - Windows cannot access the file gpt.ini for GPO CN={9DAFE49D-7B7D-455F-B0A6-FDBCC643C2F4},CN=Policies,CN=System,DC=chicagotech,DC=net. The file must be present at the location <\\chicagotech.net\SysVol\chicagotech.net\Policies\{9DAFE49D-7B7D-455F-B0A6-FDBCC643C2F4}\gpt.ini>. (The system cannot find the path specified. ). Group Policy processing aborted.

3. Logon scripts don’t synchronize between two domain controllers. Case study: We have two domain controllers named chicagotech and ms-mvps. After modified a logon script on the chicagotech, it never be updated to the ms-mvps. The problem is some computers may not run logon script if they connect to DC ms-mvp for authentication.

4. Group Policies may not update between DCs. Case study: After created a group policy on the chicagotech, it never be updated to the ms-mvps. The problem is the group policy may not apply to some computers if they connect to DC ms-mvp for authentication.

5. When using gpresult to check the group policy on a workstation, you may receive this error: “INFO: The policy object does not exist”.

6. When running rsop.msc to check group policy status, you may receive this error: “RSoP data invalid. Likely causes are, data is corrupt, data has been deleted or data has never been created."

Causes:

After a DC crashed, you try to re-store it.
You just move the SYSVOL to a different location.
Many files are added at once to a replica tree while FRS is busy, starting up, or not running.
On a server that is being used for authoritative restore, or as the primary server for a new replica partner, excessive file activity at the start of this process can consume NTFS USN journal records. Size the NTFS volume at 128 MB per 100,000 files being managed by FRS, as mentioned above, to avoid this condition.
NTFS needs to be processed with Chkdsk and Chkdsk corrects the NTFS structure. In this case, NTFS creates a new NTFS USN journal for the volume or deletes the corrupt entries from the end of the journal.
The NTFS USN journal is deleted or reduced in size.

Resolution: To fix these issues, you the administrator may need to perform a non-authoritative restore of the data.

FRS Tools

Perform a non-authoritative restore of the data

How to Repadmin.exe Tool to diagnose Replication Status