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

By | July 22, 2017

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.

 

2 thoughts on “Backup Exec – Insufficient winsock resources available to complete socket connection initiation

  1. Maqbool

    Thanks for the article , I am facing the exact issue . After disconnecting and restarting the server , any tasks to be done , Will it reconnect to the storage or should we connect it .

    Thanks
    Maq

    Reply
  2. virtualg Post author

    Hi Maq,

    Only remove the initiators that are “reconnecting” If you have ones that are connected then you will need to keep them otherwise you could lose access to active storage.

    After removing “reconnecting” initiators, reboot and the re should be no further tasks to complete.

    Good luck!
    Graham

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *