Re: Connection Failure
From: William \(Bill\) Vaughn (billvaRemoveThis_at_nwlink.com)
Date: 07/06/04
- Next message: William \(Bill\) Vaughn: "Re: Sending Variable Values to Parameter In Stored Procedures."
- Previous message: Tarang Agarwal: "App hangs after E_FAIL status"
- In reply to: Clint Colefax: "Connection Failure"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 6 Jul 2004 09:41:07 -0700
I suspect that "connection error" is one of your own error messages--which
might not be from ADO. I also suspect the connection pool might be an issue.
If the problem goes away when the application is restarted, then that would
be more likely. If you suspect the new server, the connection timeout might
need to be increased. In any case, I usually recommend exception handlers
that fallback and try to reconnect on their own after having logged the
details of the failure to the event log. This way you can monitor what's
going on without a lot of trouble.
-- ____________________________________ 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. __________________________________ "Clint Colefax" <Clint Colefax@discussions.microsoft.com> wrote in message news:94D3BF88-F326-421C-94F9-1CD59D9C39C6@microsoft.com... > I was wondering if anyone can suggest any ideas for the cause of the following problem. > > I am getting the error: > "Connection Error" > when executing various select statements on a SQL2000 database using ADO from MDAC2.7 SP1 Refresh. > > This is a sporadic error that seems to only occur on one machine per day (very strange). This is happening in a production situation and I have been un-able to reproduce this in a development environment. > > I have checked the following so far, > that MDAC versions on both server and client match. > Sql2000 connection limit is not being violated (it is set to 0 with allows infinite connections) > Application, Security and System logs on both client and server. > Sql2000 error logs. > > Does anyone have any ideas where else I could look for a cause of this problem. My next step is to set up some statement output functions that will tell me the query that is causing the error, but due to the random location in the application that this is occurring, this would be a big job. > The company recently switched to a new server (machine, not sql version) and this is when this problem started to occur so I don't believe it is application based, rather a setting is sql. > > Thank you in advance.
- Next message: William \(Bill\) Vaughn: "Re: Sending Variable Values to Parameter In Stored Procedures."
- Previous message: Tarang Agarwal: "App hangs after E_FAIL status"
- In reply to: Clint Colefax: "Connection Failure"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
