Err Msg: Web Proxy Service Failed to Start. Please Check the Server Event Log for Further Details
ID: Q220978
|
The information in this article applies to:
-
Microsoft Proxy Server version 2.0
-
Microsoft Internet Information Server versions 3.0, 4.0
IMPORTANT: This article contains information about editing the registry.
Before you edit the registry, make sure you understand how to restore it if
a problem occurs. For information about how to do this, view the "Restoring
the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help
topic in Regedt32.exe.
SYMPTOMS
When you attempt to start the Web Proxy Service in the Internet Services
Manager (IIS 3.0) or in the Microsoft Management Console (IIS 4.0), the
following error messages occur:
The Web Proxy Service failed to start. Please check the server event log
for further details.
The WWW service is running. You must stop the WWW service before starting
the Web Proxy Service.
CAUSE
This is caused by the Proxy Server 2.0 filter DLL (W3proxy.dll) either
being corrupt, deleted, missing from the proper registry key location (for
IIS 3.0), or not correctly registered as an ISAPI filter (for IIS 4.0).
RESOLUTIONWARNING: Using Registry Editor incorrectly can cause serious problems that
may require you to reinstall your operating system. Microsoft cannot
guarantee that problems resulting from the incorrect use of Registry Editor
can be solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing Keys and
Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete
Information in the Registry" and "Edit Registry Data" Help topics in
Regedt32.exe. Note that you should back up the registry before you edit it.
If you are running Windows NT, you should also update your Emergency
Repair Disk (ERD).
The W3proxy.dll should reside in the following physical path on the
server:
<local drive>\InetPub\scripts\proxy\
- If the file is missing, verify that Proxy Server 2.0 has been
installed on the server. If not, run the Microsoft Proxy Server 2.0
installation. (NOTE: If installing Microsoft Proxy Server 2.0 on Small
Business Server 4.0 or 4.0a, be sure to follow the white paper addressing this installation.)
- If Proxy 2.0 appears to be installed, reinstall it because
the installation may not have completed successfully, or other key files
other than W3proxy.dll may be missing.
- If the file exists in the proper directory, check the version
information on the file. The file that is shipped with Microsoft Proxy
Server 2.0 has the following file version information:
File: W3proxy.dll
Date: 09/15/97
Time: 01:00a
Size: 187,152 bytes
If the Microsoft Proxy 2.0 roll-up hotfix has been applied, the version
information will show the following:
File: W3proxy.dll
Date: 07/09/98
Time: 03:27a
Size: 188,176 bytes
If Microsoft Proxy 2.0 is the version included with either BackOffice
Server 4.5 or BackOffice Small Business Server 4.5, the version
information will show the following:
File: W3proxy.dll
Date: 10/01/98
Time: 06:05a
Size: 188,176 bytes
If the file version does not match either of these, reinstall Microsoft
Proxy Server 2.0.
- If the file version does match, check the following:
- In Internet Information Server 3.0, verify that the following
registry entry exists:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\Filt
er DLLs
String Value:
<local drive>\WINNT\System32\inetsrv\sspifilt.dll,<local
drive>\InetPub\scripts\proxy\w3proxy.dll
If these entries are missing, add them in as a string value with the shown
values, stop and restart the WWW Service, and then try to start the Web
Proxy Service. If this does not work, other necessary files may be
missing, which will require a reinstall of Microsoft Proxy Server 2.0.
NOTE: IIS 3.0 does not provide a place in the Internet Services
Manager to allow the editing of ISAPI filters. This is done in the
registry.
- In Internet Information Server 4.0, open the Microsoft Management
Console (MMC) and open the properties for the Default Web Site. In the
Properties Window, click the ISAPI Filters tab. If there is not a
listing for W3proxy in the installed filters box, it will need to be
manually added. First, verify that the W3proxy.dll file exists in the
default directory shown at the beginning of the Resolution section. If
this file exists, then choose the Add... button, and install the
filter.
NOTE: Change the <local path> to the drive where the
W3proxy.dll file resides.
After you install the W3proxy filter, stop and restart the Default Web
Site, and then start the Web Proxy Service.
Additional query words:
smallbiz
Keywords :
Version : winnt:2.0,3.0,4.0
Platform : winnt
Issue type :
|