John Daly
asked on
Windows cannot access the file gpt.ini for GPO
I recently rebooted both Win2K domain controllers and after restart I have been getting the following message in the application event log every 5 minutes on one of the domain controllers:
---------
Windows cannot access the file gpt.ini for GPO The file must be present at the location <>. (). Group Policy processing aborted.
----------
And immediately followed by this one:
----------
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.
-----------
Background info - Recently the other domain controller crashed, eventually recovered painfully on its own after a defective memory chip was discovered. However it has been logging the following error since that time in the FRS event log:
----------------------
The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
Recovery Steps:
[balance of lengthy text omitted, but is available if needed]
--------------
I only mention this as I think it could be relevant. I had been planning on demoting the 2nd DC with this last message, and then promoting it back to a DC status to resolve the problem (hopefully), but now this latest wrinkle has me cautious about doing anything else.
Any thoughts??
---------
Windows cannot access the file gpt.ini for GPO The file must be present at the location <>. (). Group Policy processing aborted.
----------
And immediately followed by this one:
----------
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.
-----------
Background info - Recently the other domain controller crashed, eventually recovered painfully on its own after a defective memory chip was discovered. However it has been logging the following error since that time in the FRS event log:
----------------------
The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
Recovery Steps:
[balance of lengthy text omitted, but is available if needed]
--------------
I only mention this as I think it could be relevant. I had been planning on demoting the 2nd DC with this last message, and then promoting it back to a DC status to resolve the problem (hopefully), but now this latest wrinkle has me cautious about doing anything else.
Any thoughts??
AustinComputerLabs
Are you getting a JRNL_wrap error in the file replication log as well?
ASKER
Ok, just to keep things straight, the GPO error is on what I'll call DC1 and the frs error is on what I'll call DC2.
There is a second repeating error on DC2 that accompanies the one I mentioned above:
---------
The File Replication Service is unable to add this computer to the following replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is "abgdc2.abg.local"
Replica set member name is "ABGDC2"
Replica set root path is "c:\winnt\sysvol\domain"
Replica staging directory path is "c:\winnt\sysvol\staging\d
Replica working directory path is "c:\winnt\ntfrs\jet"
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalI
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time.
------------------
THere are not FRS errors on DC1 however.
Short answer to your question: No
There is a second repeating error on DC2 that accompanies the one I mentioned above:
---------
The File Replication Service is unable to add this computer to the following replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
This could be caused by a number of problems such as:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is "abgdc2.abg.local"
Replica set member name is "ABGDC2"
Replica set root path is "c:\winnt\sysvol\domain"
Replica staging directory path is "c:\winnt\sysvol\staging\d
Replica working directory path is "c:\winnt\ntfrs\jet"
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalI
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time.
------------------
THere are not FRS errors on DC1 however.
Short answer to your question: No
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Re-issued the question. Search on Jtdaly (username) to find it.