none
Error-insufficient winsock resources available to complete socket connection initiation

    Question

  • Hello All ,

    When we left our client and server application running for 1-2 days we are getting following error-

    "insufficient winsock resources available to complete socket connection initiation". 

    If we run netstat -a command it just show that 6 sockets were consumed by our application. Both client and server are running on same machine. Only one client was communicating with this server. Both client and server were communicating with netTcpBinding. On server we have set the MaxConnection(and session) limit to 150. On client side we create the proxy using ChannelFactory. We preserve both channel and channel factory. When client exit we close both channel and factory. If any channel is faulted because of inactivity we  call abort and create new channel.

    Client and Server are not doing any resource intensive (network, processor or memory)  operation.

    I'll appreciate any help/pointer in this issue.


    Regards,
    Gurmit

    Monday, February 23, 2009 9:01 AM

All replies

  • Here is the stack trace-

    System.InsufficientMemoryException: Insufficient winsock resources available to complete socket connection initiation. ---> System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full 127.0.0.1:9005

    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)

    at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)

    at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)

    --- End of inner exception stack trace ---

    Server stack trace:

    at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)

    at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)

    at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)

    at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)

    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

    at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)

    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

    Exception rethrown at [0]:

    at System.ServiceModel.Security.IssuanceTokenProviderBase`1.DoNegotiation(TimeSpan timeout)

    at System.ServiceModel.Security.SspiNegotiationTokenProvider.OnOpen(TimeSpan timeout)

    at System.ServiceModel.Security.TlsnegoTokenProvider.OnOpen(TimeSpan timeout)

    at System.ServiceModel.Security.WrapperSecurityCommunicationObject.OnOpen(TimeSpan timeout)

    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

    at System.ServiceModel.Security.CommunicationObjectSecurityTokenProvider.Open(TimeSpan timeout)

    at System.ServiceModel.Security.SecurityUtils.OpenCommunicationObject(ICommunicationObject obj, TimeSpan timeout)

    at System.ServiceModel.Security.SecurityUtils.OpenTokenProviderIfRequired(SecurityTokenProvider tokenProvider, TimeSpan timeout)

    at System.ServiceModel.Security.SymmetricSecurityProtocol.OnOpen(TimeSpan timeout)

    at System.ServiceModel.Security.WrapperSecurityCommunicationObject.OnOpen(TimeSpan timeout)

    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

    at System.ServiceModel.Security.SecurityProtocol.Open(TimeSpan timeout)

    at System.ServiceModel.Channels.SecurityChannelFactory`1.ClientSecurityChannel`1.OnOpen(TimeSpan timeout)

    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

    at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.DoOperation(SecuritySessionOperation operation, EndpointAddress target, Uri via, SecurityToken currentToken, TimeSpan timeout)

    at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.GetTokenCore(TimeSpan timeout)

    at System.IdentityModel.Selectors.SecurityTokenProvider.GetToken(TimeSpan timeout)

    at System.ServiceModel.Security.SecuritySessionClientSettings`1.ClientSecuritySessionChannel.OnOpen(TimeSpan timeout)

    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

    at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)

    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

    at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)

    at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)

    at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)

    at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

    at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)

    at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)

    at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    Exception rethrown at [1]:

    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

    at Bioscrypt.NGVA.UnitService.IUnitService.GetAllUnitsByGroup(UnitGroup unitGroup)

    at Bioscrypt.NGVA.UnitServiceProxy.<>c__DisplayClass4.<GetAllUnitsByGroup>b__3(IUnitService unitService)

    at Bioscrypt.NGVA.ServiceProxy`1.Execute(ServiceDelegate arg)

    at Bioscrypt.NGVA.UnitServiceProxy.GetAllUnitsByGroup(UnitGroup unitGroup)

    at Bioscrypt.NGVA.NetworkStatusDialog.RetriveAllUnitsByGroup(UnitGroup unitGroup)

    at Bioscrypt.NGVA.NetworkStatusDialog.UnitGroupNode_Expanded(Object sender, RoutedEventArgs e)

    at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)

    at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)

    at System.Windows.UIElement.RaiseEventImpl(RoutedEventArgs args)

    at System.Windows.UIElement.RaiseEvent(RoutedEventArgs e)

    at System.Windows.Controls.TreeViewItem.OnExpanded(RoutedEventArgs e)

    at System.Windows.Controls.TreeViewItem.OnIsExpandedChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)

    at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)

    at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)

    at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)

    at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, OperationType operationType)

    at System.Windows.DependencyObject.SetValueCommon(DependencyProperty dp, Object value, PropertyMetadata metadata, Boolean coerceWithDeferredReference, OperationType operationType, Boolean isInternal)

    at System.Windows.DependencyObject.SetValue(DependencyProperty dp, Boolean value)

    at System.Windows.Controls.TreeViewItem.set_IsExpanded(Boolean value)

    • Proposed as answer by gadevasu Tuesday, May 19, 2009 9:18 PM
    • Unproposed as answer by Gurmit Teotia Wednesday, May 20, 2009 10:24 PM
    Monday, February 23, 2009 3:06 PM
  • Just trying to narrow down where resources are being leaked... is this error intermittent, or once you encounter it does it remain? Does recycling the client app clear it? Within the client app, does aborting the channel or closing the factory clear the error?

    You could also try System.Net tracing to get more details.

    Tuesday, February 24, 2009 9:58 PM
  • No, restarting the client application does not resolve the issue. And once this problem happened other applications also can not start network connection. We need to restart the PC.

    I'll look at System.NET tracing...

    Regards,
    Gurmit
    Wednesday, February 25, 2009 6:16 AM
  • Thanks, that sounds a bit concerning. If you're able to get trace info and/or a minimal repro, could you please open a Connect bug so we can ensure this is properly investigated?
    Wednesday, February 25, 2009 6:19 PM
  •  

    This problem got reproduced again - here is the output of Systm.net trace log-

    System.Net.Sockets Verbose: 0 : [3068] DNS::GetHostEntry(localhost)

    System.Net.Sockets Verbose: 0 : [3068] DNS::GetHostByName(localhost)

    System.Net.Sockets Verbose: 0 : [3068] Exiting DNS::GetHostByName() -> IPHostEntry#6444509

    System.Net.Sockets Verbose: 0 : [3068] Exiting DNS::GetHostEntry() -> IPHostEntry#6444509

    System.Net.Sockets Verbose: 0 : [3068] Socket#58000584::Socket(InterNetwork#2)

    System.Net.Sockets Verbose: 0 : [3068] Exiting Socket#58000584::Socket()

    System.Net.Sockets Verbose: 0 : [3068] Socket#58000584::Connect(1:9005#16786258)

    System.Net.Sockets Error: 0 : [3068] Exception in the Socket#58000584::Connect - An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full 127.0.0.1:9005

    System.Net.Sockets Verbose: 0 : [3068] Socket#58000584::Close()

    System.Net.Sockets Verbose: 0 : [3068] Socket#58000584::Dispose()

    System.Net.Sockets Verbose: 0 : [3068] Exiting Socket#58000584::Close()

    System.Net.Sockets Verbose: 0 : [0392] DNS::GetHostEntry(localhost)

    System.Net.Sockets Verbose: 0 : [0392] DNS::GetHostByName(localhost)

    System.Net.Sockets Verbose: 0 : [0392] Exiting DNS::GetHostByName() -> IPHostEntry#6444509

    System.Net.Sockets Verbose: 0 : [0392] Exiting DNS::GetHostEntry() -> IPHostEntry#6444509

    System.Net.Sockets Verbose: 0 : [0392] Socket#58000584::Socket(InterNetwork#2)

    System.Net.Sockets Verbose: 0 : [0392] Exiting Socket#58000584::Socket()

    System.Net.Sockets Verbose: 0 : [0392] Socket#58000584::Connect(1:9005#16786258)

    System.Net.Sockets Error: 0 : [0392] Exception in the Socket#58000584::Connect - An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full 127.0.0.1:9005

    System.Net.Sockets Verbose: 0 : [0392] Socket#58000584::Close()

    System.Net.Sockets Verbose: 0 : [0392] Socket#58000584::Dispose()

    System.Net.Sockets Verbose: 0 : [0392] Exiting Socket#58000584::Close()


    AND output of "netsh winsock show catalog"

    U:\>netsh winsock show catalog

    Winsock Catalog Provider Entry
    ------------------------------------------------------
    Entry Type:                         Base Service Provider
    Description:                        MSAFD Tcpip [TCP/IP]
    Provider ID:                        {E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
    Provider Path:                      %SystemRoot%\system32\mswsock.dll
    Catalog Entry ID:                   1001
    Version:                            2
    Address Family:                     2
    Max Address Length:                 16
    Min Address Length:                 16
    Socket Type:                        1
    Protocol:                           6
    Protocol Chain Length:              1

    Winsock Catalog Provider Entry
    ------------------------------------------------------
    Entry Type:                         Base Service Provider
    Description:                        MSAFD Tcpip [UDP/IP]
    Provider ID:                        {E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
    Provider Path:                      %SystemRoot%\system32\mswsock.dll
    Catalog Entry ID:                   1002
    Version:                            2
    Address Family:                     2
    Max Address Length:                 16
    Min Address Length:                 16
    Socket Type:                        2
    Protocol:                           17
    Protocol Chain Length:              1

    Winsock Catalog Provider Entry
    ------------------------------------------------------
    Entry Type:                         Base Service Provider
    Description:                        MSAFD Tcpip [RAW/IP]
    Provider ID:                        {E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
    Provider Path:                      %SystemRoot%\system32\mswsock.dll
    Catalog Entry ID:                   1003
    Version:                            2
    Address Family:                     2
    Max Address Length:                 16
    Min Address Length:                 16
    Socket Type:                        3
    Protocol:                           0
    Protocol Chain Length:              1

    Winsock Catalog Provider Entry
    ------------------------------------------------------
    Entry Type:                         Base Service Provider
    Description:                        MSAFD NetBIOS [\Device\NetBT_Tcpip_{1F2F1808
    -E900-47BC-8B6F-4B88202C94A8}] SEQPACKET 0
    Provider ID:                        {8D5F1830-C273-11CF-95C8-00805F48A192}
    Provider Path:                      %SystemRoot%\system32\mswsock.dll
    Catalog Entry ID:                   1004
    Version:                            2
    Address Family:                     17
    Max Address Length:                 20
    Min Address Length:                 20
    Socket Type:                        5
    Protocol:                           -2147483648
    Protocol Chain Length:              1

    Winsock Catalog Provider Entry
    ------------------------------------------------------
    Entry Type:                         Base Service Provider
    Description:                        MSAFD NetBIOS [\Device\NetBT_Tcpip_{1F2F1808
    -E900-47BC-8B6F-4B88202C94A8}] DATAGRAM 0
    Provider ID:                        {8D5F1830-C273-11CF-95C8-00805F48A192}
    Provider Path:                      %SystemRoot%\system32\mswsock.dll
    Catalog Entry ID:                   1005
    Version:                            2
    Address Family:                     17
    Max Address Length:                 20
    Min Address Length:                 20
    Socket Type:                        2
    Protocol:                           -2147483648
    Protocol Chain Length:              1

    Winsock Catalog Provider Entry
    ------------------------------------------------------
    Entry Type:                         Base Service Provider
    Description:                        MSAFD NetBIOS [\Device\NetBT_Tcpip_{C354CA6A
    -0D3D-4651-A9F6-2F36F1191AE1}] SEQPACKET 1
    Provider ID:                        {8D5F1830-C273-11CF-95C8-00805F48A192}
    Provider Path:                      %SystemRoot%\system32\mswsock.dll
    Catalog Entry ID:                   1006
    Version:                            2
    Address Family:                     17
    Max Address Length:                 20
    Min Address Length:                 20
    Socket Type:                        5
    Protocol:                           -1
    Protocol Chain Length:              1

    Winsock Catalog Provider Entry
    ------------------------------------------------------
    Entry Type:                         Base Service Provider
    Description:                        MSAFD NetBIOS [\Device\NetBT_Tcpip_{C354CA6A
    -0D3D-4651-A9F6-2F36F1191AE1}] DATAGRAM 1
    Provider ID:                        {8D5F1830-C273-11CF-95C8-00805F48A192}
    Provider Path:                      %SystemRoot%\system32\mswsock.dll
    Catalog Entry ID:                   1007
    Version:                            2
    Address Family:                     17
    Max Address Length:                 20
    Min Address Length:                 20
    Socket Type:                        2
    Protocol:                           -1
    Protocol Chain Length:              1

    Winsock Catalog Provider Entry
    ------------------------------------------------------
    Entry Type:                         Base Service Provider
    Description:                        MSAFD NetBIOS [\Device\NetBT_Tcpip_{623A221E
    -3DD7-4A96-BEDC-976834199F9C}] SEQPACKET 2
    Provider ID:                        {8D5F1830-C273-11CF-95C8-00805F48A192}
    Provider Path:                      %SystemRoot%\system32\mswsock.dll
    Catalog Entry ID:                   1008
    Version:                            2
    Address Family:                     17
    Max Address Length:                 20
    Min Address Length:                 20
    Socket Type:                        5
    Protocol:                           -2
    Protocol Chain Length:              1

    Winsock Catalog Provider Entry
    ------------------------------------------------------
    Entry Type:                         Base Service Provider
    Description:                        MSAFD NetBIOS [\Device\NetBT_Tcpip_{623A221E
    -3DD7-4A96-BEDC-976834199F9C}] DATAGRAM 2
    Provider ID:                        {8D5F1830-C273-11CF-95C8-00805F48A192}
    Provider Path:                      %SystemRoot%\system32\mswsock.dll
    Catalog Entry ID:                   1009
    Version:                            2
    Address Family:                     17
    Max Address Length:                 20
    Min Address Length:                 20
    Socket Type:                        2
    Protocol:                           -2
    Protocol Chain Length:              1

    Winsock Catalog Provider Entry
    ------------------------------------------------------
    Entry Type:                         Base Service Provider
    Description:                        RSVP UDP Service Provider
    Provider ID:                        {9D60A9E0-337A-11D0-BD88-0000C082E69A}
    Provider Path:                      %SystemRoot%\system32\rsvpsp.dll
    Catalog Entry ID:                   1010
    Version:                            6
    Address Family:                     2
    Max Address Length:                 16
    Min Address Length:                 16
    Socket Type:                        2
    Protocol:                           17
    Protocol Chain Length:              1

    Winsock Catalog Provider Entry
    ------------------------------------------------------
    Entry Type:                         Base Service Provider
    Description:                        RSVP TCP Service Provider
    Provider ID:                        {9D60A9E0-337A-11D0-BD88-0000C082E69A}
    Provider Path:                      %SystemRoot%\system32\rsvpsp.dll
    Catalog Entry ID:                   1011
    Version:                            6
    Address Family:                     2
    Max Address Length:                 16
    Min Address Length:                 16
    Socket Type:                        1
    Protocol:                           6
    Protocol Chain Length:              1

    Name Space Provider Entry
    ------------------------------------------------------
    Description:                        Tcpip
    Provider ID:                        {22059D40-7E9E-11CF-AE5A-00AA00A7112B}
    Name Space:                         12
    Active:                             1
    Version:                            0


    Name Space Provider Entry
    ------------------------------------------------------
    Description:                        NTDS
    Provider ID:                        {3B2637EE-E580-11CF-A555-00C04FD8D4AC}
    Name Space:                         32
    Active:                             1
    Version:                            0


    Name Space Provider Entry
    ------------------------------------------------------
    Description:                        Network Location Awareness (NLA) Namespace
    Provider ID:                        {6642243A-3BA8-4AA6-BAA5-2E0BD71FDD83}
    Name Space:                         15
    Active:                             1
    Version:                            0



     

    Apart from that restarting of client, server and net.tcp service (which we are using for port sharing) does not have any effect. We need to restart the machine to return it to normal (culprit could be some other application) state.

     

    When that problem- only outgoing connections are affected. Clients running on other healthy machines can still connect to server running on this troubled machine. But the client (or any other software- telnet) running on this machine can not initiate any connection request.

     

    I have still kept the machine in same state. Please help me in figuring out the culprit application.

     

     

    Regards,

         Gurmit
    Tuesday, March 17, 2009 2:15 PM
  • Try a netstat -n. I am not sure if -a will show you ports in TIME_WAIT-CLOSE_WAIT state.

    Have you tried increasing the ephemeral port range to see if this has a positive effect?

    Alex

    Alex
    Tuesday, March 17, 2009 6:34 PM
  • Try using the Throtlling behaviour or changing the max connections to "2147483647"

      <binding name="NetTeclBinding" maxReceivedMessageSize="2147483647" maxConnections="2147483647">
    or 

    if you use PerSession Instancing
    <behaviour name="NetTeclBindingBehaviour" >
    <servicethrottling maxConcurrentCalls="2147483647" maxConcurrentSessions="2147483647" />
    </behaviour>

    Hope this helps

    Vasu

    gv
    Tuesday, May 19, 2009 9:22 PM
  • Try using the Throtlling behaviour or changing the max connections to "2147483647"

      <binding name="NetTeclBinding" maxReceivedMessageSize="2147483647" maxConnections="2147483647">
    or 

    if you use PerSession Instancing
    <behaviour name="NetTeclBindingBehaviour" >
    <servicethrottling maxConcurrentCalls="2147483647" maxConcurrentSessions="2147483647" />
    </behaviour>

    Hope this helps

    Vasu

    gv
    Tuesday, May 19, 2009 9:23 PM
  • Hi Gurmit,

    I have a problem same error. I read your correspondence with Microsoft Connect (http://connect.microsoft.com/wcf/feedback/details/420151/insufficient-winsock-resources-available-to-complete-socket-connection-initiation#).

    Could you solve this problem? Is it an OS problem or another?


    Regards,
    Namık.
    Monday, February 01, 2010 12:27 PM
  • Hi Gurmit,

    I also have the same error!  We have an application that has been running for a long time without any problems, but got the 'Insufficient winsock resources available' exception while making a WCF call using netTCPBinding the other day.

    It appeared that other socket activity was affected too; we also got this error while trying to speak to the database on that server;

    IBatisNet.DataMapper.Exceptions.DataMapperException: Unable to open connection to "MySQL, MySQL provider 6.2.2.0". ---> MySql.Data.MySqlClient.MySqlException: Unable to connect to any of the specified MySQL hosts. ---> System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full

    We rebooted the server and the problem went away.  We have not been able to reproduce the problem.

    For me, the question is, did WCF cause the problem, or was it just having trouble like the other applications were that were using sockets on the server?

    (I'm guessing it was perhaps some generic network problems).

    Has there been any further light shed on this issue / was this found to be a bug in WCF ?

    The maxConnections in my application is also set to 10, but the load is quite low.

    Additional info;

    OS - Windows Server 2003, Standard Edition, SP2
    Computer - Quad Core AMD Opteron, Processor 2347HE, 1.90GHz, 3.25GB RAM
    OS Language - (probably US english or UK english)
    NET Framework- 3.5 SP1 + Hotfix for .Net Framework 3.5 SP1 (KB953595)

    Kind regards,

    Pete.

    Wednesday, December 22, 2010 5:04 PM
  • We have exactly same problem, but we can reproduce it each day after about 14-15 hours of server working normally.

    Our scenario is - client connects to WCF server each 2 seconds to get an update about stuff. For now, only one client is running.

    After 14 hours of normal operations we start getting InsufficientMemoryException with the message about Winsock resources lack. At this moment other network services (database, ADAM etc.) stop accepting connections as well. And, as discussed above, the only way to fix this is to restart the computer.

    Additional Info:

    OS - Windows Server 2003 R2 Enterprise Edition
    Computer - Intel Pentium Dual Core 2.4GHz, 4GB RAM
    NET Framework .NET 3.5SP1, .NET 4.0

    Also, we cannot reproduce this on Windows Server 2008 R2 - everything works fine weeks without issues on less powerful computers.

    Thanks,

    Denis

    Friday, February 04, 2011 8:41 AM
  • Hi All,

    I have not investigated this issue further, after it was concluded an OS issue. This issue was getting reproduced only at one machine in testing lab. We later noticed that this machine had fresh installation of XP; no updates were installed on it. Testing lab machines were isolated from internet environment. This issue was not getting reproduced on any of work machines; all of them were having latest updates installed. Because this issue was dragging and neither of customer (and no one else in company either ) reported this issue; we put it on back burner. However it seems lots of people are affected by this issue. I'm even getting ping on my linkedln network to know about outcome of this issue. I think you should take this issue further with Microsoft at support.microsoft.com (as suggest at connect..).

     

    As concluded at connect.microsoft.com it is an OS issue and require attention from Microsoft. Here are some of the points I think may help you in your investigation-

    -It was an OS issue not an WCF. Even if WCF was leaking resources; they should get free when we close our application but that was not happening in our case. We need to restart the machine.

    -Our application was in ideal mode, NOT doing any network activity at all. After the gap of 2-3 days when test person used to perform some action in our application, she used to get this error. I think we're bit unlucky here; some deep down bug was popping out his head from our application. Test person used to perform some activity from application and leave it ideal for 2-3 days and after 2-3 days it used to pop up. For those 2-3 days our application was not doing any activity.

    -As mentioned above as well, we noticed that svchost process was taking 100% of CPU (it was the reason to conclude it as OS issue) May be you should also look at your task manager for any such activity.

    -I did some investigation later to resolve LSP issues with net.tcp service (now I know that "netsh winsock show catalog" mean :) and confidently says no third party code was installed in network layer.

     

    I think you should try to have all Windows update on your machine and if that does not resolve issue you should escalate this issue to Microsoft. 

     

    Regards,

    Gurmit

     

     

     

     

    Friday, February 04, 2011 11:55 AM
  • We have the same exact problem.   If we change from net.tcp to wshttp binding, problem goes away.  We have tried playing around with all kinds of net.tcp throttling settings to no avail.
    Thanks, Brian
    Monday, November 14, 2011 9:47 PM
  • We experience this problem intermittently on our servers (when they are acting as the client).

    We are using .netTcp binding as well (we need netTcp because once the client established the connection, all communication is initiated by the server and pushed to the client on the callback channel).

    This is the second day in a row in which our client machine has received this error.

    It sounds like this is an OS issue, so I am posting here hoping that MS sees that there is an issue that needs to be addressed.

    Tuesday, November 15, 2011 2:15 PM