Microsoft KB Archive/238440

= Publishing Replication Fails Due to CRS Project Routes Registry Permission Problem =

Article ID: 238440

Article Last Modified on 7/15/2004

-

APPLIES TO


 * Microsoft Site Server 3.0 Standard Edition
 * Microsoft Site Server 3.0 Commerce Edition

-



This article was previously published under Q238440



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
A user who has permissions to operate a project may observe that the project files fail to replicate. By using either the Microsoft Management Console (MMC) or the WebAdmin tool, the CrsDemo project fails to start. On the CRS Source System, a red report is returned. The project status displays as Running, and then changes to Completed immediately. No error message is logged in the event log. With Security Event logging enabled, a security violation does not occur.



CAUSE
The project requires access to the route that is associated with the project as it has been configured in the Project Properties through the Site Server Administration MMC snap-in. When a user is assigned Project Operator permissions, permissions are assigned to the registry keys for the project and route. In a failing case, the registry key cannot be accessed by CRS, and the replication fails. This is due to a lack of permissions assigned for the user to access the route key.



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

Log in as an administrator, and then provide permission through Regedt32. When you log in to the CRS Source system as the user in question, the project replication is successfully started. Set the permissions for the following registry keys:

SOFTWARE\Microsoft\CRS\Routes

SOFTWARE\Microsoft\CRS\Routes\ProjectName

The user who is logged in can verify the permissions. When you are logged in as the user in question, run Regedt32. Access to the registry keys can be visually verified because the registry keys are black if permission is available.

NOTE: If you are logged in with administrative privileges, you can click the Security button to view a listing of permissions and make changes.



CRS Debugging Log Results
DBG 0 496 EVENT (15307): Project  starting.

The following error message indicates the registry key that results in the inability to route replication data:

WRN 5 496 SOFTWARE\Microsoft\CRS\Routes\ @E:\inet2fre\core\pubcore\

The following error messages are incidental and do not represent a problem:

WRN 5 346 Unable to open key SOFTWARE\Microsoft\CRS DBG 0 346 Current User is domain\user

WRN 5 496 RegOpenKeyEx @E:\inet2fre\core\pubcore\pathname.cpp 1363

DBG 0 496 Couldn't find Registry variable Destinations

WRN 5 346 Unable to open key SOFTWARE\Microsoft\CRS\Projects\

DBG 0 496 State on project  changing from Starting to Running

DBG 0 496 State on project  changing from Running to Complete

Additional query words: CRS route permissions replication

Keywords: kbprb kbpending KB238440

-

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

© Microsoft Corporation. All rights reserved.