[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
>