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

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I am getting the same problem.

I have Windows 2008 DC that is a DNS and GC. This was created by replicating from a Windows 2003 DC. That was decomissioned.

I then set up a new Windows 2008 Core DC.

AD replicated, but the13508 error kept appearing. In then I demoted and set up a new full Windows 2008 server.

Promoted to a DC, but exactly the same problem. AD is replicating, but FRS 13508 keeps appearing. I have disabled firewalls on both servers. Both servers are DNS and GC, but nothing is appearing in the SYSVOL directories.

I thought I would use one of my free technet Plus support incidents, but I have had problems doing that as well! You need a contract number, but I cann't work out where to get the contract number.

Derek Pike

"Prakashkumaar" <Prakashkumaar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:B4D14E1F-A22D-4E84-90E7-B4C1CD4DBBBE@xxxxxxxxxxxxxxxx
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

  • Site-tosite VPN Issue
    ... Windows Server 2003 domain controller ... Mixture of PCs running Windows 2000 Profressional with SP3 and Windows XP ... the VPN to the Windows Server 2003 domain controller. ... 12.7MB file from the server to the client PC. ...
    (microsoft.public.windows.server.networking)
  • RE: Internet Connection Wizard failing at Firewall Config and Secu
    ... You can use the Dcdiag.exe (Domain Controller Diagnostic Tool) included ... in Windows Support Tools to verify the AD status. ... Windows Server 2003 Active Directory Diagnostics, ...
    (microsoft.public.windows.server.sbs)
  • RE: Provide feedback to DC promotion/replacement
    ... one of the is reffering to a Windows 2000 ... As i sad in the previous posts, to rename a domain controller ... controllers in the domain must be running Windows Server 2003. ... a global catalog. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows 2003 DCPROMO Problem
    ... Controllers and you want to add a Windows Server 2003 Domain Controller. ... "Nejmos Saqeb" wrote in message ...
    (microsoft.public.windows.server.active_directory)
  • Re: Pre-authentication failed for Windows 2008 systems
    ... Failure Code: 0x19 ... Client Address: SERVER IP ... Our active directory domain consists of two windows 2003 R2 x64 ... On the domain controller, ...
    (microsoft.public.windows.server.security)