I recently moved my e-commerce website over to an Godaddy dedicated host running IIS 2003 server. When I did this, the website began crashing because of "leaky memory". The application is written in Classic ASP with MS Access Database. My website crashes frequently because of what has been described as leaky memory. Apparently this is being caused because one or more of my ASP pages are not closing the database after each use. The site crashes anywhere from once a day to once every several days. (before the move, it ran for years without ever crashing)
This is the error I usually see:
Microsoft Office Access Database Engine error '80004005'
/LM/W3SVC/1/ROOT/[url removed, login to view], line 42
Currently I do a temp fix, either by using the MS Acess "Compress and Repair" function then a restart, or by resetting my application pools in IIS, or by ending the [url removed, login to view] application in task manager. These are each temporary fixes. If I do the compress and repair, the problem does not recur for several days. I am experiencing a lot of down time.
There may be more than one way to fix this, but I believe the best way is to find the offending pages, and correct the code so that the database is closed after each use.
PLease do not bid unless you know exactly how to identify the offending code, and also how to fix it. I am not interested in upgrading to [url removed, login to view] or any other solution. I am also not interested in a lot of experimentation by someone who wants to learn how to fix this kind of issue. The website is hellocalingcards com