Microsoft KB Archive/167727

= CRS: Access Violations Occur If Route Is Over 300 Characters =

Article ID: 167727

Article Last Modified on 2/19/2004

-

APPLIES TO


 * Microsoft Commercial Internet System 1.0 Service Pack 2
 * Microsoft Content Replication System

-



This article was previously published under Q167727





SYMPTOMS
An access violation in the Content Replication System (CRS) may occur when a route contains more than 300 characters.

The following example demonstrates the behavior:
 * 1) Create a route with 31 destinations. Make the machine names at least 10 characters long so that more than 300 total characters are included in the route.
 * 2) Create a project that uses the route created in step 1.
 * 3) Start the project.
 * 4) An access violation occurs in CRS when the project starts.



CAUSE
CRS uses a hard-coded maximum route size of 300 characters.



RESOLUTION
Crsdll.dll was modified to allow creation of routes with more than 300 characters, however the CRS interface cannot be used to add servers for large routes due to limits of the interface.

To add servers for large routes, you must edit the registry manually using the following steps.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.  Start Registry Editor (Regedt32.exe). Go to the following key in the registry:

HKEY_LOCAL_MACHINE\Software\Microsoft\CRS\Routes

 Locate the key that describes the route that you need to edit. The route may be similar to the following:

HKEY_LOCAL_MACHINE\Software\Microsoft\CRS\Routes\My Route

 Edit the Value Destinations:REG_MULTI_SZ:. Enter the additional server names in the Multi-String Editor, pressing ENTER after you add each name. When you have added all the server names, click OK.</li> Exit Registry Editor.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed this to be a problem in Microsoft Commercial Internet System version 1.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Commercial Internet System version 1.0. For information on obtaining the Service Pack, query on the following article in the Microsoft Knowledge Base:

183062 MCIS 1.0 Service Packs 1 and 2 Information

Additional query words: crs mcis sp2

Keywords: kbbug kbfix KB167727

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.