[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1209
  • Last Modified:

FRS not working - Staging directory permissions lost

We have an issue with one of our domain controllers.

Basically, there were a load of event i.d. 13539 (cannot replicate the staging dir) errors on our main DC. So we stopped and started the frs service to then be presented with even worse news. We recieved a 13555 event ID (FRS is in an error state) along with a 13552 (FRS error status code is FrsErrorStageDirOpenFail).

Looking at the FRS staging directory (C:\Windows\Sysvol\Staging\, there is a folder called Domain which is unaccessible and has no permissions set on it. When you double click the folder, it brings up an error of "The name of the file cannot be resolved by the system".

We have trawled the net to find numberous suggestions, but we are concerned that none are actually addressing the issue in that the folder is inaccessible. One suggestion was that we do a non-authorative restore of the system state, but would this clear the problematic folder? We also naturally don't want to do it! Another suggestion is that we delete the Jet database files, but again, would that clear the problematic folder.

We have tried to reset the permissions from the parent folder, but this hasn't worked.

I have a new DC to install on our new site by next wednesday so any help would be really grateful.

Rob S
0
Teamsolve
Asked:
Teamsolve
  • 2
1 Solution
 
TeamsolveAuthor Commented:
Just to update everyone, I have backed up and deleted the Jet database. This has recreated successfully. However, it is still not working. Within event viewer, the error is now one single instance of event ID 13539. The directory is still inaccessible.

Looking at the FRS logs, the following is being repeated every 5 minutes:

<ThSupWaitThread:               3156:   505: S1: 21:20:53> :S: ReplicaCs: Waiting
<ThSupWaitThread:               3156:   533: S1: 21:20:53> :S: ReplicaCs: normal wait
<FrsDsFindComputer:             6064:  8796: S2: 21:21:53> :DS: Computer FQDN is cn=winserver,ou=domain controllers,dc=mydomain,dc=co,dc=uk
<FrsDsFindComputer:             6064:  8802: S2: 21:21:53> :DS: Computer's dns name is winserver.mydomain.co.uk
<FrsDsFindComputer:             6064:  8816: S2: 21:21:53> :DS: Settings reference is cn=ntds settings,cn=winserver,cn=servers,cn=mydomain-site1,cn=sites,cn=configuration,dc=mydomain,dc=co,dc=uk
<FrsOpenSourceFileW:            6064:  1467: S0: 21:21:53> NtCreateFile failed :  NTStatus: c0000280-???
<FrsOpenSourceFileW:            6064:  1478: S0: 21:21:53> ++ CreateFile failed on file \??\c:\windows\sysvol\staging\domain;  WStatus: 1921-???
<FrsVerifyVolume:               6064:  4038: S0: 21:21:53> ERROR - Unable to open root path c:\windows\sysvol\staging\domain. Retry at next poll.  WStatus: 1921-???

One other thing I have noticed is that when running NTFRSUTL DS, the primary server is a server that no longer exsists. Does this matter.

Any help would be grateful

Rob S
0
 
Kini pradeepIT Technology Senior ConsultantCommented:
well, when you say it no longer exists -- does it mean that the Dc was removed but the metadata cleanup was not done. If the server no longer exists then all its traces have to be removed from AD by performing the metadata cleanup.

http://support.microsoft.com/kb/216498

0
 
TeamsolveAuthor Commented:
The metadata cleanup hasn't been done no.

Going back to the original problem > We seem to have resolved this now by renaming the C:\windows\sysvol\staging\domain directory. The FRS service then recreated the directory and successfully sync'd with the server's it needed too.

We still have a small issue in that the new Domain controller we have is struggling to sync, but I'm confident we can sort this now.
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

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