MSysDb not found, can't open database - Error message 3011

[Guest]

I have created an Access db to manage a busy transportation department.
We've been using for about 15 months w/no significant problems. The db is on
a network drive accessed by three users. In shutting down the db to repair
as instructed in an error message, the db was somehow corrupted. Now when
attempting to open this message appears, "The Microsoft Jet database engine
could not find the object 'MSysDb'. Make sure the object exists and that you
spell its name and the path name correctly." I've tried to repair by opening
Access and using the TOOLS menu and the Compact and Repair Utility, but get
the same error message. What can I do to recover this very important
database?

 

[Guest]

What can I do to recover this very important

database?

Restore from a recent back-up copy that you made, just for this very real
possibility. No back-up? In that case, do not attempt anything further with
this database. There are database recovery services available that may be
able to recover your database for a fee, as long as you don't continue to try
opening it or manipulating it in any way. Post back if you would like some
recommendations of paid services.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Guest]

What can I do to recover this very important

database?

Restore from a recent back-up copy that you made, just for this very real
possibility. No back-up? In that case, do not attempt anything further with
this database. There are database recovery services available that may be
able to recover your database for a fee, as long as you don't continue to try
opening it or manipulating it in any way. Post back if you would like some
recommendations of paid services.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Guest]

I got the same error. I have not been able to resolve it, however, I will
share something that might help. When I use my application on my work
computer, I do not get this error. When I use the same "mdb" file on my home
computer, I get the error. I tried to copy the file over from work to home,
and was successful, but I still get the error when opening it.

What you may want to try is to open a copy of your database on a different
computer at work, and most likely you will not have an error. The error
relates to a computer, and not the MDB file. This was my experience.

If you find out how to resolve this problem, I sure would like to know!

By the way, I have reinstalled MS Access from scratch, and this did not
solve my problem.

 

[Sietske]

I encounter about the same error, which in my case does not mention MSysDb,
but only says:

The Microsoft Jet database could not fnd the object ". Make sure the object
exists and that you spell its name and the path name correctly.

It occurs when pressing the "Print"-button on my form, from one particular
desktop computer. When I enter the database (which is located on the
company's network) from any other computer, this problem does not occur.

What is wrong?
And how can it be solved?

 

[Tom Wickerath]

Hi Sietske,

When I enter the database (which is located on the
company's network) from any other computer, this problem does not occur.

Are you sharing an entire .mdb file over the network? It sure sounds like
you might be. You should be aware that Microsoft personnel on the Access
Development Team have previously identified sharing an entire .mdb file as
the number one cause of JET database corruption. You really do need to split
this application into two .mdb files: a Front-end (FE) and Back-end (BE).
Please see my Multi-User Applications paper for more details. You can access
this article here:

http://www.accessmvp.com/TWickerath/index.htm

As a minimum, I would disable Name Autocorrect, set all table subdatasheets
to [None], split the database, establish a persistent connection, and then
distribute a copy of the FE database to each user's local hard drive.

On the affected PC, I would try deleting the default print driver and
reinstalling it, since this issue is initiated by clicking on a Print button.
While this is the quickest thing to do, if it fixes the problem this doesn't
mean that you should ignore the above advice about implementing a properly
split application.

On all PCs, including the one throwing this error, I would ensure that the
latest updates have been applied. See the following Microsoft Knowledge Base
(KB) article:

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

In particular, follow the three links:

Verify that the latest operating system service pack is installed
Verify that the latest Microsoft Jet service pack is installed and
Verify that the latest service pack for your version of Office is
installed

Also recommended:
Install the latest version of MDAC (Microsoft Data Access Components)
http://www.microsoft.com/downloads/...e3-c795-4b7d-b037-185d0506396c&DisplayLang=en


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Sietske]

Hi Tom,

Many thanks for your very large reply!
I will try and follow your recommendations on the error.
You were also right with the sharing-over-the-network assumption,
so I will follow your instructions about splitting the .mdb too.

Sietske

Hi Sietske,

When I enter the database (which is located on the
company's network) from any other computer, this problem does not occur.

Are you sharing an entire .mdb file over the network? It sure sounds like
you might be. You should be aware that Microsoft personnel on the Access
Development Team have previously identified sharing an entire .mdb file as
the number one cause of JET database corruption. You really do need to split
this application into two .mdb files: a Front-end (FE) and Back-end (BE).
Please see my Multi-User Applications paper for more details. You can access
this article here:

http://www.accessmvp.com/TWickerath/index.htm

As a minimum, I would disable Name Autocorrect, set all table subdatasheets
to [None], split the database, establish a persistent connection, and then
distribute a copy of the FE database to each user's local hard drive.

On the affected PC, I would try deleting the default print driver and
reinstalling it, since this issue is initiated by clicking on a Print button.
While this is the quickest thing to do, if it fixes the problem this doesn't
mean that you should ignore the above advice about implementing a properly
split application.

On all PCs, including the one throwing this error, I would ensure that the
latest updates have been applied. See the following Microsoft Knowledge Base
(KB) article:

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

In particular, follow the three links:

Verify that the latest operating system service pack is installed
Verify that the latest Microsoft Jet service pack is installed and
Verify that the latest service pack for your version of Office is
installed

Also recommended:
Install the latest version of MDAC (Microsoft Data Access Components)
http://www.microsoft.com/downloads/...e3-c795-4b7d-b037-185d0506396c&DisplayLang=en


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

I encounter about the same error, which in my case does not mention MSysDb,
but only says:

The Microsoft Jet database could not fnd the object ". Make sure the object
exists and that you spell its name and the path name correctly.

It occurs when pressing the "Print"-button on my form, from one particular
desktop computer. When I enter the database (which is located on the
company's network) from any other computer, this problem does not occur.

What is wrong?
And how can it be solved?

 

[GS JAIN]

I have created an Access db to manage a busy transportation department.
We've been using for about 15 months w/no significant problems. The db is on
a network drive accessed by three users. In shutting down the db to repair
as instructed in an error message, the db was somehow corrupted. Now when
attempting to open this message appears, "The Microsoft Jet database engine
could not find the object 'MSysDb'. Make sure the object exists and that you
spell its name and the path name correctly." I've tried to repair by opening
Access and using the TOOLS menu and the Compact and Repair Utility, but get
the same error message. What can I do to recover this very important
database?

 

[GS JAIN]

I have created an Access db to manage a busy transportation department.
We've been using for about 15 months w/no significant problems. The db is on
a network drive accessed by three users. In shutting down the db to repair
as instructed in an error message, the db was somehow corrupted. Now when
attempting to open this message appears, "The Microsoft Jet database engine
could not find the object 'MSysDb'. Make sure the object exists and that you
spell its name and the path name correctly." I've tried to repair by opening
Access and using the TOOLS menu and the Compact and Repair Utility, but get
the same error message. What can I do to recover this very important
database?