Unable To Bind TCP/IP Socket – WSAEACCESS

This topic has 4 replies, 2 voices, and was last updated 13 years, 1 month ago by Ron Leonard.

Creator

Topic
June 15, 2012 at 1:20 pm #53148
Ron Leonard
Participant
Does anyone know what can cause ‘Unable To Bind TCP/IP Socket – WSAEACCESS’ on a receiving thread?

We encountered this in our Production Site on a thread that had been processing normally in the middle of the day. This came out of nowhere. A netstat did not show any port number conflicts.

We were not able to resolve it untill we stopped all processes on our Test Site, then the thread on the Production Site connected. The Netconfig on our Test Site does not show the port number used.

We have since been running with Test Site and Production Site up and everything is back to normal. We did not make any changes before the incident or after.

Any ideas what may have caused this?

Thanks,

Ron
Creator

Topic

Viewing 3 reply threads

Author

Replies
- June 15, 2012 at 2:01 pm #76722
  Charlie Bursell
  Participant
  It simply means “Permision Denied”
  
  Probably because it was already bound to another socket at the time. The socket may have been in a FIN state at that time
- June 15, 2012 at 5:42 pm #76723
  Ron Leonard
  Participant
  What is a ‘FIN’ state?
- June 15, 2012 at 5:57 pm #76724
  Charlie Bursell
  Participant
  FIN: No more data from sender
  
  IAW RFC 793
  
  http://www.faqs.org/rfcs/rfc793.html
  
  Anyone that deals with TCP/IP, and I think that is everyone, should read it
- June 15, 2012 at 9:04 pm #76725
  Ron Leonard
  Participant
  Thanks..
Author

Replies

Viewing 3 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.