Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Access XP Corrupt MSysDb????

Status
Not open for further replies.

rokerij

Technical User
Joined
Feb 12, 2003
Messages
199
Alright, this has happened a couple of times in the last thirty days. When we go to open Access we get an error message that the you or another user closed Access prematurely while a database was open. From what I can tell someone shuts down the database while something else is running in the background, possibly a query. Not real sure. The message than asks if you would like to attempt to repair the database. After about 10 minutes or so the screen says 'Ready' in the bottom right corner, but the hour glass never leaves. The task Manager says that Access is "Not Responding", so we end task. When you go to open the database you get a different error message. It is something to the effect that the system can not find 'MSysDb', make sure the file location and name are correct. Does anyone have any idea what may cause this in the first place and is there any way of saving my database? Luckily we made a back up copy this morning, but there is a days worth of work from 6 users that may be lost, and it's important that we retrieve it. I thank you in advance for your time and efforts!
 
I had this happen the other day. I just compacted and repaired both the back end and the front end and then relinked the tables and everything was fine. Not sure if it is the same issue, but thought I would share since it sounded like the errors I got. You might also want to make sure you compile. I seem to fix a lot of strange things by just compiling and compact and repairing.

Dawn
 
When I compacted and repaired, and tried to open it, I got
"The Microsoft Jet database engine could not find the object 'MSysDb'. Make sure the object exists and that you spell it's name and the path name correctly. So, I guess my question is this, what do you mean by both back and front? How were you able to relink tables if the database will not open? We do a compacting three days a week, is what you mean by compiling, or is there another step? I thank you Dawn! Giving me something to look at at least.
 
Do you have 2 databases or just one? In some cases all the objects are together in one file and other cases (especially when multi users are involved) there are 2 files, one with the tables (back end) and one with the other objects (front end).

I didn't realize that you database wouldn't open at all. You could try opening by holding down the shift key and that might bypass the error. Holding down the shift key allows you to go straight to the database window.

I don't know what MSysDb is so maybe you want to try and look up that error message on Microsoft.com's knowledge base.

Sorry I can't be of more help.

Dawn
 
No, I appreciate your attempts to give me a hand. We keep our entire database on one server, if I understand correctly you have two or more servers and spread the database across them? Microsoft does not really give you much on MSysDb, a JetComp utility does not even run. I will give the Shift key a try, and again I thank you!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top