Hello everyone,
When I execute the following statement in the query analyzer on a msSQL2000
database...
delete from DVD_I_Have where id in(select top 1 id from DVD_I_Have where
Userid=78 and DVDID=8 and onhold=0);
I get the following error...
Server: Msg 21, Level 20, State 1, Line 1
Warning: Fatal error 625 occurred at Jan 30 2007 2:15PM
Connection Broken
If I execute a simple SELECT statement, or any other statement, it runs ok
and doesn't cause an error.
Is there anything wrong with the above statement? and how can it be causing
that error message?
Thanks in advance for all help received!
Regards, RobertI'd run DBCC CHECKDB immediately.
Linchi
"ROBinBrampton" wrote:
> Hello everyone,
> When I execute the following statement in the query analyzer on a msSQL2000
> database...
> delete from DVD_I_Have where id in(select top 1 id from DVD_I_Have where
> Userid=78 and DVDID=8 and onhold=0);
> I get the following error...
> Server: Msg 21, Level 20, State 1, Line 1
> Warning: Fatal error 625 occurred at Jan 30 2007 2:15PM
> Connection Broken
> If I execute a simple SELECT statement, or any other statement, it runs ok
> and doesn't cause an error.
> Is there anything wrong with the above statement? and how can it be causing
> that error message?
> Thanks in advance for all help received!
> Regards, Robert
>
Showing posts with label broken. Show all posts
Showing posts with label broken. Show all posts
Monday, March 19, 2012
Fatal error 625 - Connection broken problem (Help needed)
Hello everyone,
When I execute the following statement in the query analyzer on a msSQL2000
database...
delete from DVD_I_Have where id in(select top 1 id from DVD_I_Have where
Userid=78 and DVDID=8 and onhold=0);
I get the following error...
Server: Msg 21, Level 20, State 1, Line 1
Warning: Fatal error 625 occurred at Jan 30 2007 2:15PM
Connection Broken
If I execute a simple SELECT statement, or any other statement, it runs ok
and doesn't cause an error.
Is there anything wrong with the above statement? and how can it be causing
that error message?
Thanks in advance for all help received!
Regards, Robert
I'd run DBCC CHECKDB immediately.
Linchi
"ROBinBrampton" wrote:
> Hello everyone,
> When I execute the following statement in the query analyzer on a msSQL2000
> database...
> delete from DVD_I_Have where id in(select top 1 id from DVD_I_Have where
> Userid=78 and DVDID=8 and onhold=0);
> I get the following error...
> Server: Msg 21, Level 20, State 1, Line 1
> Warning: Fatal error 625 occurred at Jan 30 2007 2:15PM
> Connection Broken
> If I execute a simple SELECT statement, or any other statement, it runs ok
> and doesn't cause an error.
> Is there anything wrong with the above statement? and how can it be causing
> that error message?
> Thanks in advance for all help received!
> Regards, Robert
>
When I execute the following statement in the query analyzer on a msSQL2000
database...
delete from DVD_I_Have where id in(select top 1 id from DVD_I_Have where
Userid=78 and DVDID=8 and onhold=0);
I get the following error...
Server: Msg 21, Level 20, State 1, Line 1
Warning: Fatal error 625 occurred at Jan 30 2007 2:15PM
Connection Broken
If I execute a simple SELECT statement, or any other statement, it runs ok
and doesn't cause an error.
Is there anything wrong with the above statement? and how can it be causing
that error message?
Thanks in advance for all help received!
Regards, Robert
I'd run DBCC CHECKDB immediately.
Linchi
"ROBinBrampton" wrote:
> Hello everyone,
> When I execute the following statement in the query analyzer on a msSQL2000
> database...
> delete from DVD_I_Have where id in(select top 1 id from DVD_I_Have where
> Userid=78 and DVDID=8 and onhold=0);
> I get the following error...
> Server: Msg 21, Level 20, State 1, Line 1
> Warning: Fatal error 625 occurred at Jan 30 2007 2:15PM
> Connection Broken
> If I execute a simple SELECT statement, or any other statement, it runs ok
> and doesn't cause an error.
> Is there anything wrong with the above statement? and how can it be causing
> that error message?
> Thanks in advance for all help received!
> Regards, Robert
>
Fatal error 625 - Connection broken problem (Help needed)
Hello everyone,
When I execute the following statement in the query analyzer on a msSQL2000
database...
delete from DVD_I_Have where id in(select top 1 id from DVD_I_Have where
Userid=78 and DVDID=8 and onhold=0);
I get the following error...
Server: Msg 21, Level 20, State 1, Line 1
Warning: Fatal error 625 occurred at Jan 30 2007 2:15PM
Connection Broken
If I execute a simple SELECT statement, or any other statement, it runs ok
and doesn't cause an error.
Is there anything wrong with the above statement? and how can it be causing
that error message?
Thanks in advance for all help received!
Regards, RobertI'd run DBCC CHECKDB immediately.
Linchi
"ROBinBrampton" wrote:
> Hello everyone,
> When I execute the following statement in the query analyzer on a msSQL200
0
> database...
> delete from DVD_I_Have where id in(select top 1 id from DVD_I_Have where
> Userid=78 and DVDID=8 and onhold=0);
> I get the following error...
> Server: Msg 21, Level 20, State 1, Line 1
> Warning: Fatal error 625 occurred at Jan 30 2007 2:15PM
> Connection Broken
> If I execute a simple SELECT statement, or any other statement, it runs ok
> and doesn't cause an error.
> Is there anything wrong with the above statement? and how can it be causin
g
> that error message?
> Thanks in advance for all help received!
> Regards, Robert
>
When I execute the following statement in the query analyzer on a msSQL2000
database...
delete from DVD_I_Have where id in(select top 1 id from DVD_I_Have where
Userid=78 and DVDID=8 and onhold=0);
I get the following error...
Server: Msg 21, Level 20, State 1, Line 1
Warning: Fatal error 625 occurred at Jan 30 2007 2:15PM
Connection Broken
If I execute a simple SELECT statement, or any other statement, it runs ok
and doesn't cause an error.
Is there anything wrong with the above statement? and how can it be causing
that error message?
Thanks in advance for all help received!
Regards, RobertI'd run DBCC CHECKDB immediately.
Linchi
"ROBinBrampton" wrote:
> Hello everyone,
> When I execute the following statement in the query analyzer on a msSQL200
0
> database...
> delete from DVD_I_Have where id in(select top 1 id from DVD_I_Have where
> Userid=78 and DVDID=8 and onhold=0);
> I get the following error...
> Server: Msg 21, Level 20, State 1, Line 1
> Warning: Fatal error 625 occurred at Jan 30 2007 2:15PM
> Connection Broken
> If I execute a simple SELECT statement, or any other statement, it runs ok
> and doesn't cause an error.
> Is there anything wrong with the above statement? and how can it be causin
g
> that error message?
> Thanks in advance for all help received!
> Regards, Robert
>
Sunday, February 26, 2012
Fake "Broken connection" error
I get the following error when running a particular query, although I know
for sure the server and network are working properly:
"[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken"
Is this a hint that something else might be wrong with my sql server?
Any funky characters in the query? If memory servers correctly thats the
message I got when I had a } one time.
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>I get the following error when running a particular query, although I know
> for sure the server and network are working properly:
>
> "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken"
>
> Is this a hint that something else might be wrong with my sql server?
>
>
|||Hi Chris,
Thank you very much for your reply. No, the query contains no funky
characters such as '{'. If it did that should return a different kind of
error, shouldn't it?
"ChrisR" wrote:
> Any funky characters in the query? If memory servers correctly thats the
> message I got when I had a } one time.
>
> "Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
> news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>
>
|||Not sure as it's been a while...
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:14502176-0C71-4B79-941C-8EF965238B15@.microsoft.com...[vbcol=seagreen]
> Hi Chris,
> Thank you very much for your reply. No, the query contains no funky
> characters such as '{'. If it did that should return a different kind of
> error, shouldn't it?
> "ChrisR" wrote:
for sure the server and network are working properly:
"[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken"
Is this a hint that something else might be wrong with my sql server?
Any funky characters in the query? If memory servers correctly thats the
message I got when I had a } one time.
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>I get the following error when running a particular query, although I know
> for sure the server and network are working properly:
>
> "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken"
>
> Is this a hint that something else might be wrong with my sql server?
>
>
|||Hi Chris,
Thank you very much for your reply. No, the query contains no funky
characters such as '{'. If it did that should return a different kind of
error, shouldn't it?
"ChrisR" wrote:
> Any funky characters in the query? If memory servers correctly thats the
> message I got when I had a } one time.
>
> "Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
> news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>
>
|||Not sure as it's been a while...
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:14502176-0C71-4B79-941C-8EF965238B15@.microsoft.com...[vbcol=seagreen]
> Hi Chris,
> Thank you very much for your reply. No, the query contains no funky
> characters such as '{'. If it did that should return a different kind of
> error, shouldn't it?
> "ChrisR" wrote:
Fake "Broken connection" error
I get the following error when running a particular query, although I know
for sure the server and network are working properly:
"[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckFor
Data
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken"
Is this a hint that something else might be wrong with my sql server?Any funky characters in the query? If memory servers correctly thats the
message I got when I had a } one time.
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>I get the following error when running a particular query, although I know
> for sure the server and network are working properly:
>
> "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckF
orData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken"
>
> Is this a hint that something else might be wrong with my sql server?
>
>|||Hi Chris,
Thank you very much for your reply. No, the query contains no funky
characters such as '{'. If it did that should return a different kind o
f
error, shouldn't it?
"ChrisR" wrote:
> Any funky characters in the query? If memory servers correctly thats the
> message I got when I had a } one time.
>
> "Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
> news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>
>|||Not sure as it's been a while...
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:14502176-0C71-4B79-941C-8EF965238B15@.microsoft.com...[vbcol=seagreen]
> Hi Chris,
> Thank you very much for your reply. No, the query contains no funky
> characters such as '{'. If it did that should return a different kind
of
> error, shouldn't it?
> "ChrisR" wrote:
>
for sure the server and network are working properly:
"[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckFor
Data
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken"
Is this a hint that something else might be wrong with my sql server?Any funky characters in the query? If memory servers correctly thats the
message I got when I had a } one time.
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>I get the following error when running a particular query, although I know
> for sure the server and network are working properly:
>
> "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckF
orData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken"
>
> Is this a hint that something else might be wrong with my sql server?
>
>|||Hi Chris,
Thank you very much for your reply. No, the query contains no funky
characters such as '{'. If it did that should return a different kind o
f
error, shouldn't it?
"ChrisR" wrote:
> Any funky characters in the query? If memory servers correctly thats the
> message I got when I had a } one time.
>
> "Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
> news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>
>|||Not sure as it's been a while...
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:14502176-0C71-4B79-941C-8EF965238B15@.microsoft.com...[vbcol=seagreen]
> Hi Chris,
> Thank you very much for your reply. No, the query contains no funky
> characters such as '{'. If it did that should return a different kind
of
> error, shouldn't it?
> "ChrisR" wrote:
>
Fake "Broken connection" error
I get the following error when running a particular query, although I know
for sure the server and network are working properly:
"[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken"
Is this a hint that something else might be wrong with my sql server?Any funky characters in the query? If memory servers correctly thats the
message I got when I had a } one time.
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>I get the following error when running a particular query, although I know
> for sure the server and network are working properly:
>
> "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken"
>
> Is this a hint that something else might be wrong with my sql server?
>
>|||Hi Chris,
Thank you very much for your reply. No, the query contains no funky
characters such as '{'. If it did that should return a different kind of
error, shouldn't it?
"ChrisR" wrote:
> Any funky characters in the query? If memory servers correctly thats the
> message I got when I had a } one time.
>
> "Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
> news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
> >I get the following error when running a particular query, although I know
> > for sure the server and network are working properly:
> >
> >
> > "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> > (CheckforData()).
> > Server: Msg 11, Level 16, State 1, Line 0
> > General network error. Check your network documentation.
> >
> > Connection Broken"
> >
> >
> > Is this a hint that something else might be wrong with my sql server?
> >
> >
> >
>
>|||Not sure as it's been a while...
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:14502176-0C71-4B79-941C-8EF965238B15@.microsoft.com...
> Hi Chris,
> Thank you very much for your reply. No, the query contains no funky
> characters such as '{'. If it did that should return a different kind of
> error, shouldn't it?
> "ChrisR" wrote:
>> Any funky characters in the query? If memory servers correctly thats the
>> message I got when I had a } one time.
>>
>> "Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
>> news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>> >I get the following error when running a particular query, although I
>> >know
>> > for sure the server and network are working properly:
>> >
>> >
>> > "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
>> > (CheckforData()).
>> > Server: Msg 11, Level 16, State 1, Line 0
>> > General network error. Check your network documentation.
>> >
>> > Connection Broken"
>> >
>> >
>> > Is this a hint that something else might be wrong with my sql server?
>> >
>> >
>> >
>>
for sure the server and network are working properly:
"[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken"
Is this a hint that something else might be wrong with my sql server?Any funky characters in the query? If memory servers correctly thats the
message I got when I had a } one time.
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>I get the following error when running a particular query, although I know
> for sure the server and network are working properly:
>
> "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken"
>
> Is this a hint that something else might be wrong with my sql server?
>
>|||Hi Chris,
Thank you very much for your reply. No, the query contains no funky
characters such as '{'. If it did that should return a different kind of
error, shouldn't it?
"ChrisR" wrote:
> Any funky characters in the query? If memory servers correctly thats the
> message I got when I had a } one time.
>
> "Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
> news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
> >I get the following error when running a particular query, although I know
> > for sure the server and network are working properly:
> >
> >
> > "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
> > (CheckforData()).
> > Server: Msg 11, Level 16, State 1, Line 0
> > General network error. Check your network documentation.
> >
> > Connection Broken"
> >
> >
> > Is this a hint that something else might be wrong with my sql server?
> >
> >
> >
>
>|||Not sure as it's been a while...
"Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
news:14502176-0C71-4B79-941C-8EF965238B15@.microsoft.com...
> Hi Chris,
> Thank you very much for your reply. No, the query contains no funky
> characters such as '{'. If it did that should return a different kind of
> error, shouldn't it?
> "ChrisR" wrote:
>> Any funky characters in the query? If memory servers correctly thats the
>> message I got when I had a } one time.
>>
>> "Ken Abe" <KenAbe@.discussions.microsoft.com> wrote in message
>> news:42E86DB8-21EE-4D35-854A-0D73B416BF9B@.microsoft.com...
>> >I get the following error when running a particular query, although I
>> >know
>> > for sure the server and network are working properly:
>> >
>> >
>> > "[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData
>> > (CheckforData()).
>> > Server: Msg 11, Level 16, State 1, Line 0
>> > General network error. Check your network documentation.
>> >
>> > Connection Broken"
>> >
>> >
>> > Is this a hint that something else might be wrong with my sql server?
>> >
>> >
>> >
>>
Subscribe to:
Posts (Atom)