asked on

How do i get solve this windows cannot access the registry policy file error on my file server

On my file server with Active directory installed. Users usually complains of not able to access share drives. Once the file server is restarted share drive will be available to users. On the Server event viewer the following error display:windows cannot access the registry policy file \\mydomain\sysvol\polices\{2981B352-AF15-42FA-8680-1AFF19E438BF}\USER\registry.pol

This problems clear once the files server is restarted. How do i solve this issue permanently.

JimsZ

Are you running shared drives on the Domain controller ? Not a great practice.

If the shares are on a domain server, you may be able to go into the event viewer on the server itself and see the events which may give a better understanding of your setup. What does the local machine events show?

femi2002

ASKER

Hi JimsZ,

Thanks for your quick respond. Yes i am running my shared drives on domain controller. What's you advise regarding this? I'm able to see the event viewer on the server. In fact the error i described in my question t is from the event viewer. The local machine events viewer shows the same error i.e windows can not access the registry policy file .......................(The data is invalid)

Regards
Femi2002

JimsZ

You can note the policy GUID {2981B352-AF15-42FA-8680-1AFF19E438BF}, open gpmc.msc on either the domain controller and or a workstation with admin pak installed on it. From there if you go down to "group policy objects" you can see the GPO's below that. If you click on an individual GPO and click the "details" tab in the right window pane you will see that GPO's GUID number.

Once you find the correct GUID, I can help you more. If it is the default domain policy that is corrupt, Microsoft has a tool that can rebuild the default domain policy, but any options you have changed will need to be changed again "or" you will have to restore the policy from backup. If it is just a separate policy you had created causing this, disabling of the policy, removal and recreation, etc should fix it

femi2002

ASKER

Hi Jimsz,

Thanks for your help in this matter. I have followed your steps as highlighted above. It is not the default domain policy that have the problem. One of the policy i created is the one causing the problem.
The correct GUID is {2981B352-AF15-42F4-8680-1AFF19E438BF}. I will appreciate your help more.

Regards
Femi2002

ASKER CERTIFIED SOLUTION

JimsZ

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

femi2002

ASKER

Hi Jimsz,

Thanks i have resolved the problem following your advise. You are a star!

Cheers
Feni2003