I have a .NET 4.0 database-oriented application (thick client, WinForms) working with SQL Server (mainly through Linq to Sql with some ADO.NET window), which is deployed in hundreds of environments (each of which is supported by our IT - customer staff). The application is a rewriting of my LegPro FoxPro product, which has been used for many years.
The app seems to work just fine for all of our clients, except for one that has intermittent exceptions, for example:
System.Data.SqlClient.SqlException (0x80131904): Timed out. The wait period expires before the operation is completed or the server is not responding.
The request did not start because the packet was interrupted, it could be caused by a cancel signal sent from the client, or another request is being executed in the same session, which makes the session busy.
Everything that I can find on the Internet about this (for example, here and here ) says that this problem is a SQL Server 2005 error, which was resolved in Service Pack 1. However, this client uses SQL Server 2008 R2 Express (this is confirmed by our company , we do not just take the client word for this). In addition, we do not use connection pools or distributed transactions, so the links I found seem less relevant.
Again, the problems are intermittent (several times a day) and occur on all their different workstations (it seems that this is not a problem with one client). The legacy FoxPro application is still present in its environment and works fine (against the same database), which seems to indicate that this is not only a problem with the server or the database server.
Any help would be greatly appreciated.
source
share