Re: NTFRS Event ID: 13568 , plz help resolveing of this issue - UR

Hello Prakashkumaar,
I would be most concerned to find out why the second dc isn't providing the redundent services you need.

Check to see if this second DC is a GC, if not promote it to a GC
http://support.microsoft.com/default.aspx?scid=kb;en-us;313994

Verify that your clients point to multiple DNS servers in your domain. I assume that you have dns running on your first DC and you need to get a secondary dc with dns as well, if you don't.

Convert Primary to AD Integrated
http://support.microsoft.com/default.aspx?scid=kb;en-us;198437

Best Practices
http://support.microsoft.com/kb/825036


Also check out my website to get info on decommissining a dc
http://www.pbbergs.com/windows/articles.htm
Select Decommissiong a DC

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4


http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This posting is provided "AS IS" with no warranties, and confers no rights.



Hi

I too have the same problem. My scenario is as follows

I have Windows 2003 R2 - 32Bit - Domain Controller (DC1) running on
virtual
server
I have tried to install additional domain controller (DC2) on another
virtual server running Windows 2003 R2 - 64 Bit
My aim was to move the FSMO roles to DC2 so that I would remove DC1
from the network. I tried to transfer the FSMO roles to DC2 having in
mind that our 64 Bit Windows server would become domain controller.

FSMO transfer was successful and suddenly I was not able to login any
of the domain controller. I could not remember what the actual issue
was. All I was able to find the issue because of FRS replication
service. Since I lost total access to both domain controllers the only
way to restore the setup is restore the DC1 virtual server from backup
(kind of restoring the entire server).

After the virtual server restores everything was working fine except
the errors related to DC2. I manually removed the active directory
related to DC2 as per the KB article
http://support.microsoft.com/kb/216498

Now I am back to the position where I was before starting this task.
ie. I am running DC1 alone and all other clients, applications are
working fine.

However I need to move the Domain controller to 64bit windows so I
decided to give one more try with fully equipped.

When I was checking the DC1 before setting up the additional domain
controller I found the same error log (Event ID 13568) under "File
Replication Service"

Having this error I hope I may not be able to setup the additional
domain controller for DC1 unless this error is rectified.

Please advice me to resolve this issue.

Thanks
Prakash
"Meinolf Weber" wrote:

Hello saqib,

This should help you:
http://support.microsoft.com/kb/290762
If not please describe your environment what happened or what you
have done before.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
JRNL_WRAP_ERROR



.

Relevant Pages

  • Re: Second domain controller does not take over in case the first fail
    ... Recently I did a test shutting down first our primary domain controller, ... which is both GC server and holds all the FSMO roles. ... local service credentials. ... DC1 was running perfectly at ...
    (microsoft.public.windows.server.active_directory)
  • Re: root forest AD DC crashed
    ... For location A install a fresh W2K3 server with SP1. ... Give DC1 it own IP address ... As preferred DNS for DC1 enter the IP of DC1 ... As alternate DNS for DC1 enter the IP of DC2 ...
    (microsoft.public.win2000.active_directory)
  • Re: Domain controller name -rename issue
    ... Because you did not know what your predecessor have done with the DC1 renaming, i would make sure that the correct existing DC2 have all 5 FSMO roles and is GC server and DNS with AD integrated zones only for the correct old named "domain" domain. ... AD users and computers and AD sites and services is cleaned up you can now promote the old DC1 again to domain controller. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Demoting a DC in W2003
    ... forrest / single domain with three DCs. ... It's only role is being a DC and our primary internal DNS server. ... transfered the FSMO roles from DC1 to DC2 using the MS KB article 324801. ... The local domain controller has attempted to replicate the following object from the following source domain controller. ...
    (microsoft.public.win2000.active_directory)
  • Re: Seize RID Master Role
    ... You need to seize the roles to the working domain controller. ... Seize the roles to the working DC, make sure this machine has DNS ... If the previous DC was a DHCP server, I would backup the DHCP database. ... Master roles instead of the full DNS name of DC1, ...
    (microsoft.public.windows.server.active_directory)