Access Runtime 2002 - User Account permissions error...

[JayBob]

(banging my head against the wall)

I have an Access 2002 MDE application that runs under MS WinXP and Access
2002 Runtime. It works great if opened from an Administrator account.
However, the following message appears if the db is opened from a user
account:

"You do not have access to make the required system configuration
modifications. Please rerun this installation from an administrators account."

I suspected that my application was read/writing somewhere bad (like
HKEY_LOCAL_MACHINE), so I created a blank MDE data base... and it too showed
the dreaded permissions message above.

I next tried adding the user account (with full access permissions) to the
registry under HKEY_LOCAL_MACHINE\software\microsoft and
HKEY_CLASSES_ROOT/CLSID. That didn't work either.

Can Access Runtime be run from non-administrator Windows accounts? If so, how?

Thanks in advance for providing any useful information!

 

[Graham Mandeno]

Hi JayBob

Access Runtime certainly *can* be run from non-administrator Windows
accounts.

There is a newsgroup thread on a similar subject here:
http://groups.google.com/group/micr...rm/thread/cedd70b5fa72cc20/2F8bc224c59419ad17

or, if that URL wraps horribly, try this one: http://tinyurl.com/y3ycqt

The context there is Windows Terminal Server, but I suggest you search HKLM
in your registry for key names including "Access\Resiliency" and try
deleting them. Be sure to back up the key first!

 

[JayBob]

Hi Graham,

I found one "Resiliency" entry, but it was under
HKLM\software\microsoft\Office\10.0\word. I backed up the registry, deleted
the entry and then logged out/back in as a user. No soap... Clicking the MDE
startup icon (using MSACC runtime) resulted in the same permissions error.

Note that the runtime application was installed as Administrator and now I'm
running as a user. Could that make any difference? There's an entry under
HKLM\software\microsoft\Office\10.0\Access called "InstallRoot" that I
haven't noticed before. (I'm grasping for straws here).

Hi JayBob

Access Runtime certainly *can* be run from non-administrator Windows
accounts.

There is a newsgroup thread on a similar subject here:
http://groups.google.com/group/micr...rm/thread/cedd70b5fa72cc20/2F8bc224c59419ad17

or, if that URL wraps horribly, try this one: http://tinyurl.com/y3ycqt

The context there is Windows Terminal Server, but I suggest you search HKLM
in your registry for key names including "Access\Resiliency" and try
deleting them. Be sure to back up the key first!
--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

(banging my head against the wall)

I have an Access 2002 MDE application that runs under MS WinXP and Access
2002 Runtime. It works great if opened from an Administrator account.
However, the following message appears if the db is opened from a user
account:

"You do not have access to make the required system configuration
modifications. Please rerun this installation from an administrators
account."

I suspected that my application was read/writing somewhere bad (like
HKEY_LOCAL_MACHINE), so I created a blank MDE data base... and it too
showed
the dreaded permissions message above.

I next tried adding the user account (with full access permissions) to the
registry under HKEY_LOCAL_MACHINE\software\microsoft and
HKEY_CLASSES_ROOT/CLSID. That didn't work either.

Can Access Runtime be run from non-administrator Windows accounts? If so,
how?

Thanks in advance for providing any useful information!

 

[Graham Mandeno]

Hi JayBob

I found one "Resiliency" entry, but it was under
HKLM\software\microsoft\Office\10.0\word. I backed up the registry,
deleted
the entry and then logged out/back in as a user. No soap... Clicking the
MDE
startup icon (using MSACC runtime) resulted in the same permissions error.

Hmmm... not surprising - that one would have something to do with Word, not
Access.

Note that the runtime application was installed as Administrator and now
I'm
running as a user. Could that make any difference?

No, it shouldn't - that's the way I do all my runtime installations.

There's an entry under
HKLM\software\microsoft\Office\10.0\Access called "InstallRoot" that I
haven't noticed before.

No, that's just the folder in which Access has been installed. Every
computer with Access installed should have that key.

(I'm grasping for straws here).

I'm sorry - I've run out of straws to pass to you! :-/

What I'm reasonably sure of is that Access (the program - not your code) is
trying to write something to the registry and is failing.

You might like to try RegMon or Process Monitor (I think this now includes
all the RegMon functionality and has superseded RegMon):
http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspx

--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

Hi JayBob

Access Runtime certainly *can* be run from non-administrator Windows
accounts.

There is a newsgroup thread on a similar subject here:
http://groups.google.com/group/micr...rm/thread/cedd70b5fa72cc20/2F8bc224c59419ad17

or, if that URL wraps horribly, try this one: http://tinyurl.com/y3ycqt

The context there is Windows Terminal Server, but I suggest you search
HKLM
in your registry for key names including "Access\Resiliency" and try
deleting them. Be sure to back up the key first!
--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

(banging my head against the wall)

I have an Access 2002 MDE application that runs under MS WinXP and
Access
2002 Runtime. It works great if opened from an Administrator account.
However, the following message appears if the db is opened from a user
account:

"You do not have access to make the required system configuration
modifications. Please rerun this installation from an administrators
account."

I suspected that my application was read/writing somewhere bad (like
HKEY_LOCAL_MACHINE), so I created a blank MDE data base... and it too
showed
the dreaded permissions message above.

I next tried adding the user account (with full access permissions) to
the
registry under HKEY_LOCAL_MACHINE\software\microsoft and
HKEY_CLASSES_ROOT/CLSID. That didn't work either.

Can Access Runtime be run from non-administrator Windows accounts? If
so,
how?

Thanks in advance for providing any useful information!

 

[JayBob]

ouch... This was the not answer I had hoped. I have been running filemon,
regmon and procmon. 16000+ entries when Access starts up. No obviously weird
stuff happening. I will go back and filter on writes only to see if there's
something going on.

Are there any Microsoft gurus lurking that might be able to help?

Hi JayBob

I found one "Resiliency" entry, but it was under
HKLM\software\microsoft\Office\10.0\word. I backed up the registry,
deleted
the entry and then logged out/back in as a user. No soap... Clicking the
MDE
startup icon (using MSACC runtime) resulted in the same permissions error.

Hmmm... not surprising - that one would have something to do with Word, not
Access.

Note that the runtime application was installed as Administrator and now
I'm
running as a user. Could that make any difference?

No, it shouldn't - that's the way I do all my runtime installations.

There's an entry under
HKLM\software\microsoft\Office\10.0\Access called "InstallRoot" that I
haven't noticed before.

No, that's just the folder in which Access has been installed. Every
computer with Access installed should have that key.

(I'm grasping for straws here).

I'm sorry - I've run out of straws to pass to you! :-/

What I'm reasonably sure of is that Access (the program - not your code) is
trying to write something to the registry and is failing.

You might like to try RegMon or Process Monitor (I think this now includes
all the RegMon functionality and has superseded RegMon):
http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspx

--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

Hi JayBob

Access Runtime certainly *can* be run from non-administrator Windows
accounts.

There is a newsgroup thread on a similar subject here:
http://groups.google.com/group/micr...rm/thread/cedd70b5fa72cc20/2F8bc224c59419ad17

or, if that URL wraps horribly, try this one: http://tinyurl.com/y3ycqt

The context there is Windows Terminal Server, but I suggest you search
HKLM
in your registry for key names including "Access\Resiliency" and try
deleting them. Be sure to back up the key first!
--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

(banging my head against the wall)

I have an Access 2002 MDE application that runs under MS WinXP and
Access
2002 Runtime. It works great if opened from an Administrator account.
However, the following message appears if the db is opened from a user
account:

"You do not have access to make the required system configuration
modifications. Please rerun this installation from an administrators
account."

I suspected that my application was read/writing somewhere bad (like
HKEY_LOCAL_MACHINE), so I created a blank MDE data base... and it too
showed
the dreaded permissions message above.

I next tried adding the user account (with full access permissions) to
the
registry under HKEY_LOCAL_MACHINE\software\microsoft and
HKEY_CLASSES_ROOT/CLSID. That didn't work either.

Can Access Runtime be run from non-administrator Windows accounts? If
so,
how?

Thanks in advance for providing any useful information!

 

[Graham Mandeno]

You should be able to create a filter in procmon to show you only registry
operations which fail (exclude result is SUCCESS) and where the application
is Access (include process name is MSACCESS.EXE).
--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

ouch... This was the not answer I had hoped. I have been running filemon,
regmon and procmon. 16000+ entries when Access starts up. No obviously
weird
stuff happening. I will go back and filter on writes only to see if
there's
something going on.

Are there any Microsoft gurus lurking that might be able to help?

Hi JayBob

I found one "Resiliency" entry, but it was under
HKLM\software\microsoft\Office\10.0\word. I backed up the registry,
deleted
the entry and then logged out/back in as a user. No soap... Clicking
the
MDE
startup icon (using MSACC runtime) resulted in the same permissions
error.

Hmmm... not surprising - that one would have something to do with Word,
not
Access.

Note that the runtime application was installed as Administrator and
now
I'm
running as a user. Could that make any difference?

No, it shouldn't - that's the way I do all my runtime installations.

There's an entry under
HKLM\software\microsoft\Office\10.0\Access called "InstallRoot" that I
haven't noticed before.

No, that's just the folder in which Access has been installed. Every
computer with Access installed should have that key.

(I'm grasping for straws here).

I'm sorry - I've run out of straws to pass to you! :-/

What I'm reasonably sure of is that Access (the program - not your code)
is
trying to write something to the registry and is failing.

You might like to try RegMon or Process Monitor (I think this now
includes
all the RegMon functionality and has superseded RegMon):
http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspx

--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

:

Hi JayBob

Access Runtime certainly *can* be run from non-administrator Windows
accounts.

There is a newsgroup thread on a similar subject here:
http://groups.google.com/group/micr...rm/thread/cedd70b5fa72cc20/2F8bc224c59419ad17

or, if that URL wraps horribly, try this one:
http://tinyurl.com/y3ycqt

The context there is Windows Terminal Server, but I suggest you search
HKLM
in your registry for key names including "Access\Resiliency" and try
deleting them. Be sure to back up the key first!
--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

(banging my head against the wall)

I have an Access 2002 MDE application that runs under MS WinXP and
Access
2002 Runtime. It works great if opened from an Administrator
account.
However, the following message appears if the db is opened from a
user
account:

"You do not have access to make the required system configuration
modifications. Please rerun this installation from an administrators
account."

I suspected that my application was read/writing somewhere bad (like
HKEY_LOCAL_MACHINE), so I created a blank MDE data base... and it
too
showed
the dreaded permissions message above.

I next tried adding the user account (with full access permissions)
to
the
registry under HKEY_LOCAL_MACHINE\software\microsoft and
HKEY_CLASSES_ROOT/CLSID. That didn't work either.

Can Access Runtime be run from non-administrator Windows accounts?
If
so,
how?

Thanks in advance for providing any useful information!