Backup Exec – Insufficient winsock resources available to complete socket connection initiation

A few months back I encountered this issue which was stopping the backup exec beremote.exe process which is required to backup Virtual Machines.

Insufficient winsock resources available to complete socket connection initiation

The cause

In my case it was a recent Windows Update that caused hundreds of false sockets to be opened within Windows Server. This was happening because the update was conflicting with the iSCSI initiator service.

The solution 

Check your iSCSI initiators and if you have any that are “reconnecting”, they will need to be removed. Delete them and reboot the server.

Note

This has happened on two Windows Server 2012 R2 instances running Backup Exec 15 and 16. On both cases, this solution resolved the issue.

Graham

Graham is a seasoned expert in VMware and Microsoft solutions, bringing deep expertise to his role at Dell Technologies. As a Senior Principal Engineer he focuses on cutting-edge virtualization and storage projects. A VMware Certified Implementation Expert, 9x VMware vExpert, and VMware User Moderator on the official VMTN forums, Graham is a trusted community resource. Connect with him on Twitter for insights! @VirtualG.uk

See Full Bio

VMware Technologies Dell Technologies