Access XP requests safe mode every other time

[Mike]

We have a problem with Access XP saying that it failed to
start correctly last time and asks if you want to start
it in safe mode. If we say yes then Access opens in safe
mode without any problems and there are no disabled
items. If Access is closed and opened again it is fine -
no safe mode request. If Access is then closed and opened
again it then comes up with the safe mode message. This
is all without opening up a database.

Access is running on a Windows 2000 Advanced Server with
users using Access in TS sessions. The problem occurs
even under the Windows administrator account.

We have tried reinstalling Access but it hasn't cured the
problem.

Does anyone have any ideas?

Thanks.

[anon...@discussions.microsoft.com]

I have some more info.

When non-administrator users close Access, they get the
following message:

'You do not have access to make the required system
configuration modifications. Please re-run this
installation from an administrators account'

Is this due to permissions and if so what permissions
(file/folder/registry) do the users require to run Access
on TS?

>.
>

[david epsom dot com dot au]

> Is this due to permissions and if so what permissions
> (file/folder/registry) do the users require to run Access
> on TS?

Don't know, but,

I can't log onto my network server. (I don't have logon
permission for that PC). That means I can't TS to that
PC. The only way to allow me to use TS to that Server
is to give me login permission.

Obviously, If I'm given logon permission for the Server,
my IT people are going to try and restrict me as much as
possible. (Even better, a separate TS machine, so I
don't need logon permission for the File Server or DNS
or Exchange Server or ....)

If I am going to run Access on the Server, at MINIMUM
I need to be able to save my User data each time I use
Access. That includes stuff like my Most Recently Used
File List - which is saved to the registry when I exit
Access. Your TS users probably should have COMPLETE
permission to their USER registry area.

Access also has configuration data in the Machine area
of the registry, but I would expect problems with that
to appear when you start Access ??? not when you close
Access ???.

(david)

<anon...@discussions.microsoft.com> wrote in message
news:0a8c01c3a2d1$f5f9a8b0$a601...@phx.gbl...

[Alick [MSFT]]

Hi Mike,

The issue could be related to the registry key on the Windows 2000 Server:

"HKLM\Software\Microsoft\Windows NT\CurrentVersion\Terminal
Server\Install\SOFTWARE\MICROSOFT\Office\10.0\Access\Resiliency"

We can try to rename the Resiliency key from the path listed above on the
server.

Also if this registry key was getting copied to the HKEY_Current_User key
when the user's log onto their session, we may also need to rename the
registry key under HKEY_Current_User key.

Please feel free to reply to the threads if you have any questions or
concerns.

Sincerely,

Alick Ye, MCSD
Product Support Services
Microsoft Corporation
Get Secure! - <www.microsoft.com/security>

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Content-Class: urn:content-classes:message
| From: "Mike" <mi...@spamfree.com>

[anon...@discussions.microsoft.com]

We have renamed the key under HKLM and it seems to have
fixed the problem.

Do you know what might have lead to this situation and
how to avoid it?

Thanks for your help.

>.
>

[Alick [MSFT]]

Hi Mike,

The registry key was created to restrict the log in user's action on
Terminal Server for some security reason; don't know why it was created on
your Server, may be by accident; however, it was possible it was created by
some program deployment, or it is related to the Server's security
environment, the Server may add the security key additionally.

Please feel free to reply to the threads if you have any concerns or
questions.

Sincerely,

Alick Ye, MCSD
Product Support Services
Microsoft Corporation
Get Secure! - <www.microsoft.com/security>

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Content-Class: urn:content-classes:message

| From: <anon...@discussions.microsoft.com>
| X-Tomcat-NG: microsoft.public.access.multiuser

[david epsom dot com dot au]

> Do you know what might have lead to this situation and
> how to avoid it?

The installer of Access had sufficient permission to create
the Resiliency key (in HKLM), but the user did not have
sufficient permission to delete the key. (???)

The installer of Access created the key in HKLM.

The user of Access looks in HKLU, does not find the key,
looks in HKLM, finds the key, writes the key to HKLU
because it exists in HKLM, even though there was no
startup error.

Next time, Access looks in HKLU, finds the key written
last time, Ask you about safe mode, deletes the key
(because there is no error). Key in HKLM is NOT deleted,
so next time loop starts again.

Solution is either to delete the key in HKLM, or give
the user sufficient permission to delete the key in HKLM??

(david)

<anon...@discussions.microsoft.com> wrote in message
news:0a7401c3a51f$31b43a10$a101...@phx.gbl...