Command Lines for Troubleshooting Content Replication (252759)


The information in this article applies to:

  • Microsoft Site Server 3.0
This article was previously published under Q252759

SUMMARY

This article lists the most commonly used command line options for Site Server Publishing when you are troubleshooting Content Replication problems.

MORE INFORMATION

Stop or start a CRS service

sscd stop
sscd start

Stop or start project replication

crs startrep ProjectName [flags]
crs stoprep ProjectName

List current projects

crs listproj or sscd listproj

List replication

crs listrep or sscd listrep

Query project

sscd queryProj ProjectName

Schedule a replication

At [time] \Every:date,[...] "c:\Microsoft Site Server\bin\crs.exe" startrep ProjectName
-or- 
At [time] \Every:date, [...] "sscd startrep ProjectName"<BR/><BR/>
For example:
At 14:30 "c:\Microsoft Site Server\bin\crs.exe" startrep MyProject1<BR/>
-or-

At 15:26 "sscd startrep ProjectName"

Enable the CRS logging feature

sscd setglobal fulllogging=yes
sscd stop && sscd start<BR/>
When you use this global parameter for CRS to enable the logging process, a Crs.log and Crssvc.log are generated. Crssvc.log gives detailed information for the project replication process. This feature is only recommended for troubleshooting purposes. It should not be enabled at all times.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

176516 CRS: How to Troubleshoot CRS Issues

Modification Type:MajorLast Reviewed:3/28/2001
Keywords:kbbug KB252759 kbAudDeveloper
©2002 Microsoft Corporation. All rights reserved.