Access file used by multiple users at the same time since copied to share on server 2012 not working anymore for more than one person

We changed the server froh sbs2003 to server 2012.
Our Access DB isn t working With  More than one user at a time.
What is the Problem?

Thanks for helping

Loosain
loosainAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dale FyeCommented:
Do each of your users have their own front end residing on their PC?  If not, they should.

First thing to check is that each user has read/write permissions in the folder where the Backend data is located.
0
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
and delete.  All users need full privs for the directory where the DB is.

Jim.
0
pcelbaCommented:
I understand the question as: Why just one user at a time can work with MC Access database?

I don't know any OS permission which allows to restrict db use to just one user. But Access itself can do it...

So, first of all check whether the database is used in shared mode. Exclusive use restricts other users.
Second, Microsoft is attempting to avoid/reduce shared file access and some of the newer technologies (SMB2, SMB3, oplocks) cause big problems in databases sharing. I would not recommend to use Access database by several users but rather upsize it to SQL Server...
0
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<I don't know any OS permission which allows to restrict db use to just one user. But Access itself can do it...>>

 If a .LDB file cannot be created by a user (which is used to place locks on), the DB gets opened exclusive regardless of settings.

<<Second, Microsoft is attempting to avoid/reduce shared file access and some of the newer technologies (SMB2, SMB3, oplocks) cause big problems in databases sharing. >>

 Microsoft did have issues with SMB2 and 3 early on, but those issues have all been worked out at this point.  They did however cause database corruption in some cases.

 But even so, those never caused a DB to remain in exclusive mode (SMB1 had the same feature, although with that you could turn it off).   Where OPLOCKS (client side caching) shows up is in delayed logins.

Jim.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
loosainAuthor Commented:
I don´t know why, but after restarting the Server everything was fine.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.