PRB: Scripts Do Not Work When You Use the CRS Commandline Tool in Terminal Server Session (282072)


The information in this article applies to:

  • Microsoft Site Server 3.0
  • Microsoft Site Server 3.0 Commerce Edition
This article was previously published under Q282072

SYMPTOMS

When you use the Content Replication Service (CRS) Commandline tool to start a CRS project in a Terminal Server session, CRS scripts do not work. The following entry (or similar) is logged in the CRS log:
12/7/2000 12:11:49 WRN 5 2436 CreateProcessAsUser
@e:\inet2fre\pubsys\crs\crsdll\util.cpp 329
Access is denied.

CAUSE

This problem occurs because of how the CRS Commandline tool interfaces with the Terminal Server.

RESOLUTION

To resolve this problem, perform the following steps:
  1. In Microsoft Management Console (MMC), connect to the remote computer as follows:
    1. At a command prompt, and type the following command:

      mmc.exe

    2. From the console menu, select Add/Remove Snap-in.
    3. Click Add, and then click Publishing.
    4. Click Close twice.
    5. Locate the Publishing tree on the left side. Right-click Publishing, and then click Add Host/Connect Host. Write the host name or Internet Protocol address of the server that you want to administrate.
    6. Click Projects, and then right-click your project (for example, TESTREPL). Click Start.
  2. Use the CRS Scheduled Replication Option as follows:
    1. Right-click your project, and click Properties.
    2. On the Schedule tab, select the Deploy automatically as content changes check box.
    3. Click Add, and select the desired scheduling interval.
Modification Type:MinorLast Reviewed:7/16/2004
Keywords:kbprb KB282072
©2004 Microsoft Corporation. All rights reserved.