Hello --
We are running various asp pages, attached to an Access 2000 db on the web server. We cannot determine when the users get this error -- and something at the server level must then be re-set for the pages to work again.
Any ideas on how we can address this without a server reset? Sorry about my ignorance -- we only have control of the ASP pages, large customer has control of the Web server.
We are running various asp pages, attached to an Access 2000 db on the web server. We cannot determine when the users get this error -- and something at the server level must then be re-set for the pages to work again.
Any ideas on how we can address this without a server reset? Sorry about my ignorance -- we only have control of the ASP pages, large customer has control of the Web server.