The information in this article applies to:
SYMPTOMSWhen you restart a computer that is running Microsoft Proxy Server 2.0, the Web Proxy service may not start. When this occurs, Event Viewer lists the following event: The following data is displayed in the Data box in Words view: This data translates to Windows NT error code 59 ("An unexpected network error occurred"). CAUSESeveral different configuration issues can cause this event to be logged. If the Data box contains "0x0000003b" as described in the "Symptoms" section, one known cause is that a service that is listening on port 1080 is running. Because a service is already bound to port 1080, the Socks Proxy service that listens on port 1080 by default does not bind to the socket. The result is that the Web Proxy also does not initialize, causing event ID 127 to be logged. RESOLUTIONTo resolve this issue, disable the Socks Proxy service by following the steps in the following article in the Microsoft Knowledge Base: Q173961 How to Disable the Proxy Socks Service by Modifying the RegistryAfter you disable the Socks Proxy service and restart the computer, verify that the Web Proxy service is started successfully. If the Web Proxy service starts, type netstat -an at a command prompt to determine if something is listening on port 1080. If you see that port 1080 is in use, and you need to use the Socks Proxy service in your environment, find out which process or service is listening on the port and disable it, or change its listening port. If you do not need the Socks Proxy service, leave it disabled. REFERENCESFor additional information about similar issues, click the article numbers below to view the articles in the Microsoft Knowledge Base: Q244223 Troubleshooting and Resolving Web Proxy Event ID 127 Q220978 Err Msg: Web Proxy Service Failed to Start. Please Check the Server Event Log for Further Details Additional query words:
Keywords : kbenv kberrmsg |
|
Last Reviewed: January 6, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |