Content Deployment Statistics Are Only Updated for 200 Replications (255093)
The information in this article applies to:
- Microsoft Site Server 3.0
This article was previously published under Q255093 WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that you can solve
problems that result from using Registry Editor incorrectly. Use Registry Editor at your own
risk.
SYMPTOMS
When you run a Content Deployment project, the state ID for the replication is always returned with the same value after 200 replications. The statistics are no longer updated.
CAUSE
The array that is created to hold the replication statistics for each replication instance is statically configured for 200 entries. Even though there is a registry entry (MaximumReplications) to increase the size of the array, it cannot be used because the service fails to start when you increase the MaximumReplications registry parameter.
WORKAROUND
To work around this problem, restart the CRS service to prevent the maximum replications from exceeding 200.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Site Server version 3.0. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
219292 How to Obtain the Latest Site Server 3.0 Service Pack
STATUSMicrosoft has confirmed that this is a problem in Site Server version 3.0. This problem was first corrected in Site Server 3.0 Service Pack 4.
Modification Type: | Major | Last Reviewed: | 10/16/2002 |
---|
Keywords: | kbbug kbQFE kbSiteServ300sp4fix KB255093 |
---|
|