statham
asked on
Access server problems
We have a number of Access databases running on a Windows 2003 server. Whenever a number of people start interacting with the databases the database services go down. Html pages still function but asp pages don't. Sometimes we notice the dreaded undeleteable ldb file lurking on the server. Rebooting the server every 10 minutes is not a solution. Anyone any idea how to stop it from happening?
<<Whenever a number of people start interacting with the databases the database services go down.>>
Need a little more detail. What service? What happens exactly?
<<Sometimes we notice the dreaded undeleteable ldb file lurking on the server. >>
Nothing unusual about that. It's just an indication that a user exited a database abnormally.
<<Anyone any idea how to stop it from happening?>>
Shane has already mentioned the closing of recordsets. Here are a few other things to check/do:
1. Turn off OPLOCKS (Opportunitic locking) in Windows - This is a registry change. See the following MSKB article:
http://support.microsoft.com/default.aspx?kbid=296264
2. Make sure the databases are not being virus scanned and "fixed".
3. Check for any client end problems. Do the users get error messages?
Need a little more detail. What service? What happens exactly?
<<Sometimes we notice the dreaded undeleteable ldb file lurking on the server. >>
Nothing unusual about that. It's just an indication that a user exited a database abnormally.
<<Anyone any idea how to stop it from happening?>>
Shane has already mentioned the closing of recordsets. Here are a few other things to check/do:
1. Turn off OPLOCKS (Opportunitic locking) in Windows - This is a registry change. See the following MSKB article:
http://support.microsoft.com/default.aspx?kbid=296264
2. Make sure the databases are not being virus scanned and "fixed".
3. Check for any client end problems. Do the users get error messages?
ASKER
We ended up calling Microsoft and found this fix:
http://support.microsoft.com/default.aspx?scid=kb;en-us;838306
Thanks for the help.
Andy
http://support.microsoft.com/default.aspx?scid=kb;en-us;838306
Thanks for the help.
Andy
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
In all of your asp pages, ensure that you explicitly close *every* recordset and connection AND set them to Nothing when you're done with them, plus make sure you are using the latest version of Jet (SP8).