Connection Broken

I am updating records in my database with the procedure below. The data is
updated as it should but the Enterprise Manager (SQL Query Analyzer) gives
the 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
It looks like this error is blocking the SQL Server from responding to new
requests immediately (3-4 seconds) after an update.
Any ideas of what can cause this problem?
The sql call with belonging SQL procedure (below) has been tested on several
SQL servers and is working OK, but on this server I am running it against at
the moment it gives error above.
p_kontaktpersoner_endre 44, 'Tor Inge', 'Rislaa', 'TIR', 840, 'IT Manager',
'Adm', '38 15 44 30', '38 15 44 35', '900 90 700', 'myemail@.vef.no', '', 1,
'Test note', 1
CREATE PROCEDURE p_kontaktpersoner_endre
@.kp_id int = 1 ,
@.fornavn varchar(50) = '' ,
@.etternavn varchar(50) = '' ,
@.initialer varchar(3) = '' ,
@.ko_id int = 0 ,
@.stilling varchar(50) = '' ,
@.avdeling varchar(50) = '' ,
@.telefon varchar(30) = '' ,
@.telefaks varchar(30) = '' ,
@.mobiltelefon varchar(30) = '' ,
@.e_post varchar(50) = '' ,
@.kategori varchar(100) = '' ,
@.prioritet int = 1 ,
@.merknad text = '' ,
@.aktiv int = 1
AS
UPDATE kontaktpersoner
SET fornavn = @.fornavn,
etternavn = @.etternavn,
initialer = @.initialer,
ko_id = @.ko_id,
stilling = @.stilling,
avdeling = @.avdeling,
telefon = @.telefon,
telefaks = @.telefaks,
mobiltelefon = @.mobiltelefon,
e_post= @.e_post,
kategori = @.kategori,
prioritet = @.prioritet,
merknad = @.merknad,
aktiv= @.aktiv
FROM kontaktpersoner
WHERE kp_id = @.kp_idHi
You don't give the version information for SQL Server, but this may be one
cause!
http://support.microsoft.com/defaul...kb;en-us;903742
John
"Tor Inge Rislaa" <tor.ingenospam@.rislaa.no> wrote in message
news:OWme0eT3FHA.636@.TK2MSFTNGP10.phx.gbl...
>I am updating records in my database with the procedure below. The data is
>updated as it should but the Enterprise Manager (SQL Query Analyzer) gives
>the 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
>
> It looks like this error is blocking the SQL Server from responding to new
> requests immediately (3-4 seconds) after an update.
>
> Any ideas of what can cause this problem?
>
> The sql call with belonging SQL procedure (below) has been tested on
> several SQL servers and is working OK, but on this server I am running it
> against at the moment it gives error above.
>
>
> p_kontaktpersoner_endre 44, 'Tor Inge', 'Rislaa', 'TIR', 840, 'IT
> Manager', 'Adm', '38 15 44 30', '38 15 44 35', '900 90 700',
> 'myemail@.vef.no', '', 1, 'Test note', 1
> CREATE PROCEDURE p_kontaktpersoner_endre
> @.kp_id int = 1 ,
> @.fornavn varchar(50) = '' ,
> @.etternavn varchar(50) = '' ,
> @.initialer varchar(3) = '' ,
> @.ko_id int = 0 ,
> @.stilling varchar(50) = '' ,
> @.avdeling varchar(50) = '' ,
> @.telefon varchar(30) = '' ,
> @.telefaks varchar(30) = '' ,
> @.mobiltelefon varchar(30) = '' ,
> @.e_post varchar(50) = '' ,
> @.kategori varchar(100) = '' ,
> @.prioritet int = 1 ,
> @.merknad text = '' ,
> @.aktiv int = 1
> AS
> UPDATE kontaktpersoner
> SET fornavn = @.fornavn,
> etternavn = @.etternavn,
> initialer = @.initialer,
> ko_id = @.ko_id,
> stilling = @.stilling,
> avdeling = @.avdeling,
> telefon = @.telefon,
> telefaks = @.telefaks,
> mobiltelefon = @.mobiltelefon,
> e_post= @.e_post,
> kategori = @.kategori,
> prioritet = @.prioritet,
> merknad = @.merknad,
> aktiv= @.aktiv
> FROM kontaktpersoner
> WHERE kp_id = @.kp_id
>|||Thanks. Do you know where to find what version or SP my server has
TIRislaa
"John Bell" <jbellnewsposts@.hotmail.com> skrev i melding
news:%23m$JfcU3FHA.2196@.tk2msftngp13.phx.gbl...
> Hi
> You don't give the version information for SQL Server, but this may be one
> cause!
> http://support.microsoft.com/defaul...kb;en-us;903742
> John
> "Tor Inge Rislaa" <tor.ingenospam@.rislaa.no> wrote in message
> news:OWme0eT3FHA.636@.TK2MSFTNGP10.phx.gbl...
>|||Hi
Try http://www.aspfaq.com/show.asp?id=2160 and
http://www.aspfaq.com/sql2000builds.asp
In your update statement you don't need the from clause as it is the
same table as the one being updated.
John
Tor Inge Rislaa wrote:
> Thanks. Do you know where to find what version or SP my server has
> TIRislaa
> "John Bell" <jbellnewsposts@.hotmail.com> skrev i melding
> news:%23m$JfcU3FHA.2196@.tk2msftngp13.phx.gbl...

Connection Bombs Out at 3900+ records

I have a customer who's running an application that's using an OLE DB
connection to the database and when retrieving records a counter shows on th
e
screen. As soon as the count reaches somewhere between 3900 and 4000 the
counting stops and the grid never fills. The message received is as follows:
[Custom Message from application saying error has occurred]
-2147467259[DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not
exist
or access denied.
Is this a timing out or connection pooling problem? I'm sorry but I don't
have the particulars about versions, systems, etc. because I've received the
question from someone else. Could you just give me an educated guess at what
the problem might be so I can start troubleshooting in the right direction?
Apparently the customer just had a problem with the log file being full so
they moved it to another server. Could this have caused a problem? This is a
very large location so I assume the dba(s) know what they are doing. Could
they have limited the number of records that can be returned?
Thanks for any help you can give.
--
GinnySearch no further...
http://support.microsoft.com/defaul...kb;en-us;328476
Note, this answer took forever to find so I'm posting everywhere...|||Thanks. I will pass on the link to the customer.
--
Ginny
"alorentz" wrote:

> Search no further...
> http://support.microsoft.com/defaul...kb;en-us;328476
> Note, this answer took forever to find so I'm posting everywhere...
>

Connection Bombs Out at 3900+ records

I have a customer who's running an application that's using an OLE DB
connection to the database and when retrieving records a counter shows on the
screen. As soon as the count reaches somewhere between 3900 and 4000 the
counting stops and the grid never fills. The message received is as follows:
[Custom Message from application saying error has occurred]
-2147467259[DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist
or access denied.
Is this a timing out or connection pooling problem? I'm sorry but I don't
have the particulars about versions, systems, etc. because I've received the
question from someone else. Could you just give me an educated guess at what
the problem might be so I can start troubleshooting in the right direction?
Apparently the customer just had a problem with the log file being full so
they moved it to another server. Could this have caused a problem? This is a
very large location so I assume the dba(s) know what they are doing. Could
they have limited the number of records that can be returned?
Thanks for any help you can give.
Ginny
Search no further...
http://support.microsoft.com/default...b;en-us;328476
Note, this answer took forever to find so I'm posting everywhere...
|||Thanks. I will pass on the link to the customer.
Ginny
"alorentz" wrote:

> Search no further...
> http://support.microsoft.com/default...b;en-us;328476
> Note, this answer took forever to find so I'm posting everywhere...
>

Connection between SQL Server 2000 SP3a and ODBC Driver

Database: SQL Server 2000 Developer Edition SP3a
Frontend: MS Access 2000 and Access 2003
A Custm-built Medical Records Database
I am having a problem connecting to my SQL server with certain ODBC drivers
(sqlsrv32.dll). But it only acts up on certain "forms" in the Database, in
particular ones which retrieve from lots of columns. On these forms there is
a long delay, and a little of the data is retrieved, but the rest of fields
arent. And there are no error messages.
I am trying to connect to a MS-SQL Server 2000 SP3a database through Access
2003 (frontend of database) on our only XP machine. All my NT machines
connect
easily, with no problems. A handful of Windows 2000 machines give me
problems with the newer ODBC drivers, but if i would replace the
SQLSRV32.DLL with a copy from the NT machines it would work ok.
I thought upgrading the Service Pack from SP2 to SP3a would help but that
didnt work. I cant figure out what the problem is, but it sounds (to me)
similar to what is described in (FIX 814410 -
http://support.microsoft.com/kb/814410 ) as a "memory leak"...could this be
it? but the SP upgrade didnt fix/help...
Please advise how I can fix it, or where i can look to figure out what the
problem is.
Thank you.
Hi
SQL Profiler will indicate what queries are running slow. Try running it
from Query Analyser and check out their query plan. You may also want to
look at the statistics and how often they are updated. You may also want to
check the
Also you may want to check the version of MDAC you are running on each
machine using the MDAC component checker
http://msdn.microsoft.com/data/mdac/default.aspx
John
"desimaj" <desimaj@.discussions.microsoft.com> wrote in message
news:92716878-DB7C-4479-A96C-892F313C6F6B@.microsoft.com...
> Database: SQL Server 2000 Developer Edition SP3a
> Frontend: MS Access 2000 and Access 2003
> A Custm-built Medical Records Database
> I am having a problem connecting to my SQL server with certain ODBC
> drivers
> (sqlsrv32.dll). But it only acts up on certain "forms" in the Database, in
> particular ones which retrieve from lots of columns. On these forms there
> is
> a long delay, and a little of the data is retrieved, but the rest of
> fields
> arent. And there are no error messages.
> I am trying to connect to a MS-SQL Server 2000 SP3a database through
> Access
> 2003 (frontend of database) on our only XP machine. All my NT machines
> connect
> easily, with no problems. A handful of Windows 2000 machines give me
> problems with the newer ODBC drivers, but if i would replace the
> SQLSRV32.DLL with a copy from the NT machines it would work ok.
> I thought upgrading the Service Pack from SP2 to SP3a would help but that
> didnt work. I cant figure out what the problem is, but it sounds (to me)
> similar to what is described in (FIX 814410 -
> http://support.microsoft.com/kb/814410 ) as a "memory leak"...could this
> be
> it? but the SP upgrade didnt fix/help...
> Please advise how I can fix it, or where i can look to figure out what the
> problem is.
> Thank you.
>

Connection between SQL Server 2000 SP3a and ODBC Driver

Database: SQL Server 2000 Developer Edition SP3a
Frontend: MS Access 2000 and Access 2003
A Custm-built Medical Records Database
I am having a problem connecting to my SQL server with certain ODBC drivers
(sqlsrv32.dll). But it only acts up on certain "forms" in the Database, in
particular ones which retrieve from lots of columns. On these forms there is
a long delay, and a little of the data is retrieved, but the rest of fields
arent. And there are no error messages.
I am trying to connect to a MS-SQL Server 2000 SP3a database through Access
2003 (frontend of database) on our only XP machine. All my NT machines
connect
easily, with no problems. A handful of Windows 2000 machines give me
problems with the newer ODBC drivers, but if i would replace the
SQLSRV32.DLL with a copy from the NT machines it would work ok.
I thought upgrading the Service Pack from SP2 to SP3a would help but that
didnt work. I cant figure out what the problem is, but it sounds (to me)
similar to what is described in (FIX 814410 -
http://support.microsoft.com/kb/814410 ) as a "memory leak"...could this be
it? but the SP upgrade didnt fix/help...
Please advise how I can fix it, or where i can look to figure out what the
problem is.
Thank you.Hi
SQL Profiler will indicate what queries are running slow. Try running it
from Query Analyser and check out their query plan. You may also want to
look at the statistics and how often they are updated. You may also want to
check the
Also you may want to check the version of MDAC you are running on each
machine using the MDAC component checker
http://msdn.microsoft.com/data/mdac/default.aspx
John
"desimaj" <desimaj@.discussions.microsoft.com> wrote in message
news:92716878-DB7C-4479-A96C-892F313C6F6B@.microsoft.com...
> Database: SQL Server 2000 Developer Edition SP3a
> Frontend: MS Access 2000 and Access 2003
> A Custm-built Medical Records Database
> I am having a problem connecting to my SQL server with certain ODBC
> drivers
> (sqlsrv32.dll). But it only acts up on certain "forms" in the Database, in
> particular ones which retrieve from lots of columns. On these forms there
> is
> a long delay, and a little of the data is retrieved, but the rest of
> fields
> arent. And there are no error messages.
> I am trying to connect to a MS-SQL Server 2000 SP3a database through
> Access
> 2003 (frontend of database) on our only XP machine. All my NT machines
> connect
> easily, with no problems. A handful of Windows 2000 machines give me
> problems with the newer ODBC drivers, but if i would replace the
> SQLSRV32.DLL with a copy from the NT machines it would work ok.
> I thought upgrading the Service Pack from SP2 to SP3a would help but that
> didnt work. I cant figure out what the problem is, but it sounds (to me)
> similar to what is described in (FIX 814410 -
> http://support.microsoft.com/kb/814410 ) as a "memory leak"...could this
> be
> it? but the SP upgrade didnt fix/help...
> Please advise how I can fix it, or where i can look to figure out what the
> problem is.
> Thank you.
>