CRS: Access Violations Occur If Route Is Over 300 Characters

• Microsoft Commercial Internet System, version 1.0

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.

1. Start Registry Editor (Regedt32.exe).

2. Go to the following key in the registry:

   HKEY_LOCAL_MACHINE\Software\Microsoft\CRS\Routes

3. 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

4. Edit the Value Destinations:REG_MULTI_SZ:.

5. Enter the additional server names in the Multi-String Editor, pressing ENTER after you add each name.

6. When you have added all the server names, click OK.

7. Exit Registry Editor.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Commercial Internet System version 1.0. A supported fix is now available, but has not been fully regression- tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Keywords          : kbfixlist
Version           : WinNT:1.0
Platform          : winnt
Hardware          : ALPHA x86
Issue type        : kbbug
Solution Type     : kbfix