Access 2003 - MSysDb error

Once in a while I got the error "The Microsoft jet Database engine could not find the object 'MSysDb"
Our databases is randomly crashing with this error from time to time.
Only solution is to revert to the backup copy.
I'm wondering what the cause for that.
Is it possibly because of multiple users with different versions of MS Access?
or People shutting down their computer without closing Access?
Who is Participating?
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
Here are some additional resources which I highly recommend you read over:

How to troubleshoot and to repair a damaged Access 2002 or later database

How to keep a Jet 4.0 database in top working condition

One of the BEST preventative maintenance things you can do (especially on a back end db in a split configuration as mentioned above) is FREQUENT Compact & Repair ... daily (say at night) if your db is in daily use.  And I speak from experience.

And Splitting your db (if not already) - as mentioned above - is almost MANDATORY for reliable performance.  This shows you how ... and it's very easy:

How to manually split a Access database in Microsoft Access

Splitting Microsoft Access Databases to Improve Performance and Simplify Maintainability

That sounds like corruption.

Assuming that you have restored to a good version of your database, read up on and take steps to prevent corruption - such as these:

One of the leading causes of corruption is users sharing a single front-end (user interface).  If you havent done so already, split your database into a shared Back-End located on a network drive and a Front-End distributed to each user and placed on each individuals local hard drive.
<or People shutting down their computer without closing Access?>

This is definitely on Allen Browne's list of causes of corruption - and a great reason to have a split database.  If a user corrupts their own front end file, it can easily be replaced without affecting anyone else.
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
btw ... the error message you are getting is guaranteed corruption, which at best ... can only be fixed by a repair service such as this one (keep this link):

And, in conjunction with frequent C&R ... backup daily - if in use daily.

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<Our databases is randomly crashing with this error from time to time.>>

 As has been said, most likely cause is corruption, but I've also seen some strange errors pop out of Access 2000/2003 when run under Windows Server 2003 and 2008.

  Typically they occur at either startup "Out of memory" "Workgroup file cannot be found", etc, or shutdown.  Shutdown is always a C0000005 memory violation.

  Doesn't sound like this would be the case from what you've said, but I thought I mention it if this happens to be a terminal services setup.

HNA071252Author Commented:
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.