"unspecified error" (-2147467259) from MSADORA
From: Rohit Wason (Wason_at_discussions.microsoft.com)
Date: 03/19/05
- Next message: Victor: "Changes are not visible with ADO and MS Access."
- Previous message: Gérard Leclercq: "Re: inserting data problem with something having to be declared"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 19 Mar 2005 02:29:02 -0800
Hi,
We have an application that's already in production for past 7-8 months. And
lately we have seen the following issue happen very frequently (once in a
day) and when this happens we have to restart the app. Being a server
application (that is supposed to cater to the clients' requests all the
time), this downtime is something that's killing us..
1) There are at least 13 clients now, that run the client s/w that connected
to the sever application thru Winsock. The clients don't reside in the office
network - they connect via Cellular Dial-up
2) The server is developed using VB6 (SP5) and ADO 2.7. Oracle 9i is used as
back-end. It runs on a Win2000 box
3) The server is supposed to query various databases in office (about 30
different kinds of queries). These queries are not in stored procedure (yet,
but we might move to SPs when this problem resolves). We make SQLs at runtime
and fire them using Recordset.Open
4) The server being able to handle multiple clients at a time (using
DoEvents, not multithreading), has to fire queries for multiple clients at
times. But since the server maintains one connection per connected-client at
a given time, there's no mutual dependence in the connections.
5) Now the problem: While firing the query, the server (once a day, not
always) gets an error
Number : -2147467259
Source : Microsoft Cursor Engine
Raising Procedure : BBASSRVR.clsAsyncData.FetchData
Description : Data provider or other service returned an E_FAIL status.
This description is still some useful. Sometimes the error description is
"Unspecified Error"
6) In finding documentation in web for this/similar issues people have
faced, I am of an opinion that this is due to using client-side cursors. Is
that correct? Are client-cursors really that bad? Coz, if I had to change the
recordsets to server-side cursors, I am not able to use Recordset.Save (xml)
method
7) Could it be an 'Oracle8i to 9i' thing? We shifted to 9i since 4-5 months
now. And as far as I remember, I didn't see this weird error back then. Is it
the drivers that are causing the problem?
I am having a hard time chasing these problems these days, let alone the
solution to them
Any directions?
Thanks,
Rohit
- Next message: Victor: "Changes are not visible with ADO and MS Access."
- Previous message: Gérard Leclercq: "Re: inserting data problem with something having to be declared"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
