how to deal with STATUS_PIPE_BUSY ?

Ben Johnson ben at blarg.net
Wed Jul 17 11:19:02 GMT 2002


On Tue, Jul 16, 2002 at 07:27:44PM -0700, Tim Potter wrote:
> On Tue, Jul 16, 2002 at 06:59:31PM -0700, Ben Johnson wrote:
> 
> > The problem comes when, after I succeed in getting a very large list of
> > group names, I ask for another.  The second request fails and I get an
> > NT error code of STATUS_PIPE_BUSY.  Does anyone know what that means?
> 
> The latest school of thought with this is that it means "try again
> later".  There are a number of KB articles on microsoft.com which make
> reference to the number of threads waiting on the named pipe and if
> these are all busy then you get STATUS_PIPE_BUSY.


This is part of a packet dump that ends with the STATUS_PIPE_BUSY.  If I
remove the user from just a few groups then I never get the
STATUS_PIPE_BUSY message and the second request goes through.  But
nothing else (that I see so far) about the dump overall changes.

Do you think I just need to wait a little while then resend the request?
Is it just that NT needs some time to rearrange its buffers or something?
That doesn't make much sense to me, but I can't figure out what else it
would be.

Thanks,

- Ben

        seconds     src        dst        proto    packet
     13 0.358420    client     server     SMB      NT Create AndX Request, Path: \samr
     14 0.359534    server     client     SMB      NT Create AndX Response, FID: 0x0800
     15 0.361407    client     server     DCERPC   Bind: call_id: 6815847 UUID 12345778-1234-abcd-ef00-0123456789ac ver 1.0
     16 0.362460    server     client     DCERPC   Bind_ack: call_id: 6815847 accept max_xmit: 5680 max_recv: 5680
     17 0.365035    client     server     SAMR     Connect2 request
     18 0.366175    server     client     SAMR     Connect2 reply
     19 0.369150    client     server     SMB      NT Create AndX Request, Path: \lsarpc
     20 0.370575    server     client     SMB      NT Create AndX Response, FID: 0x0801
     21 0.372418    client     server     DCERPC   Bind: call_id: 0 UUID 12345778-1234-abcd-ef00-0123456789ab ver 0.0
     22 0.373377    server     client     DCERPC   Bind_ack: call_id: 0 accept max_xmit: 5680 max_recv: 5680
     23 0.375864    client     server     LSA      OpenPolicy2 request
     24 0.377360    server     client     LSA      OpenPolicy2 reply
     25 0.380364    client     server     LSA      QueryInfoPolicy request
     26 0.381361    server     client     LSA      QueryInfoPolicy reply
     27 0.383770    client     server     LSA      Close request
     28 0.384693    server     client     LSA      Close reply
     29 0.387135    client     server     SMB      Close Request, FID: 0x0801
     30 0.387952    server     client     SMB      Close Response
     31 0.389790    client     server     SAMR     OpenDomain request
     32 0.390933    server     client     SAMR     OpenDomain reply
     33 0.393971    client     server     SAMR     OpenDomain request
     34 0.395081    server     client     SAMR     OpenDomain reply
     35 0.398214    client     server     SAMR     LookupNames request
     36 0.399614    server     client     SAMR     LookupNames reply
     37 0.402720    client     server     SAMR     OpenUser request, rid 0x3f0
     38 0.404168    server     client     SAMR     OpenUser reply
     39 0.407325    client     server     SAMR     GetGroups request
     40 0.408618    server     client     SAMR     GetGroups reply
     41 0.426124    client     server     TCP      1024 > 139 [ACK] Seq=75777168 Ack=268235 Win=16060 Len=0
     42 0.438507    client     server     SAMR     GetAliasMem request[Short Frame]
     43 0.604191    server     client     TCP      139 > 1024 [ACK] Seq=268235 Ack=75778628 Win=8760 Len=0
     44 0.604624    client     server     NBSS     NBSS Continuation Message
     45 0.605986    server     client     SAMR     GetAliasMem reply
     46 0.609773    client     server     SAMR     LookupRIDs request
     47 0.620714    server     client     SAMR     LookupRIDs reply[Unreassembled Packet]
     48 0.621941    server     client     NBSS     NBSS Continuation Message
     49 0.623286    server     client     NBSS     NBSS Continuation Message
     50 0.626133    client     server     TCP      1024 > 139 [ACK] Seq=75779000 Ack=272799 Win=16060 Len=0
     51 0.627676    server     client     SMB      Transaction Response[transact continuation]
     52 0.646128    client     server     TCP      1024 > 139 [ACK] Seq=75779000 Ack=274235 Win=16060 Len=0
     53 0.673459    client     server     SAMR     GetAliasMem request[Short Frame]
     54 0.804479    server     client     TCP      139 > 1024 [ACK] Seq=274235 Ack=75780460 Win=8760 Len=0
     55 0.804960    client     server     NBSS     NBSS Continuation Message
     56 0.805339    server     client     SMB      Transaction Response, Error: STATUS_PIPE_BUSY





More information about the samba-technical mailing list