Article ID: 242211
When you connect from a client to a secure Web sites using a server that was upgraded to Proxy Server 2.0 and Internet Information Server (IIS) 4.0, you may receive the following error message in the client's browser:
87 The parameter is incorrect.
An error occurred while trying to retrieve your URL.
This error could have been caused by:
This error message can occur if one or more of the following conditions exist on the IIS 4.0/Proxy Server 2.0:
If the Filter DLLs value in the following legacy registry key contains the paths to the sspifilt.dll and W3proxy.dll files:
These ISAPI filter DLLs were required by previous versions of Proxy Server and IIS, but are no longer needed when you use IIS 4.0 and Proxy Server 2.0.
If the ISAPI filter(s) specified in the properties of the Default Web Site on the IIS 4.0 are corrupted, incorrect or otherwise incompatible with the w3proxy.dll ISAPI filter. The ISAPI filter w3proxy should be loaded first and its status should indicate a green upward pointing arrow. If another ISAPI filter is present and initialized first, it may prevent the w3proxy ISAPI filter from initializing. Other ISAPI filters may be loaded for the Default Web Site, such as exchfilt.dll which is installed if Outlook Web Access is installed on the server. Normally, these additional filters are installed such that the w3proxy filter is loaded first. All ISAPI filters installed on the Default Web Site should be loaded and their status should indicate a green up arrow.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
1. If the registry key below contains any of the values indicated in part 1 of the CAUSE section above, use the Registry editor (regedt32.exe is recommended for this purpose) to delete the Filter DLLs value from the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\W3svc\Parameters2. If the properties of the Default Web Site, ISAPI Filters tab indicate that another ISAPI filter is loaded ahead of the w3proxy filter and the w3proxy filter is not initializing (indicated by a red down arrow status) then:
a. Move the w3proxy filter to the top of the load order by highlighting it and using the up arrow to the left of the ISAPI filters list window so that it is at the top of the load order.3. If the w3proxy ISAPI filter is at the top of the filter order and is not loading and initializing properly when the IIS 4.0 and Proxy Server 2.0 services are started, replace w3proxy.dll with a new copy from an appropriate source: Windows NT Option Pack, Small Business Server 4.5 distribution CDs, Back Office 4.5 distribution CDs or other known good source and repeat steps 2.a. through 2.g. as appropriate.
b. Apply the change to the Default Web Site by clicking the apply button at the bottom of the property sheet and then the OK button. Close the Internet Service Manager (ISM) Microsoft Management Console (MMC.)
c. Stop the following services using the Control Panel Services applet:
(1) Microsoft Proxy Server Administration service.e. Reopen the ISM MMC and expand to expose the Defalt Web Site. Right click on the Default Web Site then select Properties. Go to the ISAPI filters tab. Verify that the w3proxy has initialized properly as indicated by a green up arrow status and that it is the first ISAPI filter loaded for the Default Web Site.
(2) Microsoft WinSock Proxy service.
(3) The IISAdmin service.
(4) The Proxy Alert Notification Service (if not already stopped by step 2.c.(1) above.)
(5) The World Wide Web Publishing service (if not already stopped by step 2.c.3 above.)
d. Restart the services stopped in 2.c. above.
f. If the w3proxy ISAPI filter did not initialize and there are other filters beings loaded on the Default Web Site, remove them (record each one and the filter's location on the server before removing) one at a time and repeat steps 2.c through 2.f. until only the w3proxy filter is being loaded.
g. Replace the filters removed earlier (if applicable) one at a time with updated versions and repeat steps 2.a. to 2.e. to test whether the updated versions work properly with the w3proxy ISAPI filter.
Reapply the NT 4.0 Service pack installed on the server after replacing files on the server as a precaution against having mis-matched versions on the server.
Article ID: 242211 - Last Review: June 19, 2014 - Revision: 3.0
Contact us for more help