Re: Using MS Access Through Terminal Server - THANKS

From: Randy (randy_at_webtracersolutions.com)
Date: 04/02/04 

Date: Fri, 02 Apr 2004 06:20:55 -0800

THanks to all who responded. I just did a test after making the
System.mdw and its lock file open to everyone to modify and it solved my
problem.

I appreciate everyones input and help!

Thanks,
Randy

Patrick Rouse [MVP] wrote:

> This sounds like your problem:
>
> http://groups.google.com/groups?q=Could+not+use+%27Admin%27%3B+file+is+already+in+use&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=c97b9fa.0209222214.59cffa43%40posting.google.com&rnum=5
>
> Patrick Rouse
> Microsoft MVP - Terminal Server
> http://www.workthin.com
>
> ----- Tim wrote: -----
>
> Sounds like the database is either being opened exclusively by the first
> user or you have an issue with user to database mapping.
>
> IE
>
> If the intended method of using your application if for normally each user
> to have a copy of the 'Application' database, then when the DB is opened MS
> Access will create a .ldf file with the same name in the same location. This
> file records locking information.
>
> Now, you may have inadvertantly set the open mode for this 1 copy of the
> physical DB file to be Exclusive - this would explain the error.
>
> The other possibility (I don't write access applications any more..) is that
> there is an issue with the .ldf file and that MS Access may not be able to
> cope with more than 1 actual user logging in on the same physical desktop
> (the TS machine) under the same MS Access username 'Admin' where the DB is
> already open.
>
> I hope this heads you in the right direction.
>
> IE each user may need a Private copy of the MDB file.
>
> - Tim
>
>
>
> "Randy" <randy@webtracersolutions.com> wrote in message
> news:106pdf5qebhor69@corp.supernews.com...
> > Correction:
> >> The Actual Error reads:
> >> "Could not use 'Admin'; file is already in use"
> >> Each Users version of the program starts in their own subdirectory, so
> > no one is ever using their copy. If we make them an administrator, this
> > error does not come up. If we make them anything BUT an Administrator
> > this error occurs. It never occurs for our LAN users, only for the
> > Terminal Server Users.
> >> Patrick Rouse [MVP] wrote:
> >>> What tells you that they need administrator rights? It's common that
> users need write permissions to very specific files, directories or registry
> keys to run a certain program. Making users administrators to fix this
> problem is the worst solution one can do, unless you like rebuilding your TS
> often due to users bypassing or altering your security, installing programs
> and rebooting your TS while users are logged on (so you're correct to not
> want to do this).
> >>>> You can use regmon & filemon to determine which files or registry keys
> this program needs users to be ablke to write to. These can be found here:
> >> http://www.workthin.com/tsdown.htm
> >>>> Patrick Rouse
> >> Microsoft MVP - Terminal Server
> >> http://www.workthin.com
> >>>> ----- Randy wrote: -----
> >>>> I develop in a MS Access Front End to a SQL Server Database. We
> deploy
> >> our program to different Organizations, most of which use it on a
> LAN.
> >> Recently, as we have expanded to new customers, some of them have
> remote
> >> users using th program through a Terminal Service session. I have
> them
> >> all locked down so that all they can do is run the program, but in
> order
> >> to allow them to run Access through Terminal Services it tells me
> that
> >> they need Admin Rights, so I essentially end up making them
> >> administrators. They can't do anything because they are only
> allowed to
> >> run Access, but I would rather not have 15 administrators running
> around
> >> a company, but I can't figure out any other way to get it done then
> this.
> >>>> Any ideas?
> >>>>>

Relevant Pages

  • RE: Permissions
    ... >servers are available to service the logon request. ... >database does not have the proper domain registrations ... >If you are logged on as an administrator at a Domain ...
    (microsoft.public.win2000.security)
  • Re: SharePoint Portal search is not working after changing admin paasw
    ... Just a thought but it could be the access account to the actual SQL server. ... Query on SQL and see if it lets you in as the Administrator. ... > Verified Password for services on our Database Server ...
    (microsoft.public.sharepoint.portalserver)
  • RE: Permissions
    ... servers are available to service the logon request. ... - Make certain that WINS database replication is successful between WINS ... Domainregistrations that are not listed in the ... If you are logged on as an administrator at a Domain Controller, ...
    (microsoft.public.win2000.security)
  • Re: Error trying to connect to Access Database
    ... windows admin userid and password. ... your database isn't updatable because of the permissions issue. ... Are you the administrator of the server where the ASP is running? ... I do not know what else to do, and I am trying to get a web site done. ...
    (microsoft.public.access.gettingstarted)