MSysAccessStorage Error

[avagodro]

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?

 

[hermanlaksko]

1. Create a new database container.
2. Import all into this new container.

Herman

Say no to macros

 

[avagodro]

I did this previously, as was suggested by what I found in Article ID 810415. I created a new database in Access 2000, imported all tables, queries, forms, reports, and Modules. I compiled the code, converted to Access 2002, and compacted to an MDE. The error still appeared this morning when more than one user attempted to access the database.

 

[hermanlaksko]

Could it that your users are opening this database in exclucive mode ?... not likely, hmmmm

Check your ownerships in this database's tables the problem could be laying here.

Does your program conssist of a front and a backend ?
if not, and it looks like it does not, please do this!

If you have a "frontend" crash you will loose your "backend" data also, however if you use the FE/BE solution you will only loose the "program part" and this is easyly solved.

Herman

Say no to macros

 

[avagodro]

I do use a frontend and a backend. When I originally created the database, I had it all in one, then when I was preparing to take it "live", I ran the Access database splitter, which created the frontend and backend.
I can check things for the backend as well, and see if perhaps something is "corrupted" there as well.
It is surprising, though, there there is basically no information about this problem available.

 

[hermanlaksko]

When I split a database after making relationships, I do the following:

1. Create a new database container
2. Import all formes/queries (if any)/reports etc. etc into this new container.
3. Delete the imported objects in the org. database
4. Do a caompct/repair of the org. database.

This insures that I get exactly what I want in both front and backend.

However I am getting away from the problem at hand.
Did you check on ownerships to the tables ?

Herman

Say no to macros

 

[avagodro]

I guess I should ask how to check the ownership of the tables. I'm not exactly sure what you are referring to.
And, as an added side note...this database has been in use for over a year with no problems. This problem popped up on Tuesday.
The database is used over a Novell network. It was a couple of days after our IT department replaced one of the Novell Servers. I was theorizing that perhaps that was the cause, but I have not come across the issue, and I tested it on 2 different computers, and did not encounter the error.

 

[hermanlaksko]

OK - fine I saw that you did not refer to this in your reply but I assumed that you forgot.

1. Goto tools
2. Goto security
3. Goto User and group permissions

In this form you can change user/group rights.
Make sure that the user Admin is the owner of the tables and have the proper rights to queries.

Check permissions and note that you can mark all objects in any object type, so you do not have to do them one by one ;-)


Herman

Say no to macros

 

[avagodro]

I just checked the ownership for the database, tables, queries, forms, reports, etc and all are set to Admin and all options are checked.

 

[hermanlaksko]

And group rights?

Herman

Say no to macros

 

[avagodro]

Groups are set fine too. The rights would be the default, since I had no need to change them, due to not needing password protection or individual user accounts.

 

[hermanlaksko]

Ok fine if your users do not open the base in "Exclucive mode" then the problem must lie outside the database itself as you indicated priviously.

You shoud have the poss to share a folder on a pc that your users can gain access to. As this share is places outside the server itself and perhaps could be a part of a local workgroup the Novell server will not interfer.

Place your app here nad let a few users connect here.
Let me know how it goes.

Herman
Say no to macros

 

[avagodro]

I have basically found the same thing, by searching Google for the problem. It appears as though certain versions of Novell Netware have a problem with network file sharing. I am going to check the settings, and will report back as soon as I know anything.

 

[avagodro]

The issue ended up being caused by a setting on one of our Novell Netware servers. Novell has a feature called OPLOCKS (Opportunistic Locking) which conflicts with certain programs, Microsoft Access databases being one of them.
Before the IT department began looking into the issue, I had records begin to get corrupted in the database, which resulted in a complete extraction and rebuild of the database.
Once IT rebooted the server in question, it resulted in all of the LOCKS being released and there appears to be no further issues.

 

[hermanlaksko]

Excelent! - Nice to know, what really coursed this.... and how it was solved.


Herman
Say no to macros