Lost Connection WSAEWOULDBLOCK and WSAEALREADY errors

[Patricia Smith]

Hello All,

I need help from all the great minds of the Clovertech Community.  We at Owensboro Medical are having a thread lose connection at random intervals.  The connection is between our engine (Windows 2000 server SP 3) and our Dietary system Vision (Windows 2003 server SP 2).  Then Connection is over a TCP/IP VPN line. I’ve seen a couple of posts with connection problems over VPN’s but no solutions.  Our connection was working fine until Vision upgraded 2003 from Service Pack 1 to Service Pack 2. I can keep the interface up but the port shuts down for no apparent reason. I can’t tell if it’s a timeout issue or not. These messages are from the process log. I noticed the WSAEWOULDBLOCK and WSAEALREADY errors in the log.

[pdl :PDL :DBUG/2:     to_carex] PDL changed states: old 7, new 4

[pdl :PDL :DBUG/0:     to_carex] Calling Tcl procedure: hci_pd.initialize

[pdl :PDL :DBUG/0:     to_carex] with args: {}

[pdl :PDL :DBUG/0:     to_carex] Tcl procedure hci_pd.initialize returns ”

[pdl :PDL :INFO/0:     to_carex] connected to 10.100.6.44 on port 22609

[pdl :PDL :DBUG/0:     to_carex] tcp-client: attempting connect to: 10.100.6.44:22609

[pdl :PDL :INFO/0:     to_carex] tcp-client: connect error (WSAEWOULDBLOCK)

[pdl :PDL :DBUG/1:     to_carex] PDL setting timeout in 0.10 seconds

[diag:leak:DBUG/0:     to_carex] diag ev alloc 0x00AA16D0

[diag:leak:DBUG/0:     to_carex] diag dqe alloc 0x00A7A560

[pti :even:DBUG/0:     to_carex] Registering TIMER () event 0x00AA16D0 for tid 4

[pti :even:DBUG/0:     to_carex] Registering TIMER event for tid 4

[pti :even:DBUG/1:     to_carex] Closed WSAEvent 1764 on socket 1460

[msg :Msg :DBUG/0:     to_carex] [0.0.524293455] msgFree 0x00A26478

[pdl :clse:DBUG/1:     to_carex] PDL did shutdown: code = 1000

[pdl :open:INFO/1:     to_carex] Scheduling driver reopen try in 5.0 secs

[pd  :pdtd:INFO/1:     to_carex] Set driver status to PD_STATUS_OPENING

[pti :even:DBUG/0:     to_carex] Processing TIMER () event 0x0C194478

[pti :even:DBUG/1:     to_carex] Calling cb 0x41fd61

[pdl :PDL :DBUG/0:     to_carex] timeout continues: 0045A9C4

[pdl :PDL :DBUG/0:     to_carex] tcp-client: attempting connect to: XX.XXX.X.X:PPPP

[pdl :PDL :INFO/0:     to_carex] tcp-client: connect error (WSAEALREADY)

[pdl :PDL :DBUG/1:     to_carex] PDL setting timeout in 0.10 seconds

[diag:leak:DBUG/0:     to_carex] diag ev alloc 0x00A8C648

[diag:leak:DBUG/0:     to_carex] diag dqe alloc 0x0C192690

My question is if anyone has seen this before?  Any suggestions would be helpful.  I strongly believe this is a Windows issue, I just don’t know how to resolve it. I had to borrow my coworker’s username, sorry for any confusion

Thanks again,

John Calhoun

270-852-8562

jcalhoun@omhs.org

Topic

[Stephan Head]

Have you checked Microsoft’s website for what was included in SP2?  There are quite a few patches included that address security.  You may be getting “hit” with one of those.

[Charlie Bursell]

WSAEALREADY  – Error #10037

Operation already in progress.

An operation was attempted on a nonblocking socket with an operation already in progress

[Patricia Smith]

After months of troubleshooting we finally found the problem…it was on the third party’s side.  We put sniffers on both sides and found that our Engine Windows Operating systems was trying to send on a closed port on their Operating System…Their application failed to send a “Change Port” message…They made the change on their end and things have been working alot better.  Thanks for everyone’s help.

[Author]

Replies