WSAECONNREFUSED on a TCP socket breaks an open ADO connection.
- From: "Ricardo Vazquez" <rvazquez@xxxxxxxxx>
- Date: Thu, 26 May 2005 16:46:35 +0200
In the same program I have an open ADO database connection to SQL Server,
and a TCP socket.
When the socket tries to connect to a service that is inactive, the connect
statement returns WSAECONNREFUSED (10061) --> that's Ok.
BUT when I try to write this error on the database, ADO throws this error:
0x80004005 [DBNETLIB][ConnectionWrite (send()).] General network error.
After this has happened:
- I can't write to the database any more: I get 0x80004005 Connection Error.
- If I try to destroy the database object, create it again and open the
database again I get this error: 0x80004005 [DBNETLIB][ConnectionOpen
(Connect()).] SQL Server does not exists or access has been denied. But,
obviously the database is still there and I can reach it throught any other
program or restarting mine!
Does anyone know what can be happening?
How can I prevent or avoid this unsolicited shut down of the database
connection?
In case that this is not possible, is there any way to successfully restart
my connection to the database?
Thank you very much in advanced,
Ricardo Vázquez.
Madrid, Spain.
.
- Follow-Ups:
- Re: WSAECONNREFUSED on a TCP socket breaks an open ADO connection.
- From: William \(Bill\) Vaughn
- Re: WSAECONNREFUSED on a TCP socket breaks an open ADO connection.
- Prev by Date: Re: Connection object question
- Next by Date: ADODB.Recordset Open progress indicator
- Previous by thread: Connection object question
- Next by thread: Re: WSAECONNREFUSED on a TCP socket breaks an open ADO connection.
- Index(es):
Relevant Pages
|
|
