How to catch properly an SqlException: A transport-level error has occurred?

That particular error does not come from sys. Messages in SQL Server - as it's a problem with the connection. So I don't have the number to hand.

That particular error does not come from sys. Messages in SQL Server - as it's a problem with the connection. So I don't have the number to hand.

TBH, the best thing you should do is to ensure the Number is written out to the log with the exception - that way, you'll always have the number and message side by side in the logs. May not answer your current question, but it will be the best going forwards IMHO. Not only SqlException.

Number but SqlException. ErrorCode too - in instances like this I think . ErrorCode may be the one you actually need (not sure without checking).

You will not find an associated SQL Error number for this one - simply put, the error occurs because there was a problem with connecting to the server. As the code cannot connect to SQL Server, it will not have a SQL error to report. From the MSDN article about SQLException.

Number: This number corresponds to an entry in the master.dbo. Sysmessages table. For exceptions that do not have an associated SQL Error number, you may be able to use the windows HRESULT error code that will be in the ErrorCode property of the exception object.

I am developing an app on Windows Azure, and this sort of error should be caught by the retry policy. – Joannes Vermorel Feb 15 '10 at 13:08 You will have to parse the error message for something like A transport-level error has occurred when receiving results from the server and decide accordingly. – Oded Feb 15 '10 at 13:14 1 Hum, that's really ugly.

In particular, it does not even work on my machine who happen to throw a localized (French) error message... – Joannes Vermorel Feb 15 '10 at 13:18 1 I think it's the . ErrorCode property you'd be interested in, in this case - that should give a way to identify the specific error without parsing the text – AdaTheDev Feb 15 '10 at 13:21.

Folks, please examine actual exception stack before blindly claiming that SqlException doesn't have . Number just besaus some MSDN page has a boilerplate text. .

ErrorCode usually gets one single generic value (set by private CTOR). For this patricular error you can see exception stack here: social.msdn.microsoft.com/Forums/en-US/s... and if you follow it you'll see that the code that's preparing is fills in everything but it's a bit convoluted to trace actuall error number in reflector. So, whoever sees things next pleace post actual error number (or numbers).

These errors tend to be quite rare and transient and it would be good to have numbers since at the time a server sees connection hiccup it's too late to go chasing their numbers.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.