[Shared Memory] ConnectionRead (recv()) ... error

Hi I've got error below when i ran a stored procedure:
[Microsoft][ODBC SQL Server Driver][Shared Memory]
ConnectionRead (recv())
General network error.
The same error occured in different places in each run.
The SP was running locally in Query Analyzer and there is
no network connection.
Anyone came across this before?
Cheers
Frank
What operating system are you running?
Vikram
"frk" <frk_wang@.hotmail.com> wrote in message
news:1a80001c44e83$e5ea8210$a101280a@.phx.gbl...
> Hi I've got error below when i ran a stored procedure:
> ----
> [Microsoft][ODBC SQL Server Driver][Shared Memory]
> ConnectionRead (recv())
> General network error.
> ----
> The same error occured in different places in each run.
> The SP was running locally in Query Analyzer and there is
> no network connection.
> Anyone came across this before?
> Cheers
> Frank
>
|||A couple of ideas.
1. Check the version of MDAC that you're running. Make sure it's patched
as well.
2. Disable Shared Memory using the SQL Client Network Utility. Then retest.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

[MSSQL7] Backup on network drive

Hi there,
Does anyone know if it's possible to perform a MSSQL7 database backup on a network drive instead of the local drives ?
...and if yes, how to proceed ?
It seems to be possible under MSSQL2000.
Many thanks for your help in advance,
MattEach MS-SQL device must be know as a local disk to control the IO writes, and a dump device follow this rule|||many thanks for this answer ;o)|||Originally posted by fadace
Each MS-SQL device must be know as a local disk to control the IO writes, and a dump device follow this rule

It is not a true:

backup DATABASE database
to disk ='\\networkserver\BACKUP\database.bak'|||hu interresting, gonna have a try with this !! thanks !! :)

is there no read/write error risks ? I mean, if we exclude the network transmission problems, of course.|||Originally posted by mattoo
hu interresting, gonna have a try with this !! thanks !! :)

is there no read/write error risks ? I mean, if we exclude the network transmission problems, of course.

If someone cuts a network cable it should be a problem but no more.|||Fine. Many thanks again for your help ;)

[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error

We have built an application (VB 6 with a SQL 2000 backend database)
in-house and from time to time, we get the dbnetlib error message. This erro
r
message seems to happen when the machine is just idle and is driving me nuts
.
The error message doesnt seem to have the issue while the user is actively
using the application. Could this problem have something to do with
connection pooling? If anyone has any ideas, it would be much appreciated.
Thanks in advance!
Mike HartmanWe have seen this from time-to-time. It seems that the connection "ages out"
after a long period of dormancy. The solution I use is to occasionally poll
the server to make sure it knows that the application is still alive. I
don't think it's a connection pooling issue. It looks like the transport
layer is being closed at the server end (in my case).
USE <initial catalog>
is enough to do the job.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:772A11BE-EF7D-4088-8654-9C29D15F1FCC@.microsoft.com...
> We have built an application (VB 6 with a SQL 2000 backend database)
> in-house and from time to time, we get the dbnetlib error message. This
> error
> message seems to happen when the machine is just idle and is driving me
> nuts.
> The error message doesnt seem to have the issue while the user is actively
> using the application. Could this problem have something to do with
> connection pooling? If anyone has any ideas, it would be much appreciated.
> Thanks in advance!
> Mike Hartman

[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error

We have built an application (VB 6 with a SQL 2000 backend database)
in-house and from time to time, we get the dbnetlib error message. This error
message seems to happen when the machine is just idle and is driving me nuts.
The error message doesnt seem to have the issue while the user is actively
using the application. Could this problem have something to do with
connection pooling? If anyone has any ideas, it would be much appreciated.
Thanks in advance!
Mike Hartman
We have seen this from time-to-time. It seems that the connection "ages out"
after a long period of dormancy. The solution I use is to occasionally poll
the server to make sure it knows that the application is still alive. I
don't think it's a connection pooling issue. It looks like the transport
layer is being closed at the server end (in my case).
USE <initial catalog>
is enough to do the job.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:772A11BE-EF7D-4088-8654-9C29D15F1FCC@.microsoft.com...
> We have built an application (VB 6 with a SQL 2000 backend database)
> in-house and from time to time, we get the dbnetlib error message. This
> error
> message seems to happen when the machine is just idle and is driving me
> nuts.
> The error message doesnt seem to have the issue while the user is actively
> using the application. Could this problem have something to do with
> connection pooling? If anyone has any ideas, it would be much appreciated.
> Thanks in advance!
> Mike Hartman

[DBNETLIB][ConnetionWrite (WrapperWrite()).]General network error. Check your ne

Hi
While running a DTS, many times the error message: "[DBNETLIB][ConnetionWrite (WrapperWrite()).]General network error. Check your network documentation." appears.
Does somebody knows why?

I am running the DTS from a computer (not the server where the DTS is stored) and it is connected without any problem when this happens.

Thanks!!
Regards
Lautaro - Argentina.Do you get your results that your looking for from the dts?|||This looks like a network connectivity issue to me. Check (1) Network Connectivity by pinging, etc. (2) Check O/S security and permissions on any files you are trying to access, and (3) Check SQL Server login issues (i.e. SQL Service logins etc).

Great Detailed Error Messages Brought To Us By Microsoft ! ;)

Michael D.|||Hi

I am getting the same Wrapperwrite error .

The server is windows NT running SQL6.5 with all the latest service packs
The client machines are running all different operating systems.
The ODBC connections on the clients and server use either TCP/IP or named pipes but I get the same error on all clients.
The clients and server connect to a sql 6.5 database and when requesting information about certain clients, not all, the wrapperwrite error comes up and i have to close the progarm down.

I have heard people say on forums the it could be to do with the network but please note that this also happens on the server!

can any one help Please

Cheers|||General Network errors are commonly caused by tcp resets on the network.
You'll want to capture as much data about the clients and the statements they're executing using PROFILER.

Select All Errors and Warnings
RPC: Completed, Starting, sp Recompile
TSQL BatchCompleted, BatchStarting
Stmt:Starting

[DBNETLIB][ConnectionWrite(WrapperWrite()).]General network error. Check your network

I'm getting the following error on Windows XP clients only:
[DBNETLIB][ConnectionWrite(WrapperWrite()).]General network error. C
heck
your network documentation.
This error seems to occur at random times of inactivity on my application.
Here is how I am configured:
Windows 2000 Server - Standard
Windows 2000 and Windows XP Pro Clients
SQL Server 2000
MDAC 2.7 or 2.8 on various clients
The error does not occur on Windows 2000 clients, only on Windows XP Pro
clients.
My application first opens a connection to a server database. Every 2
minutes an application watchdog timer triggers and attempts to write an
timestamp value to a data table. After some period of time (seemingly
random) the attempted write fails and I get the above error message,
followed by a "Connection failure." error.
Can anyone point me in the right direction on how to fix this problem?
Thanks,
Al WillisHi Al,
I would try to capture the problem using both SQL Profiler on the
backend, and network traces on the client machines.
General Network errors are commonly caused by tcp resets on the network.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Most probably problem with NIC drivers or network harware on specific
computers.
Also it will much help if you do not expect an open connection to stay
connected forever and make new connection after for each triggering of your
watchdog.
Bojidar Alexandrov
"Al Willis" <alwillisj01@.sbcglobal.net> wrote in message
news:409aa583$1@.newsgroups.borland.com...
> I'm getting the following error on Windows XP clients only:
> [DBNETLIB][ConnectionWrite(WrapperWrite()).]General network error.
Check
> your network documentation.
> This error seems to occur at random times of inactivity on my application.
> Here is how I am configured:
> Windows 2000 Server - Standard
> Windows 2000 and Windows XP Pro Clients
> SQL Server 2000
> MDAC 2.7 or 2.8 on various clients
>
> Development Software
> --
> Delphi 6, update 2
> CoreLabs dbExpress driver for SQL Server
> The error does not occur on Windows 2000 clients, only on Windows XP Pro
> clients.
> My application first opens a connection to a server database. Every 2
> minutes an application watchdog timer triggers and attempts to write an
> timestamp value to a data table. After some period of time (seemingly
> random) the attempted write fails and I get the above error message,
> followed by a "Connection failure." error.
> Can anyone point me in the right direction on how to fix this problem?
> Thanks,
> Al Willis
> Enviroment
> --
> Windows 2000 Server - Standard
> Windows 2000 and Windows XP Pro Clients
> SQL Server 2000
> MDAC 2.7 or 2.8 on various clients
>
>|||Kevin,
Thanks for the reply.
I looked at the SQL Profiler. What categories should I trace to find my
problem?
Al Willis|||Hi Al,
You'll want to capture as much data about the clients and the
statements they're executing.
Select All Errors and Warnings
RPC: Completed, Starting, sp Recompile
TSQL BatchCompleted, BatchStarting
Stmt:Starting
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

[DBNETLIB][ConnectionWrite (WrapperWrite()).] General Network error. Check

Dear All,
I am getting this error frequently and some times sql server is getting
stopped automatically.
[DBNETLIB][ConnectionWrite (WrapperWrite()).] General Network error. Check
you network documentation.
Can any one help me out to get rid of this.
OS : Windows 2000 professional
SQL Server version is 2000
Thanks and Regards,
PeriHi Peri,
Here are some things I would do if I were in your shoes:
1) Check the Event Log for Network problems... Specif with the Network Card
2) If the SQL Server is in another subnet, check the router for errors
3) Check HOW you are connecting, use TCPIP if you can
4) Ping your machine so it pings over and over (see /flags help).. See if
you ever get dropped
5) Check for issues with the CLIENT machine to
That's all I can think of right now.. Good luck!
Erik
"Peri" <lperi@.CSPL.com> wrote in message
news:emmKD1CaFHA.3132@.TK2MSFTNGP09.phx.gbl...
> Dear All,
> I am getting this error frequently and some times sql server is getting
> stopped automatically.
> [DBNETLIB][ConnectionWrite (WrapperWrite()).] General Network error. Check
> you network documentation.
> Can any one help me out to get rid of this.
> OS : Windows 2000 professional
> SQL Server version is 2000
> Thanks and Regards,
> Peri
>|||I ran across this problem on my XP machine that went away when I re-loaded t
he machine and did NOT install Service Pack 2 of Windows. I still haven't f
igured out how to fix it yet. Maybe this information will lead you in the r
ight direction.

[DBNETLIB][ConnectionWrite (send()).]General network error

SQL Server Spec
SQL 2000, 8.00.2187 SP4 standard edition
windows 2003 SP1
sqlserver driver 2000.86.1830.00
webserver
windows 2003 r2, standard edition service pack2
sqlserver driver 2000.86.3959.00
we received "intermittance"
Error Number -2147467259 (&H80004005)
[DBNETLIB][ConnectionWrite (send()).]General network error. Check yo
ur
network documentation.
We already do this as mention in microsoft website
on SynAttackProtect:
http://support.microsoft.com/defaul...kb;en-us;899599
Any idea or any one have experience on this?
Cheers,
Liang Yewsorry,
SQL Server
windows 2003 SP2
SQL 2000, 8.00.2187 SP4 standard edition
sqlserver driver 2000.86.3959.00
"soonyu" wrote:

> SQL Server Spec
> SQL 2000, 8.00.2187 SP4 standard edition
> windows 2003 SP1
> sqlserver driver 2000.86.1830.00
> webserver
> windows 2003 r2, standard edition service pack2
> sqlserver driver 2000.86.3959.00
> we received "intermittance"
> Error Number -2147467259 (&H80004005)
> [DBNETLIB][ConnectionWrite (send()).]General network error. Check
your
> network documentation.
> We already do this as mention in microsoft website
> on SynAttackProtect:
> http://support.microsoft.com/defaul...kb;en-us;899599
> Any idea or any one have experience on this?
> Cheers,
> Liang Yew

[DBNETLIB][ConnectionWrite (send()).]General network error

SQL Server Spec
SQL 2000, 8.00.2187 SP4 standard edition
windows 2003 SP1
sqlserver driver 2000.86.1830.00
webserver
windows 2003 r2, standard edition service pack2
sqlserver driver 2000.86.3959.00
we received "intermittance"
Error Number -2147467259 (&H80004005)
[DBNETLIB][ConnectionWrite (send()).]General network error. Check your
network documentation.
We already do this as mention in microsoft website
on SynAttackProtect:
http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
Any idea or any one have experience on this?
Cheers,
Liang Yew
sorry,
SQL Server
windows 2003 SP2
SQL 2000, 8.00.2187 SP4 standard edition
sqlserver driver 2000.86.3959.00
"soonyu" wrote:

> SQL Server Spec
> SQL 2000, 8.00.2187 SP4 standard edition
> windows 2003 SP1
> sqlserver driver 2000.86.1830.00
> webserver
> windows 2003 r2, standard edition service pack2
> sqlserver driver 2000.86.3959.00
> we received "intermittance"
> Error Number -2147467259 (&H80004005)
> [DBNETLIB][ConnectionWrite (send()).]General network error. Check your
> network documentation.
> We already do this as mention in microsoft website
> on SynAttackProtect:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
> Any idea or any one have experience on this?
> Cheers,
> Liang Yew

[DBNETLIB][ConnectionWrite (send()).] General network error.

Hi,
in our environment
- Windows XP
- SQL Server Express 2005
- Internet connection via TCP/IP protocol

The described network error occurs, when we unplug the network cable:
[DBNETLIB][ConnectionWrite (send()).] General network error.

The affected database resides on the locally installed SQLExpress, it doesn't use any network connections. The error doesn't occur immediately, in most cases there are up to 30 seconds where data can be (correctly!) written to the recordset, but after that timeout the connetion is broken.

We already tried out the described workarounds:
- disable named pipes protocol
- set SynAttackProtect=0 in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

The error doesn't occur with MSDE (SQL 2000) or under Vista.

Thanks for help!

Mathias

I suggest using shared memory to connect locally or making sure your server specification is one that correctly gets resolved to use the loopback (e.g. .\ or (local) or localhost). You may also want to see if your hosts file has an entry for the machine to make sure it resolves its own name. Right now, it appears as though your communications are going out over the network. You may have some amount of data transfer after unplugging the cable because the network connection is buffered, so the server still has that much data in its network buffer before it runs out. I think the connection timeout is consuming the bulk of that 30 seconds. Vista most likely has its own hostname in its hosts file, or has some other trick for self-resolving its computer name. More than likely, your instance of SQL 2000 is using shared memory to connect or using a different specification of the hostname.

Hope that helps,

John

[DBNETLIB][ConnectionRead (WrapperRead()).]General network error. Check your network docum

Starting to get really tired of this error message, it's completely random
and happens usually on long running queries, it is not a network failure
since the sql server is on the same machine.
Things I have tried:
o Updating MDAC
o Changing connection string
o Using only TCP/IP
o Using only pipes
o Removing shared memory option
The only articles on MS site I can find talks about doing backups or
running some built in sp which is not what I'm doing.
One of the articles refer to MDAC 2.8 SP1 which does not exist !
Doing some googling reveals that this is not an uncommon problem
but so far no solutions.
This is starting to have serious side effects and needs to be solved,
please help with any ideas !
Thanks.
PL.Talke a look at the following BLOG. This helped fix my "General Networ
Errors"...
'The infamous General Network Error' (http://tinyurl.com/4yc7k)
'SQL Data Provider Patch' (http://support.microsoft.com/?kbid=328476
-
cbuzzett
----
Posted via http://www.mcse.m
----
View this thread: http://www.mcse.ms/message389824.htm|||cbuzzetta wrote:
> *Talke a look at the following BLOG. This helped fix my "General
> Network Errors"...
> 'The infamous General Network Error' (http://tinyurl.com/4yc7k)
> 'SQL Data Provider Patch' (http://support.microsoft.com/?kbid=328476)
> *
Just FYI I was getting this error on archived tables that no longer had
indexes - added indexes for them on the key fields and the error
disappeared. May not be relevant but it was the fix for me : )
X
DocFKNx
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message389824.html

[DBNETLIB][ConnectionRead (WrapperRead()).]General network error. Check your network d

Starting to get really tired of this error message, it's completely random
and happens usually on long running queries, it is not a network failure
since the sql server is on the same machine.
Things I have tried:
o Updating MDAC
o Changing connection string
o Using only TCP/IP
o Using only pipes
o Removing shared memory option
The only articles on MS site I can find talks about doing backups or
running some built in sp which is not what I'm doing.
One of the articles refer to MDAC 2.8 SP1 which does not exist !
Doing some googling reveals that this is not an uncommon problem
but so far no solutions.
This is starting to have serious side effects and needs to be solved,
please help with any ideas !
Thanks.
PL.Talke a look at the following BLOG. This helped fix my "General Network
Errors"...
'The infamous General Network Error' (http://tinyurl.com/4yc7k)
'SQL Data Provider Patch' (http://support.microsoft.com/?kbid=328476)
cbuzzetta
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message389824.html|||cbuzzetta wrote:
> *Talke a look at the following BLOG. This helped fix my "General
> Network Errors"...
> 'The infamous General Network Error' (http://tinyurl.com/4yc7k)
> 'SQL Data Provider Patch' (http://support.microsoft.com/?kbid=328476)
> *
Just FYI I was getting this error on archived tables that no longer had
indexes - added indexes for them on the key fields and the error
disappeared. May not be relevant but it was the fix for me : )
X
DocFKNx
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message389824.html

[DBNETLIB][ConnectionRead (WrapperRead()).]General network error.

I am intermittantly getting this error in a background VB app. It runs
from task scheduler before I get to work. The last 5 days it has failed
every day. The task opens a connection to an MSDE instance, deletes all
rows from two tables and then reloads them from another database. Then
when attempting to delete all rows from a third table it dies. If I
rerun it once I get to work it has no problems. If I schedule the task
to run again right after the problem run, it works fine.
Ideas?
TomLooks like I'll have to reply to my own post.
In my case it appears that the problem was a command which was taking
longer than 30 seconds to complete.
cnEI.Execute "Delete from Empinfo", , adCmdText
I changed the connection command timeout
cnEI.CommandTimeout = 90
and now all is well.
Tom
Tom Wells wrote:
> I am intermittantly getting this error in a background VB app. It runs
> from task scheduler before I get to work. The last 5 days it has failed
> every day. The task opens a connection to an MSDE instance, deletes all
> rows from two tables and then reloads them from another database. Then
> when attempting to delete all rows from a third table it dies. If I
> rerun it once I get to work it has no problems. If I schedule the task
> to run again right after the problem run, it works fine.
> Ideas?
> Tom
>

[DBNETLIB][ConnectionRead (recv()).]General network error. Check your network do

Hello all,

We have a Windows 2003 Web Edition server serving a site through IIS. It connects to a Windows 2003 Standard Edition server running SQL 2000 SP3a.

This site receives the following error as seen in the topic:
[DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.

We've configured the server network utility to only allow TCP/IP connections. The connection string for the site is as follows:

<%
' FileName="Connection_ado_conn_string.htm"
' Type="ADO"
' HTTP="false"
' Catalog=""
' Schema=""
MM_connSpankMSSQL_STRING = "Provider=sqloledb;Data Source=SERVER_IP,1433;Network Library=DBMSSOCN;Initial Catalog=ourmaindb_1;User ID=ourmaindb_1;Password=hotcookies;"
%>

Any ideas or tips on solving this issue? We've noticed it is due to larger queries as smaller ones do work with no problems.

The servers are behind a BSD box running iptables, has 1433,1434 along with standard web ports wide open. Anything outbound is allowed.

Some further testing via ODBC on the IIS server improved things. No more connection pooling for the SQL Server driver allows for 1/3 of the query to run. Still 2/3s of it doesn't show up, and that general network error message appears.

Should have 330 rows if it works right.See if this webcast can help you any:

http://support.microsoft.com/servicedesks/webcasts/seminar/shared/asp/view.asp?url=/servicedesks/webcasts/en/WC072804/manifest.xml

[DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General network error.

Hi,

I have a classic ASP application that has been running on Win2003,IIS6 and SQL2000 for 3 years without a single error.

We've just moved to SQL2005 enterprise and we're getting the following intermittent error.

Microsoft OLE DB Provider for SQL Server error '80004005'

[DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General network error. Check your network documentation.

Any ideas where to start?

this is a common connection problem and without details like your current sql server configuration and connection string, we just can write our guesses,

first, if you have not installed latest service pack for sql serer 2005, please install it before trying the following suggestions,

second, you can check if you have enabled remote connections on sql server, to check this setting go to sql server surface area configuration -> surface area configuration for services and connections -> remote connections and enable remote connections by selection "local and remote connections" and using tcp/ip only.

if the previous step did not solve your problem, you can check your connection string, please examine the following connection strings,
for odbc connections:
- Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword;
- Driver={SQL Native Client};Server=myServerAddress;Database=myDataBase;Trusted_Connection=yes;

for ole db connections
- Provider=SQLNCLI;Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword;
- Provider=SQLNCLI;Server=myServerAddress;Database=myDataBase;Trusted_Connection=yes;

for .net connections
- Data Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;
or
- Server=myServerAddress;Database=myDataBase;User ID=myUsername;Password=myPassword;Trusted_Connection=False;
- Data Source=myServerAddress;Initial Catalog=myDataBase;Integrated Security=SSPI;
or
- Server=myServerAddress;Database=myDataBase;Trusted_Connection=True;

also if you are connecting with an sql server account, please check if you have set authentication mode of sql server to mixed mode.

and finally if your sql server is on a seperate machine, please be sure that there is no firewall or router is locking the communication of iis and sql server.

if these won't help you to solve the problem, please give us some details like
- your connectionstring
- is your sql server is on another computer
- configuration details of your sql server (like active net libraries, authentication details)

|||hi kadir,

thank-you for the quick reply. i will check all your suggestions and report back.

in the meantime, sql and webserver are all on the same server and the connection string is:-

databaseServer = "PROVIDER=SQLOLEDB;DATA SOURCE=pretty.ucc.usyd.edu.au;UID=xxx;PWD=xxx;DATABASE=xxx"|||hi kadir,

i must confess i'm not an sql server expert.

1. latest service pack and mdac were already installed.

2. allow remote connections is enabled. i couldn't see where (see point 3) using tcp/ip was. i'm using the ms sql management studioto find this information.

3. using sql server configuration manager i could find the following.

sql server 2005 network config - protocols for msqlserver
shared memory enabled
named pipes disabled
tcp/ip enabled
via disabled

sql native client config - client protocols
shared memory enabled
tcp/ip enabled
names pipes enabled
via disabled

4. we are connecting using an sql account. however, i couldn't see the option to allow mixed. i could only choose between windows authentication and sql server authentication.

thanks|||ok, just found the sql server surface area configuration. will check and report back.
|||remote connections is set to "local and remote connections" and using tcp/ip only.|||sql server and windows authentication mode were selected. so it looks like everything was configured they way you wanted.|||

Hi peter, sorry for the delay,

sql server and iis is on same machine so can you please test the following connectionstrings:
Provider=SQLNCLI;Server=(local);Database=xxx;Uid=xxx;Pwd=xxx
or
Provider=SQLNCLI;Server=127.0.0.1;Database=xxx;Uid=xxx;Pwd=xxx

and please inform me about the result.

[DBNETLIB] General Network Error - (I have included the event log dump.)

I have a MS MSDE 2000 database that is serving 3 database clients. Intermittently, randomly, and more important daily, my clients receive a "SQL Database Connection Error", and they are kicked out of the database. This appears to be correlated when they are writing/retrieving a record.

MS MSDE then writes the following error in it's event log.

----------
Source: SORules.Gateway.LogErrors
Process ID: 2328

Database connection lost
Error #-2147467259
[DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.
(Source: Microsoft OLE DB Provider for SQL Server)
(SQL State: 08S01)
(NativeError: 11)
No Help file available

OpenRsRead
System.Runtime.InteropServices.COMException (0x80004005): [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.
at ADODB.RecordsetClass.Open(Object Source, Object ActiveConnection, CursorTypeEnum CursorType, LockTypeEnum LockType, Int32 Options)
at SORules.Gateway.OpenRsRead(Command& C, Boolean& ForwardOnlyCursor)
Stack trace:
at ADODB.RecordsetClass.Open(Object Source, Object ActiveConnection, CursorTypeEnum CursorType, LockTypeEnum LockType, Int32 Options)
at SORules.Gateway.OpenRsRead(Command& C, Boolean& ForwardOnlyCursor)
----------

Any help, suggestions, or thoughts would be greatly appreciated. This is for a small business line of business application that is critical for everyday business operations. These problems have resulted in lost work, short tempers, and a just frank frustration.

I am just getting started with MS SQL technologies and really need some quality help.

Thank you for your time, and have a great day.

Cheers,
MarkBasically this means that there is a "connection problem" between the client and server parts of the SQL Server software. The error isn't specific because there are way too many places for these kinds of problems to hide, most of which can't be found by the machine that notices the problem.

If the people are having regular network problems (slowness, problems reaching specific machines in their networks, web browsing issues, etc), then fixing those problems should also fix the SQL problem.

If they aren't having regular network problems, then you have to play a bit of Sherlock Holmes to track down the culprit. If I were in this situation, I'd check:

1. Visit the Windows Update site from each machine using SQL. Be sure to get the latest windows and driver patches.
2. Ping the database server from each machine, investigate any significant differences in ping times.
3. Check the Network Interface Card in each machine (including the server)
4. Check the network hardware (routers, etc)
5. Come back here if that doesn't help.

-PatP

[DBNETLIB] 2147467259(80004005) [Connection Write (Send()),] General Network Error

HI all

I am facing a problem on sql server 7 Desktop Engine with front end VB6 and ADO 2.8 my OS is windows 2000 Professional.

ie. I am doing appendchunk to add image files on SQL Table it works fine for Approximately 130 MB, But i am trying to add 249 MB size file it will be showing these error Message.

[DBNETLIB] 2147467259(80004005) [Connection write(send()),] General Network Error check your network documentation.

I do so many way to correct this problem but it stuck up overthere.

In vb appendchunk is completed and the error when Updated command starts (update command also going a long way then show the above mentioned error.

Any body have any idea or clue just tel me for experiment. and complete my project.

Once again I request you please help me.

Thanks in advance.

Note : it is working with Access Database very fine I am tested it But in Access not allow me to store me lots of images its only allow 2 GB storage totally in a table.

Error code 0x80004005 is a generic error that indicates something failed. Either the client or server broke the connection.

Two things you should try:

1. Attach SQL Profiler to trace the execution to determine if it is the client or server that is terminating the connection.

2. Check the ERRORLOG if there are any problems with the server.

[DBMSSOCN]General network error.

We've recently rebuilt our database and we're running an ASP front end.
Everything was working just fine today until about 15 minutes ago when no
one could search the database and when they attempted to do so, they
received the following error:
"[DBMSSOCN]General network error. Check your network settings ..."
I found a MSKB article on this but it didn't seem to be relevant. Any idea
what could be causing this? This is the 2nd time in as many days that the
site has worked for the majority of the day and then all of a sudden
crashed. I believe this has something to do with the way I'm connecting to
the SQL server.
Thanks!
James
Hi,
could you please write a configuration of the server (OS, etc.).
It could be a problem with Named Pipes.
Danijel
"James" <cppjames@.aol.com> wrote in message
news:%23RL5cs28EHA.2600@.TK2MSFTNGP09.phx.gbl...
> We've recently rebuilt our database and we're running an ASP front end.
> Everything was working just fine today until about 15 minutes ago when no
> one could search the database and when they attempted to do so, they
> received the following error:
> "[DBMSSOCN]General network error. Check your network settings ..."
> I found a MSKB article on this but it didn't seem to be relevant. Any
> idea
> what could be causing this? This is the 2nd time in as many days that the
> site has worked for the majority of the day and then all of a sudden
> crashed. I believe this has something to do with the way I'm connecting
> to
> the SQL server.
> Thanks!
> James
>
|||SQL Server 2000, Windows 2003. Thanks for the suggestion, I'll look into
that.
"Danijel Novak" <danijel.novak@.snt.si> wrote in message
news:hLuDd.8040$F6.1370782@.news.siol.net...[vbcol=seagreen]
> Hi,
> could you please write a configuration of the server (OS, etc.).
> It could be a problem with Named Pipes.
> Danijel
>
> "James" <cppjames@.aol.com> wrote in message
> news:%23RL5cs28EHA.2600@.TK2MSFTNGP09.phx.gbl...
no[vbcol=seagreen]
the
>

[DBMSSOCN]General network error.

We've recently rebuilt our database and we're running an ASP front end.
Everything was working just fine today until about 15 minutes ago when no
one could search the database and when they attempted to do so, they
received the following error:
"[DBMSSOCN]General network error. Check your network settings ..."
I found a MSKB article on this but it didn't seem to be relevant. Any idea
what could be causing this? This is the 2nd time in as many days that the
site has worked for the majority of the day and then all of a sudden
crashed. I believe this has something to do with the way I'm connecting to
the SQL server.
Thanks!
JamesHi,
could you please write a configuration of the server (OS, etc.).
It could be a problem with Named Pipes.
Danijel
"James" <cppjames@.aol.com> wrote in message
news:%23RL5cs28EHA.2600@.TK2MSFTNGP09.phx.gbl...
> We've recently rebuilt our database and we're running an ASP front end.
> Everything was working just fine today until about 15 minutes ago when no
> one could search the database and when they attempted to do so, they
> received the following error:
> "[DBMSSOCN]General network error. Check your network settings ..."
> I found a MSKB article on this but it didn't seem to be relevant. Any
> idea
> what could be causing this? This is the 2nd time in as many days that the
> site has worked for the majority of the day and then all of a sudden
> crashed. I believe this has something to do with the way I'm connecting
> to
> the SQL server.
> Thanks!
> James
>|||SQL Server 2000, Windows 2003. Thanks for the suggestion, I'll look into
that.
"Danijel Novak" <danijel.novak@.snt.si> wrote in message
news:hLuDd.8040$F6.1370782@.news.siol.net...
> Hi,
> could you please write a configuration of the server (OS, etc.).
> It could be a problem with Named Pipes.
> Danijel
>
> "James" <cppjames@.aol.com> wrote in message
> news:%23RL5cs28EHA.2600@.TK2MSFTNGP09.phx.gbl...
no[vbcol=seagreen]
the[vbcol=seagreen]
>

[DBMSSOCN]General network error.

We've recently rebuilt our database and we're running an ASP front end.
Everything was working just fine today until about 15 minutes ago when no
one could search the database and when they attempted to do so, they
received the following error:
"[DBMSSOCN]General network error. Check your network settings ..."
I found a MSKB article on this but it didn't seem to be relevant. Any idea
what could be causing this? This is the 2nd time in as many days that the
site has worked for the majority of the day and then all of a sudden
crashed. I believe this has something to do with the way I'm connecting to
the SQL server.
Thanks!
JamesHi,
could you please write a configuration of the server (OS, etc.).
It could be a problem with Named Pipes.
Danijel
"James" <cppjames@.aol.com> wrote in message
news:%23RL5cs28EHA.2600@.TK2MSFTNGP09.phx.gbl...
> We've recently rebuilt our database and we're running an ASP front end.
> Everything was working just fine today until about 15 minutes ago when no
> one could search the database and when they attempted to do so, they
> received the following error:
> "[DBMSSOCN]General network error. Check your network settings ..."
> I found a MSKB article on this but it didn't seem to be relevant. Any
> idea
> what could be causing this? This is the 2nd time in as many days that the
> site has worked for the majority of the day and then all of a sudden
> crashed. I believe this has something to do with the way I'm connecting
> to
> the SQL server.
> Thanks!
> James
>|||SQL Server 2000, Windows 2003. Thanks for the suggestion, I'll look into
that.
"Danijel Novak" <danijel.novak@.snt.si> wrote in message
news:hLuDd.8040$F6.1370782@.news.siol.net...
> Hi,
> could you please write a configuration of the server (OS, etc.).
> It could be a problem with Named Pipes.
> Danijel
>
> "James" <cppjames@.aol.com> wrote in message
> news:%23RL5cs28EHA.2600@.TK2MSFTNGP09.phx.gbl...
> > We've recently rebuilt our database and we're running an ASP front end.
> > Everything was working just fine today until about 15 minutes ago when
no
> > one could search the database and when they attempted to do so, they
> > received the following error:
> >
> > "[DBMSSOCN]General network error. Check your network settings ..."
> >
> > I found a MSKB article on this but it didn't seem to be relevant. Any
> > idea
> > what could be causing this? This is the 2nd time in as many days that
the
> > site has worked for the majority of the day and then all of a sudden
> > crashed. I believe this has something to do with the way I'm connecting
> > to
> > the SQL server.
> >
> > Thanks!
> > James
> >
> >
>