2 Windows DC with 13565, 13562 and 1091 errors

Hi

I have delete the that connection and the errors seems to have stopped.

However, on the second DC that I have installed I am still getting the error below -


Event Type:     Warning
Event Source:     NtFrs
Event Category:     None
Event ID:     13565
Date:          29/08/2003
Time:          11:33:25
User:          N/A
Computer:     PDCBACKUP
Description:
File Replication Service is initializing the system volume with data from another domain controller. Computer PDCBACKUP cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
 
To check for the SYSVOL share, at the command prompt, type:
net share
 
When File Replication Service completes the initialization process, the SYSVOL share will appear.
 
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.

and

Event Type:      Warning
Event Source:      NtFrs
Event Category:      None
Event ID:      13508
Date:            22/09/2003
Time:            12:03:11
User:            N/A
Computer:      PDCBACKUP
Description:
The File Replication Service is having trouble enabling replication from INTOUCHPDC to PDCBACKUP for c:\winnt\sysvol\domain using the DNS name intouchpdc.intouch.com. FRS will keep retrying.
 Following are some of the reasons you would see this warning.
 
 [1] FRS can not correctly resolve the DNS name intouchpdc.intouch.com from this computer.
 [2] FRS is not running on intouchpdc.intouch.com.
 [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
 
 This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.


I have check the DNS name on our DNS server and all seems fine.

It looks like the first DC is not replicating to the second server- how can i solve this problem?

Thanks

James

I'd recommend in reinstalling the AD your second DC.

First demote the DC (http://www.microsoft.com/windows2000/en/server/help/default.asp?url=/windows2000/en/server/help/sag_ADdemoteDC.htm) and try to reinstall. Probably this may help.

I have alreay reinstalled it once with the same errors.

I looked the debug log folder and had a look at the NtFrs_0005.log and found

<FrsDsVerifyPromotionParent:    2868:  5190: S0: 13:49:40> :S: ERROR - DOMAIN SYSTEM VOLUME (SYSVOL SHARE) does not exist on INTOUCHPDC!
<LOCAL_FrsRpcVerifyPromotionParent:2868:  1425: S0: 13:49:40> ++ ERROR - verifying set DOMAIN SYSTEM VOLUME (SYSVOL SHARE) on parent INTOUCHPDC;  WStatus: ERROR_NOT_FOUND
<SERVER_FrsRpcStartPromotionParent:2868:  1528: S0: 13:49:40> ++ ERROR - verify;  WStatus: FRS_ERR_SYSVOL_POPULATE
<FrsDsFindComputer:             2812:  8375: S2: 13:49:59> :DS: Computer FQDN is cn=intouchpdc,ou=domain controllers,dc=intouch,dc=com
<FrsDsFindComputer:             2812:  8381: S2: 13:49:59> :DS: Computer's dns name is intouchpdc.intouch.com
<FrsDsFindComputer:             2812:  8395: S2: 13:49:59> :DS: Settings reference is cn=ntds settings,cn=intouchpdc,cn=servers,cn=default-first-site-name,cn=sites,cn=configuration,dc=intouch,dc=com
<ThSupWaitThread:               2212:   501: S1: 13:50:59> :S: ReplicaCs: Waiting
<ThSupWaitThread:               2212:   529: S1: 13:50:59> :S: ReplicaCs: normal wait

It says the (SYSVOL SHARE) does not exist on INTOUCHPDC -

But it does and it is shared

Any ideas?

Thanks

James

Some more ideas:

1) Check permissions on the Sysvol share. The ACL should include full access for Administrators, Creator/Owner and system, read for server operators and authenticated users.
2) Check if PDCBACKUP do have "Authenticated Users" specified in the "Access this computer from the Network" right. If not - do so :)

3) see http://support.microsoft.com/?kbid=272279, http://support.microsoft.com/?kbid=285923, Q326855 ,

4) Apply latest servicepack (if not yet done) http://support.microsoft.com/?kbid=811370

Have you tried running dcdiag?

http://www.microsoft.com/windows2000/techinfo/reskit/tools/new/dcdiag-o.asp

Post your results...

Did you take a look at the KB articles mentioned in one of me previous postings?

http://support.microsoft.com/?kbid=<kbid>

316790
312862
296183
260575
288399

Um, is your second DC also a DNS server???  If not is it pointed to your first DC as it's primary and no secondary name server listed?  DNS errors or missing data will cause these errors almost every time.

D

The DNS server is not a on any of the DC, Th DNS is on a member server all on it own.

I do I made the second DC ponit to my first DC?

Thanks

Here is the result for the dcdiag below -

From the first dc


DC Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial non skippeable tests

   Testing server: Default-First-Site-Name\INTOUCHPDC
      Starting test: Connectivity
         ......................... INTOUCHPDC passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\INTOUCHPDC
      Starting test: Replications
         ......................... INTOUCHPDC passed test Replications
      Starting test: NCSecDesc
         ......................... INTOUCHPDC passed test NCSecDesc
      Starting test: NetLogons
         ......................... INTOUCHPDC passed test NetLogons
      Starting test: Advertising
         ......................... INTOUCHPDC passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... INTOUCHPDC passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... INTOUCHPDC passed test RidManager
      Starting test: MachineAccount
         ......................... INTOUCHPDC passed test MachineAccount
      Starting test: Services
         ......................... INTOUCHPDC passed test Services
      Starting test: ObjectsReplicated
         ......................... INTOUCHPDC passed test ObjectsReplicated
      Starting test: frssysvol
         Error: No record of File Replication System, SYSVOL started.
         The Active Directory may be prevented from starting.
         ......................... INTOUCHPDC passed test frssysvol
      Starting test: kccevent
         ......................... INTOUCHPDC passed test kccevent
      Starting test: systemlog
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 09/23/2003   09:15:01
            Event String: Driver HP LaserJet 4100 PCL 6 required for
         An Error Event occured.  EventID: 0x00000452
            Time Generated: 09/23/2003   09:15:01
            Event String: The printer could not be installed.
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 09/23/2003   09:15:01
            Event String: Driver HP LaserJet 4100 PCL 6 required for
         An Error Event occured.  EventID: 0x00000452
            Time Generated: 09/23/2003   09:15:01
            Event String: The printer could not be installed.
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 09/23/2003   09:15:02
            Event String: Driver Samsung 7000 Series PCLXL required for
         An Error Event occured.  EventID: 0x00000452
            Time Generated: 09/23/2003   09:15:02
            Event String: The printer could not be installed.
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 09/23/2003   09:15:02
            Event String: Driver ActiveTouch Document Loader required for
         An Error Event occured.  EventID: 0x00000452
            Time Generated: 09/23/2003   09:15:02
            Event String: The printer could not be installed.
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 09/23/2003   09:15:02
            Event String: Driver Samsung 7000 Series PCLXL required for
         An Error Event occured.  EventID: 0x00000452
            Time Generated: 09/23/2003   09:15:02
            Event String: The printer could not be installed.
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 09/23/2003   09:15:03
            Event String: Driver PS-NX 40 required for printer
         An Error Event occured.  EventID: 0x00000452
            Time Generated: 09/23/2003   09:15:03
            Event String: The printer could not be installed.
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 09/23/2003   09:15:03
            Event String: Driver Colorbus Canon Copier required for printer
         An Error Event occured.  EventID: 0x00000452
            Time Generated: 09/23/2003   09:15:03
            Event String: The printer could not be installed.
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 09/23/2003   09:15:04
            Event String: Driver HP LaserJet 4100 PCL 6 required for
         An Error Event occured.  EventID: 0x00000452
            Time Generated: 09/23/2003   09:15:04
            Event String: The printer could not be installed.
         ......................... INTOUCHPDC failed test systemlog

   Running enterprise tests on : intouch.com
      Starting test: Intersite
         ......................... intouch.com passed test Intersite
      Starting test: FsmoCheck

The second DC


DC Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial non skippeable tests

   Testing server: Default-First-Site-Name\PDCBACKUP
      Starting test: Connectivity
         ......................... PDCBACKUP passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\PDCBACKUP
      Starting test: Replications
         ......................... PDCBACKUP passed test Replications
      Starting test: NCSecDesc
         ......................... PDCBACKUP passed test NCSecDesc
      Starting test: NetLogons
         ......................... PDCBACKUP passed test NetLogons
      Starting test: Advertising
         Warning: DsGetDcName returned information for \\intouchpdc.intouch.com,
 when we were trying to reach PDCBACKUP.
         Server is not responding or is not considered suitable.
         ......................... PDCBACKUP failed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... PDCBACKUP passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... PDCBACKUP passed test RidManager
      Starting test: MachineAccount
         ......................... PDCBACKUP passed test MachineAccount
      Starting test: Services
         ......................... PDCBACKUP passed test Services
      Starting test: ObjectsReplicated
         ......................... PDCBACKUP passed test ObjectsReplicated
      Starting test: frssysvol
         Error: No record of File Replication System, SYSVOL started.
         The Active Directory may be prevented from starting.
         There are errors after the SYSVOL has been shared.
         The SYSVOL can prevent the AD from starting.
         ......................... PDCBACKUP passed test frssysvol
      Starting test: kccevent
         ......................... PDCBACKUP passed test kccevent
      Starting test: systemlog
         An Error Event occured.  EventID: 0x0000041B
            Time Generated: 09/23/2003   08:50:05
            Event String: The DHCP/BINL service has determined that it is
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 09/23/2003   09:09:06
            Event String: Driver HP LaserJet 4100 PCL 6 required for
         An Error Event occured.  EventID: 0x00000452
            Time Generated: 09/23/2003   09:09:06
            Event String: The printer could not be installed.
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 09/23/2003   09:09:08
            Event String: Driver HP LaserJet 4100 PCL 6 required for
         An Error Event occured.  EventID: 0x00000452
            Time Generated: 09/23/2003   09:09:08
            Event String: The printer could not be installed.
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 09/23/2003   09:09:10
            Event String: Driver Samsung 7000 Series PCLXL required for
         An Error Event occured.  EventID: 0x00000452
            Time Generated: 09/23/2003   09:09:10
            Event String: The printer could not be installed.
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 09/23/2003   09:09:13
            Event String: Driver ActiveTouch Document Loader required for
         An Error Event occured.  EventID: 0x00000452
            Time Generated: 09/23/2003   09:09:13
            Event String: The printer could not be installed.
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 09/23/2003   09:09:15
            Event String: Driver Samsung 7000 Series PCLXL required for
         An Error Event occured.  EventID: 0x00000452
            Time Generated: 09/23/2003   09:09:15
            Event String: The printer could not be installed.
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 09/23/2003   09:09:17
            Event String: Driver PS-NX 40 required for printer
         An Error Event occured.  EventID: 0x00000452
            Time Generated: 09/23/2003   09:09:17
            Event String: The printer could not be installed.
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 09/23/2003   09:09:19
            Event String: Driver Colorbus Canon Copier required for printer
         An Error Event occured.  EventID: 0x00000452
            Time Generated: 09/23/2003   09:09:19
            Event String: The printer could not be installed.
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 09/23/2003   09:09:21
            Event String: Driver HP LaserJet 4100 PCL 6 required for
         An Error Event occured.  EventID: 0x00000452
            Time Generated: 09/23/2003   09:09:21
            Event String: The printer could not be installed.
         ......................... PDCBACKUP failed test systemlog

   Running enterprise tests on : intouch.com
      Starting test: Intersite
         ......................... intouch.com passed test Intersite
      Starting test: FsmoCheck

What do you think?

Of the errors from the first DC

      Starting test: frssysvol
         Error: No record of File Replication System, SYSVOL started.
         The Active Directory may be prevented from starting.
         ......................... INTOUCHPDC passed test frssysvol

ANd errors form the Second DC -

      Starting test: Advertising
         Warning: DsGetDcName returned information for \\intouchpdc.intouch.com,
 when we were trying to reach PDCBACKUP.
         Server is not responding or is not considered suitable.

     Starting test: frssysvol
         Error: No record of File Replication System, SYSVOL started.
         The Active Directory may be prevented from starting.
         There are errors after the SYSVOL has been shared.
         The SYSVOL can prevent the AD from starting.

Thanks

James

YES - have read the following -

316790 – I tried the RESOLUTION – but it did not sort the problm
312862 – am not getting those error now
296183 - read
260575 - I dont have a problem with my password
288399 - i am not getting the error- The following error occurred while creating DFS root. Cannot create a file when that file already exists.

Thanks

One next suggestion: clearing up the jet-Databases (they probably somehow get damaged)

    net stop NetLogon
    net stop Ntfrs
    del %systemroot%\ntfrs\jet\Ntfrs.jdb
    del %systemroot%\ntfrs\jet\Sys\Edb.chk
    del %systemroot%\ntfrs\jet\log\edb.log
    del %systemroot%\ntfrs\jet\log\res1.log
    del %systemroot%\ntfrs\jet\log\res2.log
    net start NetLogon
    net start Ntfrs

Looks like you are having File Replication Service problems. If you place a file in the SYSVOl share does it replicate?  Do you have any Journal Wrap Errors in your FRS Eventlog?  You can use the ntfrsutil to view information about the FRS Service:

http://www.microsoft.com/windows2000/techinfo/reskit/en-us/default.asp?url=/WINDOWS2000/techinfo/reskit/en-us/distrib/dsdh_frs_LPXW.asp

nothing in the SYSVOL is replicated and no i do not have any Journal Wrap Errors.


I will have to use ntfrsutil the tomorrow.

Thanks

James  

I have cleaned up the jet-database in both servers and i am still getting the 13508 error

I ran the dcdiag and it look ok but for this

Domain membership test . . . . . . : Failed
    [WARNING] Ths system volume has not been completely replicated to the local machine. This machine is not working properly as a DC.

However, when i look in the active directory replication monitor - all the replication says it the last attempt was successful.

I know that the Sysvol folder on the new DC is not share so it cant be a a proper DC yet

What you think?

thank

James
 

Active directory replication is different than File System Replication. Is the SYSVOL shared on your PDC? Do a net share to see if it shows up.

Whatever other problems you have you will need to get FRS replication working for the DC to operate correctly.

A general procedure for troubleshooting FRS problems consists of the following steps:

   1. Verify that both Computer A and Computer B are available on the network. Because FRS uses the fully qualified domain name (FQDN) of the replica members, a good first check is to use a ping command specifying the fully qualified name of the problem replicas. From Computer A, send a ping command with Computer B's FQDN. From Computer B, send a ping command to Computer A's FQDN. Verify that the addresses returned by the ping command are the same as the addresses returned by an ipconfig /all command carried out on the command line of the destination computer.
   2. Use the Services administrative console to confirm that FRS is running on the remote computer.
   3. If the service is not running, review the File Replication service container of Event Viewer (Eventvwr.msc) on the problem computer. If the service has asserted, troubleshoot the assertion. Otherwise, restart the service.
   4. Verify RPC connectivity between Computer A and Computer B. Check FRS event logs on both computers. If Event ID 13508 is present, there might be a problem with the RPC service on either computer or with creating a secure connection between Computer A and Computer B.
   5. Use the Active Directory Sites and Services console to verify the replication schedule on the Connection object. Make sure that replication is enabled between Computer A and Computer B and that the connection is enabled. The Connection object is the inbound connection under Computer A's NTFRS_MEMBER object from Computer B. For SYSVOL, the connection object resides under Sites\site_name\Servers\server_name\NTDS Settings\connection_name.
   6. Create a test file on Computer B, and verify its replication to Computer A.
   7. Check for free disk space on Computer A (source directory, staging directory, and database partition) and Computer B (destination partition, preinstall partition, and database partition). Look for the following events in Event Viewer:
          * 13511: Database is out of disk space.

      For more information about how to move the database to a larger volume, see "FRS Tables" earlier in this chapter.
          * 13522: Staging directory is full.

      This can be caused by an outbound partner that has not connected for a while. Delete the connection and stop and restart FRS to force deletion of the staging files. You can also follow the procedure described in "Tuning Recommendations" earlier in this chapter to increase the size of the staging directory.
   8. Check for files that are larger than the amount of free space on the source or destination server or larger than the size of the staging directory limit in the registry. Resolve the disk space problem or increase the maximum staging file space. See Error 13522 for details.
   9. Check whether the file on the originating server is locked on either computer. If the file is locked on Computer B so that FRS cannot read the file, FRS cannot generate the staging file, which delays replication. If the file is locked on Computer A so that FRS cannot update the file, FRS continues to retry the update until it succeeds. The retry interval is 30 to 60 seconds.
  10. Check whether the source file was excluded from replication. Confirm that the file is not EFS encrypted, a NTFS junction, or excluded by a file or folder filter on the originating replica member. If any of these are true, FRS does not replicate the file or directory.
  11. If all of the previous conditions check out, try to replicate the file again.

On your PDCPACKUP when typing "\\intouchpdc.intouch.com\" in the Windows Explorer address bar - do you see the shares on the "old" PDC? Can you access them?


So then back to DNS:

Make sure your dns zone is set up for dynamic update.
When running "ipconfig /registerdns" on both DCs - any errors?
When running "netdiag /fix"on both DCs - any errors?

In the dns zone for your domain do you see the _msdcs _site _tcp and _upd folders? Try to delete them, and on the old DC run "net stop netlogon" and "net start netlogon". They should be recreated if the AD/DNS setup is correct.


xylog: I think instead of copying the resource kit, just pointing to it would be more usefull.
http://www.microsoft.com/windows2000/techinfo/reskit/en-us/default.asp?url=/windows2000/techinfo/reskit/en-us/distrib/dsdh_frs_LAHM.asp

bhoehne

Yes i can see the shares in Windows Explorer when i enter \\intouchpdc.intouch.com\ and yes i can access the sysvol folder.

I ran the ipconfig /registerdns and netdiag /fix on both DC andI did not get any errors.

On the DNS server I deleted the _msdcs _site _tcp and _upd folders and restarted the netlogon and they where recreated fine. However, I still have the error 13508 error.

I see we have gone through alot of troubleshooting with no clear answer - I even installed another (a 3rd) PC as the DC and it have the same problem  - error 13508 and can replicate to the first of second DC.

I think it can only be a problem the first DC or the DNS server - however, i just cant see the problem.

You have any more ideas?

Once other thing the the first DC has only got 300mb of space left on the the  systems drive where the sysvol is. Would this effect it? - through am not getting any disk space errors?

Thanks

James

ok sound like this could be a problem.

But do you think due to this small amount of space with stop the DC from replicating to the DC's?

Thanks

James

Hi all

Am back after so long.

I have got my self a copy of Volmune manger for windows 2000 server and i have increase the size of the c: drive to over 10 GB.

However, I am still getting the 13508 errors -

Any more ideas any one?
Thanks

James

Hey James,
I am having the same problems. Almost exactly the same except for the server names. :D

"
      Starting test: Advertising
         Warning: DsGetDcName returned information for \\omiappz.overture-media,
 when we were trying to reach OMIWEB.
         Server is not responding or is not considered suitable.
"

"
      Starting test: frssysvol
         Error: No record of File Replication System, SYSVOL started.
         The Active Directory may be prevented from starting.
"

I was able to fix the "single-label problem of service pack 4". Now these 2 are the only errors i have to fix. Were you able to find a solution?

Hey

Great it a way someone has the some problem.

Any one got a answer to the issue we are having.

Thanks

James

Thanks for the reply jmissild!

Unfortunately we couldn't wait for a fix for this. So we did the long and hard way... reformatted every server and started all over.

Thanks anyway.

Hi jameslee1977,
Try following troubleshootin guide:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Operations/4f504103-1a16-41e1-853a-c68b77bf3f7e.mspx.
Hope helps,

Hello tech,

This article refers to Active Directory replication, but the issue with this case was FRS. Thanks for the update though!
I believe that this is a closed issue since it has been so long with no response.

Jason Missildine