no read permission on msysmodules2

[jfrasier]

I have an Access 97 database stored on an NT 4 server with users in various buildings accessing it. All users in most locations have had NO problems whatsoever using this file. However users in 2 locations usually get the message "Record(s) can't be read; no read permissions on msysmodules2". From time to time the message is "disk or network error". One of the locations has never been able to use this database and the other one could for awhile but can't now.

Any ideas?

Jane Frasier

 

[jfrasier]

When you say "go to tools option advance and pick system objects" I don't see that. Do you mean Tools | Options | View | System Objects?

I have not secured this database ever with Access. I have secured another database in the past but removed the security from it months ago.

I did go into the problem database and check the permissions as you describe. The group USER already has all permissions except modify design and administer for the file that we are getting the error on.

This doesn't seem to be the answer but I appreciate your response. Any other ideas?

Jane

 

[jfrasier]

I had another thought. Many of our staff share computers at reference desks as so they use a generic login. So at any particular time there may be 2 or 4 different people on different computers that have this database open that are all logged in as refdesk. Could this be confusing the locking process? That would make some sense but it doesn't explain why none of the computers/people can use it from one location and everyone else in other locations can.

Jane

 

[MichaelRed]

Jane,

Could you review the thread and summarize what you have/have not attempted and what results you have gotten with the various (non) soloutions? For example, I do not know what happend when/if you copied the entire database to your local HD and attempted to run it.



MichaelRed
mred@duvallgroup.com
There is never time to do it right but there is always time to do it over

 

[jfrasier]

Here are some details:

The database is secured with NT, never been secured in Access. It is NOT split. No logins on any computers at one location can access the database. Error is either "disk or network error" or "no read permission for MySysmodule2". A few times after compacting the database I could at least open it once but then it would break. I generally try opening it directly from Network Neighborhood \\server\folder\filename, not using a mapped drive.

All workstations are using the same version of Access. Some are using Win95 and some are using NT 4. Some have 32MB and some have 128MB. These variables also exist in the locations where the database works fine.

I brought one workstation to another building and it worked fine. I copied the database to a hard drive at the "bad" location and it worked fine. It even runs from a floppy. I also created a new database, unhid system objects, imported all the items except the system objects. These system tables (including msysmodule2) was recreated automatically. This still did not fix the problem.

What to do...

Jane

 

[MichaelRed]

Jane,

The symptoms strongly indicate, to me, that the problem is in the networking. Since the same machine will work in one location but not another indicates that the error is in the netwoking hardware.

I cannot offer much help in that arena. My limited experience would suggest that you need professional help here. I have found simple things - which are NOT apparent to the casual observer to be quite capable of wrecking networks. A poorly crimped (fastened) connector, a total wire run length, a mis-configured router ... All may be directly responsible. The "disk of network error" is - in my opinion - the real culprit here particularly the network part.

Sorry I cannot help any further, and hope you are able to get the appropiate help and resolve the problem.



MichaelRed
mred@duvallgroup.com
There is never time to do it right but there is always time to do it over