You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by st...@locus.apache.org on 2000/07/29 21:43:36 UTC
cvs commit: httpd-docs-2.0/htdocs/manual/misc FAQ-D.html
stoddard 00/07/29 12:43:36
Modified: htdocs/manual/misc FAQ-D.html
Log:
Copy some 1.3 doc to 2.0
Revision Changes Path
1.6 +38 -2 httpd-docs-2.0/htdocs/manual/misc/FAQ-D.html
Index: FAQ-D.html
===================================================================
RCS file: /home/cvs/httpd-docs-2.0/htdocs/manual/misc/FAQ-D.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- FAQ-D.html 1999/12/10 14:56:26 1.5
+++ FAQ-D.html 2000/07/29 19:43:35 1.6
@@ -31,7 +31,7 @@
<!--#include virtual="header.html" -->
<H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
<P>
- $Revision: 1.5 $ ($Date: 1999/12/10 14:56:26 $)
+ $Revision: 1.6 $ ($Date: 2000/07/29 19:43:35 $)
</P>
<P>
The latest version of this FAQ is always available from the main
@@ -105,6 +105,12 @@
<LI><A HREF="#ws2_32dll">When I try to start Apache for Windows, I get a message
like "<samp>Unable To Locate WS2_32.DLL...</samp>". What should I do?</A>
</LI>
+ <LI><A HREF="#WSADuplicateSocket">Apache for Windows does not start.
+ Error log contains this message "<samp>[crit] (10045) The attempted
+ operation is not supported for the type of object referenced: Parent:
+ WSADuplicateSocket failed for socket ###</samp>". What does this
+ mean?</a>
+ </LI>
</OL>
</LI>
<!--#endif -->
@@ -384,7 +390,37 @@
</p>
<hr>
</LI>
-
+ <LI><A name="WSADuplicateSocket">
+ <b>Apache for Windows does not start. Error log contains this message:
+ "<samp>[crit] (10045) The attempted operation is not supported for
+ the type of object referenced: Parent: WSADuplicateSocket failed for
+ socket ###</samp>". What does this mean?</b></A>
+ <p>
+ We have seen this problem when Apache is run on systems along with
+ Virtual Private Networking clients like Aventail Connect. Aventail Connect
+ is a Layered Service Provider (LSP) that inserts itself, as a "shim,"
+ between the Winsock 2 API and Window's native Winsock 2 implementation.
+ The Aventail Connect shim does not implement WSADuplicateSocket, which is
+ the cause of the failure.
+ </p>
+ <p>
+ The shim is not unloaded when Aventail Connect is shut down. Once
+ observed, the problem persists until the shim is either explicitly
+ unloaded or the machine is rebooted. Instructions for temporarily
+ removing the Aventail Connect V3.x shim can be found here:
+ "<a href="http://support.aventail.com/akb/article00386.html"
+ >How to Remove Aventail Connect v3.x from the LSP Order for Testing
+ Purposes</a>."
+ </p>
+ <p>
+ Another potential solution (not tested) is to add <code>apache.exe</code>
+ to the Aventail "Connect Exclusion List". See this link for details:
+ "<a href="http://support.aventail.com/akb/article00586.html"
+ >How to Add an Application to Aventail Connect's Application Exclusion
+ List</a>."
+ </p>
+ <hr>
+ </LI>
</OL>
<!--#endif -->
<!--#if expr="$STANDALONE" -->