asked on
MS Access error
Situation: an Access 2007 back end database is housed on a web server that is in a DMZ. It has to be there so a public web page can access it. Company users who also access it via linked tables each have their own Access front end, some 2010, others 2007.\
Because the back end is in a DMZ, Windows authentication won't work when setting permissions to the directory. We get around this by using a batch file that runs this script to authenticate users:
net use \\webServer\IPC$ /u:webServer\AccessAppUser
Then a script runs that opens the user's Access front end.
Problem: A few users can open the front end with no problem at the same time. The rest, regardless of Access version, get this:
The Microsoft Office Access database engine cannot open or write to the file "filename". It is already opened exclusively by anothere user, or you need permission to view adn write its data.
Our network person tells me the web server would see all users connecting this way the same so directory permissions shouldn't be a issue.
Any ideas why this happens?
Thanks,
McLeanIS
Because the back end is in a DMZ, Windows authentication won't work when setting permissions to the directory. We get around this by using a batch file that runs this script to authenticate users:
net use \\webServer\IPC$ /u:webServer\AccessAppUser
Then a script runs that opens the user's Access front end.
Problem: A few users can open the front end with no problem at the same time. The rest, regardless of Access version, get this:
The Microsoft Office Access database engine cannot open or write to the file "filename". It is already opened exclusively by anothere user, or you need permission to view adn write its data.
Our network person tells me the web server would see all users connecting this way the same so directory permissions shouldn't be a issue.
Any ideas why this happens?
Thanks,
McLeanIS
Microsoft ApplicationsMicrosoft OfficeMicrosoft Access
Last Comment
McLeanIS
and by the way, rather then simply accepting an answer in the other question, you should have stuck with it and made additional comments explaining the situation.
Jim.
Jim.
I would also not use the ICP$ share, but create a new hidden share.
Make sure the share permissions are set for everyone and full control and that webServer\AccessAppUsers has full privs for the directory.
Jim.
Make sure the share permissions are set for everyone and full control and that webServer\AccessAppUsers has full privs for the directory.
Jim.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
We chose not to spend time testing permissions on files in the DMZ and use a short term fix since we decided parts of this system need redesiging.
Every user needs full read, write, and delete privs for the directory where the DB resides.
If not, and the first user in does not, then the DB is opened exclusive regardless of settings.
This includes the account used by the web site, which is a user.
So your issue boils down to security and is not an Access question per say. I would double check this is the problem for sure by:
1. Having the user execute the script.
2. Then try:
a. Creating a text file in the directory.
b. Edit the text file and save it.
c. Delete the text file.
Each user should be able to perform that test without error.
Jim.