• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1677
  • Last Modified:

My server 2003 lost sysvol info

My Server 2003 standard edition went down last night due to thunder storm, when I arrived at work I noticed that when I browsed to the server it did not have a share for sysvol or netlogin.  I have added the FRSDIAG info below, any assistance is appreciated.
------------------------------------------------------------
FRSDiag v1.7 on 4/24/2009 11:27:49 PM
.\MCNSERVER on 2009-04-24 at 11.27.49 PM
------------------------------------------------------------
 
Checking for errors/warnings in FRS Event Log .... 	
NtFrs	4/24/2009 11:25:15 PM	Error	13540	The File Replication Service cannot replicate d:\dfsshare\jwhitley because the pathname  of the customer designated staging directory:        g:\frs-staging     is not the fully qualified pathname of an existing, accessible local directory.	
NtFrs	4/24/2009 11:25:08 PM	Warning	13566	File Replication Service is scanning the data in the system volume. Computer MCNSERVER  cannot become a domain controller until this process is complete.  The system volume will then be shared as SYSVOL.        To check for the SYSVOL share, at the command prompt, type:    net share        When File Replication Service completes the scanning process, the SYSVOL  share will appear.        The initialization of the system volume can take some time.  The time is dependent on the amount of data in the system volume.	
NtFrs	4/24/2009 8:02:07 PM	Warning	13508	The File Replication Service is having trouble enabling replication  from BBSERVER to MCNSERVER for c:\windows\sysvol\domain using the DNS name bbserver.IngramLeGrand.com. FRS will keep retrying.     Following are some of the reasons you would see this warning.         [1] FRS can not correctly resolve the DNS name bbserver.IngramLeGrand.com from this computer.     [2] FRS is not running on bbserver.IngramLeGrand.com.     [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.	
NtFrs	4/24/2009 6:27:48 PM	Warning	13508	The File Replication Service is having trouble enabling replication  from BBSERVER to MCNSERVER for d:\dfsshare\alan using the DNS name bbserver.IngramLeGrand.com. FRS will keep retrying.     Following are some of the reasons you would see this warning.         [1] FRS can not correctly resolve the DNS name bbserver.IngramLeGrand.com from this computer.     [2] FRS is not running on bbserver.IngramLeGrand.com.     [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.	
NtFrs	4/24/2009 6:27:46 PM	Warning	13508	The File Replication Service is having trouble enabling replication  from BBSERVER to MCNSERVER for d:\dfsshare\alanh using the DNS name bbserver.IngramLeGrand.com. FRS will keep retrying.     Following are some of the reasons you would see this warning.         [1] FRS can not correctly resolve the DNS name bbserver.IngramLeGrand.com from this computer.     [2] FRS is not running on bbserver.IngramLeGrand.com.     [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.	
NtFrs	4/24/2009 6:24:44 PM	Error	13540	The File Replication Service cannot replicate d:\dfsshare\jwhitley because the pathname  of the customer designated staging directory:        g:\frs-staging     is not the fully qualified pathname of an existing, accessible local directory.	
NtFrs	4/24/2009 6:24:37 PM	Warning	13566	File Replication Service is scanning the data in the system volume. Computer MCNSERVER  cannot become a domain controller until this process is complete.  The system volume will then be shared as SYSVOL.        To check for the SYSVOL share, at the command prompt, type:    net share        When File Replication Service completes the scanning process, the SYSVOL  share will appear.        The initialization of the system volume can take some time.  The time is dependent on the amount of data in the system volume.	
NtFrs	4/24/2009 10:17:15 AM	Error	13540	The File Replication Service cannot replicate d:\dfsshare\jwhitley because the pathname  of the customer designated staging directory:        g:\frs-staging     is not the fully qualified pathname of an existing, accessible local directory.	
NtFrs	4/24/2009 8:37:39 AM	Warning	13522	The File Replication Service paused because the staging area is full. Staging files  are used to replicate created, deleted or modified files between partners. FRS will  automatically remove least recently used files from this staging area (in the order  of the longest time since the last access) until the amount of space in use has  dropped below 60 of the staging space-limit, after which replication will resume.        If this condition occurs frequently:        Confirm that all direct outbound replication partners receiving updates from this  member are online and receiving udpates.        Verify that the replication schedule for receiving partners is open or "on" for a  sufficient window of time to accomodate the number of files being replicated.        Consider increasing the staging area to improve system performance.            The current value of the staging space limit is 4000000 KB.  To change the staging  space limit, run regedit:        Click on Start -> Run and type  REGEDT .  Expand HKEY_LOCAL_MACHINE, SYSTEM,  CurrentControlSet, Services, NtFrs, Parameters, and the value "Staging Space  Limit in KB".	
NtFrs	4/23/2009 11:36:23 PM	Warning	13520	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.	
NtFrs	4/23/2009 11:31:18 PM	Warning	13560	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.	
NtFrs	4/23/2009 11:31:18 PM	Error	13561	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.	
NtFrs	4/23/2009 11:30:05 PM	Error	13552	The File Replication Service is unable to add this computer to the following  replica set:        "DFSROOT|JWILTLEY"        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 "mcnserver.IngramLeGrand.com"    Replica set member name is "{DD58E889-15CD-44F9-888D-A0A32C392786}"    Replica set root path is "d:\dfsshare\jwhitley"    Replica staging directory path is "g:\frs-staging"    Replica working directory path is "c:\windows\ntfrs\jet"    Windows error status code is ERROR_BAD_COMMAND    FRS error status code is FrsErrorResourceInUse        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.	
NtFrs	4/23/2009 11:30:04 PM	Error	13544	The File Replication Service cannot replicate d:\dfsshare\jwhitley because it overlaps  the replicating directory d:\dfsshare\jwhitley.	
NtFrs	4/23/2009 10:54:25 PM	Error	13540	The File Replication Service cannot replicate d:\dfsshare\jwhitley because the pathname  of the customer designated staging directory:        g:\frs-staging     is not the fully qualified pathname of an existing, accessible local directory.	
NtFrs	4/23/2009 7:03:12 PM	Error	13552	The File Replication Service is unable to add this computer to the following  replica set:        "DFSROOT|JWILTLEY"        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 "mcnserver.IngramLeGrand.com"    Replica set member name is "{DD58E889-15CD-44F9-888D-A0A32C392786}"    Replica set root path is "d:\dfsshare\jwhitley"    Replica staging directory path is "g:\frs-staging"    Replica working directory path is "c:\windows\ntfrs\jet"    Windows error status code is ERROR_BAD_COMMAND    FRS error status code is FrsErrorResourceInUse        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.	
NtFrs	4/23/2009 7:03:12 PM	Error	13544	The File Replication Service cannot replicate d:\dfsshare\jwhitley because it overlaps  the replicating directory d:\dfsshare\jwhitley.	
NtFrs	4/23/2009 1:53:26 PM	Warning	13522	The File Replication Service paused because the staging area is full. Staging files  are used to replicate created, deleted or modified files between partners. FRS will  automatically remove least recently used files from this staging area (in the order  of the longest time since the last access) until the amount of space in use has  dropped below 60 of the staging space-limit, after which replication will resume.        If this condition occurs frequently:        Confirm that all direct outbound replication partners receiving updates from this  member are online and receiving udpates.        Verify that the replication schedule for receiving partners is open or "on" for a  sufficient window of time to accomodate the number of files being replicated.        Consider increasing the staging area to improve system performance.            The current value of the staging space limit is 4000000 KB.  To change the staging  space limit, run regedit:        Click on Start -> Run and type  REGEDT .  Expand HKEY_LOCAL_MACHINE, SYSTEM,  CurrentControlSet, Services, NtFrs, Parameters, and the value "Staging Space  Limit in KB".	
NtFrs	4/22/2009 6:58:45 PM	Error	13552	The File Replication Service is unable to add this computer to the following  replica set:        "DFSROOT|JWILTLEY"        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 "mcnserver.IngramLeGrand.com"    Replica set member name is "{DD58E889-15CD-44F9-888D-A0A32C392786}"    Replica set root path is "d:\dfsshare\jwhitley"    Replica staging directory path is "g:\frs-staging"    Replica working directory path is "c:\windows\ntfrs\jet"    Windows error status code is ERROR_BAD_COMMAND    FRS error status code is FrsErrorResourceInUse        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.	
NtFrs	4/22/2009 6:58:45 PM	Error	13544	The File Replication Service cannot replicate d:\dfsshare\jwhitley because it overlaps  the replicating directory d:\dfsshare\jwhitley.	
NtFrs	4/22/2009 1:40:12 PM	Warning	13522	The File Replication Service paused because the staging area is full. Staging files  are used to replicate created, deleted or modified files between partners. FRS will  automatically remove least recently used files from this staging area (in the order  of the longest time since the last access) until the amount of space in use has  dropped below 60 of the staging space-limit, after which replication will resume.        If this condition occurs frequently:        Confirm that all direct outbound replication partners receiving updates from this  member are online and receiving udpates.        Verify that the replication schedule for receiving partners is open or "on" for a  sufficient window of time to accomodate the number of files being replicated.        Consider increasing the staging area to improve system performance.            The current value of the staging space limit is 4000000 KB.  To change the staging  space limit, run regedit:        Click on Start -> Run and type  REGEDT .  Expand HKEY_LOCAL_MACHINE, SYSTEM,  CurrentControlSet, Services, NtFrs, Parameters, and the value "Staging Space  Limit in KB".	
NtFrs	4/21/2009 6:54:06 PM	Error	13552	The File Replication Service is unable to add this computer to the following  replica set:        "DFSROOT|JWILTLEY"        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 "mcnserver.IngramLeGrand.com"    Replica set member name is "{DD58E889-15CD-44F9-888D-A0A32C392786}"    Replica set root path is "d:\dfsshare\jwhitley"    Replica staging directory path is "g:\frs-staging"    Replica working directory path is "c:\windows\ntfrs\jet"    Windows error status code is ERROR_BAD_COMMAND    FRS error status code is FrsErrorResourceInUse        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.	
NtFrs	4/21/2009 6:54:06 PM	Error	13544	The File Replication Service cannot replicate d:\dfsshare\jwhitley because it overlaps  the replicating directory d:\dfsshare\jwhitley.	
NtFrs	4/21/2009 2:43:45 PM	Error	13507	The File Replication Service cannot start replica set DFSROOT|JWILTLEY on computer MCNSERVER  for directory g:\frs-staging because the type of volume \\.\g: is not NTFS 5.0 or later.        The volume's type can be found by typing "chkdsk \\.\g:".        The volume can be upgraded to NTFS 5.0 or later by typing "chkntfs /E \\.\g:".	
NtFrs	4/21/2009 12:01:38 PM	Warning	13522	The File Replication Service paused because the staging area is full. Staging files  are used to replicate created, deleted or modified files between partners. FRS will  automatically remove least recently used files from this staging area (in the order  of the longest time since the last access) until the amount of space in use has  dropped below 60 of the staging space-limit, after which replication will resume.        If this condition occurs frequently:        Confirm that all direct outbound replication partners receiving updates from this  member are online and receiving udpates.        Verify that the replication schedule for receiving partners is open or "on" for a  sufficient window of time to accomodate the number of files being replicated.        Consider increasing the staging area to improve system performance.            The current value of the staging space limit is 4000000 KB.  To change the staging  space limit, run regedit:        Click on Start -> Run and type  REGEDT .  Expand HKEY_LOCAL_MACHINE, SYSTEM,  CurrentControlSet, Services, NtFrs, Parameters, and the value "Staging Space  Limit in KB".	
NtFrs	4/21/2009 3:27:42 AM	Error	13540	The File Replication Service cannot replicate d:\dfsshare\jwhitley because the pathname  of the customer designated staging directory:        g:\frs-staging     is not the fully qualified pathname of an existing, accessible local directory.	
NtFrs	4/20/2009 11:45:44 AM	Warning	13522	The File Replication Service paused because the staging area is full. Staging files  are used to replicate created, deleted or modified files between partners. FRS will  automatically remove least recently used files from this staging area (in the order  of the longest time since the last access) until the amount of space in use has  dropped below 60 of the staging space-limit, after which replication will resume.        If this condition occurs frequently:        Confirm that all direct outbound replication partners receiving updates from this  member are online and receiving udpates.        Verify that the replication schedule for receiving partners is open or "on" for a  sufficient window of time to accomodate the number of files being replicated.        Consider increasing the staging area to improve system performance.            The current value of the staging space limit is 4000000 KB.  To change the staging  space limit, run regedit:        Click on Start -> Run and type  REGEDT .  Expand HKEY_LOCAL_MACHINE, SYSTEM,  CurrentControlSet, Services, NtFrs, Parameters, and the value "Staging Space  Limit in KB".	
NtFrs	4/20/2009 3:24:08 AM	Error	13540	The File Replication Service cannot replicate d:\dfsshare\jwhitley because the pathname  of the customer designated staging directory:        g:\frs-staging     is not the fully qualified pathname of an existing, accessible local directory.	
NtFrs	4/19/2009 3:22:15 AM	Error	13540	The File Replication Service cannot replicate d:\dfsshare\jwhitley because the pathname  of the customer designated staging directory:        g:\frs-staging     is not the fully qualified pathname of an existing, accessible local directory.	
NtFrs	4/18/2009 3:20:52 AM	Error	13540	The File Replication Service cannot replicate d:\dfsshare\jwhitley because the pathname  of the customer designated staging directory:        g:\frs-staging     is not the fully qualified pathname of an existing, accessible local directory.	
NtFrs	4/17/2009 9:00:45 AM	Warning	13522	The File Replication Service paused because the staging area is full. Staging files  are used to replicate created, deleted or modified files between partners. FRS will  automatically remove least recently used files from this staging area (in the order  of the longest time since the last access) until the amount of space in use has  dropped below 60 of the staging space-limit, after which replication will resume.        If this condition occurs frequently:        Confirm that all direct outbound replication partners receiving updates from this  member are online and receiving udpates.        Verify that the replication schedule for receiving partners is open or "on" for a  sufficient window of time to accomodate the number of files being replicated.        Consider increasing the staging area to improve system performance.            The current value of the staging space limit is 4000000 KB.  To change the staging  space limit, run regedit:        Click on Start -> Run and type  REGEDT .  Expand HKEY_LOCAL_MACHINE, SYSTEM,  CurrentControlSet, Services, NtFrs, Parameters, and the value "Staging Space  Limit in KB".	
NtFrs	4/17/2009 3:17:17 AM	Error	13540	The File Replication Service cannot replicate d:\dfsshare\jwhitley because the pathname  of the customer designated staging directory:        g:\frs-staging     is not the fully qualified pathname of an existing, accessible local directory.	
NtFrs	4/16/2009 8:37:19 AM	Warning	13522	The File Replication Service paused because the staging area is full. Staging files  are used to replicate created, deleted or modified files between partners. FRS will  automatically remove least recently used files from this staging area (in the order  of the longest time since the last access) until the amount of space in use has  dropped below 60 of the staging space-limit, after which replication will resume.        If this condition occurs frequently:        Confirm that all direct outbound replication partners receiving updates from this  member are online and receiving udpates.        Verify that the replication schedule for receiving partners is open or "on" for a  sufficient window of time to accomodate the number of files being replicated.        Consider increasing the staging area to improve system performance.            The current value of the staging space limit is 4000000 KB.  To change the staging  space limit, run regedit:        Click on Start -> Run and type  REGEDT .  Expand HKEY_LOCAL_MACHINE, SYSTEM,  CurrentControlSet, Services, NtFrs, Parameters, and the value "Staging Space  Limit in KB".	
NtFrs	4/15/2009 2:03:00 PM	Warning	13522	The File Replication Service paused because the staging area is full. Staging files  are used to replicate created, deleted or modified files between partners. FRS will  automatically remove least recently used files from this staging area (in the order  of the longest time since the last access) until the amount of space in use has  dropped below 60 of the staging space-limit, after which replication will resume.        If this condition occurs frequently:        Confirm that all direct outbound replication partners receiving updates from this  member are online and receiving udpates.        Verify that the replication schedule for receiving partners is open or "on" for a  sufficient window of time to accomodate the number of files being replicated.        Consider increasing the staging area to improve system performance.            The current value of the staging space limit is 4000000 KB.  To change the staging  space limit, run regedit:        Click on Start -> Run and type  REGEDT .  Expand HKEY_LOCAL_MACHINE, SYSTEM,  CurrentControlSet, Services, NtFrs, Parameters, and the value "Staging Space  Limit in KB".
	WARNING: Found Event ID 13508 errors without trailing 13509 ... see above for (up to) the 3 latest entries!
 
 ......... failed 32
Checking for errors in Directory Service Event Log .... passed
Checking for minimum FRS version requirement ... passed
Checking for errors/warnings in ntfrsutl ds ... passed
Checking for Replica Set configuration triggers... passed
Checking for suspicious file Backlog size... 
	ERROR : File Backlog TO server "INGRAMMACON\BBSERVER$" is : 18743  :: Unless this is due to your schedule, this is a problem!
failed with 1 error(s) and 0 warning(s)
 
Checking Overall Disk Space and SYSVOL structure (note: integrity is not checked)... passed
Checking for suspicious inlog entries ... passed
Checking for suspicious outlog entries ... passed
Checking for appropriate staging area size ...
	WARNING: Staging are is 72% filled up! You should consider increasing the staging area size! NTFRS STAGE USAGE: 2897535 KB of 4000000 KB allocated
		For more information refer to articles:
		KB.329491 Configuring Correct Staging Area Space for Replica Sets
		KB.307777 Possible Causes of a Full File Replication Service Staging Area
 ......... passed with a warning
Checking for errors in debug logs ...
	ERROR on NtFrs_0005.log : "ERROR_ACCESS_DENIED" : <DbsRecoverStagingAreas:        3328:  3397: S0: 23:25:34> ++ ERROR - Enumerating preinstall area for DFSROOT|MJONES :  WStatus: ERROR_ACCESS_DENIED
	ERROR on NtFrs_0005.log : "ERROR_ACCESS_DENIED" : <DbsRecoverPreInstallFiles:     3328:  2911: S1: 23:25:34> ++ ERROR - SetCurrentDirectory(d:\dfsshare\jwilliamson\DO_NOT_REMOVE_NtFrs_PreInstall_Directory);  WStatus: ERROR_ACCESS_DENIED
	ERROR on NtFrs_0005.log : "ERROR_ACCESS_DENIED" : <DbsRecoverStagingAreas:        3328:  3397: S0: 23:25:34> ++ ERROR - Enumerating preinstall area for DFSROOT|JWILLIAMSON :  WStatus: ERROR_ACCESS_DENIED
	ERROR on NtFrs_0001.log : "IBCO_STAGING_RETRY" :  4/24-08:51:24 :T: LocnCmd:   NoCmd    State: IBCO_STAGING_RETRY       ReplicaName: DFSROOT|JWHITLEY (52)
	ERROR on NtFrs_0001.log : "IBCO_STAGING_RETRY" :  4/24-09:20:02 :T: LocnCmd:   NoCmd    State: IBCO_STAGING_RETRY       ReplicaName: DFSROOT|JWHITLEY (52)
	ERROR on NtFrs_0002.log : "IBCO_STAGING_RETRY" :  4/24-13:44:10 :T: LocnCmd:   NoCmd    State: IBCO_STAGING_RETRY       ReplicaName: DFSROOT|JWHITLEY (52)
	ERROR on NtFrs_0004.log : "ERROR_RETRY" : <SndCsMain:                     5228:   904: S0: 23:12:11> :SR: Cmd 046f63b0, CxtG 291addc6, WS ERROR_RETRY, To   bbserver.IngramLeGrand.com Len:  (374) [SndFail - Send Penalty]
	ERROR on NtFrs_0004.log : "ERROR_RETRY" : <SndCsMain:                     6052:   877: S0: 23:14:14> :SR: Cmd 046f6ba0, CxtG 291addc6, WS ERROR_RETRY, To   bbserver.IngramLeGrand.com Len:  (374) [SndFail - rpc call]
	ERROR on NtFrs_0004.log : "ERROR_RETRY" : <SndCsMain:                     6052:   904: S0: 23:14:14> :SR: Cmd 046f6ba0, CxtG 291addc6, WS ERROR_RETRY, To   bbserver.IngramLeGrand.com Len:  (374) [SndFail - Send Penalty]
 
	Found 12 ERROR_ACCESS_DENIED error(s)! Latest ones (up to 3) listed above
	Found 3 IBCO_STAGING_RETRY error(s)! Latest ones (up to 3) listed above
	Found 208 ERROR_RETRY error(s)! Latest ones (up to 3) listed above
 
 ......... failed with 223 error entries
Checking NtFrs Service (and dependent services) state...
	ERROR : Cannot access SYSVOL share on MCNSERVER
	ERROR : Cannot access NETLOGON share on MCNSERVER
 ......... failed 2
Checking NtFrs related Registry Keys for possible problems...
	SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Enable Journal Wrap Automatic Restore = 1 :: ERROR: Enabling Journal Wrap Automatic Restore is NOT recommended in post-SP2 version of FRS. Please see KB.292438 (Troubleshooting Journal_Wrap Errors on Sysvol and DFS Replica Sets) for further information!
	SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\SysvolReady = 0 :: ERROR: SysvolReady is not set to 1 :: SYSVOL is likely not Sharing! This key should NOT be changed manually but this should be addressed! See article KB.327781 (How to Troubleshoot Missing SYSVOL and NETLOGON Shares on Windows Server) for further information!
failed with 2 error(s) and 0 warning(s)
 
Checking Repadmin Showreps for errors...passed

Open in new window

0
IngramEntities
Asked:
IngramEntities
  • 7
  • 3
  • 2
2 Solutions
 
ryansotoCommented:
First thing is to try and restart the netlog on service.  
If thats a no go....
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B315457
0
 
IngramEntitiesAuthor Commented:
I tried restarting Netlogin and no change.  I can browse to c:\windows\sysvol and see the data however it is not shared out like it use to.  I thin kwhen the power went off theis server was offine a few hours, and when it came back on it woulnd not talk to other DC any longer.
0
 
ryansotoCommented:
Does the other DC share sysvol OK?
0
Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

 
ChiefITCommented:
Ryan, long time no see:

Are you thinking Burflag to rebuild the sysvol and netlogon shares?
0
 
IngramEntitiesAuthor Commented:
Not sure, never used Burflag, we have a small network, 1 point to point T1 connecting 2 sites.  Each site has 1 DC, and web server.  The remote site sysvol info looks good, just will no longer talk to our server on the other end of Point to Point after storm.
0
 
IngramEntitiesAuthor Commented:
I ran FRSdiag tool and got losts of log files that I am reviewing, I will share and see if you guys see anything that jumps out at you.  Thanks to all the Experts providing assistance,
connstat.txt
evl-Application.txt
evl-Directory-Service.txt
evl-DNS-Server.txt
evl-File-Replication-Service.txt
evl-System.txt
FRSDiag.txt
FRSDiag-Log.txt
NtFrs-0001.log
NtFrs-0002.log
NtFrs-0003.log
NtFrs-0004.log
NtFrs-0005.log
0
 
IngramEntitiesAuthor Commented:
This is the last of them, sorry for the volume, I just wanted to make sure I put all the logs out here so you can see what I am seeing as far as troubleshooting this problem.

Thanks,
repadmin-showconn.txt
repadmin-showreps.txt
0
 
IngramEntitiesAuthor Commented:
Ryan, do you think I still need to proceed with Burflag?  If so anything special I need to know before I download and read steps on how to use?

Thanks,
Mike
0
 
ryansotoCommented:
Hi Chief - been away job hunting for the last 2 months :)
I think we should definately proceed with the burflags to rebuild the shares.

Ingram - its a pretty straight forward process just follow it step by step.  Always always make sure you have good backups before doing such.

Also looking through some of the logs - did you by chance change where active directory was located?
0
 
ChiefITCommented:
Ryan is correct:

99.999% of the time a problem with FRS replication comes from a DNS issue.
0
 
IngramEntitiesAuthor Commented:
Thanks,
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 7
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now