WebSphere HTTP Server - Re: [warn] (OS 64)The specified network name is no longer available. : winnt_accept:

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere HTTP Server > January 2005 > Re: [warn] (OS 64)The specified network name is no longer available. : winnt_accept:





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: [warn] (OS 64)The specified network name is no longer available. : winnt_accept:
Sunit Patke

2005-01-27, 5:54 pm

After you add the directive and try to restart the server what do you see in
error_log?

Sunit

"Jorge Jarpa" <jjarpa@bcontinental.com> wrote in message
news:ct8s41$58oo$1@news.boulder.ibm.com...
>I have IBM HTTP Server 2.0.47 running on Windows 2000 Server.
>
> I am getting this errors in the HTTP Server's log:
> [warn] (OS 64)The specified network name is no longer available. :
> winnt_accept: Asynchronous AcceptEx failed.
> [warn] (OS 121)The semaphore timeout period has expired. : winnt_accept:
> Asynchronous AcceptEx failed.
>
> IBM Says on
> http://www-1.ibm.com/support/docvie...0&dc=DA420&dc=D

A500&dc=DA410&dc=DB540&dc=DB510& q1=winnt_accept%3a+Asynchronous+AcceptEx
+failed&uid=swg1PQ84990&loc=en_US&cs=utf-8&lang=en
>
> That is a Bug detected:
> PQ84990: Periodic performance slowdown problem with AcceptEx.
>
> And it is fixed adding the directive " Win32DisableAcceptEx " in the
> httpd.conf file
>
> But When I do that, IBM HTTP Server Service donīt start !
>
> What I am doing wrong ?
>
>
> Regards,
> Jorge Jarpa
>



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com