I have a VB6 application running on an SQLServer database. At first, the co
nnection to the database succeeds, a number of sql subsequent statements (bo
th select and update statements) succeed and then from some point on (after
about 80 sql statements), I
get the following error message : -2147467259 : [Microsoft][ODBD SQL
Server Driver]Communication link failure.
This happens on a number of P.C.'s, however not on all of them.
Thanks,
John DesmetThis sounds like it might share a few common features with a posting I made
here on March 5, under the heading:
Re: Occasional "Timeout expired" message - on SP that should take 1 second
What do you think? This syndrome sometimes also generates the
"Communication Link Failure" message.
- ITFred|||Thank you for your reply. At the end of the day (literally), we found out t
hat the Symantic Client Firewall is causing the problem. When it is turned
off, the problem no longer occurs. Now, we have to modify a number of firew
all settings.
Thanks,
John Desmet
Showing posts with label subsequent. Show all posts
Showing posts with label subsequent. Show all posts
Friday, February 24, 2012
Communication link failure
Labels:
application,
communication,
connection,
database,
failure,
link,
microsoft,
mysql,
number,
oracle,
running,
server,
sql,
sqlserver,
statements,
subsequent,
succeeds,
vb6
Subscribe to:
Posts (Atom)