Solved

Offline files going online

Posted on 2006-06-12
7
661 Views
Last Modified: 2012-06-27
I have been having difficulties with offline files. I have a pc with Windows XP sp2 on a Widows 2003 network. I have set up in Group policy to configure offline files slow link speed to be 150000. I have set up the user's my documents to work offline. When I boot the pc not connected to the nework it comes up working offline as it should. I then use the modem (connecting at 31k) to connet to the internet and vpn to connect to our network. After about 1 minute the pc will go online and the pc will acces the files on the server instead of local. Why is the policy not working? Is there something more I need to set up? I have tried this on more than on pc and have the same problem. I am really trying to make this work for laptops but have had to test it with pc's configured witha modem since I dont have a laptop at the moment.
0
Comment
Question by:tcispx
  • 3
  • 2
7 Comments
 
LVL 13

Expert Comment

by:Kini pradeep
ID: 16897880
if i am not wrong the default threshold if a value is not given is 64000bps, any value below it would be considered a low speed and the client would not attempt to connect to the file server even if its able to find it.
can you change the threshold value to higher speeds and try. or probably even better thing to do is to try and see whether  the policy is hitting the w/s. try a gpresult or rsop and see whether the slow link detection policy is applied, cause i belive that the threshold is quite enough.

what OU is this policy applied ?
does that OU have the comp acc or user acc ?
any errors seen in the eventvwr ?

can you explain.
0
 

Author Comment

by:tcispx
ID: 16898144
I have created a seperate ou for my test pc and my user account. It is a child ou of where most of the other pc's reside. I put the new policy in the same ou with the test pc and my user account. It does seem though that the policy is not being applied and the parent ou's policies are being applied instead. In the past though I know the policy has been applied through gp results. It seems to have stopped working. I may have other problems going on here. We are having errros with NtFrs. If we are having NtFrs errors would this cause file replication and policy replication to fail sometimes? I did test the connection at a time when the policy did apply and it still connected. The setting of 150000 is much higher than the default 64000. Even with the default level though why is it connecting with a 33k modem connection? Is it possible that I am just having so much difficulty because our file replication is not working proper?
0
 
LVL 13

Expert Comment

by:Kini pradeep
ID: 16898195
what is the frs errors, of course if there is a problem with file replication then its going to impact the group policies (31b and 6AC ) the default policies as well.
you would have to resolve the NTFRS problems first.because you never know whether thats causing the problem.

can you stop and start the ntfrs then check the errors in the frs eventvwr.

can you please paste these logs ?
also if you could let us know how many DC's in the domain, how many experiencing the problem ?

thanks .
0
 

Author Comment

by:tcispx
ID: 16898461
We have 2 dc's. Errors are on only one. The company is going to bring someone in to work on the NtFrs problems. If you believe this is what is causing problems with my policies I guess there is not much I can do right now. Below are the errors. If you want to add anything please respond. If you believe this is what is causing my problems I will accept your answer.


Event ID 13505 1.17.19

The File Replication Service has stopped after taking an assertion failure.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event ID 13552 1.16.18

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 "TCIFM-SRVR1.tci.spx.com"
Replica set member name is "TCIFM-SRVR1"
Replica set root path is "c:\windows\sysvol\domain"
Replica staging directory path is "c:\windows\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"
Windows error status code is  
FRS error status code is FrsErrorSuccess
 
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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event id 13552 1.16.17
The File Replication Service is unable to add this computer to the following replica set:
    "FILES|DEPARTMENTS"
 
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 "TCIFM-SRVR1.tci.spx.com"
Replica set member name is "{EE4989FA-5531-427B-AAB8-0C6090EB0D3B}"
Replica set root path is "d:\departments"
Replica staging directory path is "c:\frs-staging"
Replica working directory path is "c:\windows\ntfrs\jet"
Windows error status code is  
FRS error status code is FrsErrorSuccess
 
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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event id 13552 1.16.17

The File Replication Service is unable to add this computer to the following replica set:
    "FILES|SYSTEM|PROFILES"
 
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 "TCIFM-SRVR1.tci.spx.com"
Replica set member name is "{EE4989FA-5531-427B-AAB8-0C6090EB0D3B}"
Replica set root path is "d:\profiles"
Replica staging directory path is "c:\frs-staging"
Replica working directory path is "c:\windows\ntfrs\jet"
Windows error status code is  
FRS error status code is FrsErrorSuccess
 
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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event id 13552 1.16.17

The File Replication Service is unable to add this computer to the following replica set:
    "FILES|SYSTEM|USERS DOCUMENTS"
 
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 "TCIFM-SRVR1.tci.spx.com"
Replica set member name is "{EE4989FA-5531-427B-AAB8-0C6090EB0D3B}"
Replica set root path is "d:\users documents"
Replica staging directory path is "c:\frs-staging"
Replica working directory path is "c:\windows\ntfrs\jet"
Windows error status code is  
FRS error status code is FrsErrorSuccess
 
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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event id 13502 1.16.17

The File Replication Service is stopping.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event ID 13555 1.16.17

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:
 
 [1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
 
    net stop ntfrs
    net start ntfrs
 
If this fails to clear up the problem then proceed as follows.
 
 [2] For Active Directory Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
 
If there is at least one other Domain Controller in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
 
If there are NO other Domain Controllers in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
 
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
 
 
 [3] For Active Directory Domain Controllers that host DFS alternates or other replica sets with replication enabled:
 
 (3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
 (3-b) If this server is the only Active Directory Domain Controller for this domain then, before going to (3-c),  make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
 (3-c) Restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
 (3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
 
 
 [4] For other Windows servers:
 
 (4-a)  If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
 (4-b)  net stop ntfrs
 (4-c)  rd /s /q  c:\windows\ntfrs\jet
 (4-d)  net start ntfrs
 (4-e)  Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
 
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event id 13506 1.16.17

The File Replication Service failed a consistency check
  (QKey != QUADZERO)
in "QHashInsertLock:" at line 696.
 
The File Replication Service will restart automatically at a later time. If this problem persists a subsequent entry in this event log describes the recovery procedure.
 For more information about the automatic restart right click on My Computer and then click on Manage, System Tools, Services, File Replication Service, and Recovery.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event id 13568 1.16.17

The File Replication Service has detected that the replica set "FILES|TRADE" is in JRNL_WRAP_ERROR.
 
 Replica set name is    : "FILES|TRADE"
 Replica root path is   : "d:\trade"
 Replica root volume is : "\\.\D:"
 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 "\\.\D:" has been formatted.
 [2] The NTFS USN journal on volume "\\.\D:" has been deleted.
 [3] The NTFS USN journal on volume "\\.\D:" 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 "\\.\D:".
 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.
 
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
 
To change this registry parameter, run regedit.
 
Click on Start, Run and type regedit.
 
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
   "System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
   "Enable Journal Wrap Automatic Restore"
and update the value.
 
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

0
 
LVL 13

Accepted Solution

by:
Kini pradeep earned 500 total points
ID: 16905700
the FRS is showing its stopped facing an assertion error, the logs also show a jrnl-wrap error. this could be caused by low disk space on the drive hosting the sysvol.
if that is not the case then it could be that the FRS (service) was stopped on this DC for a long time owing to which its not able to find the entries in the jrnl.

to resolve this issue first find the cause , if its low disk space then you can either free up space or you can relocate sysvol, and to answer your question its got everything to do with group policies not getting applied, it could also affect the security policies.

if there is no problem with the disk space then what you could do is (back up all the policies and scripts folder ubder c:\windows\sysvol\domain) stop NTFRS and rename the Jet database (ntfrs.jdb) its under C:\windows\ntfrs
start NTFRS it should reinitialise the sysvol

articles : relocate sysvol
http://support.microsoft.com/?kbid=842162

do you use DFS if yes then do not rename the ntfrs.jdb because its gonna reinit dfs as well.

http://support.microsoft.com/?kbid=889655

all these articles talk about low disk space.

reason why it occurs:
any changes are written to the USN journal, anything related to the sysvol is written in the inbound and the outbound replica logs, if the jrnl cannot be written then the frs is gonna be in error state, i cannot explain it any better i guess check it out on technet, it also tells how to increase the jrnl size.
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Join & Write a Comment

Suggested Solutions

We recently endured a series of broadcast storms that caused our ISP to shut us down for brief periods of time. After going through a multitude of tests, we determined that the issue was related to Intel NIC drivers on some new HP desktop computers …
Resolve DNS query failed errors for Exchange
This video shows how to remove a single email address from the Outlook 2010 Auto Suggestion memory. NOTE: For Outlook 2016 and 2013 perform the exact same steps. Open a new email: Click the New email button in Outlook. Start typing the address: …
This tutorial demonstrates a quick way of adding group price to multiple Magento products.

757 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now