Results 1 to 10 of 10
  1. #1
    Join Date
    Aug 2002
    Posts
    1

    Unanswered: Problem with MS Access Versions 2 and 97 Table MsysModules2 is Exclusively locked

    The message "Table MsysModules2 is Exclusively locked by user X on machine Y" appears when attempting to access either Access Versions 2 and 97 systems.

    This problem does not occur every time the databases are opened.


    What I've tried already :

    1. I repair and compact the databases when these problems are reported.
    2. I've recreated the MDA and MDW files for the systems.
    3. In some cases based on earlier programming methods data and forms are held in separate databases. I've restored the forms and tables databases from backups. Repairing and compacting the databases before putting them live.

    Is there a simple solution to this problem.

    Please help

  2. #2
    Join Date
    Jul 2002
    Posts
    67
    I use this answer a lot but you would be amazed at what you can find if you go to MSDN and do a search on your problem. I personally have never encountered your particular problem before but it just might be documented on MSDN.
    Don't do today, what can be done tomorrow.

  3. #3
    Join Date
    Aug 2003
    Posts
    5

    Same MSYSMODULE2 Error

    I got the same error under the same circumstances. appears to be something with security, but no help from microsoft. KB Article 170696 is no help. anyone else have a solution?

  4. #4
    Join Date
    Jun 2002
    Location
    Mpls/St.Paul area
    Posts
    303

    Re: Problem with MS Access Versions 2 and 97 Table MsysModules2 is Exclusively locked

    I vaguely remember (story of my life) some similar problem.
    Perhaps changing the permissions on that object will help.
    Try this...

    Tools | Options | on the 'View' tab select System Objects.
    Now MSysModules2 and other system tables are viewable.

    Tools | Security | User Group and Permissions.
    Change the permissions on the table in question.

    Does that help?
    John
    This is the day the Lord has made, I will rejoice and be glad in it.

  5. #5
    Join Date
    Aug 2003
    Posts
    5
    unfortunately no. i tried that/ the problem is cache on the network server as i just found out.

  6. #6
    Join Date
    Jun 2002
    Location
    Mpls/St.Paul area
    Posts
    303
    "the problem is cache on the network server"

    Could you expound please?
    John
    This is the day the Lord has made, I will rejoice and be glad in it.

  7. #7
    Join Date
    Jul 2003
    Location
    Michigan
    Posts
    1,941
    I used to have a similar problem. Turned out to be the .ldb file
    that is created when a secure database is opened using a .mdw
    that is stored on a network. It stopped once I got all my users on
    the same versions of Windows and Access. I read something on the
    MSDN site about another cause being "unelegant exits" (ctl+alt+delete).

    Anyway, every time this happened, I had to get the network gods
    (or fiends) to delete the .ldb file, and then the DB was accesible again.
    Inspiration Through Fermentation

  8. #8
    Join Date
    Aug 2003
    Posts
    5
    Originally posted by jpshay
    "the problem is cache on the network server"

    Could you expound please?
    http://65.61.175.198/showthread.php?...t=msysmodules2

    is where answer is

  9. #9
    Join Date
    Oct 2003
    Posts
    1

    Thumbs up THE ANSWER TO THIS IS HERE

    Here is a guranteed fix for the following problem with MS Access,

    When you try to open an access db, you get this error
    "The table MsysModules2 is already opened exclusively by another user, or it is already open through the user interface and cannot be manipulated programmatically (error 3008)"

    If you are trying to open a db that resides on a network and the server is an NT or 2000 server you need to go to server manager in NT and view the current sessions and open folders on the network, look for the db in question. If you find a current session connected to the db then close or cancel the session. this will release the db. In a windows 2000 server enviroment you have to go to computer management and view current open files, this is listed under shared files, scroll through the list of currently open files and find the db filename in question, if you find a connection for the db your trying to open cancel the session and close the file. this will release the db. Now try to open your db. it should open.

  10. #10
    Join Date
    Oct 2004
    Posts
    1

    Talking For all Novell server users

    We had the same issue here and we are on Novell Servers.
    You have to turn off the file caching in each Novell client that is having the issue.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •