Component Deployment Does Not Install and Register Components When Routes Are Used

ID: Q234941


The information in this article applies to:
  • Microsoft Site Server version 3.0


SYMPTOMS

When you use a route as the destination for a project, Component Deployment does not install and register the components that you deploy. The CAB file is replicated properly to the end-point server, but it is not ready to use because it is not expanded and registered.

If you use an end-point server instead of a route as the destination for the project, everything works as intended. The deployed component is expanded and registered properly.


WORKAROUND

To work around this problem, do the following:

  1. On the end-point server, enable time release for the project. To do this, select Properties for the project and check Enable timed release on the Advanced tab.


  2. On the staging server, run the project as normal or as a scheduled replication.


  3. On the staging server, schedule an apply for the project. To do this, select Properties for the project and click the Schedule tab. Click the Add... button, choose Schedule apply, and then configure the schedule start time options.


  4. When the Schedule apply is finished running, make sure that the component is working as intended on the end-point server.


Additional query words: CRS CD Component Deployment Content Route Routes

Keywords :
Version : winnt:3.0
Platform : winnt
Issue type : kbprb


Last Reviewed: September 8, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.