No buffer space available errors appear in Windows Event Log
search cancel

No buffer space available errors appear in Windows Event Log

book

Article ID: 315279

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Windows Event log reports these errors:

  • WSAENOBUFS 10055 No buffer space available
  • An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full


Environment

VMware ESX Server 3.0.x

Resolution

WSAENOBUFS occurs when the system does not have enough memory or other system resources to open new TCP/IP socket, or to handle socket data. The issue occurs when the total count of opened sockets reaches the max supported by the Operating System.

To see the total number of ports opened:
  1. Log in to the Guest Operating System with Administrator privileges.
  2. Click Start > Run, type cmd, and click OK. The Command Prompt window opens.
  3. Run the netstat -ab command in the command prompt.
  4. Press Enter.
  5. Check the number of ports/sockets opened.

    Note: The maximum allowed is 2000.
Note:To check the total number of established connections, run this command:
 
netstat -nao | find /i "estab" /c

Additional Information

For translated versions of this article, see:

Additional Information

"An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full" error when ESXi hosts disconnect and reconnect in vCenter Server