I have not seen this before and am not quite sure where to start as I cannot reproduce it, it is happening on average once a day. Any ideas what this is typically or where to start looking?






Keith Chisarik

Hey Keith, it looks as though the error is just manifesting itself through the Save....but the actual error is happening on the backend through the connection in the DAL.  The error is actually happening within the System.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync method.  It seems that one of two things could be happening:

1. The connection has already been established but the process is taking a long time.  This can happen if you are using a standard SQL Server connection to a remote site via a VPN connection.  The TDS stream is actually very large and there would be no compression either, so if there were a lot fo records being save and there was any type of latency in the network or internet connection, then a timeout could be happening.  In this cas you would need to beef up the connection timeout to more than 30 seconds (the default) by modifying the connection string of the SQL connection.
2. Something within the TDS stream (the update tag) is causing the error.  In this case you would want to turn on data debugging to see what is going back to the server....I will tell you that I think this is not as likely as number 1 above.

This is one reason the Enterprise Server is extremely beneficial when talking with remote data sources....it is fast!  All of the TDS data, encryption, and compression is applied and there is an absolute minumum of data going across the wire.

It is that age old problem...if you can reproduce it you can fix it