• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1454
  • Last Modified:

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?
0
HNA071252
Asked:
HNA071252
3 Solutions
 
mbizupCommented:
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:
http://allenbrowne.com/ser-25.html

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.
0
 
mbizupCommented:
<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.
0
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
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
http://support.microsoft.com/kb/283849/EN-US

How to keep a Jet 4.0 database in top working condition
http://support.microsoft.com/?kbid=303528

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
http://support.microsoft.com/kb/304932

Splitting Microsoft Access Databases to Improve Performance and Simplify Maintainability
http://www.fmsinc.com/MicrosoftAccess/DatabaseSplitter/Index.html

mx
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
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):

http://www.everythingaccess.com/accessdatabaserepair.htm

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

mx
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<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.

Jim.
0
 
HNA071252Author Commented:
Thanks.
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now