FRS errors

  • Thread starter Thread starter Rp
  • Start date Start date
R

Rp

One of the DC servers crashed and was rebuilt from
scratch. The AD information was never reloaded and a
dcpromo was run to promote it to a DC. In the event viewer
I see

error 13552

Using replmon under group ploicy objects is SYSVOL: error

Everything gets replicated to other DC's when I make a
change to a user or groupin AD User's and Computer's .

Can anyone help out on what I need to do to get the sysvol
in sync with the other 2 DC's.

thank you
-Rp-
 
Hi Rp

Can you provide some more information with respect to the rebuilt DC?

Was the Active Directory cleaned up to remove the existance of the failed DC
before it was rebuilt?

Was the DC rebuilt with the same name?

How many DC's are in your environment?

Did the failed DC own any FSMO roles?

Were FSMO roles on the failed DC transferred to another DC?

Are you able to provide the full event 13552 description as it appears in
the log?

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Sounds like you need to do a metadata cleanup. Follow the steps in this
article for more info.: http://support.microsoft.com/?id=216498

If you've brought up a DC with the same name as another, or SYSVOL has never
replicated for whatever reason, modifying the following registry value to D2
will force that DC to pull SYSVOL from another DC:

HKLM\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Proce
ss at Startup\BurFlags [REG_DWORD]




--

Paul Williams
_________________________________________
http://www.msresource.net - Under construction, but coming soon...


Join us in our new forums!
http://forums.msresource.net
_________________________________________
 
See below for response to questions and thx for your help !
-----Original Message-----
Hi Rp

Can you provide some more information with respect to the rebuilt DC?

Was the Active Directory cleaned up to remove the existance of the failed DC
before it was rebuilt?- No

Was the DC rebuilt with the same name?- yes

How many DC's are in your environment? a total of 3
Click to expand...
including the one with the problem(very small shop)
Did the failed DC own any FSMO roles?- No all roles were
Click to expand...
kept on the 1st server that dcpromo was run on
Were FSMO roles on the failed DC transferred to another
Click to expand...
DC?- no FSMO roles were on the server
Are you able to provide the full event 13552 description as it appears in
the log?-yes
Click to expand...

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:
invalid root path
missing directory
missing disk volume
file system on a non ntfs 5.0 volume

The information below might help to resolve the problem:

computer name= mycomputer.domain.com
replica set member name is "computer name"
replica set root path = c:\winnt\sysvol\domain
replica staging directory path=
c:\winnt\sysvol\staging\domain
replica working dir path= c:\winnt\ntfrs\jet
windows error code is error_invalid_handle
frs error status code is frserrornotfound

This server was an NT40 server that was upgraded to w2k
and then dcpromo was run.
also-- The sysvol is not shared like on the other 2 DC's.





-----Original Message-----
Hi Rp

Can you provide some more information with respect to the rebuilt DC?

Was the Active Directory cleaned up to remove the existance of the failed DC
before it was rebuilt?

Was the DC rebuilt with the same name?

How many DC's are in your environment?

Did the failed DC own any FSMO roles?

Were FSMO roles on the failed DC transferred to another DC?

Are you able to provide the full event 13552 description as it appears in
the log?

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.



One of the DC servers crashed and was rebuilt from
scratch. The AD information was never reloaded and a
dcpromo was run to promote it to a DC. In the event viewer
I see

error 13552

Using replmon under group ploicy objects is SYSVOL: error

Everything gets replicated to other DC's when I make a
change to a user or groupin AD User's and Computer's .

Can anyone help out on what I need to do to get the sysvol
in sync with the other 2 DC's.

thank you
-Rp-
Click to expand...


.
Click to expand...
 
Hi Rp

Running metadata cleanup is certainly an option but you'll need to rebuild
this problematic DC again to ensure everything is clean. I'd suggest:

1. Remove the problematic DC from the network.

2. Run metadata cleanup:

216498 HOW TO: Remove Data in Active Directory After an Unsuccessful
Domain
http://support.microsoft.com/?id=216498

3. Format and re-install the OS on the problematic DC.

4. Ensure that the problematic DC points to the correct DNS server that owns
the zone for your internal name space.

5. Run DCPromo to promote back into the domain.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.

Rp said:
See below for response to questions and thx for your help !
-----Original Message-----
Hi Rp

Can you provide some more information with respect to the rebuilt DC?

Was the Active Directory cleaned up to remove the existance of the failed DC
before it was rebuilt?- No

Was the DC rebuilt with the same name?- yes

How many DC's are in your environment? a total of 3
Click to expand...
including the one with the problem(very small shop)
Did the failed DC own any FSMO roles?- No all roles were
Click to expand...
kept on the 1st server that dcpromo was run on
Were FSMO roles on the failed DC transferred to another
Click to expand...
DC?- no FSMO roles were on the server
Are you able to provide the full event 13552 description as it appears in
the log?-yes
Click to expand...

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:
invalid root path
missing directory
missing disk volume
file system on a non ntfs 5.0 volume

The information below might help to resolve the problem:

computer name= mycomputer.domain.com
replica set member name is "computer name"
replica set root path = c:\winnt\sysvol\domain
replica staging directory path=
c:\winnt\sysvol\staging\domain
replica working dir path= c:\winnt\ntfrs\jet
windows error code is error_invalid_handle
frs error status code is frserrornotfound

This server was an NT40 server that was upgraded to w2k
and then dcpromo was run.
also-- The sysvol is not shared like on the other 2 DC's.





-----Original Message-----
Hi Rp

Can you provide some more information with respect to the rebuilt DC?

Was the Active Directory cleaned up to remove the existance of the failed DC
before it was rebuilt?

Was the DC rebuilt with the same name?

How many DC's are in your environment?

Did the failed DC own any FSMO roles?

Were FSMO roles on the failed DC transferred to another DC?

Are you able to provide the full event 13552 description as it appears in
the log?

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.



One of the DC servers crashed and was rebuilt from
scratch. The AD information was never reloaded and a
dcpromo was run to promote it to a DC. In the event viewer
I see

error 13552

Using replmon under group ploicy objects is SYSVOL: error

Everything gets replicated to other DC's when I make a
change to a user or groupin AD User's and Computer's .

Can anyone help out on what I need to do to get the sysvol
in sync with the other 2 DC's.

thank you
-Rp-
Click to expand...


.
Click to expand...
Click to expand...
 
Back
Top