RE: [us...@httpd] What are OS64 and OS10054 errors typically caused by (Win32)

2010-10-15 Thread Steve Hay
Eric Covener wrote on 2010-10-15: > On Fri, Oct 15, 2010 at 7:59 AM, Steve Hay wrote: >>     (OS 64)The specified network name is no longer >> available.  : winnt_accept: Asynchronous AcceptEx failed. > > Try Win32DisableAcceptEX We have tried that already, and EnableMMAP off Enable

Re: [us...@httpd] What are OS64 and OS10054 errors typically caused by (Win32)

2010-10-15 Thread Eric Covener
On Fri, Oct 15, 2010 at 7:59 AM, Steve Hay wrote: >     (OS 64)The specified network name is no longer available.  : > winnt_accept: Asynchronous AcceptEx failed. Try Win32DisableAcceptEX > >     (OS 10054)An existing connection was forcibly closed by the > remote host. 

[us...@httpd] What are OS64 and OS10054 errors typically caused by (Win32)

2010-10-15 Thread Steve Hay
I have a customer running Apache 2.2.14 / mod_perl 2.0.4 / Perl 5.10.1 on Windows Server 2003 R2 SP2 (in a VMware setup). Their error.log (with Loglevel set to debug) has many of the following errors in it: (OS 64)The specified network name is no longer available. : winnt_a