25 Feb 2013 11:56 AM It used to be that the slightest drop in network connection between SL and the SQL server would cause a succession of SQL errors (10054, 10005, etc). Most always it was a failing piece of hardware or external force such as a router, switch, NIC, squirrel chewing on a network cable, etc. When Server 2008/Windows vista/Windows 7 came out, it seems these operating systems helped Microsoft Dynamics SL to recover better from a dropped network connection and we here in support saw a decline in instances of this happening. Though I don't know what may have changed technically, I can only conclude it had something to do with the combination of Operating System version and version of Microsoft Dynamics SL. Recently, we have had several reports of sporadic 10232 errors in various screens and during various processes in Microsoft Dynamics SL. In troubleshooting these issues, it seems as if these errors may be related to dropped network packets (signifying a network disconnect). If there is anyone reading this blog who has experienced, or has a customer who has experienced this type of behavior in Microsoft Dynamics SL, please reply in the comments section with any details you may be able to provide. If you have access to network monitoring software, you may want to implement it in your environment and see if there are any instances where the 10232 error coincides with a network disconnect.