Databases
StackOverflow2013
Postsdbo
PODifference between two SQLExceptions ("A transport-level error.." and "A network-related or ...")
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODifference between two SQLExceptions ("A transport-level error.." and "A network-related or ...")
    primarykey
    data
    text
    <p>I have a bunch of users on my WPF/Linq2SQL application and I log all their exceptions at the database in a separate connection (which I create efter the exception has been thrown).</p> <p>Occasionally I get the SQLExceptions:</p> <ol> <li>A network-related or instance-specific error occurred while establishing a connection to SQL Server </li> <li>A transport-level error has occurred when receiving results from the server</li> </ol> <p>To me, they both means that Linq2SQL were unable to connect to the database or was disconnected. But I assume there is some difference between them since Microsoft bother to have them both.</p> <p>NB: It is not the server or the database which is the problem. One user may get crashed while the other 10 happily continues to work.</p> <p>I know for a fact that 2) occasionally happens and I get nothing logged (because I log in a table on the same server/database) it seems logically that if the connection breaks down, I cannot save to the errorlog-table either. But both types of SQLExceptions do get logged occationally, meaning that a new connection is able to connect.</p> <p>The user's setup is a laptop computer with both wire and wireless connections. They run windows. Occasionally my forget to disable wireless networking on their laptop when there's a cable to the machine. I have been told that this may cause trouble. Occasionally remember to disable wireless, but then they will disconnect their laptop from the network altogether to go to a meeting (where they re-connect).</p> <p>I need help to figure out which exceptions should be ignored by the program, and which are important enough to let the program crash. And if I should bother re-try the operation before letting the program crash.</p> <p>So.. basically I would like to know the difference between the two exceptions. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USchue x
    1. USiakob
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PODifference between two SQLExceptions ("A transport-level error.." and "A network-related or ...")
      1. USHarsh Baid
      1. VTFavorite
    2. VO
      singulars
      1. PODifference between two SQLExceptions ("A transport-level error.." and "A network-related or ...")
      1. This table or related slice is empty.
      1. VTUpMod
    1. COException 1 is that the program can't connect to the server to establish a connection, exception 2 is that it did previously manage to get a connection but it was interrupted.
      singulars
      1. PODifference between two SQLExceptions ("A transport-level error.." and "A network-related or ...")
      1. USsteoleary
    2. COThanks. I guess the text in the messages really says so, too. So pulling the wireless connection from under the program may result in either exception..
      singulars
      1. PODifference between two SQLExceptions ("A transport-level error.." and "A network-related or ...")
      1. USiakob
    3. COYep, depending where the program has got to at the time, you could get either. What might be worth doing is handling the error so that it retries the connection a couple of times and if this doesn't work, show a dialog box with a reconnect or quit button so that the user can either sort the problem and reconnect once they fixed the problem, or exit gracefully. Better than just letting it crash.
      singulars
      1. PODifference between two SQLExceptions ("A transport-level error.." and "A network-related or ...")
      1. USsteoleary
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload