Have a Question?
< All Topics
Print

Sysvol Replication failed due to cab_xxx files

Posted
Updated
ByYongKW

Steps to resolve the sysvol replication failed due to cab_xxx files

Issues reported by our client

  1. Group Policy is NOT applied to client machines
  2. C Drive only have 0% Free Space

C Drive filled up by cab_xxx files

We noticed the there are several cab_xxx files located in C:\Windows\Temp and caused C Drive to full

Refer to Large Trusted Installer CBS log (Over 2GB), and the following steps are taken

  1. Stopped Windows Modules Installer (TrustedInstaller) Service
  2. Delete all the files in C:\Windows\Logs\CBS
  3. Delete all the files started with cab_xxxx in C:\Windows\Temp
  4. Started Windows Modules Installer (TrustedInstaller) Service
  5. Monitor for half an hours and there is no more cab_xxxx files generated in C:\Windows\Temp

Group Policy is NOT applied

We noticed that following error message in Event Viewer on one of the Domain Controller

  • File Replication failed due to no free space
  • The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR
  • GPO Policies files in C:\Windows\SYSVOL\domain\Policies are NOT the same in both Domain Controllers

Sysvol Replication failed due to cab_xxx files

How to resolve Sysvol Replication failed due to cab_xxx files

The following steps are taken by refering to [Solved] NTFRS – Journal Wrap Errors detected on Domain Controller

  1. Create a new REG_DWORD–Enable Journal Wrap Automatic Restore–Value=1– under HKLM:\System\CurrentControlSet\Services\NtFrs\Parameters

  1. Restart File Replication Services
 Get-Service -Name "NtFrs" | Restart-Service
  1. Wait for few minutes until the following message show in Event Viewer

  1. Verify the no of files in C:\Windows\SYSVOL\domain\Policies are same in both AD Domain Controllers now

  2. Manually create a new file / folder in C:\Windows\SYSVOL\domain\scripts and it should appear in the 2nd Domain Controller – Sysvol Replication is working fine

  3. Go to Registry and change the value of Enable Journal Wrap Automatic Restore back to 0

There should be no error message when users try to enforce the GPO via "gpupdate /force"

Table of Contents
Scroll to Top