RE: NTFRS/USERENV SBS2003 Std Issues
- From: Steve <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 12 Mar 2008 08:33:03 -0700
In addition i have the NETDIAG results:
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{897DB9E2-9266-4774-97C3-FA4F36AAEA44}
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{897DB9E2-9266-4774-97C3-FA4F36AAEA44}
The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Failed
[FATAL] Cannot find DC in domain 'DOMAINNAME'. [ERROR_NO_SUCH_DOMAIN]
DC list test . . . . . . . . . . . : Failed
'DOMAINNAME': Cannot find DC to get DC list from [test skipped].
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Skipped
'DOMAINNAME': Cannot find DC to get DC list from [test skipped].
LDAP test. . . . . . . . . . . . . : Failed
Cannot find DC to run LDAP tests on. The error occurred was: The
specified d
omain either does not exist or could not be contacted.
[WARNING] Cannot find DC in domain 'DOMAINNAME'.
[ERROR_NO_SUCH_DOMAIN]
"Steve" wrote:
I noticed errors in file replication services in the Event Viewer this.
morning, followed the instructions to fix it. In the 3rd Event below, the
sysvol folders were moved around, in my opinion causing 4th Event below. I'm
wondering what would happen if i restore the sysvol directories by copying
the data back into them from the subfolders which were
created(c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog)?
1st Event:
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13561
Date: 3/12/2008
Time: 9:29:07 AM
User: N/A
Computer: DOMAINSERVER
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:\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:".
Following recovery steps will 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.
[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.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
2nd Event:
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13560
Date: 3/12/2008
Time: 9:29:07 AM
User: N/A
Computer: DOMAINSERVER
Description:
The File Replication Service is deleting this computer from the replica set
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" as an attempt to recover from the error
state,
Error status = FrsErrorSuccess
At the next poll, which will occur in 5 minutes, this computer will be
re-added to the replica set. The re-addition will trigger a full tree sync
for the replica set.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
3rd Event:
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13520
Date: 3/12/2008
Time: 9:34:07 AM
User: N/A
Computer: DOMAINSERVER
Description:
The File Replication Service moved the preexisting files in
c:\windows\sysvol\domain to
c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
The File Replication Service may delete the files in
c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog at any time. Files
can be saved from deletion by copying them out of
c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog. Copying the files
into c:\windows\sysvol\domain may lead to name conflicts if the files already
exist on some other replicating partner.
In some cases, the File Replication Service may copy a file from
c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog into
c:\windows\sysvol\domain instead of replicating the file from some other
replicating partner.
Space can be recovered at any time by deleting the files in
c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
4th Event: (Application)
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1006
Date: 3/12/2008
Time: 11:09:06 AM
User: NT AUTHORITY\SYSTEM
Computer: domainSERVER
Description:
Windows cannot bind to domainname.local domain. (Local Error). Group Policy
processing aborted.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
- Follow-Ups:
- RE: NTFRS/USERENV SBS2003 Std Issues
- From: Steve
- RE: NTFRS/USERENV SBS2003 Std Issues
- References:
- NTFRS/USERENV SBS2003 Std Issues
- From: Steve
- NTFRS/USERENV SBS2003 Std Issues
- Prev by Date: Re: SBS SP1 installing for over 8 hours..... let it continue, or what?
- Next by Date: Re: Clocks auto-adjust after time change
- Previous by thread: NTFRS/USERENV SBS2003 Std Issues
- Next by thread: RE: NTFRS/USERENV SBS2003 Std Issues
- Index(es):
Relevant Pages
|
