BUG: Replication Target Status Not "Succeeded" After Large Out-of-Cluster Deployments (302503)
The information in this article applies to:
- Microsoft Application Center 2000
This article was previously published under Q302503 SYMPTOMS
The Application Center 2000 Administration Console synchronizations pane may not indicate "Succeeded" for the status of specific target computers after a large out-of-cluster content deployment to several target computers has finished. This is true even though the final job status appears as "Succeeded" and the deployed content exists on all target computers.
CAUSE
For the Administration Console synchronizations pane status to be accurate, the cluster controller must receive regular synchronization status notifications from the target computers. In this case, the Console is not receiving status notifications from the targets because of a design limitation in the Application Center 2000 replication service. The replication service has a limited number of worker threads in a pool. The service uses these threads to handle replication engine tasks as well as synchronization status notifications. In this case, the thread pool is busy handling the large content deployment. As a result, the threads do not handle the synchronization status notifications, so the target status is not updated.
RESOLUTION
This problem does not prevent the actual replication of content. However, as a precaution, you should verify the content after you perform large content deployments to multiple out-of-cluster target computers.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Major | Last Reviewed: | 10/22/2002 |
|---|
| Keywords: | kbbug kbDSupport KB302503 |
|---|
|