CRS: Replication Through a Proxy Server Fails Using FTP and HTTP (168863)
The information in this article applies to:
- Microsoft Commercial Internet System 1.0
- Microsoft Content Replication System
This article was previously published under Q168863 SYMPTOMS
The Content Replication System (CRS) fails to replicate from an FTP
and an HTTP URL when a proxy server is required.
CAUSE
When a proxy is selected for a CRS project, CRS must specify the proxy
using the Windows Internet API (Wininet.dll).
In Microsoft Commercial Internet System (MCIS) version 1.0, you can use
either of two different methods to specify a proxy using the Wininet.dll
file.
However, the Wininet.dll file was updated in Microsoft Internet Explorer
version 3.02 so that only one supported method to specify a proxy exists.
CRS 1.0 does not use the currently supported method for specifying a proxy,
which causes the proxy setting to fail.
RESOLUTION
The Crsdll.dll file was modified to use the supported method for specifying
the proxy in the Wininet.dll file. This change requires Internet Explorer
version 3.02 to allow it to work correctly for the updated Wininet.dll
file.
NOTE: This hotfix has a known limitation: You cannot run an HTTP pull
simultaneously with an FTP pull if they are both going through proxies.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Commercial
Internet System version 1.0. This problem has been corrected in the
latest U.S. Service Pack for Microsoft Commercial Internet System
version 1.0. For information on obtaining the Service Pack, query
on the following article in the Microsoft Knowledge Base:
ARTICLE-ID: 183062
TITLE : MCIS 1.0 Service Packs 1 and 2 Information
Modification Type: | Major | Last Reviewed: | 2/19/2004 |
---|
Keywords: | kbbug kbfix kbother KB168863 |
---|
|