Strange Windows 2000 Server - Group Policy Object - error

[Mr Davo 69]

Hi Everyone,

I am currently running Windows 2000 Server (SP4), and I am receiving a strange error related to Group Policy.

The error description is:

Windows cannot access the file gpt.ini for GPO The file must be present at the location <>.(). Group Policy processing aborted.

I am also seeing the error message:

Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by this policy engine.

Any help with the above errors will be greatly appreciated. I am stumped by the first message as no file location is given for the gpt.ini file.

Thanks in advance for your assistance.

Kind Regards,

Davo

[MANEMAN]

Hi Davo, welcome.

I've had a look around. There seems to be quite a lot of information on this error.

With Symptoms, Causes, and Resolutions.

Try these links:

/>http://support.microsoft.com/?id=887303

/>http://support.microsoft.com/kb/839499

/>http://blogs.dirteam.com/blogs/jorge/archive/2005/11/24/151.aspx

Also a load more results **HERE**

Hope this was the sort of thing that you were looking for, and that you get up and running soon.

John.

[MANEMAN]

So............. For the sake of other readers. How did it all work out then ?

John.

[bludgard]

Edited by doug

What's that?

[rong]

spam

[bludgard]

Didn't that used to come in a can?

[Mr Davo 69]

Hi Guys,

In answer to Maneman, here are the steps that I followed to sort this:

1). Read the error log, as follows:

Event Type: Error

Event Source: NtFrs

Event Category: None

Event ID: 13568

Date: 2/08/2010

Time: 10:32:14 AM

User: N/A

Computer: SVR-SCEMELB1

Description:

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

Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"

Replica root path is : "c:\winnt\sysvol\domain"

Replica root volume is : "\\.\C:"

A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.

[1] Volume "\\.\C:" has been formatted.

[2] The NTFS USN journal on volume "\\.\C:" has been deleted.

[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.

[4] File Replication Service was not running on this computer for a long time.

[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".

Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.

[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.

[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.

WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.

To change this registry parameter, run regedit.

Click on Start, Run and type regedit.

Expand HKEY_LOCAL_MACHINE.

Click down the key path:

"System\CurrentControlSet\Services\NtFrs\Parameters"

Double click on the value name

"Enable Journal Wrap Automatic Restore"

and update the value.

If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.

2). Performed the fix as detailed above.

I was then presented with another error condition, wherein SYSVOL was not appearing as shared, even after several hours.

3). Performed the Nonauthoritive Restore, outlined here:

Using the BurFlags registry...

After doing so SYSVOL was shared again, and all was good.

I hope this helps somebody else! :)

Cheers

Davo

[bludgard]

Thanks for the update,Mr Davo 69.

It's all a little over my head but I'm glad you got it worked out. :D