EventID 1058 Code 5, Sysvol is subdir of Sysvol - how to fix?
- by nulliusinverba
I have been trying to resolve this error, like many others:
The processing of Group Policy failed. Windows attempted to read the file \domain.local\SysVol\domain.local\Policies{3EF90CE1-6908-44EC-A750-F0BA70548600}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. 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.
Error code: 5 = Access Denied.
The incredibly helpful post is this one (http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/A_1073-Diagnosing-and-repairing-Events-1030-and-1058.html). Quoting from this post:
HERE IS A LIST OF POTENTIAL PROBLEMS THAT CAN LEAD TO 1030 AND 1058 EVENT ERRORS:
--Sometimes the permissions of the file folders that contain Group policies (the Sysvol folder) can be corrupted.
--Sometimes you have problems with NetBIOS:
--Sometimes the GPO itself is corrupt, or you have a partial set of data for that GPO.
--Sometimes you may have problems with File Replication Services, which almost always indicates a problem with DNS
--Sysvol may be a subfolder of itself: Sysvol/Sysvol
I have the problem listed where sysvol is a subfolder of sysvol.
The directory structure is:
-sysvol
-domain
-staging
-staging areas
-sysvol (shared as "\\server\sysvol")
-domain.local
-ClientAgent
-Policies
-scripts
Interestingly, the second sysvol folder is the one that is shared as "\server\sysvol". This makes me confident this is the issue with the permissions and error code 5.
Also interestingly, my server 2008 R2 servers can see it fine - my server 2008 servers cannot, and get the error. This is consistent across all my servers.
This latter fact makes me uncertain what I need to do to fix this up. Do I, e.g., simply move the shared sysvol folder up a level to replace the non-shared one?
Any help greatly appreciated.
Cheers,
Tim.
