How To Troubleshoot the File Replication Service in Windows Server 2003
IN THIS TASK
back to the top
Verify Disk SpaceOn computer A, look for free disk space on the source folder, the staging folder, and the database partition. On computer B, check the destination partition, the preinstall partition, and the database partition.
- Click Start, click Run, type Eventvwr.msc, and then press ENTER.
- In the console tree, double-click File Replication Service, and then look for the following two events in the display pane:Event id:13511 Database is out of disk space.
Event id:13522 Staging directory is full. An outbound partner that has not connected for a while can cause this. Delete the connection and stop and restart FRS to force deletion of the staging files.
Create a Test ScenarioCreate a test file on computer B, and then make sure it replicates to computer A.
back to the top
Verify That the Computers are Available on the NetworkVerify 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, use a ping command that specifies the fully qualified name of the problem replicas:
- On computer A, click Start, click Run, type cmd, and then click OK.
- At the command prompt type, ping FQDN of computer B, and then press ENTER. Note the IP address for computer B.
- At the command prompt type, ping FQDN of computer A, and then press ENTER. Note the IP address of computer A.
- At the command prompt on computer A, type IPCONFIG /all, and then press ENTER. Make sure that all the information is correct and that the IP address matches the earlier results from the ping command.
- At the command prompt on computer B, type IPCONFIG /all, and then press ENTER. Make sure that all the information is correct and that the IP address matches the earlier results from the ping command.
Check Configurations in the Services Console
- Start the Services Administrative console. To do so, click Start, click Run, type services.msc, and then click OK.
- In the display pane, click File Replication Service, and then confirm that FRS is started and running.
- Following this procedure on both computer A and B.
- If the service is not running, review the FRS container in Event Viewer on the computer on which FRS is not running properly. To do so, click Start, click Run, type Eventvwr.msc, and then click OK. In the console tree, click File Replication Service, and then view the results in the display pane to the right.
- Test the remote procedure call (RPC) connectivity between computer A and computer B. To do so, start Event Viewer on computer B from computer A (which uses RPC). Check FRS event logs on both computers. If Event ID 13508 is present, there may be a problem with the RPC service on either computer or with creating a secure connection between computer A and computer B.
Check Configuration in the Active Directory Sites and Services Console
- On computer A, click Start, point to Administrative Tools, and then click Active Directory Sites and Service. Make sure that the replication between computer A and computer B is turned on. Verify the replication schedule on the Connection object. The Connection object is the inbound connection under computer A's NTFRS_MEMBER object from computer B. For System Volume (SYSVOL), the Connection object is located in the Sites\Site_name\Servers\Server_name\Ntds Settings\Connection_name folder.
- On computer B, click Start, point to Administrative Tools, and then click Active Directory Sites and Service. Make sure that the replication between computer A and computer B is turned on.
NOTE: For DFS, view the connection links in Active Directory Users and Computers. Start Active Directory Users and Computer, on the View menu, make sure that Advanced Settings are selected. View the System container. The location of the Connection objects is in the System\File Replication Service\DFS Volumes folder.
Share AccessDetermine whether or not 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, and this 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.
Determine whether or not the source file had been excluded from replication. Confirm that the file is not Encrypting File System (EFS) encrypted, an NTFS file system (NTFS) junction, or excluded by a file or folder filter on the originating replica member. If any of these situations are true, FRS does not replicate the file or folder.
back to the top
Examine the Log FilesIf the information in this article did not resolve the issue, use Windows Explorer to examine the log files that are created for FRS. The log files are located in the %Systemroot%\Debug folder. The file names are listed from NtFrs_001.log to NtFrs_005.log.
back to the top
Article ID: 327341 - Last Review: 12/03/2007 04:27:22 - Revision: 7.5
- kbactivedirectory kbactivedirectory kbenv kbhowtomaster KB327341