should I just wait?

Common on shared hosting sites... usually due to bad coding by someone on the shared served... e.g. failure to close/release objects, setting up connections in global.asa, bad record set handling, filling up the Jet tmp directory, etc.

The other causes are associated with exceeding MS access limits or not having enough memory on the machine to load the ms access query results. Doing a compact and repair on offending DB's helps but may not fix.

Usually fixed by an iis restart but sometimes the server needs to be bounced. Some hosts will restart iis every day just to clean up MS Access. It's a good practice for company web sites.

It's worthwhile submitting a trouble ticket to your host whenever it happens as they can often id the account that's causing the problem and get the owner to clean up their act.

There's a few windows hosts that are starting to offer plans on servers without MS access in order to provide better uptime. If you're trying to run any sort of mission critical site on the cheap by using shared hosting, those hosts are a good option.


Edited by dpyers - 04 February 2006 at 4:35pm