IIS cuts off the OLE DB provider when Database error occurs
We are developing an Intranet-extranet system where we have an ACCESS
database in the backend.
We use ODBC-OLE DB to make the connection between the Server-side ASP and
the ACCESS database.
One of our queries in the ASP generated an error message- "Too many client
tasks" . Once this occurs, the next time you navigate to another page, and
read from the database again, an error then occurs, - "Provider error
80004005 (Unspecified error)" .
Once this happens, there is no way anyone can login to the database again.
What we need to do is to Stop the IIS service in the server and Start it
again, in order to enable clients to reconnect to the database.
The - "Too many client tasks" error can be solved by code work-around, and
error handling routines, but then, if other database errors outside the
handling routines still occur, which leads to the "Provider error 80004005",
what will happen?
Are there SERVER parameters that need to be configured in order to make the
OLE DB
Provider fault-tolerant?
Thanks.
Venny