Microsoft KB Archive/282072

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

Article ID: 282072

Article Last Modified on 7/16/2004

-

APPLIES TO


 * Microsoft Site Server 3.0 Standard Edition
 * 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:  In Microsoft Management Console (MMC), connect to the remote computer as follows:  At a command prompt, and type the following command:

mmc.exe

 From the console menu, select Add/Remove Snap-in. Click Add, and then click Publishing. Click Close twice. 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.</li> Click Projects, and then right-click your project (for example, TESTREPL). Click Start.</li></ol> </li> Use the CRS Scheduled Replication Option as follows: <ol style="list-style-type: lower-alpha;"> Right-click your project, and click Properties.</li> On the Schedule tab, select the Deploy automatically as content changes check box.</li> Click Add, and select the desired scheduling interval.</li></ol> </li></ol>

Additional query words: TSE

Keywords: kbprb KB282072

-

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

© Microsoft Corporation. All rights reserved.