Topic: MS access database unable to operate with more than 1 or 2 users

[JBrennan]

Ours is a fairly simple setup.  A half dozen users running Win XP and connected to the SME server, functioning in server mode only. It is a recent installation running 7.5 I think and everything else seems to be operating satisfactorily. But our shared database, configured with the Access scripts on the users machines and the data on the server becomes either unresponsive or slow if there are more than 1 user with the database open.

It is important to note that this program was operating well with the Access data file on another linux based file server.  I simply
1.   Copied the contents of the folder on that old server over to the SME server
2.   Altered a mdb configuration file that contains project data, so that it pointed to the SME server. This in effect involved little more than changing the mapped drive letter.

Is there any other information you need  know?
Any help would be much appreciated.

John

[Stefano]

John

take a lok at VetoOplockFiles  directive in http://wiki.contribs.org/DB_Variables_Configuration page

anyway, IMHO, access is the worst tool.. I suggest you to use it simply as a frontend, moving your data to mysql (native in SME)

My 2c

[JBrennan]

Stefano,

Thanks for this suggestion. I have no choice about the type of database even if I had the know-how to change it.

My linux knowledge is rudimentary and I won't be in front of the machine for a couple of days. Do I understand right, that I should open the  /etc/samba/smb.conf  file in an editor like pico and alter the VetoOplockFiles variable to the value: veto oplock files ?

John

[Stefano]

Thanks for this suggestion. I have no choice about the type of database even if I had the know-how to change it.

....

Do I understand right, that I should open the  /etc/samba/smb.conf  file in an editor like pico and alter the VetoOplockFiles variable to the value: veto oplock files ?

no

if you re-read carefully you'll see:

  Samba per i-bay settings (smbd)

Usage

db accounts setprop ibay_name variable value
signal-event ibay-modify

where ibay_name is your ibay name, variable and value are in the table below that sentence..

to apply that change you have to log in as root in console or via ssh

HTH

[JBrennan]

Worked great!  Thanks Stefano for your patient explanation of the steps required

[JBrennan]

Sorry but I've got to come back to this again

After a shut down and restart, the same problem reappeared again. I reentered the two commands which fixed it, but how do I make this fix more permanent?

Incidentally, the shutdown takes 10 - 15 minutes (I used the web page management option). Is that normal?

Thanks

John

[janet]

JBrennan

Please quote here exactly the commands that you issued.
As far as I can see there is no reboot command involved.

Changing the database setting as Stefano indicated should be a permanent change, unless of course you have entered it incorrectly or done something else you are not telling us about.
You should not be editing the conf file manually.

What does this show
db accounts show ibayname
(replace ibayname with your ibayname)

Re reconfigure/reboot time I assume you did a
signal-event post-upgrade
reboot
On an older slower machine this could take 15 minutes or even more. On a fast modern machine maybe 3 or 4 minutes all up, it depends also on your particular configuration, number of ibays & users etc. What is your server spec ?

[JBrennan]

Thanks Mary for your full reply
Changing the database setting as Stefano indicated should be a permanent change,
I'm not entirely sure what happened, but after the reboot I entered
db accounts setprop ibay_name variable value  - which was accepted

and
signal-event ibay-modify   - which appeared to be rejected

and everything is working fine.
My previous reboot had been initiated through the web page, but I have since tested it by pulling the plug

reboot
On an older slower machine this could take 15 minutes or even more. On a fast modern machine maybe 3 or 4 minutes all up, it depends also on your particular configuration, number of ibays & users etc. What is your server spec ?
It is older - so now I know what to expect

[Stefano]

First of all, please, use the standard quote tag, don't "invent" a new way to quote, thank you

I'm not entirely sure what happened, but after the reboot I entered
db accounts setprop ibay_name variable value  - which was accepted

please post the result of

Code: [Select]

db accounts show ibayname


signal-event ibay-modify   - which appeared to be rejected

ok.. but... you forgot to tell us the message you read.. you say "rejectes".. I'm quite sure SME  told you something (the reason for failure)

and everything is working fine.

mmmhhh... sincerely.. I can't figure how it could be..

[JBrennan]

Dear Stefano,

[

First of all, please, use the standard quote tag, don't "invent" a new way to quote, thank you

Couldn't find it the other day. After seeing the ugly result I had resolved not to try that again   Hope I got the quote thing right this time.

please post the result of

Code: [Select]

db accounts show ibayname


db accounts show ibayname
[/code]
CgiBin=disabled
Gid=5012
Group=shared
name= Database and Backup
PasswordSet=No
PublicAccess=none
Vid=5012
UserAccess=wr=group-rd-group

ok.. but... you forgot to tell us the message you read.. you say "rejectes".. I'm quite sure SME  told you something (the reason for failure)
Sorry. forgot to note it down

and everything is working fine.
        mmmhhh... sincerely.. I can't figure how it could be..

You are right. Hadn't done enough testing. Concurrent searches on different machines is working (when it wasn't before), but this afternoon with my machine entering new records, other machines would hang on start up as they could not reconnect to the data file.

thanks

John

[Boris]

Could your iBay name be a problem?
Its long and have spaces.

[JBrennan]

Rounding off the post.

Just for the record, I put these four commands in [altering the word 'name']:

db accounts setprop ibay_name VetoOplockfiles veto oplock files
signal-event ibay-modify
signal-event post-upgrade
reboot

and so far it has passed the tests that I have undertaken.
Be prepared for a long wait after the 'post-upgrade' command

Thanks Boris for the suggestion, but the shortname for the ibay is just one word. The name that returned for the show ibayname command is the longname or the description of the ibay.

[Boris]

Rounding off the post.

Just for the record, I put these four commands in [altering the word 'name']:

db accounts setprop ibay_name VetoOplockfiles veto oplock files
signal-event ibay-modify "HERE Should be IBAYNAME"
signal-event post-upgrade
reboot

and so far it has passed the tests that I have undertaken.
Be prepared for a long wait after the 'post-upgrade' command

Thanks Boris for the suggestion, but the shortname for the ibay is just one word. The name that returned for the show ibayname command is the longname or the description of the ibay.

[cactus]

db accounts setprop ibay_name VetoOplockfiles veto oplock files
signal-event ibay-modify
signal-event post-upgrade
reboot

For the record the commands need a little adjustment indeed:

Code: [Select]

db accounts setprop ibay_name VetoOplockfiles veto oplock files
signal-event ibay-modify ibay_name
signal-event post-upgrade
signal-event reboot

[janet]

JBrennan

Based on what you write in this thread, there are serious fundamental errors in your commands eg VetoOplockfiles is misspelt (case is wrong), it should be spelt VetoOplockFiles
Also the setting value is also in error, it would not be veto oplock files (which is three words), it would be the type of files that you want to apply the oplocks veto to.

See this forum post for details
http://forums.contribs.org/index.php/topic,36140.msg159638.html#msg159638

You need to fix whatever incorrect setting you have made.
Please show the current output of
db accounts show ibayname
(replace ibayname with the actual name of the ibay where the Access database is)
eg if the ibay name is acessdata then do
db accounts show accessdata
do not leave out or obfuscate anything

Try these commands (which will more likely do the job you want)

Code: [Select]

db accounts setprop accessdata VetoOplockFiles /*.mdb/*.MDB/
signal-event ibay-modify accessdata
(Of course, replace accessdata with the name of the ibay where the Access database is)
I don't believe it is necessary to do the post upgrade and reboot steps.