Differences in these errors

I understand timeouts and SQL Server does not exist error messages, but I am
not too sure under what conditions do the following 2 messages occur and the
difference. We dont see it often, but at times our applications spits out
these messages and would like to know where to start investigating and what
they mean. Can you help me narrow it down?
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()). ~08S01
(11): [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
Check your network documentation.
[Microsoft][ODBC SQL Server Driver]Communication link failure
ThanksMy guess is that they both lead to the same thing (an intermittent problem
with your network), and they are just raised at different points (e.g. the
first may be when it can't connect, and the second may be when it has
connected but then gets cut off).
"Hassan" <hassan@.hotmail.com> wrote in message
news:uHDddtZ6HHA.5360@.TK2MSFTNGP03.phx.gbl...
>I understand timeouts and SQL Server does not exist error messages, but I
>am not too sure under what conditions do the following 2 messages occur and
>the difference. We dont see it often, but at times our applications spits
>out these messages and would like to know where to start investigating and
>what they mean. Can you help me narrow it down?
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
> ~08S01 (11): [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network
> error. Check your network documentation.
> [Microsoft][ODBC SQL Server Driver]Communication link failure
> Thanks
>|||So is it safe to conclude that its definitely network bound and not some SQL
Server error that inteprets it as those error messages ?
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:OgmhrwZ6HHA.4436@.TK2MSFTNGP03.phx.gbl...
> My guess is that they both lead to the same thing (an intermittent problem
> with your network), and they are just raised at different points (e.g. the
> first may be when it can't connect, and the second may be when it has
> connected but then gets cut off).
>
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:uHDddtZ6HHA.5360@.TK2MSFTNGP03.phx.gbl...
>>I understand timeouts and SQL Server does not exist error messages, but I
>>am not too sure under what conditions do the following 2 messages occur
>>and the difference. We dont see it often, but at times our applications
>>spits out these messages and would like to know where to start
>>investigating and what they mean. Can you help me narrow it down?
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
>> ~08S01 (11): [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network
>> error. Check your network documentation.
>> [Microsoft][ODBC SQL Server Driver]Communication link failure
>> Thanks
>|||> So is it safe to conclude that its definitely network bound and not some
> SQL Server error that inteprets it as those error messages ?
Why would you assume that it's NOT a network problem? Do you think SQL
Server is trying to trick you, maybe it's embarrassed about some bug that
hasn't been fixed?|||Yes.
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:eyCqJJb6HHA.5160@.TK2MSFTNGP05.phx.gbl...
>> So is it safe to conclude that its definitely network bound and not some
>> SQL Server error that inteprets it as those error messages ?
> Why would you assume that it's NOT a network problem? Do you think SQL
> Server is trying to trick you, maybe it's embarrassed about some bug that
> hasn't been fixed?
>|||Ok. <shrug>
"Hassan" <hassan@.hotmail.com> wrote in message
news:us4$8pr6HHA.2752@.TK2MSFTNGP06.phx.gbl...
> Yes.
> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in
> message news:eyCqJJb6HHA.5160@.TK2MSFTNGP05.phx.gbl...
>> So is it safe to conclude that its definitely network bound and not some
>> SQL Server error that inteprets it as those error messages ?
>> Why would you assume that it's NOT a network problem? Do you think SQL
>> Server is trying to trick you, maybe it's embarrassed about some bug that
>> hasn't been fixed?
>|||We have been getting the same issue and have ruled out the network as the
cause. This appears to have caused by additional load on the server as we
recently moved some databases on it. We are going to allocate more memory to
SQL and move some of the databases off the server. Hopefully this will
resolve the issue.
"Hassan" wrote:
> So is it safe to conclude that its definitely network bound and not some SQL
> Server error that inteprets it as those error messages ?
> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:OgmhrwZ6HHA.4436@.TK2MSFTNGP03.phx.gbl...
> > My guess is that they both lead to the same thing (an intermittent problem
> > with your network), and they are just raised at different points (e.g. the
> > first may be when it can't connect, and the second may be when it has
> > connected but then gets cut off).
> >
> >
> >
> > "Hassan" <hassan@.hotmail.com> wrote in message
> > news:uHDddtZ6HHA.5360@.TK2MSFTNGP03.phx.gbl...
> >>I understand timeouts and SQL Server does not exist error messages, but I
> >>am not too sure under what conditions do the following 2 messages occur
> >>and the difference. We dont see it often, but at times our applications
> >>spits out these messages and would like to know where to start
> >>investigating and what they mean. Can you help me narrow it down?
> >>
> >> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
> >> ~08S01 (11): [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network
> >> error. Check your network documentation.
> >>
> >> [Microsoft][ODBC SQL Server Driver]Communication link failure
> >>
> >> Thanks
> >>
> >
> >
>
>|||Moving a high load database off the server and rebooting it has resolved the
issue.
"Hassan" wrote:
> I understand timeouts and SQL Server does not exist error messages, but I am
> not too sure under what conditions do the following 2 messages occur and the
> difference. We dont see it often, but at times our applications spits out
> these messages and would like to know where to start investigating and what
> they mean. Can you help me narrow it down?
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()). ~08S01
> (11): [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error.
> Check your network documentation.
> [Microsoft][ODBC SQL Server Driver]Communication link failure
> Thanks
>
>