1-800-691-1991 | 9am - 8pm ET

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


After installing Windows April update KB4015553 Veeam jobs and services fail at different operations with:
"An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full"


This particular update (and all consequent rollups that include it) causes the system to run out of free RPC ports when there are failed iSCSI connections.


Repairing or removing unsuccessful iSCSI connections, followed by the server reboot, was found to fix the issue. Additionally, remove any unused targets from the ‘Favorite Targets’ tab that are associated with these connections as they may be reconnected after reboot.

This issue has been addressed by Microsoft. Apply the appropriate update below to resolve the issue

For 2016: 
For 2012 R2:


The update that resolved the above Buffer Space iSCSI issue (KB4025335) has caused another iSCSI issue that only affects Backup from Storage Snapshots using an iSCSI connection.
After installing Windows Update KB4025335, KB4034681, KB4025333, or KB4025336, Veeam jobs utilizing Backup from Storage Snapshots using an iSCSI connection fail with the following errors:
“Error: Cannot retrieve physical extents for connecting iSCSI target IQN on proxy IQN”
In the logs, it can be seen with this error:
Task Log:

[25.07.2017 09:44:54] <61> Error Failed to find physical drive for LUN with lun Id 'WwnOrIqn: '', LunId: '10', 
[25.07.2017 09:44:54] <61> Error Unable to retrieve devices for iSCSI session. number of retry attempts: '20'. Interval: '100'. (Veeam.Backup.Common.CCppComponentException)
[25.07.2017 09:44:54] <61> Error in c++: void __thiscall disklib::vmfs_san::iscsi_api::iscsi_discovery::GetDevicesForSessionWithRetry(struct _ISCSI_UNIQUE_SESSION_ID &,class std::vector<struct ISCSI_DEVICE_ON_SESSIONW,class std::allocator<struct ISCSI_DEVICE_ON_SESSIONW> > &,int,int) failed.
[25.07.2017 09:44:54] <61> Error in c++: void __thiscall disklib::vmfs_san::iscsi_api::iscsi_discovery::LoginTarget(const class std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> > &,class std::vector<struct disklib::vmfs_san::iscsi_api::IscsiDriveInfo,class std::allocator<struct disklib::vmfs_san::iscsi_api::IscsiDriveInfo> > &) failed.

Proxy Resources Log:

[04.08.2017 13:50:55] < 4016> cli| VMFSSAN.ConnectISCSITarget
[04.08.2017 13:50:55] < 4016> cli| (EString) TargetName =
[04.08.2017 13:50:55] < 4016> cli| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[04.08.2017 13:50:55] < 4016> dsk| Retrieving devices for target ''.
[04.08.2017 13:50:55] < 4016> dsk| WARN|The data area passed to a system call is too small.

The above issue is resolved by installing Windows Update KB4075212, which can be found here:

More information

If after performing the steps outlined above the issue still occurs, a support case with Microsoft may be needed.
Veeam Backup & Replication
Last Modified:
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.


error icon

Oops! Something went wrong.

Please go back try again later.