Vitaliy-er
15.04.2009, 11:55
Здравствуйте форумчане.
Может кто-нибудь толково помочь решить ошибки, коорые регистрируются в File Replication Service.
Тип события: Ошибка
Источник события: NtFrs
Категория события: Отсутствует
Код события: 13568
Дата: 15.04.2009
Время: 10:36:31
Пользователь: Н/Д
Компьютер: DC01NERUD
Описание:
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:\windows\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.
Тип события: Предупреждение
Источник события: NtFrs
Категория события: Отсутствует
Код события: 13508
Дата: 15.04.2009
Время: 1:52:14
Пользователь: Н/Д
Компьютер: DC03NERUD
Описание:
The File Replication Service is having trouble enabling replication from DC01NERUD to DC03NERUD for c:\windows\sysvol\domain using the DNS name dc01nerud.nerud.PICompany.ru. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name dc01nerud.nerud.PICompany.ru from this computer.
[2] FRS is not running on dc01nerud.nerud.PICompany.ru.
[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.
Дополнительные сведения можно найти в центре справки и поддержки, в "http://go.microsoft.com/fwlink/events.asp".
Данные:
0000: d5 04 00 00 Õ...
Добавлено через 32 минуты 51 секунду
Папка SYSVOL расшарена на двух контроллерах, но весит по-разному.
Добавлено через 6 минут 26 секунд
Сделал dcdiag ... не понравилось следующее
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
Может кто-нибудь толково помочь решить ошибки, коорые регистрируются в File Replication Service.
Тип события: Ошибка
Источник события: NtFrs
Категория события: Отсутствует
Код события: 13568
Дата: 15.04.2009
Время: 10:36:31
Пользователь: Н/Д
Компьютер: DC01NERUD
Описание:
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:\windows\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.
Тип события: Предупреждение
Источник события: NtFrs
Категория события: Отсутствует
Код события: 13508
Дата: 15.04.2009
Время: 1:52:14
Пользователь: Н/Д
Компьютер: DC03NERUD
Описание:
The File Replication Service is having trouble enabling replication from DC01NERUD to DC03NERUD for c:\windows\sysvol\domain using the DNS name dc01nerud.nerud.PICompany.ru. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name dc01nerud.nerud.PICompany.ru from this computer.
[2] FRS is not running on dc01nerud.nerud.PICompany.ru.
[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.
Дополнительные сведения можно найти в центре справки и поддержки, в "http://go.microsoft.com/fwlink/events.asp".
Данные:
0000: d5 04 00 00 Õ...
Добавлено через 32 минуты 51 секунду
Папка SYSVOL расшарена на двух контроллерах, но весит по-разному.
Добавлено через 6 минут 26 секунд
Сделал dcdiag ... не понравилось следующее
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.