MSysDb Error

[rajeevs]

Hi All
I have an issue with one of my access DB which was working perfect for years. It was in a network and suddenly crashed. Now whenever I try to open the DB the error I am getting is about could not find MSysDb object.
This DB is password protected so after supplying the password it is showing the error. I read some articles about repairing DB by using Compact and Repair option but in this case I am unable to do this. I tried to import the objects from the DB to a new database but still the error message appears and thus I am unable to get the tables.
Hope someone can guide me how to get atleat all the tables with data from the database.
Thank you all in advance

[zmbd]

What is the EXACT error message.
There are few different ones that MySYSDb can generate
Please post the
EXACT:
Title
Number
Descriptive text

Also need to know which version of office/access with which the file was originally created.

Also need to know which version of office/access you are using to open the file.

(on the surface... the prognosis is very bad - hope you have a recent backup)
( might try Allen Browne - Database Recovery and Repair
Try to get a copy to a secure standalone PC and work on the copy.

[rajeevs]

Thank u for the quick response
There is no error number or title but the error message read as,
The microsoft database engine could not find the object 'MSysDb'. Make sure the object exists and that you spell its name and the path name correctly. If 'MSysDb' is not a local object , check your network connection or contact the server administrator.
The db is .mdb and we were using office 2010 and now 2013. It was ok with office 2013 for the last couple of months. This error started appearing from yesterday only and unable to open the DB. Hope there could be a work around to get atleat the tables from the DB

[zmbd]

Welcome to cross version hell.
It is a known bug in ACC2007/2010 and now I suspect ACC2013 that opening and using the older mdb (ACC2003 and older) files can lead to corruption.

The workaround was to create the older style file type from within ACC200/2010/2013 and then import all the old file objects into the newer "old-style" file.

Most likely the corruption had been creeping in and when you moved to the newest ACC2013 that was the final straw.

I am sorry to say that aside from some commercial tools, there is most likely no recovery and the commercial tools are only 50/50 from what I've seen on the net.

1) restore from backup.
Do the version workaround as talked about above.

2) Before you start, as directed in Allen Browne's article I linked you to...
MAKE A BACKUP
My mantra... MAKE A BACKUP (x 1E10000000)
Sorry, it's a pet peeve of mine... we almost lost 15 years worth of data in the lab (been awhile ago now); however, I happened to make a back-up copy to the LAN from the local C-Drive for my own needs to improve the data-entry forms! The other potentially catastrophic event, IT saved our bacon because they have a weekly backup of the network based user-drives.

For all of the following steps start with a "clean" backup of your file. Each step might cause further damage so it is best to start from "square-one" each time

3) Find an old installation of ACC2003 or the original version and attempt to open the file from this version. I keep a PC in my office at work with an installation of ACC2003 just for this reason.
IF IT OPENS
Remove the password
Compact and repair
Open a second instance of ACC2003
Create a new database, and move everything to this new database.
Then do the workaround as I mentioned above for the newer version.

4) Open the file again, holding down the shiftkey (except as needed for the password entry) during the entire startup process. - IF you can get the file to open this way. COMPACT AN REPAIR from the database tools... then perform the work around as given above.

5) http://support.microsoft.com/?kbid=295334
This is a tool from Microsoft. It will sometimes repair the databases.
If this works... CONVERT YOUR DATABASE TO THE NEWEST FORMAT.
If you must keep the workgroup userlevel security, create a new mdb from within your newest version of ACC.

6)It sounds like you've done this... create the new database and attempt to import the old objects from the old file.

7) Open excel.
External data tab.
New database query.
Try to import the tables into the workbook... the ODBC driver works at a very low level so it may avoid some of the issues that requiring a user GUI creates.

8) Allen Browne's link in my previous post

9) LAST DITCH

http://www.rogersaccesslibrary.com/forum/fix-corrupt-access-database-v45_topic25.html

This is a VERY OLD paper from MVP Jerry Whittle proved for and by MVP Roger Carlson. Not an easy read; however, because you are working with such an old data file something might help.

Otherwise, you are going to have to go to a paid data recovery professional.

MODERATORS NOTE
For those that would post professional software recovery products (including freeware and shareware) and/or services, such posts are subject to deletion per the terms of use for this site. We appreciate the need to promote such services; however, this is a captive audience and such efforts are unfair to our membership.

[rajeevs]

Thnak u zmbd. I had a backup DB and I managed to import all the tables from the crashed DB. Thank you for the support and detailed explanation for the recovery

[zmbd]

I am really very happy this worked out for you and I hope something I could offer helped

I'd also like to thank you for posting for help... May your misery be a red flag for others to keep a back up of their databases and to start rolling forward their older files.

Remember for all of you still using files originally created using an older version of Access... if you don't roll forward, it is especially imperative that backups be made!