windows-server-2008

The Processing of Group Policy Failed


There are a number of reasons why The processing of Group Policy failed error could happen. When you try to run gpupdate /force you receive the following error:

User policy could not be updated successfully. The following errors were encountered.

The processing of Group Policy failed. Windows attempted to read the file domain.localSysVoldomain.localPolicies{Policy_Folder}gpt.ini from a domain controller and was not successful. Group Policy settings my not be applied until this event is resolved.

This issue may be transient and could be caused by one or more of the following:

This issue may be transient and could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain controller.
b) File Replication Service Latency (a file created on another domain controller
has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled
.

the processing of group policy failed. windows attempted to read the file

You may encounter such an error not only when you manually run the gpupdate /force command, but also after running DCDIAG tools, in the Event Viewer when a user login. In some cases, when this error appears, you won’t be able to open network shared folders or DFS domain resources with the error “The Network Path Was Not Found”.

The error can occur both on desktops (Windows 10, 8.1, 7) and on Windows Server 2016/2012 R2/2008 R2.

What is the Сause of The processing of Group Policy failed Error?

The first thing you will want to do is take a look at the Event Viewer logs. Check if there are any event logs related to the Journal Wrapping error which was causing File Replication Services to fail on our domain controllers.

The error usually looks like this: The File Replication Service has detected that the replica set “DOMAIN SYSTEM VOLUME(SYSVOL SHARE)” is in JRNL_WRAP_ERROR

the processing of group policy failed

This error may indicate damage to the SYSVOL folder in domains where replication is based on outdated FRS instead of more modern DFS replication. Compare the contents of the folder on the problem domain controller DC_namesysvoldomain.localPolicies with any other DC. You can force the sysvol folder to synchronize from another DC.

Microsoft’s solution says that you can force the sysvol folder to synchronize in the problem DC from another DC:

  1. Open the Registry Editor (regedit.exe);
  2. Go to the registry key HKEY_LOCAL_MACHINESystemCurrentControlSetServicesNtFrsParameters;
  3. Change (create) a registry key named “Enable Journal Wrap Automatic Restore” and change its value to 1;
  4. Restart the NTFRS service: net stop ntfrs && net start ntfrs
  5. Verify that the following events in the File Replication Service log consistently appear.:
    Event ID 13553 – The File Replication Service successfully added this computer to the following replica set: “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)”
    Event ID 13554 – The File Replication Service successfully added the connections shown below to the replica set: “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)”
  6. Wait a while. After successful replication the following event should appear:
    Event ID 13516 – The File Replication Service is no longer preventing the computer DC from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.
  7. Now you need to change the value Enable Journal Wrap Automatic Restore to 0;
  8. Make sure that Netlogon and Sysvol shared folders are accessible on the domain controller.

However if you are running on a post Windows Server 2000 than this is not a good solution. Instead you should use the Burflags method as described by Rune in this article: http://adfordummiez.com/?p=61

If you didn’t find the “Journal Wrapping” error in the client’s Event Viewer, open the services console (services.msc) and check that the “TCP/IP Netbios Helper” service is running and its startup type is set to automatic.

the processing of group policy failed windows attempted to read the file

Perhaps the error is related to problems with DNS or with the domain controller itself. Use the nslookup and ping utility to check that your DNS server (usually this is a domain controller) is available and responding. You can find out the name of your domain controller with the command:

systeminfo | find "Logon Server"

In this example, your DC name is xxx-dc01.

the processing of group policy failed. windows attempted to read the file gpt.ini

If the previous command returned N/A, then your DC is not accessible.

processing of group policy failed

You need to check the availability of the domain controller with the commands:

Ping xxx-dc01

Nslookup xxx-dc01

Make sure both commands return a successful response.

Check availability of DC via RPC protocol using the command:

nltest /dsgetdc:yourdoman.com

the processing of group policy failed gpt.ini

Try to open the list of network folders on DC by clicking WIN+R > Run > Type “xxx-dc01”.

You should see a list of folders on your domain controller. Among them must be the folders NetLogon and Sysvol.

windows attempted to read the file gpt.ini

If DC is available:

  1. Check that the computer account in Active Directory is active;
  2. Delete the file C:WindowsSystem32GroupPolicyMachineRegistry.pol;
  3. Restart the computer.

After that try running gpupdate /force and it should result in success!

gpt.ini from a domain controller and was not successful

User Policy update has completed successfully.

Computer Policy update has completed successfully.

Comments
  1. Posted by Mike

Add Your Comment