pls HELP :( some clients can not connect to a multiuser db

[Kevin Schulze]

Hi,

after years i have a big Problem here.

Some Clients in Network can not connect to the Fileserver Access97 Database.
The Clients ("only" 5) get the Error "Table XXX can not open, exclusiv open
from User XXX on Computer XXX"

But the DB is working in Mutiuser, there are many other Clients online in
this DB.

If no people connect, the "damaged" Client can connect.
And a "normal" Client get 2 times a error "cannot open because exclusive"
but on the 3rd try he connect and use the DB in "Shared Modus" togetther
with the "damaged" Client.

Hope you can help me.
I have no idea

greetings Kevin

System: NT4 / 2k ; Acc97 ; NDS

 

[Nikos Yannacopoulos]

Kevin,

I'm just guessing here, but it's worth a shot: if my guess
is correct, your problem might be solved by going to menu
Tools > Options, selecting tab Advanced and changing the
default open mode to Shared on your problematic client.

Nikos

 

[Kevin Schulze]

Hi Nikos,

thanks for answer, but this is done as first.... nothing happens.

The Client configuration is controlled too... no differnzes.

The only one, i think...
It is possible that this error comes truh the Network.
Here is a Network based on Novell's NDS but.. all clients working over this
net and all, without this 5 can connect.

Hope on help
greetings Kevin

PS: excuse my simple english please

 

[Nikos Yannacopoulos]

Kevin,

I'm afraid I'm running out of ideas... it's probably some
Access setting or installation problem, but I wouldn't
know where to look, to be honest.

I can't really tell whether it could be a network problem,
I don't know much about networks. I can offer a suggestion
on how to check it, though; try to use the same PC and
logon to Novell as another user (preferably one of those
on whose PCs it runs OK). If it works it is indeed the
network, if it doesn't it's not.

Good luck,
Nikos

 

[Kevin Schulze]

Many thanks for answer.

This one i did first... without a result.
This Problem is only on Workstation's equal wich User is Logon.

For example, i login on my Station... all works clear.
i login on a station with trouble... nothing works (if any other user login
before from a clear station).

If any User logon on the Mutiuser Database.. and a problem station try to
login too, its rase the Problem.

If any User logon from a problem station and noone is before in the database
its works.. but no other can login without 2 or 3 try's but then it works
under full locking (complete table).

All Settings in Access and in the Registry are checked.
no differences...
A new ms-office installation no effect's...


A complete new and empty Database rase the problem too. It is not my
Database, what i think first, there are all ms-access databases.


greetings Kevin

 

[Nikos Yannacopoulos]

Kevin,

Apparently you've done your homework! I'm sorry it was to
no avail... and I have no clue what it might be. The only
suggestion I could still make is you repost, in case you
get luckier (perhaps if you posted in the Security
newsgroup... the details in your last posting seem to be
pointing that way possibly).

Good luck,
Nikos

 

[Kevin Schulze]

Hi Nikos,
at now the last possible option i will do... "format c:\"

Hope this one resolve the problem.
Noone knows this, not in this and not in other newsgroups have hearded
anyone about this Problem it must be a Workstation Problem.

But howevery, thank you for the time you have investet for me.

greetings Kevin

 

[Tony Toews]

Some Clients in Network can not connect to the Fileserver Access97 Database.
The Clients ("only" 5) get the Error "Table XXX can not open, exclusiv open
from User XXX on Computer XXX"

This is probably a permissions problem on the directory in which the
backend is installed. The users must have create/delete privileges
to that directory. What is happening is that Access can't create the
..ldb file which allows multiple users to update the MDB. So Access
only allows one user at a time.

One simple way of testing this is to ensure the users can create and
delete a file in the network share. Any file, even using notepad, is
enough to test this. I simply don't trust all those permissions screen
within the OS. You never quite know whats lurking behind the advanced
button. So test this yourself.

Sometimes it could only be one user who does not have create
privileges to cause problems who just happens to be the first user
into the MDB at that moment in time. Then all the other Access users
can't access the file because the first user is in exclusively.

"I found that I could keep the permissions set to Change, but had to
ensure that the directory in which the db resides was set to not
inherit permissions from it's parent. It seemed that every time a new
user logged onto a given machine, it got messed up."

See ACC: Determining Which User Has Opened Database Exclusively
(Q169648)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q169648
Essentially you must use tools on the server to determine who has
locked the file.

For MS info see ACC: Introduction to .ldb Files (95/97) [Q136128]. Or
the version appropriate for your version of Access.

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

 

[Kevin Schulze]

Hi,

thanks for answer!

But that cant be the cause.
As example:
i have create, delete, write, filescan, read permission on fileserver.

If i login on my workstation all works fine, but if i login on a problem
workstation the self error raise. So it can't be the permission on
fileserver (and mdb also).
The Fileserver is NDS (Novell) and all permission sets on User not on
Workstation.

That is what i didnt understand.

greetings Kevin

Some Clients in Network can not connect to the Fileserver Access97 Database.
The Clients ("only" 5) get the Error "Table XXX can not open, exclusiv open
from User XXX on Computer XXX"

This is probably a permissions problem on the directory in which the
backend is installed. The users must have create/delete privileges
to that directory. What is happening is that Access can't create the
.ldb file which allows multiple users to update the MDB. So Access
only allows one user at a time.

One simple way of testing this is to ensure the users can create and
delete a file in the network share. Any file, even using notepad, is
enough to test this. I simply don't trust all those permissions screen
within the OS. You never quite know whats lurking behind the advanced
button. So test this yourself.

Sometimes it could only be one user who does not have create
privileges to cause problems who just happens to be the first user
into the MDB at that moment in time. Then all the other Access users
can't access the file because the first user is in exclusively.

"I found that I could keep the permissions set to Change, but had to
ensure that the directory in which the db resides was set to not
inherit permissions from it's parent. It seemed that every time a new
user logged onto a given machine, it got messed up."

See ACC: Determining Which User Has Opened Database Exclusively
(Q169648)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q169648
Essentially you must use tools on the server to determine who has
locked the file.

For MS info see ACC: Introduction to .ldb Files (95/97) [Q136128]. Or
the version appropriate for your version of Access.

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