Re: -2147467259 Unspecified Error

From: William \(Bill\) Vaughn (billvaRemoveThis_at_nwlink.com)
Date: 04/29/04 

Date: Wed, 28 Apr 2004 19:42:46 -0700

Humm. I'm just guessing here, but consider that ADO also uses a connection
pool. If the server fails for some reason (high severity level or other
issues), the connection in the pool will be "dented". That is, the
connection will be unusable if accessed again. Is this a Windows forms
application, a middle-tier component or an ASP application? In your
situation, the application would work for awhile, but if the server dented
the connection, it might not be able to connect without getting an
exception. I would trap the exception and retry the open. If it does not
work, I could be that the pool is full and needs to be flushed. It should
flush itself as the connections are attempted--one at a time. Restarting the
app creates a new pool...

hth 

-- 
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
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.
__________________________________
"Terry" <anonymous@discussions.microsoft.com> wrote in message
news:E9C992DB-4B40-4B49-B393-8A0303149576@microsoft.com...
> -2147467259 Unspecified Error.  That's what I get when opening an ADO
connection in VB6.  The open works fine in production scenerio for many
weeks and then out of nowhere, I get this error.  It happens about every 2-3
weeks.  I restart VB application and it will run for another period of time.
I'm suspicious that the ADO has lost contact with the database in a way that
it cannot recover.  I don't think I have any control over this, but I can
trap for this.  But once trapped, I cannot fix it wihtou killing .exe and
starting it again.  Is there a way to restart/kick the ADO for the .exe
without having to bring down the entire .exe?  Any other ideas or approaches
welcome!
>
> Thanks,
> Terry