If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > PC based Database Applications > Microsoft Access > error 3011: access database could not find the object 'MSysDb'

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old
Registered User
 
Join Date: Aug 2008
Posts: 16
error 3011: access database could not find the object 'MSysDb'

Hi guys,

I'm really expecting a reply and really really hopeful that i'll get my solution here.

My db is sitting on a n/w that's accessed by everyone. It got roasted this morning and now everytime i try to access it, i get 2 kinds of errors. It doesn't even allow me to compact and repair cuz the moment i try to open it, that error msg pops up.

1. The microsoft access database could not find the object 'MSysDb'. Make sure the object exists and that you spell its name and path name correctly.

2. Error 3011: The microsoft jet database could not find the object 'MSysDb'. Make sure the object exists and that you spell its name and path name correctly.

I've tried a lot of free tools, even jetcom.exe but no help. The mdb repair tools available on the net are not free to save the file. Does any one know a cracked version or where i can download a tool to fix the currupt db.

I really really need the db by monday. Any help would be really appreciated.
Reply With Quote
  #2 (permalink)  
Old
Moderator
 
Join Date: Dec 2004
Location: Madison, WI
Posts: 3,925
Have you tried the JetCu40.exe (or JetUtils.exe) utility?

I believe you can download it here:
http://www.filewatcher.com/m/jetcu40...13328.0.0.html
(although I'm not sure how dated this is.)

Here's another (again, which I haven't tested):
http://www.s2services.com/access-tools.htm

And here's some switches you can utilize opening an mdb:
http://support.microsoft.com/kb/209207
or
http://support.microsoft.com/kb/105128
or
http://www.vb123.com/workbench/help/commandline.htm

(the /decompile switch might be an option to try.)

I might also try creating a new mdb and see if you can import the objects into it. This really sounds like a database corruption issue and since you can't repair the mdb, I would see if you can perhaps import (or export) the objects into another mdb, especially if time is critical.

Also, I'm assuming you tried opening the mdb using the shift key.

Try copying the mdb to a local drive and see if you can do any compacting/repairing on your local drive (I believe it's always better to try and do this kind of stuff from a local drive, and of course, a backup copy.)

As a note, asking for a cracked version of a software is not a good idea on this site.

Good luck.
__________________
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)
Reply With Quote
  #3 (permalink)  
Old
Registered User
 
Join Date: Aug 2008
Posts: 16
Thanks stormy for the response. I really appreciate it.

I tried using the Jetcom utility but that didn't work. It kept saying error compacting database.

Everytime i try the decompile option, doesn't work for me. May b i'm doing it wrong,

I've tried to import the database to a new db but that gives me the same error.

I even manually tried to compile it with the command but that shows the same error.

Have tried using the shift key before opening but no luck =(. Even tried copying to local drive but that doesn't help.

The only thing i'ven't tried is playing with the code which i'm not sure how to do manual commands given in the following website.
http://support.microsoft.com/kb/209207

If you can really help me, i can send you the db, may be you can help me fix it.

Thanks in advance,

really appreciate your help

Quote:
Originally Posted by pkstormy
Have you tried the JetCu40.exe (or JetUtils.exe) utility?

I believe you can download it here:
http://www.filewatcher.com/m/jetcu40...13328.0.0.html
(although I'm not sure how dated this is.)

Here's another (again, which I haven't tested):
http://www.s2services.com/access-tools.htm

And here's some switches you can utilize opening an mdb:
http://support.microsoft.com/kb/209207
or
http://support.microsoft.com/kb/105128
or
http://www.vb123.com/workbench/help/commandline.htm

(the /decompile switch might be an option to try.)

I might also try creating a new mdb and see if you can import the objects into it. This really sounds like a database corruption issue and since you can't repair the mdb, I would see if you can perhaps import (or export) the objects into another mdb, especially if time is critical.

Also, I'm assuming you tried opening the mdb using the shift key.

Try copying the mdb to a local drive and see if you can do any compacting/repairing on your local drive (I believe it's always better to try and do this kind of stuff from a local drive, and of course, a backup copy.)

As a note, asking for a cracked version of a software is not a good idea on this site.

Good luck.
Reply With Quote
  #4 (permalink)  
Old
Registered User
 
Join Date: Aug 2008
Posts: 16
Here is the db called Pulaski 2008.zip

If anyone can try to fix it, would be much appreciated.

Thanks.

Last edited by shilp66; 08-11-08 at 09:44.
Reply With Quote
  #5 (permalink)  
Old
L33t Helpa Munky
 
Join Date: Nov 2007
Location: Adelaide, South Australia
Posts: 4,049
Have you tried restoring from a backup??
__________________
Owner and Manager of
CypherBYTE, Microsoft Access Development Specialists.
Microsoft Access MCP.
And all around nice guy!


"Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
"...teach a man to code and he'll be frustrated for life! " -- georgev
Reply With Quote
  #6 (permalink)  
Old
Moderator
 
Join Date: Dec 2004
Location: Madison, WI
Posts: 3,925
Your mdb

Here's your mdb after I ran it through a few utilities I had. It doesn't recover the Forms, Queries, Reports, and Modules but your tables are all there. I hope you have a backup for the other objects and hope this helps - best I could do. As a note, you have a lot of tables without an autonumber (or primary key designated) field. I would highly encourage you to create autonumber fields for ALL your tables and perhaps set some primary key fields. Autonumber type fields (in my opinion), helps maintain a good clean table which helps prevents some database table corruption problems. Defining Primary Key fields will also help in maintaining good recordsets (but perhaps the utilities I used removed these.)
Attached Files
File Type: zip Pulaski2008Fixed.zip (541.0 KB, 367 views)
__________________
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

Last edited by pkstormy; 08-11-08 at 01:21.
Reply With Quote
  #7 (permalink)  
Old
Registered User
 
Join Date: Aug 2008
Posts: 16
Thanks a million stormy. I do have tables with autonumber, just couldn't be recovered. With this zip, i lost all the data that was there.
Can you let me know how did you manage to recover. It'll be very helpful if something like that happens in the nearby future.

Thanks once again.


Quote:
Originally Posted by pkstormy
Here's your mdb after I ran it through a few utilities I had. It doesn't recover the Forms, Queries, Reports, and Modules but your tables are all there. I hope you have a backup for the other objects and hope this helps - best I could do. As a note, you have a lot of tables without an autonumber (or primary key designated) field. I would highly encourage you to create autonumber fields for ALL your tables and perhaps set some primary key fields. Autonumber type fields (in my opinion), helps maintain a good clean table which helps prevents some database table corruption problems. Defining Primary Key fields will also help in maintaining good recordsets (but perhaps the utilities I used removed these.)
Reply With Quote
  #8 (permalink)  
Old
L33t Helpa Munky
 
Join Date: Nov 2007
Location: Adelaide, South Australia
Posts: 4,049
I'm interested too
__________________
Owner and Manager of
CypherBYTE, Microsoft Access Development Specialists.
Microsoft Access MCP.
And all around nice guy!


"Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
"...teach a man to code and he'll be frustrated for life! " -- georgev
Reply With Quote
  #9 (permalink)  
Old
Moderator
 
Join Date: Dec 2004
Location: Madison, WI
Posts: 3,925
After trying out the JetUtil and opening the mdb with different parameters, I then used the Advanced Access Repair Tool (http://www.repair-access.com/ or http://www.freedownloadscenter.com/B...s_Repair.html). Although my copy is not the freeware version.
__________________
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

Last edited by pkstormy; 08-11-08 at 19:21.
Reply With Quote
  #10 (permalink)  
Old
L33t Helpa Munky
 
Join Date: Nov 2007
Location: Adelaide, South Australia
Posts: 4,049
Thanks, I'll look into it
__________________
Owner and Manager of
CypherBYTE, Microsoft Access Development Specialists.
Microsoft Access MCP.
And all around nice guy!


"Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
"...teach a man to code and he'll be frustrated for life! " -- georgev
Reply With Quote
  #11 (permalink)  
Old
Registered User
 
Join Date: Aug 2008
Posts: 16
stormy,

I don't mind using these tools but the problem is, these expensive tools only recovers the cfg tables and not the tbl tables which contains all the data.

Anyhow, i appreciate all your help.

Thanks.
Reply With Quote
  #12 (permalink)  
Old
Moderator
 
Join Date: Dec 2004
Location: Madison, WI
Posts: 3,925
Yes - that can be a problem with a corrupt mdb and a msysdb error (although I thought I saw your data in the tables.) As StarTrekker mentioned, your best option is to restore from a backup with this kind of corruption. Hopefully you have a backup somewhere.

Something I might recommend if you aren't already doing this:
I personally use SQL Server which has a great backup system for the tables (Point-in-Time restores from SQL Server are unbeatable!! I'll set it so it backs up the tables every hour or every 4 hours.)

If SQL Server isn't an option (even though SQL Server Express is free), I'd recommend (if you haven't already), that you split the mdb/mde and again, have the mdb with the tables on a network drive which is backed up nightly (so the most you'll lose is 1 days worth of data if there is a corruption problem.)

For the mdb source code, I keep that safely hidden on my drive (and have the network guys backup my mdb folder). I prefer doing any mdb work off of my local drive to remove any network hiccups out of the picture for any problems. I always do a quick copy->paste before doing any coding work (I may have 10-20 copies of the mdb at the end of the day and then put these in folders labeled with the date.) After a week or so, I'll go through and remove older backup folders. And then I make an mde file which I throw out on the network drive for the users.

I can't help you much more on the mdb you uploaded. If I had more time, I could probably try a few other things (stabbing in the dark) but the msysdb error is a nasty one to try and overcome and fix. I'll usely go to my backups with this kind of error since it can be time-consuming trying out different ways to recover the mdb and may not even get results (and honestly, I'd only go to that extreme for my own mdb - I did this rather quickly on your mdb.) Admittingly though, I've rarely ever gotten this type of error since I do tend to compact/repair on a daily basis as well. You can try one of the services which may help you restore the mdb but you may not get much more than just the tables restored (but you never know.) It's not terribly expensive to have them give it a shot (I think around $100-$200 but don't quote me on that.)

Good luck.
__________________
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)

Last edited by pkstormy; 08-12-08 at 17:03.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On