File Replication Service error - Event ID 13552

J

Jeff

Exchange 2000 Server gets FRS error 13552 as shown below.
Knowledge Base Article 819268 talks about this Event ID
but the error is not related to the USN Journal as
described in the KB article.

Anyone seen this error?
Windows error status code is ERROR_INVALID_HANDLE
FRS error status code is FrsErrorNotFound

Error and DCDIAG printouts below:

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13552
Date: 9/17/2003
Time: 11:57:17 AM
User: N/A
Computer: CR4
Description:
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:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support
NTFS 5.0

The information below may help to resolve the problem:
Computer DNS name is "cr4.CRDOMAIN"
Replica set member name is "CR4"
Replica set root path is "c:\winnt\sysvol\domain"
Replica staging directory path
is "c:\winnt\sysvol\staging\domain"
Replica working directory path is "c:\winnt\ntfrs\jet"
Windows error status code is ERROR_INVALID_HANDLE
FRS error status code is FrsErrorNotFound

DCDIAG RESULTS:

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

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

Doing primary tests

Testing server: Default-First-Site-Name\CR4
Starting test: Replications
......................... CR4 passed test
Replications
Starting test: NCSecDesc
......................... CR4 passed test
NCSecDesc
Starting test: NetLogons
......................... CR4 passed test
NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for
\\cr1.CRDOMAIN, when we w
ere trying to reach CR4.
Server is not responding or is not considered
suitable.
......................... CR4 failed test
Advertising
Starting test: KnowsOfRoleHolders
......................... CR4 passed test
KnowsOfRoleHolders
Starting test: RidManager
......................... CR4 passed test
RidManager
Starting test: MachineAccount
......................... CR4 passed test
MachineAccount
Starting test: Services
......................... CR4 passed test Services
Starting test: ObjectsReplicated
......................... CR4 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.
......................... CR4 passed test
frssysvol
Starting test: kccevent
......................... CR4 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC0001A2E
Time Generated: 09/17/2003 11:54:11
Event String: DNS Server has updated its own
host (A) records.
......................... CR4 failed test
systemlog

Running enterprise tests on : CRDOMAIN
Starting test: Intersite
......................... CRDOMAIN passed test
Intersite
Starting test: FsmoCheck
......................... CRDOMAIN passed test
FsmoCheck
 
J

Jerold Schulman

See tip 3605 in the 'Tips & Tricks' at http://www.jsiinc.com

Exchange 2000 Server gets FRS error 13552 as shown below.
Knowledge Base Article 819268 talks about this Event ID
but the error is not related to the USN Journal as
described in the KB article.

Anyone seen this error?
Windows error status code is ERROR_INVALID_HANDLE
FRS error status code is FrsErrorNotFound

Error and DCDIAG printouts below:

Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13552
Date: 9/17/2003
Time: 11:57:17 AM
User: N/A
Computer: CR4
Description:
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:
-- an invalid root path,
-- a missing directory,
-- a missing disk volume,
-- a file system on the volume that does not support
NTFS 5.0

The information below may help to resolve the problem:
Computer DNS name is "cr4.CRDOMAIN"
Replica set member name is "CR4"
Replica set root path is "c:\winnt\sysvol\domain"
Replica staging directory path
is "c:\winnt\sysvol\staging\domain"
Replica working directory path is "c:\winnt\ntfrs\jet"
Windows error status code is ERROR_INVALID_HANDLE
FRS error status code is FrsErrorNotFound

DCDIAG RESULTS:

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

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

Doing primary tests

Testing server: Default-First-Site-Name\CR4
Starting test: Replications
......................... CR4 passed test
Replications
Starting test: NCSecDesc
......................... CR4 passed test
NCSecDesc
Starting test: NetLogons
......................... CR4 passed test
NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for
\\cr1.CRDOMAIN, when we w
ere trying to reach CR4.
Server is not responding or is not considered
suitable.
......................... CR4 failed test
Advertising
Starting test: KnowsOfRoleHolders
......................... CR4 passed test
KnowsOfRoleHolders
Starting test: RidManager
......................... CR4 passed test
RidManager
Starting test: MachineAccount
......................... CR4 passed test
MachineAccount
Starting test: Services
......................... CR4 passed test Services
Starting test: ObjectsReplicated
......................... CR4 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.
......................... CR4 passed test
frssysvol
Starting test: kccevent
......................... CR4 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC0001A2E
Time Generated: 09/17/2003 11:54:11
Event String: DNS Server has updated its own
host (A) records.
......................... CR4 failed test
systemlog

Running enterprise tests on : CRDOMAIN
Starting test: Intersite
......................... CRDOMAIN passed test
Intersite
Starting test: FsmoCheck
......................... CRDOMAIN passed test
FsmoCheck


Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top