Before implementing some upgrades to a network I checked the Event Logs for problems to resolve first. I have found that there is an FrsErrorMismatchedJournalId error on the EMAIL server. Replication of the sysvol is not happening between the EMAIL server and the PDC server @ this site.
The EMAIL server has two event log errors:
Windows cannot access the file gpt.ini for GPO CN={6AC6EDA9-CDD9-4708-87ED-72D7B7849C22},CN=Policies,CN=System,DC=organization,DC=org. The file must be present at the location <\\organization.org\SysVol\organization.org\Policies\{6AC6EDA9-CDD9-4708-87ED-72D7B7849C22}\gpt.ini>. (The system cannot find the path specified. ). Group Policy processing aborted.
-----
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 "email.organization.org"
Replica set member name is "EMAIL"
Replica set root path is "c:\winnt\sysvol\domain"
Replica staging directory path is "c:\winnt\sysvol\staging\domain"
Replica working directory path is "c:\winnt\ntfrs\jet"
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
The PDC server has one error:
The File Replication Service is having trouble enabling replication from EMAIL to PDC for c:\winnt\sysvol\domain using the DNS name email.organization.org. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name email.organization.org from this computer.
[2] FRS is not running on email.organization.org.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
Apparently this has been going on sometime now and was most likely due to the EMAIL server C drive filling up completely a month or two ago from what I gather so there is no system state backups available pre-problem. From reading about "FrsErrorMismatchedJournalId" errors some say that there is a file that can be deleted to resolve the problem however I wanted to gather more information before I start deleting files and crossing fingers.
I appreciate all your help!
John A.
|
