Saturday, January 19, 2013 12:18 AM
I am running SQL Server 2008 on a Windows 2008 R2 64 Bit SP1 server. The server has 256GB of RAM.
About every 10-15 days I get the following error message, and at the same time SSIS packages are unable to import files from a samba share.
"An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full"
around the same time i also get the following error
The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
Restarting server resolves the problem.
The registry keys TcpTimedWaitDelay = 30 and MaxUserPort = 59999 have been added. However the TcpTimedWaitDelay = 30 does not seem to take affect since, after running netstat -aonb every 35 seconds, the same ports are stuck in a TIME_WAIT state.
Can someone please provide any insight as to what is going on and what can be done to resolve the problem?
Saturday, January 19, 2013 2:54 PM
do you have min/max memory settings configured on your SQL server to allow sufficient memory for O/S? (1-2GB)
Monday, January 21, 2013 8:54 AMModerator
Thanks for posting your issue in the forum. Regarding the current issue, I suggest we could refer to the following similar thread and article to see if it could help.
Windows 2008 R2 64Bit system lacked sufficient buffer space
Understanding the error “An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.”
TechNet Community Support
- Marked As Answer by Andy QiMicrosoft Contingent Staff, Moderator Friday, February 01, 2013 8:55 AM
Tuesday, January 22, 2013 7:29 PMYes, 128 GB out of 256 GB is available for the OS.
Tuesday, January 22, 2013 7:33 PM
Thanks for your response.
I have tried the steps of the first link by adding registry keys for TcpTimedWaitDelay = 30 and MaxUserPort = 59999, but they don't seem to take effect. The server has been restarted )(several times to mitigate the error, since that's that only way I currently know how) since adding the new registry keys.
only applies to Windows Server 2003, Windows XP, and earlier versions. My SQL instance is running on Windows 2008 R2.
Wednesday, January 23, 2013 3:39 AM
In your netstat -anob, the PID is related to SQL ?
If yes, did the SQL is patched ?
- Marked As Answer by Andy QiMicrosoft Contingent Staff, Moderator Friday, February 01, 2013 8:56 AM