Hey guys... haven't posted here in awhile!
A client of ours is currently having a strange issue with our software. There is a Windows service which runs and accepts connections from an administration front end built with WPF. Occasionally, the user will get the following error:
Exception Type: System.InsufficientMemoryException
Message: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full
Stack Trace:
at System.Net.Sockets.Socket.DoBeginConnect(EndPoint endPointSnapshot, SocketAddress socketAddress, LazyAsyncResult asyncResult)
at System.Net.Sockets.Socket.BeginConnect(EndPoint remoteEP, AsyncCallback callback, Object state)
|
This is baffling to me and I can't figure out what's causing it. I had the user run 'netstat -ab' and the results seemed perfectly normal. No gaggle of sockets opened on their machine and the only sockets that were open were the ones between the service and front end application and an accessory socket for listening for remote client connections. The receive/transmit buffers on the socket are initially set to 25 KB and then later after the authentication process has completed, are set to 7.5 KB so I really doubt it's a problem with taking up too much network buffer space. I also checked the users boot.ini file and didn't find the suggested /3GB fix, either. I've been banging my head on this one all day and since I'm a solo programmer, I have NO ONE more experienced to ask :( What do you guys think could be possible causes for this? Anything we can try that might alleviate the problem would be very helpful!
The user is running Windows XP Professional 32-bit w/SP3. If you guys need ANY more information, let me know and I'll do my best to get it.
Brandon
EDIT: Well, after a bit of diligent research and alot of help on the customers part (thank goodness for customers who actually have some Windows administrative knowledge) I think we have narrowed the issue to actually being a permissions problem. When the user runs the Windows application as administrator, it works flawlessly. But when they run it as a user with limited permissions, it coughs, hacks, and dies. Odd that it would cause this problem, but I suppose if the user account they are logged on as has very limited network permissions it could be restricting resources to the Windows application and causing the problem.