Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

MSysAccessStorage Error

Discussion in 'Information Technology' started by Steve Voorhees, Oct 27, 2005.

  1. Steve Voorhees

    Steve Voorhees
    Expand Collapse
    Guest

    I am receiving the message "The table 'MSysAccessStorage' is already opened
    exclusively by another user, or it is already open through the user interface
    and cannot be manipulated programmatically."
    I searched the Knowledgebase yesterday, and thought that perhaps this was
    related to Database Bloat (Article ID 810415) but that didn't seem to correct
    the issue.
    Any suggestions?
     
  2. Loading...


  3. Tony Toews

    Tony Toews
    Expand Collapse
    Guest

    "Steve Voorhees" <SteveVoorhees@discussions.microsoft.com> wrote:

    >I am receiving the message "The table 'MSysAccessStorage' is already opened
    >exclusively by another user, or it is already open through the user interface
    >and cannot be manipulated programmatically."
    >I searched the Knowledgebase yesterday, and thought that perhaps this was
    >related to Database Bloat (Article ID 810415) but that didn't seem to correct
    >the issue.


    Sounds like corruption.

    For more information on corruption including possible causes,
    determining the offending PC, retrieving your data, links, official MS
    KB articles and a list of vendors who state they can fix corruption
    see the Microsoft Access Corruption FAQ at
    http://www.granite.ab.ca/access/corruptmdbs.htm

    Tony
    --
    Tony Toews, Microsoft Access MVP
    Please respond only in the newsgroups so that others can
    read the entire thread of messages.
    Microsoft Access Links, Hints, Tips & Accounting Systems at
    http://www.granite.ab.ca/accsmstr.htm
     
  4. Steve Voorhees

    Steve Voorhees
    Expand Collapse
    Guest

    Thank you. This response helped.
    The issue was caused by a setting on a new Novell Netware server (OPLOCKS)
    being turned on, rather than off. I reported to our IT department, who
    checked the issue. They rebooted the server in question, which released all
    of the locks.
    I did, however, end up having to extract all the data from the database and
    completely rebuild, as the OPLOCKS problem caused the database to start
    losing data. More data connections than actual data, but I was able to
    recover all of the data successfully.
    Very helpful.

    "Tony Toews" wrote:

    > "Steve Voorhees" <SteveVoorhees@discussions.microsoft.com> wrote:
    >
    > >I am receiving the message "The table 'MSysAccessStorage' is already opened
    > >exclusively by another user, or it is already open through the user interface
    > >and cannot be manipulated programmatically."
    > >I searched the Knowledgebase yesterday, and thought that perhaps this was
    > >related to Database Bloat (Article ID 810415) but that didn't seem to correct
    > >the issue.

    >
    > Sounds like corruption.
    >
    > For more information on corruption including possible causes,
    > determining the offending PC, retrieving your data, links, official MS
    > KB articles and a list of vendors who state they can fix corruption
    > see the Microsoft Access Corruption FAQ at
    > http://www.granite.ab.ca/access/corruptmdbs.htm
    >
    > Tony
    > --
    > Tony Toews, Microsoft Access MVP
    > Please respond only in the newsgroups so that others can
    > read the entire thread of messages.
    > Microsoft Access Links, Hints, Tips & Accounting Systems at
    > http://www.granite.ab.ca/accsmstr.htm
    >
     
  5. Tony Toews

    Tony Toews
    Expand Collapse
    Guest

    "Steve Voorhees" <SteveVoorhees@discussions.microsoft.com> wrote:

    >Thank you. This response helped.
    >The issue was caused by a setting on a new Novell Netware server (OPLOCKS)
    >being turned on, rather than off. I reported to our IT department, who
    >checked the issue. They rebooted the server in question, which released all
    >of the locks.
    >I did, however, end up having to extract all the data from the database and
    >completely rebuild, as the OPLOCKS problem caused the database to start
    >losing data. More data connections than actual data, but I was able to
    >recover all of the data successfully.
    >Very helpful.


    Thank you for your response. I appreciate knowing what was causing
    corruptions so I can ensure it's on my pages.

    Tony
    --
    Tony Toews, Microsoft Access MVP
    Please respond only in the newsgroups so that others can
    read the entire thread of messages.
    Microsoft Access Links, Hints, Tips & Accounting Systems at
    http://www.granite.ab.ca/accsmstr.htm
     

Share This Page