Article ID: 255093
Article Last Modified on 10/16/2002
APPLIES TO
- Microsoft Site Server 3.0 Standard Edition
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.
RESOLUTION
To 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
STATUS
Microsoft 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.
MORE INFORMATION
With this fix installed, the MaximumReplications registry value can be configured to increase the maximum number of replications allowed. In addition, this fix allows the entries in the array to be successfully recycled. As a result, when the MaximumReplications registry value is exceeded, statistics are saved in the first entries of the array.
Configuring MaximumReplications
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.
To configure the MaximumReplications registry value, do the following:
- Start Registry Editor (Regedt32.exe).
- Locate the following key in the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\CRS
- On the Edit menu, click Add Value, and then add the following registry value:
Value Name: Maximumreplications
Data Type: REG_DWORD
Value: <see the following NOTE>NOTE: By default, this registry value is set to 200; however, it can be incrementally increased. The Maximumreplications registry value configures a statically defined array. The ID is an index into this data structure. Each increment of 1 results in the static allocation of an array entry. For example, if you set the Maximumreplications registry value to 300, the result is an allocation of 300x376 bytes = 112800 bytes, ~ 113k. As a result of this increase in memory use, this parameter needs to be incrementally increased.
- Quit Registry Editor.
Configuring Event Notification
With the fix installed, an event (event ID 15357) can be provided if the MaximumReplications registry value is exceeded. The Translatedevents table in the event sink is only updated by performing the following steps:
- Stop the CRS service.
Run the following sample Visual Basic Script to add the new event to the Translatedevents table:
'Change the path on the first line to the location of 'your events.mdb strConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\microsoft site server\data\publishing\Events.mdb" Set cnn = wscript.CreateObject("ADODB.Connection") cnn.Open strConnectionString strSQL = "INSERT INTO TranslatedEvents values (1073757181, 15357, 'I', 'Site Server Content Deployment service maximum replications have been reached - reusing instance ID numbers.')" cnn.Execute strSQL,,adCmdText + adExecuteNoRecords <BR/> <BR/>- In the Site Server Administration MMC, expand Content Deployment, expand Servers, expand Properties, and then expand Log Settings.
- Restart the CRS service.
Keywords: kbbug kbfix kbqfe kbsiteserv300sp4fix KB255093
