I am running an update statement in query analyzer to update a database with
data from another database on another server.
I am running into the error : Error: Contains more than the maximum number
of prefixes. Maximum is 3
How do I overcome this error. I am the admin on both servers.
> I am running an update statement in query analyzer to update a database
with
> data from another database on another server.
> I am running into the error : Error: Contains more than the maximum number
> of prefixes. Maximum is 3
> How do I overcome this error. I am the admin on both servers.
Object names in SQL Server have 4 parts: server.database.owner.objectname
Therefore, you ca have only 3 prefixes. Check the names in your Update
query.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
Thursday, March 29, 2012
Error: ConnectionCheckForData (CheckforData()).
Here is the error message that I am getting:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData (CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
The situation is this:
Client: Microsoft Windows 2003 Standard
Client s/w: Microsoft SQL Server 2000 Client Tools (patched with SP4)
Server: Microsoft Windows 2003 Standard (SP1)
Server s/w: MSDE 2000, SP3
Network:
Connection is made over a MAN through two firewalls.
Error conditions:
1. I am able to make the initial connection.
2. I am able to perform:
a. SELECT @.@.VERSION
b. SELECT Host_Name()
c. SELECT TOP 1 * FROM sysfiles
3. I get the error whenever I attempt to perform any multi-row recordset (such as SELECT TOP 2 * FROM sysfiles).
We have restarted the SQL instance and the error repeated itself immediately.
When we restart the server, the error goes away. Right now, I am trying to figure out how long from the time the server is restarted to the time the failures appear. By the way, the server is not mine; it's managed by a partner agency so I have limited access to system statistical functions. I have tried inspecting @.@.PACK_SENT, @.@.PACK_RECEIVED and @.@.PACKET_ERRORS, but I do not have access to sysperfinfo or perf monitor.
I have tried Googling the error message and the results seem to be scattered: there was a problem with corrupt indexes (fixed in SP4), a problem with distributed inserts and some other issues that don't seem to apply in this situation.
I am mystified and I don't know what to suggest. If any of you have any ideas, I would be grateful for your thoughts.
Regards,
hmscottCheck ur networking hardware or configuration
somewhere. Look at your network interface settings - especially duplex
settings. Sometimes setting the NICs to Auto duples causes these errors.
checked SQL Server error log? Stack dumps?
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData (CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
The situation is this:
Client: Microsoft Windows 2003 Standard
Client s/w: Microsoft SQL Server 2000 Client Tools (patched with SP4)
Server: Microsoft Windows 2003 Standard (SP1)
Server s/w: MSDE 2000, SP3
Network:
Connection is made over a MAN through two firewalls.
Error conditions:
1. I am able to make the initial connection.
2. I am able to perform:
a. SELECT @.@.VERSION
b. SELECT Host_Name()
c. SELECT TOP 1 * FROM sysfiles
3. I get the error whenever I attempt to perform any multi-row recordset (such as SELECT TOP 2 * FROM sysfiles).
We have restarted the SQL instance and the error repeated itself immediately.
When we restart the server, the error goes away. Right now, I am trying to figure out how long from the time the server is restarted to the time the failures appear. By the way, the server is not mine; it's managed by a partner agency so I have limited access to system statistical functions. I have tried inspecting @.@.PACK_SENT, @.@.PACK_RECEIVED and @.@.PACKET_ERRORS, but I do not have access to sysperfinfo or perf monitor.
I have tried Googling the error message and the results seem to be scattered: there was a problem with corrupt indexes (fixed in SP4), a problem with distributed inserts and some other issues that don't seem to apply in this situation.
I am mystified and I don't know what to suggest. If any of you have any ideas, I would be grateful for your thoughts.
Regards,
hmscottCheck ur networking hardware or configuration
somewhere. Look at your network interface settings - especially duplex
settings. Sometimes setting the NICs to Auto duples causes these errors.
checked SQL Server error log? Stack dumps?
Error: ConnectionCheckForData (CheckforData())
Hi,
I'm running SQL 2k SP3a on a 2.2P4 workstation with 250GB
drives and Windows Server 2003 sp1. I'm running a fairly
simple stored proc and I get the following error:
[Microsoft][ODBC SQL Server Driver][Shared Memory]
ConnectionCheckForData (CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
I've tried changing protocols in the client utiltiy (tcp
and named pipes) as suggested elsewhere. There are no
errors in the application log or the sql log.
Any ideas what is happening? The same query doesn't
crash on W2k Server/SQL Server 2k. It happens repeatedly,
but sometimes on the first, second or third execution of
the stored proc.
Thanks for any insight.Fred,
You could try to adjust couple of parameters of your SQL
Server:
network packet size (B):
default 4096, change it to eg. 1024
remote query timeout (s):
default 30 or 60, change it to eg. 600
You can see the current configuration with "sp_configure".
You could also design your procedure to interact
with "the client program" more frequently. One
possibility is to add rows like
PRINT 'Just sending something to the interface'
to your procedure. The idea is to keep the connection
alive.
I've tested these and it helped with some procedures (but
not with everyone).
If anyone has any other ideas, please let us know!
.mika
>--Original Message--
>Hi,
>I'm running SQL 2k SP3a on a 2.2P4 workstation with
250GB
>drives and Windows Server 2003 sp1. I'm running a
fairly
>simple stored proc and I get the following error:
>[Microsoft][ODBC SQL Server Driver][Shared Memory]
>ConnectionCheckForData (CheckforData()).
>Server: Msg 11, Level 16, State 1, Line 0
>General network error. Check your network documentation.
>Connection Broken
>I've tried changing protocols in the client utiltiy (tcp
>and named pipes) as suggested elsewhere. There are no
>errors in the application log or the sql log.
>Any ideas what is happening? The same query doesn't
>crash on W2k Server/SQL Server 2k. It happens
repeatedly,
>but sometimes on the first, second or third execution of
>the stored proc.
>Thanks for any insight.
>.
>|||Hi Fred,
Have had this problem recently, it seems a common error with quite a
few different symptoms. I will tell you our story, which may or may
not help.
For our case, we had this error executing dynamic SQL over ADO.NET,
but could also recreate the problem via Query Analyser using different
protocols.
We were using a complex query and got either your error or the
following:
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 51 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Connection Broken
We only got this error under certain conditions but could reproduce it
faithfully under those conditions.
Sniffing around the newsgroups, the general opinion was that if you
changed the query slightly, then in some cases the problem just "went
away".
I found 2 solutions to our problem.
Solution 1
Our query was using a view and by putting a "TOP 100 PERCENT" clause
in the view the problem went away. This is the solution we went with.
Solution 2
By using "OPTION(MERGE JOIN)" or "OPTION(LOOP JOIN)" in the SQL
statement, the problem went away. By forcing "OPTION(HASH JOIN)" the
problem re-appeared.
My theory is that merge joins were causing the problem (possibly in
conjunction with parallel query execution) but can't prove anything
because when you get this problem, you can't even get a query plan.
Looking at the query plan after using "TOP 100 PERCENT" I noticed that
there were no merge joins, although that proves nothing.
I wish you luck.
"Fred Jones" <anonymous@.discussions.microsoft.com> wrote in message news:<98f701c3ea99$2d681e80$a501280a@.phx.gbl>...
> Hi,
> I'm running SQL 2k SP3a on a 2.2P4 workstation with 250GB
> drives and Windows Server 2003 sp1. I'm running a fairly
> simple stored proc and I get the following error:
> [Microsoft][ODBC SQL Server Driver][Shared Memory]
> ConnectionCheckForData (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> I've tried changing protocols in the client utiltiy (tcp
> and named pipes) as suggested elsewhere. There are no
> errors in the application log or the sql log.
> Any ideas what is happening? The same query doesn't
> crash on W2k Server/SQL Server 2k. It happens repeatedly,
> but sometimes on the first, second or third execution of
> the stored proc.
> Thanks for any insight.
I'm running SQL 2k SP3a on a 2.2P4 workstation with 250GB
drives and Windows Server 2003 sp1. I'm running a fairly
simple stored proc and I get the following error:
[Microsoft][ODBC SQL Server Driver][Shared Memory]
ConnectionCheckForData (CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
I've tried changing protocols in the client utiltiy (tcp
and named pipes) as suggested elsewhere. There are no
errors in the application log or the sql log.
Any ideas what is happening? The same query doesn't
crash on W2k Server/SQL Server 2k. It happens repeatedly,
but sometimes on the first, second or third execution of
the stored proc.
Thanks for any insight.Fred,
You could try to adjust couple of parameters of your SQL
Server:
network packet size (B):
default 4096, change it to eg. 1024
remote query timeout (s):
default 30 or 60, change it to eg. 600
You can see the current configuration with "sp_configure".
You could also design your procedure to interact
with "the client program" more frequently. One
possibility is to add rows like
PRINT 'Just sending something to the interface'
to your procedure. The idea is to keep the connection
alive.
I've tested these and it helped with some procedures (but
not with everyone).
If anyone has any other ideas, please let us know!
.mika
>--Original Message--
>Hi,
>I'm running SQL 2k SP3a on a 2.2P4 workstation with
250GB
>drives and Windows Server 2003 sp1. I'm running a
fairly
>simple stored proc and I get the following error:
>[Microsoft][ODBC SQL Server Driver][Shared Memory]
>ConnectionCheckForData (CheckforData()).
>Server: Msg 11, Level 16, State 1, Line 0
>General network error. Check your network documentation.
>Connection Broken
>I've tried changing protocols in the client utiltiy (tcp
>and named pipes) as suggested elsewhere. There are no
>errors in the application log or the sql log.
>Any ideas what is happening? The same query doesn't
>crash on W2k Server/SQL Server 2k. It happens
repeatedly,
>but sometimes on the first, second or third execution of
>the stored proc.
>Thanks for any insight.
>.
>|||Hi Fred,
Have had this problem recently, it seems a common error with quite a
few different symptoms. I will tell you our story, which may or may
not help.
For our case, we had this error executing dynamic SQL over ADO.NET,
but could also recreate the problem via Query Analyser using different
protocols.
We were using a complex query and got either your error or the
following:
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 51 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Connection Broken
We only got this error under certain conditions but could reproduce it
faithfully under those conditions.
Sniffing around the newsgroups, the general opinion was that if you
changed the query slightly, then in some cases the problem just "went
away".
I found 2 solutions to our problem.
Solution 1
Our query was using a view and by putting a "TOP 100 PERCENT" clause
in the view the problem went away. This is the solution we went with.
Solution 2
By using "OPTION(MERGE JOIN)" or "OPTION(LOOP JOIN)" in the SQL
statement, the problem went away. By forcing "OPTION(HASH JOIN)" the
problem re-appeared.
My theory is that merge joins were causing the problem (possibly in
conjunction with parallel query execution) but can't prove anything
because when you get this problem, you can't even get a query plan.
Looking at the query plan after using "TOP 100 PERCENT" I noticed that
there were no merge joins, although that proves nothing.
I wish you luck.
"Fred Jones" <anonymous@.discussions.microsoft.com> wrote in message news:<98f701c3ea99$2d681e80$a501280a@.phx.gbl>...
> Hi,
> I'm running SQL 2k SP3a on a 2.2P4 workstation with 250GB
> drives and Windows Server 2003 sp1. I'm running a fairly
> simple stored proc and I get the following error:
> [Microsoft][ODBC SQL Server Driver][Shared Memory]
> ConnectionCheckForData (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> I've tried changing protocols in the client utiltiy (tcp
> and named pipes) as suggested elsewhere. There are no
> errors in the application log or the sql log.
> Any ideas what is happening? The same query doesn't
> crash on W2k Server/SQL Server 2k. It happens repeatedly,
> but sometimes on the first, second or third execution of
> the stored proc.
> Thanks for any insight.
Error: ConnectionCheckForData (CheckforData())
Hi,
I'm running SQL 2k SP3a on a 2.2P4 workstation with 250GB
drives and Windows Server 2003 sp1. I'm running a fairly
simple stored proc and I get the following error:
[Microsoft][ODBC SQL Server Driver][Shared Memory]
ConnectionCheckForData (CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
I've tried changing protocols in the client utiltiy (tcp
and named pipes) as suggested elsewhere. There are no
errors in the application log or the sql log.
Any ideas what is happening? The same query doesn't
crash on W2k Server/SQL Server 2k. It happens repeatedly,
but sometimes on the first, second or third execution of
the stored proc.
Thanks for any insight.Hi Fred,
Have had this problem recently, it seems a common error with quite a
few different symptoms. I will tell you our story, which may or may
not help.
For our case, we had this error executing dynamic SQL over ADO.NET,
but could also recreate the problem via Query Analyser using different
protocols.
We were using a complex query and got either your error or the
following:
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 51 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Connection Broken
We only got this error under certain conditions but could reproduce it
faithfully under those conditions.
Sniffing around the newsgroups, the general opinion was that if you
changed the query slightly, then in some cases the problem just "went
away".
I found 2 solutions to our problem.
Solution 1
Our query was using a view and by putting a "TOP 100 PERCENT" clause
in the view the problem went away. This is the solution we went with.
Solution 2
By using "OPTION(MERGE JOIN)" or "OPTION(LOOP JOIN)" in the SQL
statement, the problem went away. By forcing "OPTION(HASH JOIN)" the
problem re-appeared.
My theory is that merge joins were causing the problem (possibly in
conjunction with parallel query execution) but can't prove anything
because when you get this problem, you can't even get a query plan.
Looking at the query plan after using "TOP 100 PERCENT" I noticed that
there were no merge joins, although that proves nothing.
I wish you luck.
"Fred Jones" <anonymous@.discussions.microsoft.com> wrote in message news:<98f701c3ea99$2
d681e80$a501280a@.phx.gbl>...
> Hi,
> I'm running SQL 2k SP3a on a 2.2P4 workstation with 250GB
> drives and Windows Server 2003 sp1. I'm running a fairly
> simple stored proc and I get the following error:
> [Microsoft][ODBC SQL Server Driver][Shared Memory]
> ConnectionCheckForData (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> I've tried changing protocols in the client utiltiy (tcp
> and named pipes) as suggested elsewhere. There are no
> errors in the application log or the sql log.
> Any ideas what is happening? The same query doesn't
> crash on W2k Server/SQL Server 2k. It happens repeatedly,
> but sometimes on the first, second or third execution of
> the stored proc.
> Thanks for any insight.sql
I'm running SQL 2k SP3a on a 2.2P4 workstation with 250GB
drives and Windows Server 2003 sp1. I'm running a fairly
simple stored proc and I get the following error:
[Microsoft][ODBC SQL Server Driver][Shared Memory]
ConnectionCheckForData (CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
I've tried changing protocols in the client utiltiy (tcp
and named pipes) as suggested elsewhere. There are no
errors in the application log or the sql log.
Any ideas what is happening? The same query doesn't
crash on W2k Server/SQL Server 2k. It happens repeatedly,
but sometimes on the first, second or third execution of
the stored proc.
Thanks for any insight.Hi Fred,
Have had this problem recently, it seems a common error with quite a
few different symptoms. I will tell you our story, which may or may
not help.
For our case, we had this error executing dynamic SQL over ADO.NET,
but could also recreate the problem via Query Analyser using different
protocols.
We were using a complex query and got either your error or the
following:
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 51 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Connection Broken
We only got this error under certain conditions but could reproduce it
faithfully under those conditions.
Sniffing around the newsgroups, the general opinion was that if you
changed the query slightly, then in some cases the problem just "went
away".
I found 2 solutions to our problem.
Solution 1
Our query was using a view and by putting a "TOP 100 PERCENT" clause
in the view the problem went away. This is the solution we went with.
Solution 2
By using "OPTION(MERGE JOIN)" or "OPTION(LOOP JOIN)" in the SQL
statement, the problem went away. By forcing "OPTION(HASH JOIN)" the
problem re-appeared.
My theory is that merge joins were causing the problem (possibly in
conjunction with parallel query execution) but can't prove anything
because when you get this problem, you can't even get a query plan.
Looking at the query plan after using "TOP 100 PERCENT" I noticed that
there were no merge joins, although that proves nothing.
I wish you luck.
"Fred Jones" <anonymous@.discussions.microsoft.com> wrote in message news:<98f701c3ea99$2
d681e80$a501280a@.phx.gbl>...
> Hi,
> I'm running SQL 2k SP3a on a 2.2P4 workstation with 250GB
> drives and Windows Server 2003 sp1. I'm running a fairly
> simple stored proc and I get the following error:
> [Microsoft][ODBC SQL Server Driver][Shared Memory]
> ConnectionCheckForData (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> I've tried changing protocols in the client utiltiy (tcp
> and named pipes) as suggested elsewhere. There are no
> errors in the application log or the sql log.
> Any ideas what is happening? The same query doesn't
> crash on W2k Server/SQL Server 2k. It happens repeatedly,
> but sometimes on the first, second or third execution of
> the stored proc.
> Thanks for any insight.sql
Tuesday, March 27, 2012
Error: connection is busy with results for another hstmt
Good Afternoon. I have a Crystal report that accesses a sql 2000 server. W
hen I run the report twice with the same parrameters. I get the following e
rror:
crystal reports connection is busy with results for another hstmt
As I understand it, this has to do with multiple record sets, and something
to the effect that my report is not consuming everything and therefore leavi
ng a cursor.
And while I understand that for the most part, I can't even begin to think h
ow to troubleshoot the report and find the problem. It's a HUGE report with
excess of 30 subreports. It is designed to only return 1 record, with nume
rous fields from throughout
the database placed on the report. Like I said it has numerous subreports,
and all are linked to the same URN. Anyway, is there anything I can do shor
t of upgrading the server to 2005?
From http://www.developmentnow.com/g/111...server-odbc.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.comafter nearly 30 hours of searching, I finally posted my question here.
What's funny is that 2 hours later I found my answer:
http://support.microsoft.com/kb/173410
From http://www.developmentnow.com/group...
=995268
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
hen I run the report twice with the same parrameters. I get the following e
rror:
crystal reports connection is busy with results for another hstmt
As I understand it, this has to do with multiple record sets, and something
to the effect that my report is not consuming everything and therefore leavi
ng a cursor.
And while I understand that for the most part, I can't even begin to think h
ow to troubleshoot the report and find the problem. It's a HUGE report with
excess of 30 subreports. It is designed to only return 1 record, with nume
rous fields from throughout
the database placed on the report. Like I said it has numerous subreports,
and all are linked to the same URN. Anyway, is there anything I can do shor
t of upgrading the server to 2005?
From http://www.developmentnow.com/g/111...server-odbc.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.comafter nearly 30 hours of searching, I finally posted my question here.
What's funny is that 2 hours later I found my answer:
http://support.microsoft.com/kb/173410
From http://www.developmentnow.com/group...
=995268
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
Error: connection is busy with results for another hstmt
Good Afternoon. I have a Crystal report that accesses a sql 2000 server. When I run the report twice with the same parrameters. I get the following error:
crystal reports connection is busy with results for another hstmt
As I understand it, this has to do with multiple record sets, and something to the effect that my report is not consuming everything and therefore leaving a cursor.
And while I understand that for the most part, I can't even begin to think how to troubleshoot the report and find the problem. It's a HUGE report with excess of 30 subreports. It is designed to only return 1 record, with numerous fields from throughout the database placed on the report. Like I said it has numerous subreports, and all are linked to the same URN. Anyway, is there anything I can do short of upgrading the server to 2005?
From http://www.developmentnow.com/g/111_2007_7_0_0_0/sql-server-odbc.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
after nearly 30 hours of searching, I finally posted my question here.
What's funny is that 2 hours later I found my answer:
http://support.microsoft.com/kb/173410
From http://www.developmentnow.com/groups/viewthread.aspx?newsgroupid=111&threadid=995268
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
crystal reports connection is busy with results for another hstmt
As I understand it, this has to do with multiple record sets, and something to the effect that my report is not consuming everything and therefore leaving a cursor.
And while I understand that for the most part, I can't even begin to think how to troubleshoot the report and find the problem. It's a HUGE report with excess of 30 subreports. It is designed to only return 1 record, with numerous fields from throughout the database placed on the report. Like I said it has numerous subreports, and all are linked to the same URN. Anyway, is there anything I can do short of upgrading the server to 2005?
From http://www.developmentnow.com/g/111_2007_7_0_0_0/sql-server-odbc.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
after nearly 30 hours of searching, I finally posted my question here.
What's funny is that 2 hours later I found my answer:
http://support.microsoft.com/kb/173410
From http://www.developmentnow.com/groups/viewthread.aspx?newsgroupid=111&threadid=995268
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
error: connection is busy
Error: 0xC0202009 at Load SQL Deals, Insert SQL Deals [12494]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Connection is busy with results for another command".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Connection is busy with results for another command".
Why isn't the connection manager managing this?
How can I trace the cause? The data flow component (insert SQL deals) is just a simple INSERT statment.You can always run SQL Profiler to see what's going on.
Subscribe to:
Posts (Atom)